A number of HL7 message types contain references to anyHL7Segment and anyZSegment, the two placeholders defined in the hl7.org-supplied XML Schema to serve as indicators that you must provide a valid HL7 segment or Z segment in their place. The XML Schema for the HL7 message types with such references is included in HL7 Module. However, by default HL7 Module does not generate IS document types for these message types, because they are not enabled in the message.properties file. The messages.properties file is included with the XML Schema for every supported HL7 version under the Integration Server_directory \packages\WmHL7\data\xsd\wm.ip.hl7.docTypes\v<version_number\> directory and determines the default generation of HL7 messages. HL7 Module does not generate IS document types for HL7 message types not enabled in the messages.properties file.

To generate IS document types for HL7 message types with references to anyHL7Segment and anyZSegment, you must first customize the XML Schema definition for these message types by replacing the reference to anyHL7Segment or anyZSegment with a valid segment identifier for the respective HL7 version. After you customize the XML Schema of any of the message type definitions, you can uncomment the HL7 message type name or include it in the messages.properties file. The wm.ip.hl7.utils:generateMessageScheme service will then be able to generate the IS document types.

Following is an example for HL7 message version 2.3.1. The message.properties file includes the following definition:

This definition means that HL7 Module will not generate an IS document type for message types MFN_M01, MFN_M03, and MFR_M01 because they contain the placeholders anyHL7Segment or anyZSegment. To generate IS document types for these message types, you must edit the corresponding XML Schema definition for each message type. For example, for the MFN_M01 message type, you must edit the MFN_M01.xsd file and replace the occurrences of anyHL7Segment and/or anyZSegment with a valid segment identifier, defined in the segments.xsd file.

For the steps in customizing an XML Schema and generating a custom message scheme, see Creating a Custom Message Scheme.

The following table lists the HL7 Module message types that contain direct references to anyHL7Segment and anyZSegment: