--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ay bundleId : - delta3ay --- # Combined HL7 v2.x Integration release notes for upgrades from Yokohama to Australia # Combined HL7 v2.x Integration release notes for upgrades from Yokohama to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Combined HL7 v2.x Integration release notes for upgrades from Yokohama to Australia This document consolidates the HL7 v2.x Integration release notes from Yokohama through to the Australia release, helping ServiceNow customers prepare for their upgrade by summarizing new features, changes, removals, and activation information relevant to HL7 v2.x Integration. Show full answer Show less ## Key Features in Australia Release * **HL7 v2.x Inbound REST API:** This new API enables receiving inbound HL7 v2.x ADT messages directly from EHR systems over HTTP. It follows the HAPI HL7-over-HTTP convention, accepting raw pipe-delimited ER7 message bodies and returning standard HL7 v2.x acknowledgment (ACK) responses without requiring custom scripting on the integration engine side. * **HL7 Message Log:** Every inbound HL7 v2.x message is logged with details including the raw payload, ACK response, metadata (such as message type, trigger event, sending application/facility, and control ID), and processing status. These metadata fields are queryable and usable as trigger conditions within ServiceNow Flow Designer, facilitating automation. * **Parser Configurations:** Incoming messages are parsed according to configurable parser profiles that specify which segments and fields to extract, writing the parsed data into structured JSON within the message log. This no-code parser enables workflow automation without requiring HL7 v2.x technical expertise. * **Demo Parser Configurations:** Demo parsers are provided for common ADT message types (A01 - Admit, A02 - Transfer, A03 - Discharge, A08 - Update), covering key segments like EVN, PID, and PV1. These are editable and clonable to allow hospital-specific customization. ## Upgrade and Activation * There are no reported changes, removals, or deprecations from Yokohama through Australia releases affecting HL7 v2.x Integration features. * HL7 v2.x Integration is delivered as a separate application via the ServiceNow Store. To activate it, customers must request and install this application on their instance. * There are no additional requirements, browser restrictions, accessibility, or localization updates noted for this upgrade path. ## Practical Benefits for ServiceNow Customers * Receive and process HL7 v2.x ADT messages directly within ServiceNow without the need for external integration engines or custom scripting. * Automate hospital workflows by leveraging the structured JSON output from parsed HL7 messages and trigger conditions based on comprehensive message metadata. * Quickly get started with prebuilt demo parsers for common ADT workflows, then customize them to meet specific hospital needs. Consolidated page of all release notes for HL7 v2.x Integration from Yokohama to Australia. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family HL7 v2.x Integration release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Australia. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading HL7 v2.x Integration to Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-hl7v2xintegration-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## New features Between your current release family and Australia, new features were introduced for HL7 v2.x Integration. {#dfrn3-hl7v2xintegration-summary__entry__10} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | [HL7 v2.x Inbound REST API](https://www.servicenow.com/docs/access?context=hl7-inbound-api&family=australia&ft:locale=en-US) : The HL7 v2.x Inbound REST API receives inbound HL7 v2.x ADT messages from EHR systems over HTTP and returns standard HL7 v2.x acknowledgment responses. It implements the HAPI HL7-over-HTTP convention, accepting raw pipe-delimited ER7 message bodies and processing them against configured parser profiles. [HL7 message log](https://www.servicenow.com/docs/access?context=hl7-message-log-about&family=australia&ft:locale=en-US) : Every inbound HL7 v2.x message is stored with its raw payload, ACK response, message metadata (type, trigger event, sending application and facility, message control ID), and processing status. Metadata fields are queryable and available as Flow Designer trigger conditions. [Parser configurations](https://www.servicenow.com/docs/access?context=hl7-parser-configs-about&family=australia&ft:locale=en-US) : When a message is received, ServiceNow parses it with the matching parser configuration and writes the extracted values to the message log record's structured JSON (`parsed_data`). Parser configurations define which segments and fields to extract and the output path for each value. Demo parser configurations : Demo parser configurations for ADT A01, A02, A03, and A08 are available when you load demo data, covering the EVN, PID, and PV1 segments. They are editable, and you can clone them for hospital-specific customization. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing HL7 v2.x Integration features. {#dfrn3-hl7v2xintegration-summary__entry__18} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Removed Between your current release family and Australia, some HL7 v2.x Integration features or functionality were removed. {#dfrn3-hl7v2xintegration-summary__entry__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some HL7 v2.x Integration features or functionality were deprecated. {#dfrn3-hl7v2xintegration-summary__entry__34} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate HL7 v2.x Integration. {#dfrn3-hl7v2xintegration-summary__entry__42} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | HL7 v2.x Integration is distributed as a separate application through the ServiceNow Store. Request the application from the ServiceNow Store and install it to activate it on your instance. | [ ] ## Additional requirements If any additional requirements were introduced or changed for HL7 v2.x Integration we have noted them here. {#dfrn3-hl7v2xintegration-summary__entry__50} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for HL7 v2.x Integration we have noted them here. {#dfrn3-hl7v2xintegration-summary__entry__58} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for HL7 v2.x Integration, such as specific requirements or compliance levels. {#dfrn3-hl7v2xintegration-summary__entry__66} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for HL7 v2.x Integration we have noted them here. {#dfrn3-hl7v2xintegration-summary__entry__74} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for HL7 v2.x Integration we have noted them here. {#dfrn3-hl7v2xintegration-summary__entry__82} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | * Works alongside the HL7 v2.x Inbound REST API to receive HL7 v2.x messages from EHR systems over HTTP and return standards-compliant acknowledgment responses. * Receive raw HL7 v2.x messages directly in ServiceNow and automatically return standards-compliant ACK responses --- with no custom scripting on the integration engine side. * Parse raw HL7 v2.x messages into structured JSON on the message log using a configurable, no-code parser, enabling hospital workflow automation without HL7 v2.x expertise. * Demo parser configurations for ADT A01 (Admit), A02 (Transfer), A03 (Discharge), and A08 (Update) provide ready-to-edit starting points for the most common hospital ADT workflows. | [ ]