Integrations

Connects to the EHR you're already using — via FHIR R4.

Prioriq reads encounter data, pushes structured notes, and retrieves supporting documents through your EHR's FHIR R4 API. No separate login for providers. No parallel documentation. HL7 v2 supported as a fallback for systems with limited FHIR exposure.

Major EHR platforms, fully integrated.

All EHR integrations use HL7 FHIR R4 as the primary exchange standard, leveraging SMART on FHIR launch for OAuth 2.0 authentication. HL7 v2.x (ADT, ORM, ORU, MDM) is supported as a fallback for systems with limited FHIR exposure.

FHIR R4
Epic

Full read/write integration via Epic's FHIR R4 API. Supports note push, order read, patient data pull, and PA status sync. Compatible with Epic on-premise and cloud deployments.

FHIR R4
Cerner

Integration via Cerner's Millennium FHIR API. Note generation pushes directly to the encounter. Lab results and imaging orders are read for PA evidence compilation.

FHIR R4
athenahealth

Integrates via athenahealth's athenaClinicals FHIR API. Supports encounter documentation push and PA tracking within the athenaNet interface.

FHIR R4 / HL7 v2
eClinicalWorks

Dual integration path: FHIR R4 for note delivery and HL7 v2 for lab result and order retrieval. Full encounter-to-PA automation supported on eCW cloud and on-premise.

HL7 v2 / FHIR R4
Allscripts

Integration via Allscripts' Unity and Professional APIs. Note push and PA packet assembly supported. HL7 v2 ADT feeds supported for patient demographic sync.

Custom
Other EHR Systems

Using a different EHR? Contact us. If your EHR exposes FHIR R4 or HL7 v2 interfaces, Prioriq can integrate. Custom EHR connector development is available on System plan.

Major payer networks covered.

Prioriq maintains a procedure-specific PA criteria library for each payer — covering commercial, Medicare Advantage, and Medicaid managed care plans. Coverage policies and medical necessity criteria are reviewed quarterly against published payer bulletins.

UnitedHealth / Optum
Aetna / CVS Health
Anthem / BCBS
Cigna / Evernorth
Humana
Tufts Health
Harvard Pilgrim
Medicare Advantage plans
Medicaid managed care
Molina Healthcare
Centene / WellCare
Point32Health

Under the hood.

Prioriq is built on published healthcare interoperability standards — HL7 FHIR R4 and HL7 v2. We do not use proprietary connectors. If your EHR exposes a standards-compliant API, Prioriq can integrate with it without custom middleware.

Primary Standard
FHIR R4

HL7 FHIR Release 4 is the primary data exchange standard. All EHR read and write operations use FHIR-compliant resource types (Patient, Encounter, Observation, MedicationRequest, Condition).

Fallback Standard
HL7 v2.x

HL7 v2.3 through v2.8 supported for EHRs with limited FHIR exposure. ADT, ORM, ORU, and MDM message types supported. Inbound and outbound interface configurations available.

Security
OAuth 2.0 / SMART on FHIR

All EHR API access uses OAuth 2.0 with SMART on FHIR launch protocols. Tokens are scoped to minimum required permissions. No persistent storage of raw PHI outside encrypted audit logs.

PA Submission
Direct API + eFax

Payers with electronic PA APIs receive submissions directly. For payers without API access, Prioriq uses structured eFax with OCR confirmation. API submission is available for UnitedHealth, Aetna, Cigna, and Humana.

Uptime
99.9% SLA (System plan)

The Prioriq API layer targets 99.9% uptime for System plan accounts, backed by a contractual SLA. PA submission retries are automatic on timeout or payer-side errors. Status updates are delivered within 60 seconds of payer response.

Deployment
Cloud-hosted (AWS)

Prioriq is hosted on AWS in HIPAA-eligible services (EC2, RDS with encryption, S3 with server-side encryption, CloudTrail). No on-premise installation required. VPN connectivity available for health system accounts.

Ready to connect your system?

Tell us which EHR you're running and we'll outline the FHIR integration path, typical setup time, and what your IT team will need to provide — access credentials and application registration, typically a 1–2 hour IT task for most EHR platforms.

Start integration conversation