Message Context
Message Context Format
Message Context defined in this guide is intended to be displayed both in a human readable and codified format. To achieve this, we leveraged the existing structure in the Submission Set Metadata used for XDR Edge Protocol, defined in section 6.2.2 of the XDR and XDM for Direct Messaging Specification.
Surescripts is basing its implementation on the SubmissionSet.contentTypeCode, which is intended to define the purpose of the message. Within the XDR Specification, Surescripts recommends that implementers draw from the HITSP C80, version 2.0.1, Table 2-144, to populate the contentTypeCode. This table defines common LOINC values many health technologies can already read and interpret.
Example:
Net2Net REST DocumentData
DocumentData is a conditional message element as defined through the Net2Net Implementation Guide, which allows for additional data to be placed in the message. It consists of a collection of items with a key attribute and the value.
Note: Values that are not supported by the recipient should be ignored.
<DocumentData>
<Item key="x-kryptiq-notification">onetime</Item>
<Item key="x-kryptiq-message-class-type">Standard</Item>
<Item key="x-kryptiqtrackingid">6dabf2a36fa4406eacd09ce23190ceb1</Item>
<Item key="x-kryptiqremotemessagekey">jzcs3dnchvrbhbdvso2eatloj4molg</Item>
</DocumentData>Message Context in DocumentData
To achieve pass, the MessageContext described in section 2.1 above (as part of the Document data defined in section 2.2), Surescripts has defined the following Item keys:
<Item key=”x-classification-code”>VALUE</Item>
<Item key=”x-classification-scheme”>VALUE</Item>
<Item key=”x-classification-name”>VALUE</Item>The x-classification-code key value should be populated with the type code. The x-classification-scheme key value should be populated with the coding system. The x-classification-name should be populated with the display name. An example of a fully populated DocumentData element based on the Immunization example reviewed earlier is displayed below.
<DocumentData>
<Item key="x-classification-code">11369-6</Item>
<Item key="x-classification-scheme">2.16.840.1.113883.6.1</Item>
<Item key="x-classification-name">History of Immunization</Item>
</DocumentData>Surescripts Processing of Message Context
Since there are Edge Implementations for Direct, recipients will receive this information in different formats. The following sections define how the information presented by the Net2Net REST senders' information is delivered to the intended recipient.
Net2Net REST to Net2Net REST
Surescripts will not modify the DocumentData element, and will deliver the content exactly as it was presented by the sender.
Net2Net REST to XDR
Surescripts takes the x-classification Item keys and populates the Classification element in the XDR message.
<Classification id="d008d7a2-eae1-4cc7-b316-972a21d957c3"
objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
classificationScheme="urn:uuid:aa543740-bdda-424e-8c96-df4873be8500"
classifiedObject="1.2.840.114350.1.13.239.2.7.3.688883.80.48060976.96032010"
nodeRepresentation="11369-6">
<Slot name="codingScheme">
<ValueList>
<Value>2.16.840.1.113883.6.1</Value>
</ValueList>
</Slot>
<Name>
<LocalizedString xml:lang="en-us" charset="UTF-8"
value="History of Immunization"/>
</Name>
</Classification>Net2Net REST to Direct
Surescripts takes the x-classification Item keys and presents the information as x-headers in the MIME message going out via Direct.
Example: