--- sourceDocument: Australia Healthcare and Life Sciences sourceDocumentLink: https://www.servicenow.com/docs/r/australia/healthcare-life-sciences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Healthcare and Life Sciences ft:clusterId : - hcls bundleId : - hcls workflow : - Customer and Industry --- # How HL7 integration works in ServiceNow # How HL7 integration works in ServiceNow {#ariaid-title1} Release version: Australia Updated May 11, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of How HL7 integration works in ServiceNow ServiceNow supports inbound HL7 v2.x message integration by receiving messages sent from external integration engines, such as Epic's, via HTTPS POST requests. This integration enables healthcare organizations to automate workflows based on clinical event data without requiring custom configuration beyond the endpoint URL and credentials. Show full answer Show less ## Key Features * **Message Reception and Acknowledgment:** ServiceNow accepts raw ER7-formatted HL7 messages sent through a REST endpoint, validates the MSH header, and returns standard HL7 acknowledgment codes (AA for accept, AE for error, AR for reject) to indicate processing status. * **Message Logging and Parsing:** ServiceNow automatically matches incoming messages to a single active parser configuration based on sending application, facility, HL7 version, message type, and trigger event. Parsed segment fields are extracted into JSON format and stored in a new HL7 message log record with status Pending or Failed. * **Workflow Execution:** A Flow Designer flow triggers on the creation of the message log record, filtering by metadata such as message type and sending facility. The flow uses parsed data to perform downstream actions like patient room status updates, task creation, and notifications within healthcare operations applications. ## Practical Example In a typical use case, an ADT\^A03 discharge message triggers a room turnover process: the EHR system sends the message, which ServiceNow validates and parses. A flow then marks the discharged patient's room as needing cleaning, creates housekeeping tasks, and notifies staff---fully automating the room turnover workflow without manual steps. ## Important Considerations * ServiceNow does not support HL7 message transport over MLLP or TCP/IP; an external integration engine must handle message delivery over HTTPS. * The integration is inbound only; ServiceNow does not send HL7 messages back to the EHR system. HL7 v2.x messages flow through four stages in ServiceNow: reception and acknowledgment, message logging, parsing, and workflow execution. ## End-to-end message flow The following describes the path of an inbound HL7 v2.x message from the integration engine through to workflow execution: 1. **Integration engine sends a message.** The integration engine (for example, Epic's integration engine) POSTs a raw ER7-formatted HL7 message to the ServiceNow REST endpoint over HTTPS. The integration engine requires no custom configuration beyond the endpoint URL and credentials. For the endpoint URL, authentication, and message schema, see the [HL7 Inbound API](https://www.servicenow.com/docs/access?context=hl7-inbound-api&version=australia&pubname=australia-api-reference&ft:locale=en-US) reference. 2. **ServiceNow validates and acknowledges.** ServiceNow validates the MSH header and returns an acknowledgment indicating the outcome --- AA (accept), AE (error), or AR (reject). For acknowledgment codes and HTTP status behavior, see [HL7 ACK codes](https://www.servicenow.com/docs/c5bRe3e4qYeAD5FANpJ65A "ServiceNow returns one of three HL7 acknowledgment codes in the MSA segment of every ACK response. The code indicates whether the message was accepted, rejected at the application level, or resulted in an error."). 3. **ServiceNow parses and stages the message.** ServiceNow looks up the single active parser configuration whose sending application, sending facility, HL7 version, message type, and trigger event match the message. It then extracts the configured segment fields into the `parsed_data` JSON on a new HL7 message log record. On success the record is created with status Pending; if no single configuration matches, or a field cannot be parsed, the record is created with status Failed. Parsing happens automatically at reception --- no flow or action is required. 4. **A downstream flow runs.** A Flow Designer flow in a consuming application triggers when the message log record is created. The flow's trigger condition can filter on the record's metadata (for example, message type = ADT, trigger event = A03, sending facility = MAIN). The flow then reads the parsed values from `parsed_data` to drive downstream work --- such as room turnover tasks, care team notifications, or encounter updates. ## North star scenario: ADT\^A03 discharge to room turnover A patient is discharged from room 4B-401-A. The EHR system sends an ADT\^A03 message to the integration engine, which POSTs it to ServiceNow. ServiceNow validates the message, parses it against the matching ADT\^A03 parser configuration into `parsed_data`, stages a message log record with status Pending, and returns ACK(AA). A Flow Designer flow in the room turnover application triggers on the new record and reads the PV1 location values (unit, room, bed) from `parsed_data`. It then marks the room as Needs Cleaning, creates and assigns an EVS task, and notifies the charge nurse --- all without manual intervention. The room turnover flow lives in a downstream Healthcare Operations application, not in the HL7 integration application. ## What ServiceNow does not do ServiceNow does not listen for HL7 messages over MLLP or TCP/IP. Your existing integration engine handles transport and delivers messages to ServiceNow over HTTPS. ServiceNow does not write back to the EHR --- the integration is inbound only.