Source: https://quadevs.com/healthcare/fhir-tefca-integration/

Title: TEFCA and FHIR API integration, SMART on FHIR | quadevs

[Home](https://quadevs.com/)/ [Healthcare software development](https://quadevs.com/healthcare/)/ TEFCA and FHIR integration

# 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.

[Tell us about your project](https://quadevs.com/contact/)  [or email us](mailto:hello@quadevs.com)

**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

A strict FHIR R4 server with US Core, SMART on FHIR app launch, QHIN partners, USCDI mapping, Bulk Data and a consent-scoped audit.

- ### 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

- [FHIR · TEFCA · USCDI integration](https://quadevs.com/case/fhir-tefca-uscdi/)

  External info-blocking review of our FHIR platform asked for no changes. The server has 42 resource providers, and adding a TEFCA partner means one new row in a configuration registry.
- [HIPAA audited file proxy](https://quadevs.com/case/hipaa-file-proxy/)

  Download links from our HIPAA file proxy are valid for one document, one recipient and one time window. Its first external HIPAA security audit passed with no remediation.
- [Clinical data aggregation hub](https://quadevs.com/case/clinical-data-hub/)

  Consumers of our aggregation hub read many clinical sources through one contract, and every request they make is logged for audit.
- And many more projects

  [All case studies](https://quadevs.com/cases/) [Ask about your project](https://quadevs.com/contact/)

Work happens under your BAA. Put any info-blocking review or QHIN go-live date in the brief; it sets the schedule.

## 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](https://quadevs.com/contact/)

## 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

[### TEFCA vs FHIR: what each one does

 Interop · 8 min read Read](https://quadevs.com/insights/tefca-vs-fhir/)   [### USCDI and FHIR: data classes and the API that carries them

 Interop · 8 min read Read](https://quadevs.com/insights/uscdi-and-fhir/)   [### FHIR AuditEvent: an audit trail that passes review

 Compliance · 7 min read Read](https://quadevs.com/insights/fhir-auditevent/)

## 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
