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 immunization content type code, display name, and coding system 11369 6, history of immunization, 2 16 840 1 113883 6 1 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 example \<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 example \<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 example \<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 example \<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 x classification code 11369 6 x classification scheme 2 16 840 1 113883 6 1 x classification name history of immunization