ADT & HIE Integration
Plenty of firms can say “healthcare analytics.” Far fewer can explain what happens between a hospital sending an A03 and a care manager picking up the phone.
DAX builds that chain end to end: ingestion, identity resolution, deduplication, normalization, and routing into the workflow that actually gets worked — on infrastructure you own.
What we wire up
Feeds & connectivity
- HL7 v2 interface feeds from hospitals and health systems
- Regional and state HIE connectivity
- National notification network subscriptions
- Direct health system point-to-point interfaces
- MLLP listeners and secure file transport
Event types
- A01 admit
- A03 discharge
- A08 update
- A04 registration and ED presentation
- A02, A06, and A07 transfers, where the sending system supports them
Real-time ingestion
- Streaming ingestion with durable message capture
- Replay from raw messages when logic changes
- Latency monitoring by feed and sending facility
- Alerting when a feed goes quiet
Identity resolution
- Matching hospital identifiers to your enterprise patient identity
- Probabilistic matching where identifiers are absent
- Attribution check against active contracts
- Crosswalks retained for audit
Deduplication
- Collapsing duplicate messages from overlapping sources
- Reconciling the same encounter reported by HIE and direct feed
- Admit/discharge pairing into a single encounter
- Suppression of repeat notifications for one event
Event normalization
- Standard event model across every sending facility
- Facility and unit reference data alignment
- Discharge disposition normalization
- Diagnosis capture from the message where present
From ADT event to completed follow-up
- ADT event
- Identity resolution
- Longitudinal patient record
- Actionable discharge
- TCM / care management workflow
Actionable discharges
A discharge that reaches a work queue the same day, attributed and matched, rather than a notification email nobody owns.
TCM workflows
The 48-hour contact and follow-up visit windows tracked from the actual discharge event, with the clock visible to the care team.
Readmission prevention
Recent admissions and ED patterns surfaced against the longitudinal record so teams can intervene before the next event.
Care management triggers
Events routed by risk, attribution, and program enrollment to the team that should act on them.
Utilization signal
Near-real-time admission and ED activity months ahead of the claims that will eventually confirm it.
Contract performance
Transitions managed and readmissions avoided, measured on your own event data rather than on a retrospective payer report.
All of it lands in a foundation your organization owns. The applications that read it — DAX's, your existing tools, or something your team builds — stay interchangeable.
Where do your hospital events land today?
If the answer is an inbox, a portal, or a spreadsheet somebody checks in the morning, there is a straightforward path to routing them into real work.