![]() For example, enter:ĭo #class().Interactive() This is the namespace where the custom schema will be stored. A custom schema is based on one of these library schemas.Ĭhange to the namespace that contains or will contain the HL7 interoperability productions that route your HL7 messages. In the Management Portal, a schema’s document structures are listed on the DocType Structure tab.Ĭollectively refers to the schemas, document structures, segments, data structures, and code tables that are defined in the Management Portal.Ī base schema, for example 2.7.1, that is available in the Management Portal. The Message Analyzer uses the following terminology: TermĪ HL7 message structure such as ADT_01. Validate messages against a given document structure, optionally updating the custom schema’s segments, data structures, and code tables to allow failing messages. ![]() Most commonly, the derived document structure contains Z segments found in the scanned messages. Scan HL7 messages and compare them to a given document structure, deriving a new document structure that matches the messages. The Message Analyzer is a command-line utility that allows you to:
0 Comments
Leave a Reply. |