3.1 Two Business Actor Use Case

The Initiating System and its sending HISP will need to communicate the Direct Secure Messages as described in Section 4.1.1.3. Receiving HISPs will communicate with Recipient Systems as needs dictate. Responsibilities for communicating required attachments are shown in the table following.

Responsibility	Initiating System	Sending HISP System	Receiving HISP System	Recipient System
Context Metadata	SHALL produce and include either an XDR message, an XDM package with full XDS metadata or a Context IG metadata as specified in Section 4.1.2	SHALL include Context Metadata as provided by Initiating System or transmit XDM packages from XDR. The Sending HISP MAY send either an XDM package or the Context IG metadata or both. Context Metadata SHALL be mapped as shown in Section 4.2.1.	SHALL deliver message contents and associated context as appropriate to the Edge protocol in use.	SHOULD make use of Context to alert appropriate users and inform workflow
HL7 V2 Message Content Payload	SHALL produce and include an HL7 V2 message with all required content.	SHALL include HL7 V2 messages as produced by Initiating Systems. These may be sent within XDM packages	SHALL accept HL7 V2 messages and communicate them based on the needs of the Recipient System	SHOULD repose or parse and repose HL7 V2 content provided by Receiving HISP
Human readable text that contains the Event Notification Information	SHALL produce and include a human-readable text attachment.	SHALL include the human readable text attachment in the Message Body If XDM format, an identical human readable text SHALL be included in the XDM Package Note: For Document Entry associated with the V2 message classCode SHALL be: 2.16.840.1.113883.6.1:86530-3 For Document Entry associated with the human readable, classCode may vary to support existing implementations between HISPs and edge systems to define the body message. The preferred value established by this IG is 56444-3 (LOINC), but other guidance may prevail.	SHALL assure that the human readable text (from either source) is delivered based upon the needs of the Recipient System	SHALL display either the included human readable text attachment OR a human readable message constructed from other included data

Responsibility

Initiating System

Sending HISP System

Receiving HISP System

Recipient System

Context Metadata

SHALL produce and include either an XDR message, an XDM package with full XDS metadata or a Context IG metadata as specified in Section 4.1.2

SHALL include Context Metadata as provided by Initiating System or transmit XDM packages from XDR. The Sending HISP MAY send either an XDM package or the Context IG metadata or both. Context Metadata SHALL be mapped as shown in Section 4.2.1.

SHALL deliver message contents and associated context as appropriate to the Edge protocol in use.

SHOULD make use of Context to alert appropriate users and inform workflow

HL7 V2 Message Content Payload

SHALL produce and include an HL7 V2 message with all required content.

SHALL include HL7 V2 messages as produced by Initiating Systems. These may be sent within XDM packages

SHALL accept HL7 V2 messages and communicate them based on the needs of the Recipient System

SHOULD repose or parse and repose HL7 V2 content provided by Receiving HISP

Human readable text that contains the Event Notification Information

SHALL produce and include a human-readable text attachment.

SHALL include the human readable text attachment in the Message Body

If XDM format, an identical human readable text SHALL be included in the XDM Package

Note: For Document Entry associated with the V2 message classCode SHALL be:

2.16.840.1.113883.6.1:86530-3

For Document Entry associated with the human readable, classCode may vary to support existing implementations between HISPs and edge systems to define the body message. The preferred value established by this IG is 56444-3 (LOINC), but other guidance may prevail.

SHALL assure that the human readable text (from either source) is delivered based upon the needs of the Recipient System

SHALL display either the included human readable text attachment OR a human readable message constructed from other included data

3.1 Two Business Actor Use Case ​

3.1 Two Business Actor Use Case