--- title: Detailed Clinical Direct Messaging Workflows slug: net2net-rest/guide/detailed-clinical-direct-messaging-workflows docTags: createdAt: 2026-06-12T09:48:23.783Z --- 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 ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/JvjHiyzzuaY2WH_x2ZS9Z_detailed-clinical-messaging727x135.png" position="flex-start" size="60" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_727x135.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_727x135.png" width="727" height="135" darkWidth="727" darkHeight="135" showCaption="false"} **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 ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/4NszDSjGZ3Yxhu7nor-pE_detailed-clinical-messaging1730x201.png" position="flex-start" size="60" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_1_730x201.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_1_730x201.png" width="730" height="201" darkWidth="730" darkHeight="201" showCaption="false"} **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 ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/xfb2XmNKMDRBnAUlygGlh_detailed-clinical-messaging2732x133.png" position="flex-start" size="60" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_2_732x133.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_2_732x133.png" width="732" height="133" darkWidth="732" darkHeight="133" showCaption="false"} **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 ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/3ZiDEmb04llL_QA4EkY_o_detailed-clinical-messaging3731x185.png" position="flex-start" size="60" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_3_731x185.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_3_731x185.png" width="731" height="185" darkWidth="731" darkHeight="185" showCaption="false"} **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 ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/8kPGA_Yg67qv85uxLnXtw_detailed-clinical-messaging4735x374.png" position="flex-start" size="60" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_4_735x374.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_4_735x374.png" width="735" height="374" darkWidth="735" darkHeight="374" showCaption="false"} **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.) :::hint{type="info"} **Note: **Receiving systems' responses can occur in any order. ::: ### Multiple Recipient Message with Errors and Verifies ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/MQUSlHZAwNA8NngfqtELr_detailed-clinical-messaging5730x633.png" position="flex-start" size="60" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_5_730x633.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_5_730x633.png" width="730" height="633" darkWidth="730" darkHeight="633" showCaption="false"} **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. :::hint{type="info"} **Note: **Receiving Systems’ responses can occur in any order. ::: ### Undeliverable Messages ### Surescripts’ Error Response ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/b1w7GHWItMM-NauwhK4_2_detailed-clinical-messaging6.png" position="flex-start" size="50" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_6.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_6.png" width="500" height="150" darkWidth="500" darkHeight="150" showCaption="false"} **Scenario 7** Sender generates a *Clinical* message. 7a). Sending System sends *Clinical* message to Surescripts. 7b). Sending System receives an *Error* response from Surescripts. :::hint{type="info"} **Note: **This scenario applies to both single and multiple recipient messages. ::: ### Surescripts: Transaction Not Recognized ::Image[]{src="https://api.archbee.com/api/optimize/fNEeV2bO-J-V0NK1eH_VR/WkfLKxJQAANMf3fHKI6VW_detailed-clinical-messaging7547x130.png" position="flex-start" size="60" initialPath="../../Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_7_547x130.png" githubPath="Content/Resources/Images/Net2Net REST v1.5/Detailed Clinical Messaging_7_547x130.png" width="547" height="130" darkWidth="547" darkHeight="130" showCaption="false"} **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 :::hint{type="info"} **Note: **Surescripts ACRs are not enforced as part of validations, but instead through the certification process. :::