I had forgot that a while ago, I had to create a custom HL7 message, and I saw a question on the forum asking how you can do it.
Here are the steps: (All modifications take place in both the MSH_231_GLO_DEF and the tablevalues.xsd). In this example I am creating a ZZZ^Z01 message;
- Edit Table76 and add the message type (add an enumeration) by editing the schema in a text editor:(in my case ZZZ)
- Edit Table3 to represent the trigger:(in my case Z01)
- Edit the MSH 9.0 Sub Element
- Edit the MSH 9.1 Sub Element
- Finally create your schema with the root node that follows the following algorithm: Body schema type = TargetNS + “#” + MSH9.1 + MSH9.2 + MSH12.1 (with dots removed) + MSH12.2 (or GLO if the value is blank) + MSH12.3 (or DEF if the value is blank), and don’t forget to make sure that the target namespace of the schema matches what you have defined in the BTAHL7 Configuration Explorer
Some things to make note of:
- If you are making this new message for a target namespace not the default, the MSH schema that comes needs to be modified. The BTAHL7 pipeline will only look for the default one that comes installed.
- Make sure that the message that is coming in has the EVN.1 code that matches the MSH.9
posted @ Tuesday, August 15, 2006 12:00 PM