--- sourceDocument: brazil Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/delta-australia-brazil Release : - brazil ft:locale : - en-US ft:publication_title : - brazil Combined Product Files ft:clusterId : - delta3ba bundleId : - delta3ba --- # Combined HL7 v2.x Integration release notes for upgrades from Australia to Brazil # Combined HL7 v2.x Integration release notes for upgrades from Australia to Brazil {#ariaid-title1} Release version: Brazil 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 Australia to Brazil This consolidated guide assists ServiceNow customers in preparing for the HL7 v2.x Integration upgrade from the Australia to Brazil release versions. It combines all relevant release notes, highlighting new features, changes, activation steps, and important upgrade considerations to ensure a smooth transition. Show full answer Show less ## Key Features * **HL7 v2.x Inbound REST API:** Enables receiving HL7 v2.x ADT messages from Electronic Health Record (EHR) systems over HTTP, returning standard HL7 acknowledgment (ACK) responses without requiring custom scripting on the integration engine. * **HL7 Message Log:** Stores every inbound HL7 message with raw payload, ACK response, message metadata (such as type, trigger event, sending application, and message control ID), and processing status. Metadata fields are queryable and usable as Flow Designer trigger conditions. * **Parser Configurations:** Parses received HL7 messages into structured JSON in the message log. Configurations define which segments and fields to extract and their output paths, enabling no-code hospital workflow automation without HL7 expertise. * **Demo Parser Configurations:** Ready-to-edit demo parsers for common ADT message types (A01 Admit, A02 Transfer, A03 Discharge, A08 Update) covering EVN, PID, and PV1 segments, which can be cloned and customized for specific hospital needs. ## Upgrade and Activation Notes * No changes, removals, or deprecations were introduced between the Australia and Brazil releases for HL7 v2.x Integration. * HL7 v2.x Integration is a separate application available through the ServiceNow Store and must be installed to activate on your instance. * There are no additional requirements, browser compatibility changes, accessibility considerations, or localization updates noted for the Brazil release. ## What to Expect Upgrading to the Brazil release maintains existing HL7 v2.x Integration capabilities without disruption or feature removals. Customers gain access to the HL7 v2.x Inbound REST API and no-code parsing tools to easily automate hospital workflows using HL7 messages. The included demo configurations accelerate implementation for common ADT scenarios, enhancing integration efficiency and reducing the need for HL7 protocol expertise. Consolidated page of all release notes for HL7 v2.x Integration from Australia to Brazil. ## 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 Australia to Brazil. 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 Brazil Before you upgrade to Brazil, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-hl7v2xintegration-summary__entry__2} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## New features Between your current release family and Brazil, new features were introduced for HL7 v2.x Integration. {#dfrn3-hl7v2xintegration-summary__entry__8} | Release | Release notes | |-|-| | 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. | | Brazil | No updates for this release. | [ ] ## Changes Between your current release family and Brazil, some changes were made to existing HL7 v2.x Integration features. {#dfrn3-hl7v2xintegration-summary__entry__14} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Removed Between your current release family and Brazil, some HL7 v2.x Integration features or functionality were removed. {#dfrn3-hl7v2xintegration-summary__entry__20} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | No updates for this release. | [ ] ## Deprecations Between your current release family and Brazil, some HL7 v2.x Integration features or functionality were deprecated. {#dfrn3-hl7v2xintegration-summary__entry__26} | Release | Release notes | |-|-| | Australia | No updates for this release. | | Brazil | 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 | |-|-| | 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. | | Brazil | No updates for this release. | [ ] ## 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 | |-|-| | Australia | No updates for this release. | | Brazil | 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 | |-|-| | Australia | No updates for this release. | | Brazil | 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 | |-|-| | Australia | No updates for this release. | | Brazil | 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 | |-|-| | Australia | No updates for this release. | | Brazil | 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 | |-|-| | 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. | | Brazil | No updates for this release. | [ ]