--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined HL7 v2.x Integration release notes for upgrades from Zurich to Australia # Combined HL7 v2.x Integration release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Zurich to Australia This consolidated release notes document provides ServiceNow customers with essential information about upgrading the HL7 v2.x Integration application from the Zurich release to the Australia release. It summarizes new features, changes, activation procedures, and other relevant details to support a smooth upgrade process. Show full answer Show less ## Key Features * **HL7 v2.x Inbound REST API:** Introduced in the Australia release, this API enables receiving HL7 v2.x ADT messages directly from Electronic Health Record (EHR) systems over HTTP. It follows the HAPI HL7-over-HTTP convention and processes raw pipe-delimited ER7 message bodies, returning standard HL7 acknowledgment (ACK) responses automatically without requiring custom integration engine scripting. * **HL7 Message Log:** Every inbound message is logged with its raw payload, ACK response, metadata (including message type, trigger event, sending application, facility, message control ID), and processing status. Metadata fields are queryable and available as triggers in Flow Designer, facilitating workflow automation. * **Parser Configurations:** The system parses incoming messages using configurable parser profiles that specify which segments and fields to extract and where to map them in the structured JSON output. This no-code parsing approach simplifies integration and automation within hospital workflows without needing HL7 expertise. * **Demo Parser Configurations:** Demo configurations are available for common ADT message types (A01 - Admit, A02 - Transfer, A03 - Discharge, A08 - Update), covering key segments (EVN, PID, PV1). These demos can be loaded with sample data and customized or cloned to meet hospital-specific needs. ## Upgrade and Activation Guidance * The Australia release introduces no removals, deprecations, or other changes to existing HL7 v2.x Integration features compared to Zurich. * HL7 v2.x Integration is now distributed as a separate application via the ServiceNow Store. Customers must request and install it from the Store to activate it on their instance. * Pre- and post-upgrade tasks should be reviewed and completed as appropriate to ensure a successful upgrade. * There are no new additional requirements, browser requirements, accessibility considerations, or localization changes introduced in the Australia release. ## Benefits for ServiceNow Customers * Directly receive and acknowledge HL7 v2.x ADT messages over HTTP without custom scripting, reducing integration complexity. * Gain transparency and control through detailed message logging and metadata availability for automated workflows. * Leverage configurable, no-code parsers to transform raw HL7 messages into structured data, facilitating downstream processing and hospital automation. * Accelerate implementation using pre-built demo parser configurations tailored for common hospital admission, transfer, discharge, and update workflows. Consolidated page of all release notes for HL7 v2.x Integration from Zurich 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 Zurich 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 | |-|-| | 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__8} | Release | Release notes | |-|-| | 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__14} | Release | Release notes | |-|-| | 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__20} | Release | Release notes | |-|-| | 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__26} | Release | Release notes | |-|-| | 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__32} | Release | Release notes | |-|-| | 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__38} | Release | Release notes | |-|-| | 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__44} | Release | Release notes | |-|-| | 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__50} | Release | Release notes | |-|-| | 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__56} | Release | Release notes | |-|-| | 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__62} | Release | Release notes | |-|-| | 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. | [ ]