PRS

Dear Colleagues,

I have been testing the new Information Routes maintenance functionality, and I thought it would be worth briefing you about the changes to the message schemas, since they affect existing test files.

The two main changes are:
1. We now message the DATA SET for the COMMUNICATION MECHANISM in the Information Route.
2. We now allow Information Routes to be linked to Work Locations.

Thus there could be two work locations optionally involved in an Information Route:

1. The Work Location for the "Event" about which the provider wants to receive information.
2. The Work Location for the Address/Telephone/Email where the provider wants the information sent.

So, in the case where both the Information Route and the Communication have a Work Location associated with them, the provider's saying something like...

"For XRays taken at Royal Jubilee (the Event WL), I'd like them Couriered to my Office Address at Vic General (the Communication or Destination WL)."

So far, all of our testing has not taken into consideration either the DATA SET for the COMMUNICATION MECHANISM, nor the Event Work Location.

The COMMUNICATION MECHANISM DATA SET has become mandatory, because it's part of the Business Key for the COMMUNICATION. Therefore, existing test files will fail because they don't have this tag in.

Here's a snippet from one of my test files for distribution:


ECG
COURIER
Y
BC
M

2004-03-28T00:00:00


This will not work in the next drop, because the COMMUNICATION doesn't have a full business key. I've managed to fix this with a global edit:


ECG
COURIER
Y
BC
M

2004-03-28T00:00:00
HA1

I just replaced the ending tag with a longer string including the missing field...

HA1

Because each file in the distribution test suite uses only one Data Owner Code, I could do a global search and replace to effect this. For more complex files, this won't work unfortunately, and you'll have to do a manual edit.

For the Event Work Location, things are a little different. You actually have to message the Information Route as part of the Work Location itself. None of our testing so far has attempted to create or manipulate Work Location Information Routes, so this is new material, and existing test files shouldn't be affected.

But here's a summary of the four scenarios, and sample messages (generated by the Web Application)...




ECG
FAX
N
BC
HA1

C


2004-05-05T00:00:00
HA1





XRAY
COURIER
N
BC
HA1
M


2
2004-05-05T00:00:00
HA1






2
HA1

ECG
COURIER
N
BC
HA1
M



2004-05-05T00:00:00
HA1






1
HA1

TRANSCRIPT
COURIER
N
DR
HA1
M


2
2004-05-05T00:00:00
HA1



Enjoy!