Skip to main content
Alma Health AI
EHR integrations

Live across leading ambulatory and enterprise environments.

The Referral Review Engine integrates into existing EHR referral workflows. Implementation scope varies by EHR, site configuration, and workflow — we plan implementation jointly with each customer's IT, clinical, and operations leads.

Supported environments

Direct and partner-connector integrations.

EHR / Environment
Integration mode
Status
eClinicalWorks
Direct integration
Live
athenahealth
Direct integration
Live
NextGen
Direct integration
Live
Allscripts
Direct integration
Live
Greenway
Direct integration
Live
Veradigm
Direct integration
Live
Epic
Partner connectors
Where in place
Cerner / Oracle Health
Partner connectors
Where in place
Meditech
Partner connectors
Where in place
Other ambulatory EHRs
Direct or HL7/FHIR
Scoped per environment
Data flow

What goes in. What comes out.

Inbound to the engine

  • Specialty requested (structured)
  • Indication or chief complaint (free text)
  • Optional: in-network preference flags (when preferred-network integration is configured)

Outbound from the engine

  • Routing recommendation: specialist-required / PCP-LED management / escalate / conditional
  • Cited guideline source
  • Recommendation ID and timestamp
  • Engine version and guideline version
  • Audit record metadata for downstream logging
Workflow integration

Where the engine enters the referral workflow.

01

Coordinator initiates referral in EHR

Standard EHR referral order workflow — no change to UI for the coordinator beyond an in-line panel or modal.

02

Engine called via API on referral submit

Two inputs (specialty, indication) sent to the Alma engine. Recommendation returned in under ten seconds.

03

Recommendation presented inline to coordinator and clinician

Recommendation shown with rationale, cited guideline source, and three actions: Accept, Override with reason, Print rationale.

04

Clinician decides

Override authority preserved on every non-safety decision. The 39 hardcoded safety escalations cannot be overridden.

05

Audit record written to EHR and Alma audit store

Field-level diff tracking. Append-only. Exportable for plan audits, CMS data validation, and regulatory inspection.

Implementation

What an implementation involves.

Integration scoping call.

Confirm EHR version, referral workflow conventions, in-network preferences, audit log routing, and data retention requirements.

De-identified sample review.

Customer shares de-identified indications and requested specialties only — no PHI. Alma returns estimated referral appropriateness, coordinator time saved, and modeled ROI. PHI never leaves customer infrastructure during this phase.

BAA execution.

A Business Associate Agreement is executed before any production integration that processes PHI.

Production integration.

API connectivity, authentication, audit log routing, in-line UI rendering. Typical timeline: 4–8 weeks for ambulatory EHRs; 8–16 weeks for enterprise / partner-connector environments.

Site go-live.

First 50 recommendations reviewed jointly. Specialty matrix tuned to local guideline patterns. Engine Champion on-site Week 1.

PHI handling

PHI never leaves customer infrastructure during sample reviews.

During the de-identified sample review phase, customers share only indications and requested specialties — no patient identifiers, no clinical narrative beyond chief complaint. Alma returns modeled outputs using production data and national benchmarks. PHI is governed by a HIPAA-aligned BAA executed before any production integration that processes PHI. Database and application infrastructure is hosted on SOC 2 Type II–attested platforms (Supabase, Vercel).

Test the integration on a de-identified referral sample.

Share indications and requested specialties only. Alma returns estimated referral appropriateness, coordinator time saved, and modeled ROI using production data and national benchmarks.

Request a sample review →