Overview

Agencies that use an EMR that supports HL7 can bring documents into SutureHealth without the Partner API. Homecare Homebase (HCHB) is one of the systems we support for this integration.

For EMRs that support HL7, SutureHealth offers an MDM-based pipeline:

1. ADT patient feed: An HL7 ADT message (A01 / A08) arrives first so patient demographics stay in sync, including insurance.
2. Send document (MDM): The EMR sends an MDM message with the PDF and the embedded signer and patient details.
3. Status callback (ORU): When the document reaches a terminal state (signed or rejected), SutureHealth sends an HL7 ORU with the final state and any error or reject reason.

Signing still happens in SutureHealth Inbox. The EMR does not need a portal. It sends HL7 in and gets HL7 back.

How the HL7 path works

The connected EMR keeps the patient current, then sends the document. SutureHealth routes it to the signer and later notifies the EMR of the outcome.

sequenceDiagram
  autonumber
  participant EMR as Connected EMR
  participant SH as SutureHealth

  Note over EMR,SH: Patient management
  EMR->>SH: ADT (patient add/update)

  Note over EMR,SH: Document ingestion
  EMR->>SH: MDM: signer (NPI, address), patient, PDF

  Note over EMR,SH: Terminal state
  SH->>EMR: ORU: signed or rejected with reason

What each message carries

ADT: patient add or update

Send this before the document when demographics change. Typical events are admit (A01) and update (A08). SutureHealth uses the payload to match or create the patient so the later MDM can attach to the right record.

MDM: document for signature

The MDM is the signature request. It includes:

• Signer: NPI and address so SutureHealth can route to the right inbox
• Patient: an id you already sent on ADT, or enough demographics to match
• Document: the PDF to sign

ORU: signed or rejected

After the signer completes or rejects the document, SutureHealth sends an ORU back to the connected EMR. The message includes the terminal state. A rejection includes the reason.

Next

If your system does not send HL7, use the Partner API to create and track signature tasks over HTTP.

Supported systems include: