Hospital integration teams rely on HL7 v2.x messaging to keep ADT (admit, discharge, transfer) events flowing between EMRs, integration engines, and downstream systems — but connecting that traffic to ServiceNow has traditionally required custom scripting and message parsing built by hand.
HL7 v2.x Integration gives ServiceNow a standards-compliant REST endpoint that accepts raw ER7 HL7 v2.x messages directly from your integration engine (such as Mirth), returning standard ACK/NACK responses so your existing retry and monitoring logic keeps working without changes. Every message is logged with queryable metadata extracted from the MSH segment, and a built-in parser engine converts raw messages into structured data pills usable in any Flow Designer flow — no scripting required.
Out-of-the-box parser configs cover the most common ADT events — Admit (A01), Transfer (A02), Discharge (A03), and Update (A08) — so operational workflows like room turnover, bed status updates, and care team notifications can be triggered directly from EMR events. Administrators can clone and customize any OOB config for their EMR's specific HL7 variations while ServiceNow maintains an upgradable baseline, and the entire setup and monitoring experience is no-code, built for administrators who think in HL7 terms.
- Standards-compliant REST endpoint for raw ER7 HL7 v2.x message receipt, with standard ACK/NACK responses
- Message log with queryable MSH metadata to trigger Flow Designer flows
- No-code HL7 parser engine and Flow Designer action for structured data pills
- OOB parser configs for Admit, Transfer, Discharge, and Update (ADT A01/A02/A03/A08) events
- Clonable, customizable parser configs for EMR-specific HL7 variations
New Features
- HL7 v2.x REST Endpoint: Standards-compliant HTTPS endpoint that accepts raw ER7-formatted HL7 v2.x messages, so integration engines can send HL7 messages to ServiceNow with no custom scripting.
- Standard ACK/NACK Responses: Every received message gets a standards-compliant HL7 ACK message in the response, so existing integration-engine error handling, retry logic, and monitoring work without modification.
- Message Log with Queryable Metadata: Every received message is stored in a dedicated log table with metadata extracted from the MSH segment, enabling Flow Designer triggers on message type, event, and sending facility.
- HL7 v2.x Parser Engine: Message-type-agnostic parser that converts raw ER7 messages into structured JSON.
- Parser as a Flow Designer Action: Exposed as a no-code Flow Designer action, producing data pills for use in any flow.
- Out-of-the-Box ADT Parser Configs: Ready-to-use parser configs for Admit (A01), Transfer (A02), Discharge (A03), and Update (A08) events.
- Customer-Clonable Parser Configs: Clone OOB parser configs and customize field mappings for your EMR's specific HL7 variations without affecting the upgradable baseline.
- No-Code Setup and Monitoring: Configure parser configs and monitor message flow entirely through the UI, without writing code.
The HL7 v2.x Integration application is an independent application scope with no dependency on Healthcare and Life Sciences Service Management Core for core HL7 receipt/parsing functionality.
- Requires Flow Designer (included with the Now Platform) to consume parsed HL7 data in flows
- Requires an integration engine or EMR capable of sending HL7 v2.x messages over HTTPS (e.g., Mirth Connect)
Role required to install the application: Administrator (admin)