Interoperability

The Data Layer Underneath Every Chain on This Site

None of the connection chains described elsewhere on this site work without a continuous, reliable feed of clinical, administrative, and payer data. This is how that feed reaches the platform, and how the platform reaches back out.

FHIRHL7SMART on FHIREpicOracle Health (Cerner)MEDITECHTruBridge (CPSI)Altera Digital Health (Paragon, Sunrise)MEDHOSTNetsmartAzalea Healthathenahealth (athenaOne)

EHR Connectivity

Data flows in continuously

Clinical and administrative data feeds every module on the platform in real time. Where a direct interface isn't available, RPA brings the data in anyway, rather than leaving a gap in the feed that every downstream chain depends on.

EHR

FHIR and HL7 feeds

InterQual · MCG

Review criteria

Payers

Fax, e-mail and portals

RPA where needed

When there is no direct interface

CMS-0057-F readiness

Illustrative — sample data.

Rules Engine

The payer's own rules police the workflow

Payor Grid holds each payer's rules — notification windows, documentation requirements, submission endpoints, contacts. A rules engine watches the actual work against those rules continuously, and the moment work departs from what a payer requires, a deviation is recorded automatically. The Payer Compliance analytics tab reads that deviation stream directly, so payer compliance becomes a measured number instead of an opinion offered in a meeting.

Payor Grid

Holds each payer’s rules

Notification window
Documentation
Submission endpoint

Rules engine

Watches the actual work

Deviation recorded

The moment work departs

Deviation

Payer Compliance

A measured number

Illustrative — sample data.

Direct to payer portals: Payor Grid communicates directly with payer portals via API — submitting and checking status without a person working through each payer's own website.

Standards & Readiness

Standards and readiness

CMS-0057-F — the federal prior-authorization interoperability rule — applies directly to Authorization Management's function.

CMS-0057-F readinessFHIR interoperabilityHL7 interoperabilitySMART on FHIRPayer connectivity

The Product

Payor Grid

Frequently asked

Epic (via an application in the Epic Showroom), Oracle Health (Cerner), MEDITECH, TruBridge (CPSI), Altera Digital Health (Paragon, Sunrise), MEDHOST, Netsmart, Azalea Health, and athenahealth (athenaOne), via FHIR and HL7.

RPA is used where needed to bring the data in anyway, rather than leaving a gap in the feed.

Yes. CMS-0057-F readiness is part of the platform, alongside FHIR, HL7, and SMART on FHIR support.

Yes. Payor Grid communicates directly with payer portals via API, so requests and status checks don't require a person working through each payer's website separately.

See how the data reaches every module.