Interoperability
Currently automatically converts HL7 V2 messages and CCDA documents into FHIR R4 bundles — with resource relationship preservation, validation, and multiple export paths.
Resources
Each resource is mapped from the corresponding HL7 segments or CCDA sections with relationship preservation.
Demographics, identifiers, and administrative information from PID segments or CCDA patient role.
Visit information, admissions, and patient interactions from PV1/PV2 segments or encounter sections.
Lab results, vital signs, and clinical measurements from OBX segments or results organizers.
Diagnoses, problems, and clinical conditions from DG1 segments or problem sections.
Prescriptions and medication history from RXE/RXA segments or medication sections.
Surgical history and interventions from PR1 segments or procedure sections.
Lab reports, imaging results, and diagnostic findings from OBR/OBX groupings.
Healthcare provider information from PV1 attending/referring fields or author elements.
Hospital, clinic, and facility data from MSH sending/receiving fields or custodian elements.
Capabilities
Honest capabilities — conversion and export, built into the processing pipeline.
HL7 V2 and CCDA documents are converted to FHIR R4 as part of the standard pipeline — no separate project.
Every converted record produces a FHIR bundle stored and browsable through the platform.
Get FHIR data out of Currently in the format your systems need.
The same pipeline that produces FHIR also produces OMOP CDM 5.4 — no duplicate processing.
Use Cases
FHIR R4 bundles from Currently integrate with downstream systems for interoperability, analytics, and patient access.
Deliver health records to patient-facing portals and mobile apps using standard FHIR resources.
Share structured patient data across providers in a network using FHIR bundles.
Feed FHIR data (alongside OMOP) into research platforms for standardized population health analysis.
Power HIE networks with FHIR-based data sharing between participating organizations.
Extract structured quality measures from FHIR resources for value-based care programs.
Push FHIR bundles directly to Google Cloud Healthcare API for managed FHIR store hosting.
Get started
Start processing HL7 messages, ensure data quality, and enable FHIR-based interoperability — all from one platform.