Net2Net Clinical Message

a clinical message is used to communicate patient related clinical information between health care providers it may contain textual data, as well as structured content and file attachments net2net message xml diagram sending a net2net clinical message to send a net2net clinical message, the customer must collect message content, attachments, and the recipient information; validate that the message conforms to the schema; and call the surescripts api to submit the clinical message(s) once a clinical message is sent, the surescripts api provides a synchronous response to the submission of a message this response is a status message "010" if the message was received and delivered; a status message "000" if the message was accepted for processing, or an error message if the message could not be accepted for processing receiving a clinical message to receive a message, customers must set up a server to which surescripts can send messages surescripts will send all messages to the customer as an http post the customer system must provide a synchronous response to messages and freestanding error/verify messages see detailed clinical messaging workflows docid\ dq5r0k g9dft4kt wanyk for more information clinical document message xml diagram net2net clinical message body elements m/c mandatory or conditional element code comments clinicalmessage mandatory subject mandatory the subject of the clinical message protected health information (phi) under hipaa must not be included in the subject document mandatory required if sending a clinical message in the message body plaintext mandatory example "abc clinic has provided services to the patient named in the attached document the patient has identified you as their primary care physician " htmltext conditional this is optional and allows for content formatting documentdata conditional specifies the additional data in the message this consists of a collection of items, with a key attribute and the value ignore values not supported by your system for example \<documentdata> \<item key="x kryptiq notification">onetime\</item> \<item key="x kryptiq message class type">standard\</item> \<item key="x kryptiq trackingid">6dabf2a36fa4406eacd09ce23190ceb1\</item> \<item key="x kryptiq remotemessagekey">jzcs3dnchvrbhbdvso2eatloj4molg\</item> \</documentdata> note empty tags are permitted for use in the documentdata element item mandatory specified data value item/@key mandatory identifier of the specified data value attachment mandatory a collection of one or more attachments each occurrence consists of a documentname and one (only one) of the document elements documentname mandatory filename of the document the file extension should be included example visitsummary pdf cda\ clinicaldocument conditional the sender can use this type of attachment to include a cda attachment note inline xml is the preferred method for passing the cda file conditional the sender can use this type of attachment to include a file attachment documenttype mandatory if a file attachment is included, then a \<documenttype> must be specified and should be a valid mime type for example application/pdf documentversion conditional optional version number for the document documentdata mandatory the base64 encoded string of the file attachment