Translate any healthcare format to any other — in days
Health1st is the universal translator for healthcare data. One AI-native engine converts bidirectionally across HL7 v2, FHIR, C-CDA, X12, NCPDP and DICOM, so you clear interface backlogs, meet CMS-0057-F, and modernize without rip-and-replace.
- Any format to any format, bidirectional by design
- AI maps it; your team approves it, with a full audit trail
- Runs in your environment, so you keep control of PHI
Built for HIPAA, HITECH & SOC 2
One engine for every healthcare format
A single hospital runs HL7 v2 for admissions, FHIR for apps, X12 for claims, NCPDP for prescriptions, and DICOM for imaging — all at once. Health1st speaks them all, in both directions.
HL7 v2.x ⇄ FHIR
ADT, ORU, ORM, SIU, MDM and more ↔ US Core FHIR resources — both directions.
C-CDA / CDA
Parse and generate CCD and clinical documents ↔ FHIR Composition & DocumentReference.
X12 EDI
270/271 eligibility, 278 prior auth, 837/835 claims ↔ FHIR & Da Vinci.
NCPDP
SCRIPT e-prescribing and Real-Time Prescription Benefit ↔ FHIR MedicationRequest.
DICOM
Imaging metadata and structured reports ↔ FHIR ImagingStudy.
Direct & IHE
Secure Direct messaging and XDS/MHD cross-community document exchange.
Flat & custom
CSV, JSON, XML, fixed-width, Z-segments and proprietary formats.
Terminology
ICD-10, SNOMED CT, LOINC, CPT, RxNorm and NDC crosswalks.
See the actual transformation — pick a format
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 mellitusAgent
{ "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" }] } }See the full protocol matrix on the platform page →
Interoperability is stuck between a deadline and a backlog
Healthcare data still speaks HL7 v2, while regulators and partners demand FHIR. Bridging the two by hand is slow and expensive.
Interface backlogs measured in months
Every new HL7 v2 interface is hand-built and hand-tested by scarce, expensive integration analysts. Projects slip; roadmaps stall.
A 2027 deadline that won't move
CMS-0057-F requires four FHIR APIs by January 1, 2027. As of late 2025, roughly 43% of payers hadn't started. The clock is the project.
Must expose FHIR, still run HL7 v2
The Cures Act mandates a FHIR API in every certified EHR, but the operational reality is still v2. That gap is exactly what we close.
An AI-native pipeline, with humans in the loop
Every message flows through the same four stages. AI does the heavy lifting; your analysts review and approve before anything ships.
- 1
Ingest
Connect any source (EHR, lab, pharmacy, payer) over HL7 v2, FHIR, X12, NCPDP or flat files.
- 2
AI map
The Mapping & Terminology agents draft field and code mappings and explain every decision.
- 3
Validate
The Validation agent checks output against US Core, Da Vinci and IPS profiles before release.
- 4
Deliver
The Orchestration agent routes, retries and guarantees delivery — real-time, batch or streaming.
A real translation: HL7 v2 → FHIR
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 mellitusAgent
{ "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" }] } }Twelve specialized agents, one platform
Each agent owns a job (mapping, terminology, validation, prior auth, pharmacy and more), coordinated into a single interoperability engine.
Mapping Agent
codename “Cartos”Generates and refines field/schema mappings between any two formats.
Terminology Agent
codename “Lexid”Translates and normalizes codes across clinical & billing code systems.
Transformation Agent
codename “Morphi”Converts every message in both directions without losing meaning.
Validation Agent
codename “Conforma”Guarantees output conforms to the correct profile / implementation guide.
Prior-Auth Agent
codename “Authra”Runs end-to-end electronic prior authorization.
Pharmacy Agent
codename “Rxena”Owns the drug-industry interoperability surface.
The pain is the same for everyone. The fix depends on your role.
Payers & Health Plans
Stand up all four CMS-0057-F FHIR APIs before Jan 2027 — Patient Access, Provider Access, Payer-to-Payer, and Prior Auth (PARDD).
Learn moreHealth Systems
Clear a months-long interface backlog and modernize HL7 v2 to FHIR without ripping out your existing engine.
Learn moreDigital Health Vendors
Ship EHR integrations in days, embedded under your brand. Stop drowning in one-off connectors.
Learn moreHIEs, QHINs & Labs
Automate v2 ↔ FHIR at the network edge and onboard trading partners without linear headcount.
Learn moreCMS-0057-F is a deadline, not a project
Impacted payers must run four FHIR APIs by January 1, 2027, with operational provisions starting in 2026. Health1st gets you there — mapping, PARDD prior auth, and conformance included.
AI-native, built for speed
Legacy engines can take 6–12 weeks and $10K–$30K+ to stand up a single interface; managed API networks lock you into their cloud and per-transaction fees. Health1st is built for speed, on-prem/VPC control, and transparent pricing.
| Capability | Health1st | Redox | Rhapsody | Mirth (OSS) |
|---|---|---|---|---|
| Bidirectional HL7 v2 ↔ FHIR | ||||
| AI-native mapping (drafts + validates) | ||||
| No-code mapping studio | ||||
| Deploy on-prem / in your VPC | ||||
| Transparent, usage-based pricing | ||||
| Days to first interface |
Comparison reflects public positioning; capabilities and pricing vary by deployment. See detailed comparisons.
Security & Compliance
Where our compliance actually stands
Protecting PHI is non-negotiable. Here's exactly where our certifications stand — no overclaiming.
Compliant · BAAs available
Audit in progress
On roadmap
Native, by design
AWS HIPAA-eligible infrastructure · Business Associate Agreements (BAAs) · Encryption in transit & at rest · See our security details →
Connects with your entire healthcare ecosystem
EHRs, national networks, payers, pharmacies and devices — over HL7 v2, FHIR, C-CDA, X12, NCPDP and DICOM. If it speaks a healthcare standard, Health1st speaks to it.
EHR Systems
HIE / QHIN Networks
CMS & Payers
Pharmacy & Devices
Product names are trademarks of their respective owners. Listing indicates interoperability, not endorsement or partnership.
Quick answers about our platform
Ready to turn months of interface work into days?
See a live HL7 v2 ↔ FHIR translation on your own message types. No obligation.