Empowering HIEs with
seamless data integration.
Process millions of HL7 messages, ensure data quality, and enable modern FHIR-based interoperability — all from one platform.
Quickstart
Connect your EMR, process HL7, and serve FHIR — with a single configuration. No custom middleware required.
$ npx aquila connect --source epic --format hl7v2Steps
Stop managing
HL7 complexity.
Define the source.
Connect your EMR/EHR systems, labs, or hospital interfaces. Any HL7 endpoint, any direct database, any data feed — one configuration.
Process and validate.
Automated parsing, normalization, and quality scoring. Every message is checked, cleaned, and enriched before it moves downstream.
Approve and go.
Review your FHIR output. Set quality thresholds. Hit go. Monitor from the dashboard. Query from the API.
Features
Everything you need for
healthcare data integration.
Real-time Processing
Process thousands of HL7 messages per minute with sub-second latency. Built for peak load and critical healthcare workflows.
HIPAA Compliant
Enterprise-grade security with end-to-end encryption, full audit logging, and HIPAA compliance built in from day one.
Multi-Source Integration
Connect to multiple EMR/EHR systems, hospitals, and data sources. One unified pipeline for your entire network.
Advanced Analytics
Built-in analytics with Metabase integration. Track data quality scores, processing rates, and operational health.
FHIR R4 Ready
Full FHIR R4 compliance with automatic conversion from HL7 v2.x messages. Zero custom code required.
Developer API
RESTful API with comprehensive docs, webhooks, and SDKs. Build on top of Aquila without touching the pipeline.
Multi-Source Integration
Bring your own
data source.
Your Epic, Cerner, and Allscripts — organized under one pipeline, pointed at one goal. If it can send HL7, it's connected.
Works with any EMR
Epic, Cerner, Allscripts, Meditech, and any system that speaks HL7 v2.x or CDA. Direct database ingestion also supported.
Quality at ingestion
Every message is validated and quality-scored before entering the pipeline. Bad data is flagged, not forwarded.
Real-time monitoring
Track per-source message rates, error counts, and latency from the dashboard. Alerts when something needs attention.
FHIR R4
Keep your data aligned
on the standard.
Every HL7 message is automatically converted to FHIR R4. Your downstream systems get clean, structured, standards-compliant data — every time.
MSH|^~\&|EPIC|MEMORIAL|AQUILA|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"
}]
}Automatic conversion
HL7 v2.x messages are mapped to FHIR R4 resources in real-time. No custom code. No manual mapping.
Full resource coverage
Patient, Encounter, Observation, Condition, MedicationStatement, AllergyIntolerance — all standard resources supported.
Terminology normalization
SNOMED CT, LOINC, ICD-10, CPT, and RxNorm codes are resolved and mapped to standard value sets automatically.
Data Quality
Know what every
source costs you.
Every record gets a quality score. Every source gets a report. When data quality drops, you know — before it hits downstream.
Per-source scoring
Track quality scores, error rates, and message volumes per data source. See which hospitals send clean data and which need attention.
Anomaly detection
Automatic alerts when message patterns change — volume drops, error spikes, or new message types appear unexpectedly.
Delegation & routing
Route messages by type, source, or quality score. Quarantine bad data. Escalate issues to the right team automatically.
Problems solved
What changes
with Aquila.
Without
You manage 12 different HL7 interfaces manually. One change at one hospital breaks three downstream systems.
With Aquila
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 Aquila
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 Aquila
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 Aquila
Full observability: per-source dashboards, message traces, and quality reports out of the box.
Identity
What Aquila is.
A unified integration layer
Every data source — EMRs, labs, devices, HIEs — funneled into one normalized pipeline. One connection to manage.
A quality enforcement system
Every record scored. Every anomaly flagged. Every source graded. Data quality is enforced at ingestion, not patched downstream.
A FHIR transformation engine
Every HL7 message automatically converted to FHIR R4. Terminology normalized. Resources structured. Ready for modern apps.
A compliance foundation
HIPAA-ready from day one. End-to-end encryption, full audit trails, role-based access, and BAA support built in.
A developer platform
REST API, webhooks, FHIR endpoints. Build healthcare applications without building the data infrastructure beneath them.
What Aquila is not.
Not an EHR
Aquila sits between your data sources and your applications. It normalizes and delivers — it does not store or manage patient records.
Not a point-to-point interface
We don't build one-off connections between systems. Aquila is a platform — every source feeds one pipeline.
Not a data warehouse
Aquila transforms and routes data in real-time. For long-term storage and analytics, it exports to your warehouse of choice.
Use cases
Who benefits
from Aquila.
Health Information Exchanges
Automate data ingestion from member hospitals. Standardize HL7 processing. Provide FHIR-based APIs to all participants from a single integration layer.
Healthcare Organizations
Connect to regional HIEs and share data seamlessly. Improve care coordination. Reduce duplicate orders from better patient data visibility across systems.
Research & Analytics Teams
Access clean, normalized, de-identified healthcare data for population health studies, outcomes research, and predictive modeling at scale.
Health IT Vendors
Embed Aquila's integration layer into your product. Your customers get enterprise HIE connectivity. You get a REST API and webhooks.
FAQ
Frequently asked questions.
How is Aquila different from a traditional integration engine?
Traditional engines require per-interface configuration and custom mapping. Aquila provides a single pipeline that automatically normalizes any HL7 source to FHIR R4 with built-in quality scoring.
Can I connect my existing EMR systems?
Yes. Aquila works with any system that produces HL7 v2.x messages — Epic, Cerner, Allscripts, Meditech, and more. Direct database ingestion is also supported.
What happens when data quality drops?
Aquila 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.
Is Aquila HIPAA compliant?
Yes. End-to-end encryption, full audit logging, role-based access control, and BAA support are built in from day one.
Do I need a dedicated engineering team?
No. Configuration is declarative. Point Aquila at your HL7 endpoint, set your quality thresholds, and it handles everything automatically.
Can I run multiple organizations?
Yes. Full multi-tenancy with complete data isolation between organizations. One deployment, many HIEs.
Get started
From fragmented data to
unified health records.
$ npx aquila connect --source epic --format hl7v2Connect your EMR, process HL7, and serve FHIR. Interactive setup walks you through configuration.