HealthFlo
Help healthcare software and medical systems exchange important information more easily. HealthFlo is in development and planned for 2027.
Connect clinical systems that speak different formats
HealthFlo is built to map, route and monitor clinical messages between systems, so an HL7 v2 feed from one system can become FHIR resources for another.
Who it's for
- Health tech startups integrating with EHRs
- Hospital and clinic IT teams
- Digital health platforms
- Labs and imaging providers
Hospital data exchange, mapped
An HL7 v2 admission message from a hospital system becomes a FHIR Patient resource a modern app can use.
MSH|^~\&|ADT|MERCY_HOSP|NEXFLO|HEALTHFLO|20261104103000||ADT^A01|MSG00001|P|2.5.1
EVN|A01|20261104103000
PID|1||MRN448812^^^MERCY^MR||DOE^JANE^A||19840212|F|||12 LAKE ST^^DULUTH^MN^55802
PV1|1|I|4W^412^1^MERCY||||1234567893^SMITH^ALAN{
"resourceType": "Patient",
"identifier": [{
"system": "urn:mercy:mrn",
"value": "MRN448812"
}],
"name": [{ "family": "Doe", "given": ["Jane", "A"] }],
"gender": "female",
"birthDate": "1984-02-12",
"address": [{
"city": "Duluth",
"state": "MN",
"postalCode": "55802"
}]
}What we're building
HL7 v2
Planned parsing and generation for common message types like ADT, ORM and ORU.
FHIR
Work with FHIR R4 resources over a modern API.
Data mapping
Map fields between formats with reusable, versioned mappings.
Message routing
Send each message to the right destination based on its content.
Monitoring
See message flow, failures and retries in one dashboard.
Alerts
Get notified when an interface stops sending or starts failing.
Supported standards
Planned for launch in 2027.
| HL7 v2 | Event-based messages (ADT, ORM, ORU and more) |
| FHIR R4 | Modern REST-based healthcare resources |
Join the HealthFlo waitlist
We'll let you know as soon as HealthFlo opens, and early waitlist members get first access.
✓ You're on the list. We'll be in touch from aadithbalaji@nexflo.cloud.