quadevs

TEFCA and FHIR integration

FHIR R4 servers and APIs, SMART on FHIR app launch, QHIN connectivity under TEFCA and USCDI mapping for payers, providers and health tech vendors.

Health information exchange in the United States rests on three pieces. FHIR R4 is the API and data model. USCDI lists the data classes certified systems must exchange, and US Core maps them onto FHIR resources. TEFCA lets you query organizations you have no contract with, through a Qualified Health Information Network (QHIN).

Interoperability work

  • FHIR server development

    Strict FHIR R4 servers with US Core 6.1.0, CARIN BB and Da Vinci implementation guides.

  • SMART on FHIR

    Version 2.1 app launch with PKCE and asymmetric client credentials; scopes checked at every endpoint.

  • TEFCA and QHIN connectivity

    Patient discovery and document query through one adapter per QHIN partner.

  • USCDI mapping

    USCDI v3 data classes mapped from vendor exports, with a terminology service for LOINC, SNOMED CT, RxNorm and ICD-10.

  • Bulk Data jobs

    Population-level $export and $import on checkpointed background jobs.

  • Consent-scoped audit

    Each read and write linked to the Consent resource that allowed it, in a hash-linked chain.

Exchange platforms in production

How an exchange project starts

  1. Scope the exchange

    Endpoints, partners, USCDI data classes and any review or go-live date.

  2. Specification review

    We read your conformance statement and the partner specifications and write a plan with the risks of each module.

  3. Conformance before partners

    Profiles and terminology pass validation before the first partner connection opens.

And much more. Ask about your project

Common questions

What is TEFCA?
TEFCA, short for Trusted Exchange Framework and Common Agreement, sets the national rules under which Qualified Health Information Networks exchange clinical data. An organization joins through a QHIN and can then query participants it has no direct agreement with. Our adapters implement version 2.0 of the Common Agreement.
Do we need a FHIR API if we connect through TEFCA?
Usually yes. TEFCA governs who may query whom across networks; a FHIR API is how your own apps, partners and patients read your data. Projects that join a QHIN tend to build or upgrade the FHIR server in the same scope.
What does SMART on FHIR add to a FHIR server?
SMART on FHIR is the OAuth 2.0 profile that lets a third-party app launch next to the EHR and receive a token limited to named scopes, for example patient/Observation.rs. Version 2 brought finer-grained scopes and made PKCE mandatory.

Further reading in Insights

Is a QHIN go-live or an info-blocking review coming up?

Send the date, the exchange partners and the data classes in scope.

Your project brief

A short brief gets a real reply within one business day.

Budget range (optional)

By sending this you agree we can use your email to reply. Privacy policy.

Or email hello@quadevs.com.