Skip to content
All integrationsAltera Digital Health

Hospital EHR integration

Draft the chart in Sunrise, Paragon, or TouchWorks. Review. Sync.

AGIMAN captures the visit on an appliance inside your network and drafts the note, the ICD and CPT codes, and the visit documents in the clinician's style. After the clinician reviews and signs, AGIMAN maps the approved record to the right Altera fields and syncs it to the chart.

  • HIPAA compliant
  • Runs on your network
  • Clinician signs every note
Altera Digital Health logo
System
Altera Digital Health
Category
EHR
Used by
Hospitals, health systems, and larger physician practices
Connects over
Altera Developer Program

The connection

How AGIMAN connects to Altera Digital Health.

What Altera Digital Health is

Altera Digital Health builds and runs hospital and health-system EHRs, including Sunrise for acute and ambulatory care, Paragon for community and critical access hospitals, TouchWorks for larger physician practices, and dbMotion for cross-organization data aggregation. It is the former Allscripts hospital and large-practice business, acquired by Harris in 2022 and relaunched as Altera. The systems are run by hospital IT and clinical informatics teams, not by individual providers.

Who runs it

Hospitals, health systems, and larger physician practices

The access path

FHIR R4USCDISMART on FHIROAuth 2.0HL7v2

AGIMAN registers as a FHIR app through the Altera Developer Program and reads patient and encounter context from your Sunrise, Paragon, or TouchWorks instance over FHIR R4 with SMART on FHIR and OAuth 2.0, scoped to USCDI. Altera's FHIR API is read-only, so the signed note and accepted codes are written back through the access path your IT team approves for that instance, the bidirectional Unity API or an HL7v2 interface depending on your version. Your team activates the app for your organization and points it at the right endpoints before anyone uses it. The export path is scoped to your fields and tested against your own instance before go-live, never turned on blind.

The Altera export path is scoped to your fields and tested against your own Sunrise, Paragon, or TouchWorks instance before it is turned on at go-live.

The workflow

From the exam room to Altera Digital Health, with you in control.

1

Capture

AGIMINION records the room

The AGIMINION device captures the visit audio and sends it to the AGIMAN appliance on your network. Transcription runs locally, with no internet connection required.

2

Draft

Note and codes in your style

AGIMAN drafts the chart note in the clinician's style and suggests the ICD and CPT codes for the encounter, plus any referral letters, intake forms, and the follow-up task. It pulls patient and visit context from Altera over FHIR R4 to ground the draft.

3

Review and sign

The clinician decides

The clinician reviews every line, edits what is wrong, and signs. Nothing reaches the chart until a human approves it, and the codes stay suggestions until accepted.

4

Sync

Back into Altera

AGIMAN maps the signed note and accepted codes to the matching fields in Sunrise, Paragon, or TouchWorks and writes them back through the Unity API or HL7v2 path your IT team approved. A review log records what was sent.

After sign-off

What AGIMAN hands back to Altera Digital Health.

Signed note

The chart note

The reviewed and signed encounter note, drafted in the clinician's style, mapped to the note fields in your Sunrise, Paragon, or TouchWorks instance.

ICD / CPT

Codes for the encounter

Suggested ICD and CPT codes the clinician accepted during review, attached to the visit so coding and billing start from a clean record.

Documents

Letters and forms

Referral letters, patient handouts, and intake or visit forms prepared from the visit, saved against the encounter for the clinician to send or finalize.

On your network

Local first, before any export.

  • Room audio and transcripts stay on the appliance on your network.
  • Transcription and note drafting run on site, with no internet connection required.
  • Nothing reaches Altera Digital Health until the clinician reviews and signs.
  • Exports use the access path your practice approves, with a BAA available.

Questions

Altera Digital Health, answered.

Where does the visit audio and the draft note live?

Room audio, transcripts, and drafts stay on the AGIMAN appliance on your practice network. Transcription and drafting run locally, so no internet connection is needed to produce the note. Only the approved record leaves the appliance, through the export path your IT team approves.

How does AGIMAN write back to Sunrise or Paragon if the FHIR API is read-only?

AGIMAN reads patient and encounter context over Altera's read-only FHIR R4 API. Because that API does not accept write-backs, the signed note and accepted codes are sent through the path your version supports, the bidirectional Unity API or an HL7v2 interface, scoped and tested against your own instance before go-live.

Does AGIMAN write to the chart on its own?

No. AGIMAN drafts, and the clinician reviews, edits, and signs. Nothing syncs to Altera until a human approves it, and the suggested ICD and CPT codes are accepted by the clinician before they are attached. A review log records what was sent.

Get started

Run AGIMAN alongside Altera Digital Health.

Buy the appliance and room devices, then scope the Altera Digital Health export path with us. We test it against your instance before it is turned on.