--- 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 October 8, 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 note provides ServiceNow customers with essential information about upgrading the HL7 v2.x Integration from the Zurich release to the Australia release. It highlights new features, changes, and activation details to help you prepare and execute the upgrade effectively. Show full answer Show less ## Key Features * **HL7 v2.x Inbound REST API:** Introduced in Australia, this API allows inbound HL7 v2.x ADT messages from Electronic Health Record (EHR) systems to be received over HTTP. It supports the HAPI HL7-over-HTTP convention, processing raw pipe-delimited ER7 message bodies and returning standard HL7 acknowledgment (ACK) responses automatically without custom scripting on the integration engine side. * **HL7 Message Log:** Each inbound HL7 message is logged with its raw payload, ACK response, message metadata (including type, trigger event, sending application and facility, message control ID), and processing status. These metadata fields are queryable and can be used as trigger conditions in Flow Designer, enabling automation. * **Parser Configurations:** Messages are parsed using configurable parser profiles that define which HL7 segments and fields to extract and where to output the values in structured JSON format. This no-code parsing empowers hospitals to automate workflows without needing deep HL7 expertise. * **Demo Parser Configurations:** Ready-to-use demo parsers are available for common ADT message types (A01 Admit, A02 Transfer, A03 Discharge, A08 Update), covering key segments such as EVN, PID, and PV1. These can be edited or cloned for hospital-specific customization, accelerating implementation. ## Activation and Installation HL7 v2.x Integration in Australia is provided as a separate application available through the ServiceNow Store. To activate it, customers must request and install this application on their ServiceNow instance. ## Upgrade and Changes There are no removals, deprecations, or changes from Zurich to Australia releases for HL7 v2.x Integration. If no updates exist for a particular release family, this is clearly indicated to avoid confusion. ## Additional Notes * No new browser, accessibility, or localization requirements were introduced in the Australia release. * The integration works seamlessly alongside the HL7 v2.x Inbound REST API to handle message receipt and acknowledgment, simplifying hospital integration workflows. ## Practical Benefits for ServiceNow Customers * Receive raw HL7 v2.x messages directly into ServiceNow with automatic acknowledgment, reducing integration complexity. * Utilize no-code, configurable parsers to convert HL7 messages into structured JSON for workflow automation. * Leverage demo configurations to quickly start common hospital ADT scenarios and customize them as needed. * Simplify upgrade planning with clear pre- and post-upgrade task guidance and consolidated release information. 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. | [ ]