Overview

How post signature sync works

After a document is signed in SutureHealth, we push it back into the physician's EMR so it lives in the patient's chart. The signer completes the document in Inbox. SutureHealth then matches the patient, saves the signed file in the chart, and creates a claim when the document is a cert or recert.

sequenceDiagram
  autonumber
  participant EMR as Connected EMR
  participant SH as SutureHealth
  actor Signer as Signer

  Signer->>SH: Document signed

  Note over EMR,SH: Patient match
  SH->>EMR: Patient identifiers from the agency
  EMR-->>SH: External patient id

  Note over EMR,SH: Document sync
  SH->>EMR: Save document in patient chart

  alt Document is a cert or recert
    Note over EMR,SH: Claim sync: G0179 / G0180
    SH->>EMR: Claim creation
  end

Sync Steps

1. Patient match

Using identifiers passed during ingestion (for example patient MRN and date of birth), we locate the patient record in the receiving EMR. We match about 96% of patients automatically. The remaining 4% need someone at the practice to choose the patient in Inbox before the sync can finish. Patient match user experience is that review. It looks the same for every EMR. The external patient id from the match is what later steps use to file the document and claim.

2. Document sync

The signed PDF is written directly into the patient's chart, so the practice does not download or upload the file. By default we sync every document that is signed in SutureHealth. You can also filter so that only specific documents are synced.

3. Claim creation

If the signed document is a cert or recert for codes G0179 or G0180, SutureHealth creates the claim in the EMR with pre-filled charge codes and custom fields so billing can start without delay.

How do we connect to the EMR?

It depends on the EMR and how that system exposes its data.

For athenahealth, we connect through their APIs. For Epic, we connect through FHIR APIs and HL7 interfaces. For eClinicalWorks, the practice approves the SutureHealth app and shares a FHIR R4 base URL. Those steps are in eClinicalWorks. In each case we look for the most compliant and secure way to add this data to the chart.

Supported systems include: