Subject:ORM / ORU Seqments Author:Aaron Forman Date:02 Oct 2008 05:27 PM
I am reviewing the stylus studio to purchase for or organization...
I am reviewing a document for one of the largest lab testing facilities in the united states. When i try and match up any of the versions of HL7 to their speifications it does not seem to match. Specifically there are segments like ZCC, ZBL, ZCY, ZSA, ZEF, ZPS... Am I to assume that these are just custom HL7 segments that they have added.... OR are they missing from your templates...
Subject:ORM / ORU Seqments Author:Tony Lavinio Date:02 Oct 2008 10:32 PM
According to the specifications on local extensions (for example,
section 2.11 page 37 for HL7 2.6), all custom-defined messages and
segments must begin with the letter Z.
So those segments are all defined independently of the specs.
However, we do allow you to add custom definitions to the existing
built-in standards, so as long as you have the documentation, we can
help you to support messages with the Z** segments.
Subject:ORM / ORU Seqments Author:Aaron Forman Date:03 Oct 2008 10:48 AM
Actually Tony now i have another question.... So i took out all the Z segments ran it through the EDI XML converter and everything worked great. Now I need to change the XSD so that it includes the Z segments. How do I do that so that the processor knows to look at the new XSD? Is there a video?
Subject:ORM / ORU Seqments Author:Aaron Forman Date:03 Oct 2008 10:51 AM
when i run it through the edi converter how do i know which xsd it used to convert the edi file? i need to know that so i can figure out which one to add the Z segments too... ughh
Subject:ORM / ORU Seqments Author:Tony Lavinio Date:05 Oct 2008 11:11 PM
You don't need the XSD to convert from HL7 to XML.
Nor does the converter use an XSD.
Internally, it has a repository of the HL7 standards, and will
automatically write XML that is valid.
What we use the XSD for is when a user wants to generate an HL7
file. They can create an XSD based on the particular version and
message/event, and then write XML into that structure - because
that describes what the XML-to-HL7 converter is expecting.
So changing the XSD will not help; it's a form of output, not
used for the actual conversion but for the convenience of the
developer writing HL7 from XSD.
In order to modify the interpretation of the HL7 file, you need
to supply a mapping file which contains the definitions of the new
segment. For XML Converters 3.2, it's an .extension XML file.
Subject:ORM / ORU Seqments Author:Aaron Forman Date:06 Oct 2008 03:04 PM
ok well i need to change the xsd for any "Z" segments being written to an edi file, and i need to change the reading of the edi for any "Z" sent in... do you have any directions in help menus on how to do this?