HL7 is inbound only. HealOS does not send notes or results back over HL7. Finished notes reach the chart through the EHR’s own connection or the Chrome extension.
What HealOS does with each message
Patients are matched within your organization by MRN, so the same MRN from your feed always updates the same HealOS patient.
In AI Scribe, recent results appear as visit context, grouped as Recent Labs, Imaging, Pathology, Microbiology, Blood Bank and Provider Documents. By default HealOS uses the last 90 days, up to 30 reports; HealOS can tune this for your organization.
How the feed reaches HealOS
Your system gets the HL7 acknowledgement from the receiving endpoint. HealOS processes each message after it arrives: a temporary failure is retried automatically, and a message that still fails is set aside for review instead of being lost.
Who does what
Monitoring and support
- HealOS tracks when it last received each message type. If the feed goes quiet, HealOS shares the last-received time per message type with your interface team, which is usually the fastest way to find a stopped channel.
- Messages that fail processing are kept and reviewed; send corrected messages again as usual.
- To add a message type (for example pharmacy), contact HealOS: each new type needs a handler before it is used.
Security
- Option A uses TLS with OAuth service credentials; option B carries MLLP inside an IPsec tunnel.
- Each customer has its own HL7 store and pipeline; HealOS accepts messages only from your configured feed and links them only to your organization.
- Use test patients for all testing; HL7 messages contain PHI.