Detailed Clinical Direct Messaging Workflows
Glossary of workflow terms:
- Sending System: System connected to Surescripts network originating Clinical message.
- Sender: Originator of Clinical message routed through sending system.
- Receiving System: System connected to Surescripts network receiving original Clinical message.
- Recipient: Receiver of the original Clinical message within the receiving system.
Single Recipient
Receiving System's Response Status 010
Scenario 1:
Sender generates a Clinical message.
1a). Sending System sends Clinical message to Surescripts.
1b). Receiving System receives the Clinical message forwarded by Surescripts.
1c). Receiving System sends a Status 010 response to Surescripts to indicate that the Clinical message has been delivered.
1d). Sending System receives the Status 010 response forwarded by Surescripts.
Receiving System's Verify Message
Scenario 2:
Sender generates a Clinical message.
2a). Sending System sends a Clinical message to Surescripts.
2b). Receiving System receives the Clinical message forwarded by Surescripts.
2c). Receiving System responds with a Status 000 response to Surescripts indicating the Clinical message was accepted for processing.
2d). Sending System receives the Status 000 response forwarded by Surescripts.
2e). Receiving System sends a Verify message to Surescripts indicating the Clinical message was successfully delivered electronically to Recipient.
2f). Sending System receives the Verify message forwarded by Surescripts.
2g). Sending System responds to the Verify message with a Status 010 response to Surescripts.
2h). Receiving System receives the Status 010 response forwarded by Surescripts.
Receiving System's Error Response
Scenario 3:
Sender generates a Clinical message.
3a). Sending System sends Clinical message to Surescripts.
3b). Receiving System receives the Clinical message forwarded by Surescripts.
3c). Receiving System responds with an Error response to Surescripts.
3d). Sending System receives the Error response forwarded by Surescripts.
Error Message
Scenario 4:
Sender generates a Clinical message.
4a). Sending System sends a Clinical message to Surescripts.
4b). Receiving System receives the Clinical message forwarded by Surescripts.
4c). Receiving System sends a Status 000 response to Surescripts.
4d). Sending System receives the Status 000 response forwarded by Surescripts.
4e). Receiving System sends an Error message to Surescripts.
4f). Sending System receives the Error message forwarded by Surescripts.
4g). Sending System responds to the Error message with a Status 010 response to Surescripts.
4h). Receiving System receives the Status 010 response forwarded by Surescripts.
Multiple Recipients
Receiving Systems' Status 010 Response
Scenario 5:
Sender generates a Clinical message.
5a). Sending System sends a Clinical message to Surescripts.
5b). Sending System receives a Status 000 response generated by Surescripts for all multiple recipient messages.
5c). Receiving Systems A and B receive the Clinical message forwarded by Surescripts.
5d). Receiving System A responds with a Status 010 response to Surescripts.
5e). Sending System receives a Verify message generated by Surescripts.
5f). Sending System responds with a Status 010 response to Surescripts. (Surescripts does not forward response to Receiving System.)
5g). Receiving System B responds with a Status 010 response to Surescripts.
5h). Sending System receives a Verify message generated by Surescripts.
5i). Sending System responds to the Verify message with a Status 010 response to Surescripts. (Surescripts does not forward response to Receiving System.)
Note: Receiving systems' responses can occur in any order.
Multiple Recipient Message with Errors and Verifies
Scenario 6:
Sender generates a Clinical message.
6a). Sending System sends a Clinical message to Surescripts.
6b). Sending System receives a Status 000 response generated by Surescripts for all multiple recipient messages.
6c). Receiving Systems A, B, C, and D receive the Clinical message forwarded by Surescripts.
6d). Receiving System A responds with a Status 010 response to Surescripts.
6e). Sending System receives a Verify message generated by Surescripts.
6f). Sending System responds with a Status 010 response to Surescripts. (Surescripts does not forward response to Receiving System.)
6g). Receiving System B responds with a Status 000 response to Surescripts indicating the Clinical message was accepted for processing (not forwarded to Sending System).
6h). Receiving System B sends a Verify message to Surescripts.
6i). Sending System receives the Verify message forwarded by Surescripts.
6j). Sending System responds to the Verify message with a Status 010 response to Surescripts.
6k). Receiving System B receives Status 010 response forwarded by Surescripts.
6l). Receiving System C sends an Error response to Surescripts.
6m). Sending System receives an Error message generated by Surescripts.
6n). Sending System responds to the Error message with a Status 010 response to Surescripts (not forwarded to Receiving System C).
6o). Receiving System D responds with a Status 000 to Surescripts.
6p). Receiving System D sends an Error message to Surescripts.
6q). Sending System receives the Error message forwarded by Surescripts.
6r). Sending System responds to the Error message with a Status 010 response to Surescripts.
6s). Receiving System D receives the Status 010 response forwarded by Surescripts.
Note: Receiving Systems’ responses can occur in any order.
Undeliverable Messages
Surescripts’ Error Response
Scenario 7
Sender generates a Clinical message.
7a). Sending System sends Clinical message to Surescripts.
7b). Sending System receives an Error response from Surescripts.
Note: This scenario applies to both single and multiple recipient messages.
Surescripts: Transaction Not Recognized
Scenario 8:
Sender generates a Clinical message.
8a). Sending System sends a Clinical message to Surescripts.
8b). Sending System receives Transaction Not Recognized response from Surescripts.
Message Validation
Surescripts will ensure that customers are in compliance with the message specifications outlined in this guide during testing and will continue to enforce once in production.
At a minimum, Surescripts validations include:
- XML schema validation
- The sender identification and authentication
- The recipient identification
- Syntax of the message, including field lengths, data types, and code values
- Surescripts business rules
Note: Surescripts ACRs are not enforced as part of validations, but instead through the certification process.