---
sourceDocument: Brazil Healthcare and Life Sciences
sourceDocumentLink: https://www.servicenow.com/docs/r/healthcare-life-sciences

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Healthcare and Life Sciences

ft:clusterId :

    - hcls

bundleId :

    - hcls

workflow :

    - Customer and Industry


---

# Components installed with HL7 v2.x Integration

# Components installed with HL7 v2.x Integration {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Several types of components are installed with activation of the
HL7 v2.x Native Integration plugin, including tables, user roles, and
Flow Designer actions.

## Roles installed {#hl7-installed-components__hl7-installed-roles}

{#hl7-installed-components__hl7-installed-roles__entry__3}

| Role title \[name\] | Description | Contains roles |
|-|-|-|
| HL7 Integration Administrator \[`sn_hl7_v2.admin`\] | Manages HL7 integration configuration, including parser configurations and message log access. Required for all administrative tasks in the HL7 integration application. | None |
[ ]

## Tables installed {#hl7-installed-components__hl7-installed-tables}

{#hl7-installed-components__hl7-installed-tables__entry__2}

| Table | Description |
|-|-|
| HL7 Message Log \[`sn_hl7_v2_message_log`\] | Stores every inbound HL7 v2.x message received by ServiceNow, including the raw payload, ACK response, extracted MSH metadata fields, and processing status. The `raw_payload` field is protected by a column-level ACL. |
| HL7 Parser Configuration \[`sn_hl7_v2_parser_config`\] | Defines parser configurations that map HL7 message types and sending system identities to segment and field extraction rules. Extends `sys_metadata`. |
| HL7 Parser Segment \[`sn_hl7_v2_parser_segment`\] | Defines individual HL7 segments (for example, PV1, PID) within a parser configuration, including the segment code and human-readable label. Extends `sys_metadata`. |
| HL7 Parser Field Map \[`sn_hl7_v2_parser_field_map`\] | Maps an HL7 field position within a parser segment to a dotted output path (`field_name`) in the message log's `parsed_data`, with an optional human-readable label. Supports field and component extraction. Extends `sys_metadata`. |
[ ]

## UI actions installed {#hl7-installed-components__hl7-installed-ui-actions}

The application installs two UI actions on the parser configuration form.
Parse Sample Payload parses the configuration's sample
payload and populates the parsed value on each field map.
Clone deep-copies a configuration and its segments and
field maps to a new, inactive configuration.

## Demo parser configurations installed {#hl7-installed-components__hl7-installed-oob-configs}

The following parser configurations are installed only when you select
Load demo data during installation. They are editable
examples, not read-only records.
{#hl7-installed-components__hl7-installed-oob-configs__entry__2}

| Configuration | Description |
|-|-|
| HL7 v2.8 ADT\^A01 --- Admit | Demo parser configuration for ADT\^A01 (patient admit) messages. Covers the EVN, PID, and PV1 segments. |
| HL7 v2.8 ADT\^A02 --- Transfer | Demo parser configuration for ADT\^A02 (patient transfer) messages. Covers the EVN, PID, and PV1 segments. |
| HL7 v2.8 ADT\^A03 --- Discharge | Demo parser configuration for ADT\^A03 (patient discharge) messages. Covers the EVN, PID, and PV1 segments. |
| HL7 v2.8 ADT\^A08 --- Update | Demo parser configuration for ADT\^A08 (patient information update) messages. Covers the EVN, PID, and PV1 segments. |
[ ]