Health1st AI Logo
For HIEs, QHINs & Diagnostic Labs

Your network's hardest problem is format heterogeneity.

Every trading partner speaks a slightly different HL7 v2. Health1st automates per-partner v2 ↔ FHIR mapping and translates at the network edge — so onboarding scales with the network instead of against it.

  • AI-drafted, per-partner mappings — reviewed by your team
  • Edge translation for TEFCA/QHIN exchange
  • US Core & USCDI conformance, validated before go-live
How translation works
HL7 v2.5.1 · ADT^A01inbound
MSH|^~\&|EPIC|HOSP|H1ST|DST|202601..||ADT^A01|
PID|1||MRN12345^^^HOSP^MR||DOE^JOHN^A||
    19701225|M|||123 MAIN ST^^AUSTIN^TX
PV1|1|I|ICU^101^A|||...admit...
DG1|1|I10|E11.9^Type 2 diabetes mellitus
PID → Patient
PV1 → Encounter
DG1 → Condition
AIMapping
Agent
validate · normalize · map
FHIR R4 · Bundleoutbound
{ "resourceType": "Patient",
  "identifier": [{ "value": "MRN12345" }],
  "name": [{ "family": "Doe",
             "given": ["John","A"] }],
  "gender": "male",
  "birthDate": "1970-12-25" }

{ "resourceType": "Condition",
  "code": { "coding": [{
    "system": "…/icd-10-cm",
    "code": "E11.9" }] } }
US CoreR4.0.1validated
An inbound HL7 v2.5.1 ADT^A01 admission message is parsed segment by segment — PID maps to a FHIR Patient, PV1 to an Encounter, and the DG1 diagnosis segment (ICD-10 E11.9, Type 2 diabetes) to a FHIR Condition — by the AI Mapping Agent, validated against US Core and FHIR R4.0.1. The reverse direction (FHIR back to HL7 v2) is also supported.

In short

Exchange networks and labs live with massive trading-partner heterogeneity — every member sends slightly different HL7 v2 — and onboarding each new partner by hand doesn't scale. Health1st automates a per-partner v2 ↔ FHIR mapping (AI-drafted, team-reviewed), crosswalks local codes to standards, validates against US Core and USCDI, and translates at the network edge for TEFCA/QHIN exchange — including high-volume lab ORU results. With TEFCA volume growing from ~10 million to over 1 billion records exchanged in under a year, the edge-translation layer is now core infrastructure, not an experiment.
Per-partner
AI-drafted mappings
reuse the pipeline
Edge
v2 ↔ FHIR translation
for TEFCA/QHIN exchange
US Core
conformance validated
before go-live
ORU → FHIR
lab results at volume
LOINC-normalized
Where networks get stuck

Heterogeneity you can't hire your way past

A network's value grows with every participant — but so does its onboarding backlog, when every partner is a hand-built interface with its own dialect of v2.

Every partner speaks a different dialect

Hundreds of trading partners, each with their own HL7 v2 quirks, Z-segments, code sets, and local conventions. Heterogeneity is the whole problem — and it grows with every new member.

Onboarding doesn't scale

Each new participant is a manual interface project. Your onboarding queue is the bottleneck on network growth, and hand-mapping every partner doesn't get cheaper with volume.

v2 ↔ FHIR at the network edge

Members still push HL7 v2 while the network needs to query and respond in FHIR. Translation has to happen at the edge, per-partner, at exchange volume — reliably.

US Core & TEFCA conformance

It isn't enough to translate — the output has to conform. US Core profiles, USCDI data content, and TEFCA/QHIN governance all have to be satisfied and evidenced.

How partner onboarding works

Onboard a partner once; reuse the pipeline for the next

AI drafts the per-partner mapping and code crosswalks; your team validates against US Core before anything enters the network.

  1. 1

    Ingest the partner's real messages

    Point Health1st at a new trading partner's HL7 v2 feed — ADT, ORU lab results, ORM orders, MDM documents — including their local Z-segments and code conventions.

  2. 2

    AI drafts a per-partner mapping

    The Mapping Agent proposes a partner-specific v2 ↔ FHIR mapping to US Core, and the Terminology Agent crosswalks local codes to LOINC, SNOMED, ICD-10, and RxNorm — with confidence scores.

  3. 3

    Validate against US Core & TEFCA

    Conformance-test the output against US Core profiles and USCDI content before the partner goes live, so what enters the network is already valid — not fixed after the fact.

  4. 4

    Translate at the edge, at scale

    Run bidirectional translation at the network edge for that partner in production. The next partner reuses the pipeline — onboarding becomes repeatable instead of bespoke.

What you get

Translation built for many-partner, high-volume exchange

Automated per-partner mapping

Each trading partner gets an AI-drafted, versioned mapping instead of a from-scratch interface build. Onboarding scales with the network, not against it.

Edge translation for QHIN exchange

Bidirectional v2 ↔ FHIR at the network edge, so members can keep sending v2 while the network queries and responds in FHIR for TEFCA exchange.

Lab results (ORU) at volume

Diagnostic labs push HL7 v2 ORU results everywhere. Health1st maps ORU to FHIR Observation/DiagnosticReport with LOINC normalization, at production throughput.

US Core & USCDI conformance

Output is validated against US Core profiles and USCDI data content, with audit trails — conformance you can evidence to partners and governance bodies.

Who this is for

Built for the people who run the network

Platform and interoperability leaders accountable for onboarding throughput and conformance.

VP Engineering / Platform

Scale trading-partner onboarding without linearly scaling headcount — a repeatable pipeline instead of bespoke interface builds.

Chief Interoperability Officer

Demonstrable US Core / USCDI conformance and TEFCA-ready edge translation, with audit trails for governance.

Head of Standards / Conformance

Validated output before partners go live, and local-code crosswalks to LOINC/SNOMED/ICD-10 handled consistently across the network.

Security & Compliance

Enterprise-grade trust, stated honestly

Protecting PHI is non-negotiable. Here's exactly where our certifications stand — no overclaiming.

HIPAAActive

Compliant · BAAs available

SOC 2 Type IIIn Progress

Audit in progress

HITRUST CSFOn Roadmap

On roadmap

HL7 · FHIRCore

Native, by design

AWS HIPAA-eligible infrastructure · Business Associate Agreements (BAAs) · Encryption in transit & at rest · See our security details →

Frequently asked questions

Make partner onboarding repeatable, not bespoke.

Send us a trading partner's real v2 feed — ORU, ADT, or otherwise. We'll draft the US Core mapping live.

See how translation works