6/18/2023 0 Comments Vmd tutorialsWe used our “Mapping HL7 to HL7” channel from the Mapping Messages: HL7 to HL7 tutorial: Open a basic channel that uses the example/demo.vmd.Test the demo_lab.vmd file in a project.In this case two triggers R01 and R02 (separated by a vertical bar”|”) will be recognized. Tip: To constrain the Identity to only match certain events you need to add the Trigger Event, like this: No action is required, the Identity will match all events by default.Click on the ellipsis (…) in the Field column and choose the Message Code:.Click on the ellipsis (…) in the Segment column and select the MSH segment:.Set the criteria to match the ORU message type.Double click on Identity to open the settings dialog:.This is the Message Identity definition:.Change the Identity settings to match the Lab Message Definition.Comparing the two message grammars shows that the example/demo.vmd is considerably more complex, but the segments and groups in our file are in the same order (which is important):.Get the example/demo.vmd from the Translator project file pane: Open the supplied example/demo.vmd (\edit\admin\other\example\demo.vmd) in Chameleon.Compare the new message grammar to example/demo.vmd.The finished Message Grammar should look this:. ![]() Drag the OBX segment into the OBSERVATION group.Notice the angle brackets that indicate that is optional
0 Comments
Leave a Reply. |