--- title: Clinical Direct Messaging Processing Summary slug: net2net-rest/guide/clinical-direct-messaging-processing-summary docTags: createdAt: 2026-06-12T09:48:24.016Z --- This section explains the processing that takes place for *Clinical *messages exchanged between a sending customer and a receiver. | **Event ID** | **Event** | **Process** | **Type of Message** | **Code** | **Desc. Code** | **Description** | | ------------ | -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------- | -------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | 1.0 | **Surescripts receives a message** | | | | | | | 1.1 | | Surescripts fails to recognize the type of message. | N/A | N/A | N/A | A text message that says "Malformed payload sent to system" | | 1.2 | | Surescripts recognizes that the message is a clinical message but does not have enough information to create an error message. | N/A | N/A | N/A | A text message that says "Malformed payload sent to system" | | 1.3 | | Sender ParticipantID or Password is Invalid | N/A | N/A | N/A | A text message that says "Authentication failed: Invalid UID and password." Or "Missing authorization info in the header" | | 1.4 | | Any other system-related error which makes it impossible for Surescripts to accept the message. | N/A | N/A | N/A | A general text message describing the error. | | 2.0 | **Surescripts processes the message** | | | | | | | 2.1 | | Surescripts determines that the sender is not valid. | Error | 900 – Transaction rejected | 001 - Sender ID not on file | | | 2.2 | | Surescripts determines that the sender is not certified to send this type of message. | Error | 900 – Transaction rejected | None | Message type not supported by sender | | 2.3 | | Surescripts determines that the receiver is not valid. | Error | 900 – Transaction rejected | 002 – Receiver ID not on file. | | | 3.0 | **Synchronous Message** **Delivery** | | | | | | | 3.1 | | Message was delivered to recipient. | Status | 010 | Specified by receiving system | | | 3.2 | | Message could not be delivered to recipient. | Error | 601 | Specified by the receiving system | | | 3.3 | | A problem processing the message was encountered by the receiving system. | Error | 602 | Specified by the receiving system | | | 4.0 | **Surescripts accepts message for delivery** | | | | | | | 4.1 | | Surescripts sends a Status message to sender of clinical message, indicating it was accepted for delivery. | Status | 000 | None | | | 4.1.0 | **Surescripts attempts delivery** | The result of the delivery attempt will be communicated back to the sender by means of one of the following free standing messages. | | | | | | 4.1.1 | | Message is delivered to the recipient. | Verify | 010 | None | | | 4.1.2 | | Message could not be delivered to recipient. | Error | 601 | Specified by the receiving system. | | | 4.1.3 | | A problem processing the message was encountered by the receiving system. | Error | 602 | Specified by the receiving system. | |