Process millions of HL7 messages, ensure data quality, and enable modern FHIR-based interoperability — all from one platform.
The Platform
HL7 messages arrive broken. C-CDA documents are bloated. CSV schemas don't exist. Currently normalizes everything into clean FHIR R4 and OMOP CDM — automatically.
Fragmented and inconsistent across vendors. Every hospital sends different field mappings — segments missing, values in the wrong fields, timestamps in dozens of formats.
Bloated XML with optional sections everywhere. Missing data is the norm. Validation is rarely enforced, so documents that technically "pass" are still unusable.
No schema. Column names vary by source. Date formats, encoding, delimiters — all inconsistent. You spend more time cleaning than analyzing.
Locked behind proprietary schemas. Every vendor and version requires custom queries. Upgrades break extracts without warning.
Unreliable delivery. Files arrive late, duplicated, or truncated. Error handling is an afterthought — or nonexistent.
Clean, validated, standards-compliant. Every resource passes US Core profiles automatically. No manual remediation needed.
Athena vocabulary-resolved. Ready for population health analytics and outcomes research at scale, right out of the box.
Live quality grades per source. Anomaly detection fires at ingestion — before bad data reaches your downstream systems.
Full CRUD with real-time event hooks. Build downstream applications without ever touching the pipeline internals.
One-click exports in any format. Schedule recurring jobs or run on-demand. Filter by date, source, type, or quality score.
Epic, Cerner, Allscripts, Meditech, and any system that speaks HL7 v2.x or CDA. Direct database ingestion also supported.
Every message is validated and quality-scored before entering the pipeline. Bad data is flagged, not forwarded.
Track per-source message rates, error counts, and latency from the dashboard. Alerts when something needs attention.
Steps
Connect your EMR/EHR systems, labs, or hospital interfaces. Any HL7 endpoint, any direct database, any data feed — one configuration.
Automated parsing, normalization, and quality scoring. Every message is checked, cleaned, and enriched before it moves downstream.
Review your FHIR output. Set quality thresholds. Hit go. Monitor from the dashboard. Query from the API.
Features
Process thousands of HL7 messages per minute with sub-second latency. Built for peak load and critical healthcare workflows.
Enterprise-grade security with end-to-end encryption, full audit logging, and HIPAA compliance built in from day one.
Connect to multiple EMR/EHR systems, hospitals, and data sources. One unified pipeline for your entire network.
Built-in analytics with Metabase integration. Track data quality scores, processing rates, and operational health.
Full FHIR R4 compliance with automatic conversion from HL7 v2.x messages. Zero custom code required.
RESTful API with comprehensive docs, webhooks, and SDKs. Build on top of Currently without touching the pipeline.
See It Work
Raw HL7 goes in broken. Currently produces FHIR R4, cleaned HL7, OMOP CDM, and a quality report — all from a single message.
MSH|^~\&|EPIC|MEMORIAL|CURRENTLY|HIE|
EVN|A01|20260311143022||
PID|1||MRN-00293847^^^MEM^MR||
JOHNSON^SARAH^M||19840312|F||
|123 Main St^^Chicago^IL^60601||
(312)555-0142|||S||
PV1|1|I|MED^4210^01||||
7788^Smith^Robert^J^MD|||MED||
|||7788^Smith^Robert^J^MD|S||
||||||||||||||||||||||||
DG1|1||J18.9^Pneumonia^ICD10|||A|{
"resourceType": "Patient",
"id": "pt-8821-memorial",
"identifier": [{
"system": "urn:oid:2.16.840.1",
"value": "MRN-00293847"
}],
"name": [{
"family": "Johnson",
"given": ["Sarah", "M"]
}],
"birthDate": "1984-03-12",
"gender": "female",
"address": [{
"line": ["123 Main St"],
"city": "Chicago",
"state": "IL",
"postalCode": "60601"
}]
}HL7 v2.x messages are mapped to FHIR R4 resources in real-time. No custom code. No manual mapping.
Patient, Encounter, Observation, Condition, MedicationStatement, AllergyIntolerance — all standard resources supported.
SNOMED CT, LOINC, ICD-10, CPT, and RxNorm codes are resolved and mapped to standard value sets automatically.
Data Quality
Every record gets a quality score. Every source gets a report. When data quality drops, you know — before it hits downstream.
Track quality scores, error rates, and message volumes per data source. See which hospitals send clean data and which need attention.
Automatic alerts when message patterns change — volume drops, error spikes, or new message types appear unexpectedly.
Route messages by type, source, or quality score. Quarantine bad data. Escalate issues to the right team automatically.
Problems solved
Without
You manage 12 different HL7 interfaces manually. One change at one hospital breaks three downstream systems.
With Currently
One unified pipeline ingests all sources automatically. Add a new hospital in minutes, not months.
Without
Data quality issues go undetected until they cause failures in clinical workflows or reporting.
With Currently
Real-time quality scoring catches anomalies at ingestion — before they touch your downstream systems.
Without
Converting to FHIR requires a dedicated engineering team and six months of custom mapping work.
With Currently
Automatic FHIR R4 conversion for every HL7 message. Zero custom code. Zero maintenance.
Without
You have no visibility into message volumes, error rates, or which sources are unreliable.
With Currently
Full observability: per-source dashboards, message traces, and quality reports out of the box.
Identity
Every data source — EMRs, labs, devices, HIEs — funneled into one normalized pipeline. One connection to manage.
Every record scored. Every anomaly flagged. Every source graded. Data quality is enforced at ingestion, not patched downstream.
Every HL7 message automatically converted to FHIR R4. Terminology normalized. Resources structured. Ready for modern apps.
HIPAA-ready from day one. End-to-end encryption, full audit trails, role-based access, and BAA support built in.
REST API, webhooks, FHIR endpoints. Build healthcare applications without building the data infrastructure beneath them.
Currently sits between your data sources and your applications. It normalizes and delivers — it does not store or manage patient records.
We don't build one-off connections between systems. Currently is a platform — every source feeds one pipeline.
Currently transforms and routes data in real-time. For long-term storage and analytics, it exports to your warehouse of choice.
Use cases
Automate data ingestion from member hospitals. Standardize HL7 processing. Provide FHIR-based APIs to all participants from a single integration layer.
Connect to regional HIEs and share data seamlessly. Improve care coordination. Reduce duplicate orders from better patient data visibility across systems.
Access clean, normalized, de-identified healthcare data for population health studies, outcomes research, and predictive modeling at scale.
Embed Currently's integration layer into your product. Your customers get enterprise HIE connectivity. You get a REST API and webhooks.
FAQ
Traditional engines require per-interface configuration and custom mapping. Currently provides a single pipeline that automatically normalizes any HL7 source to FHIR R4 with built-in quality scoring.
Yes. Currently works with any system that produces HL7 v2.x messages — Epic, Cerner, Allscripts, Meditech, and more. Direct database ingestion is also supported.
Currently scores every message at ingestion. When a source's quality drops below your configured threshold, processing pauses for that source and an alert is sent.
Yes. End-to-end encryption, full audit logging, role-based access control, and BAA support are built in from day one.
No. Configuration is declarative. Point Currently at your HL7 endpoint, set your quality thresholds, and it handles everything automatically.
Yes. Full multi-tenancy with complete data isolation between organizations. One deployment, many HIEs.
Get started
Connect your data sources, process HL7 and CCDA, and deliver clean FHIR R4 + OMOP CDM 5.4 — from one platform.