---
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


---

# Clone and customize a parser configuration

# Clone and customize a parser configuration {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Clone a demo parser configuration to create a customizable copy that you
can modify for hospital-specific field variations and relabeling.

## Before you begin

Role required: `sn_hl7_v2.admin`

## About this task

The demo parser configurations are editable records. Edit one in place, or
clone it to keep the original intact. Modify the copy to add hospital-specific
field labels, include additional fields, or adjust field positions. Cloning also
creates a quick variant for a different sending facility.  
Important:  
Programmatic field keys in your clone remain stable even if you change field labels. Existing scripts and flows that reference field keys by name continue to work after relabeling.

## Procedure

1. Navigate to AllHL7 IntegrationParser Configurations.
2. Open the demo configuration you want to clone.
3. Click Clone.
4. In the Name field, enter a descriptive name for your configuration that identifies the sending facility or customization purpose.
5. Update the Sending application and Sending facility fields to match the values in MSH-3 and MSH-4 of the messages sent by your integration engine.  
   The combination of sending application, sending facility, HL7 version,
   message type, and trigger event must be unique across all active
   configurations.
6. Click Save.
7. To add, remove, or modify segment definitions, open the Segments related list and make changes as needed.
8. To modify field labels or required and optional designations, open a segment record and update the field map entries in its Field Maps related list.  
   Note:  
   Changing a field label does not change the field's programmatic key. Flows and scripts that reference the key continue to work without modification.
9. Set the configuration to Active and click Save.

## Result

Your custom parser configuration is active. When ServiceNow receives a
matching message, it uses your configuration to extract fields into the
message log's parsed data. A matching message shares the same sending
application, sending facility, HL7 version, message type, and trigger event.
**Related tasks**   

* [Test a parser configuration with a sample payload](https://www.servicenow.com/docs/Iu1yOADZLEJJ4PI0RFfUaA "Run a parser configuration against a sample HL7 v2.x message to confirm that it extracts the segments and fields you expect before you use it in a workflow. The parsed values appear on the configuration's field maps.")  
**Related reference**   

* [Parser config fields](https://www.servicenow.com/docs/hoJHEDVy4Ng~FTen1qvvkQ "Field reference for the parser configuration, parser segment, and field map tables that define how the HL7 parser engine extracts message data.")

*[\>]: and then