{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":19510,"path":"healthcare-life-sciences/hl7-parser-config-clone.md","title":"Clone and customize a parser configuration","bundle":null,"doc_type":null,"release":"australia","body":"\n# Clone and customize a parser configuration\n\nClone a demo parser configuration to create a customizable copy that you can modify for hospital-specific field variations and relabeling.\n\n## Before you begin\n\nRole required: `sn_hl7_v2.admin`\n\n## About this task\n\nThe 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.\n\n**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.\n\n## Procedure\n\n1.  Navigate to **All** > **HL7 Integration** > **Parser Configurations**.\n\n2.  Open the demo configuration you want to clone.\n\n3.  Click **Clone**.\n\n4.  In the **Name** field, enter a descriptive name for your configuration that identifies the sending facility or customization purpose.\n\n5.  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.\n\n    The combination of sending application, sending facility, HL7 version, message type, and trigger event must be unique across all active configurations.\n\n6.  Click **Save**.\n\n7.  To add, remove, or modify segment definitions, open the **Segments** related list and make changes as needed.\n\n8.  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.\n\n    **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.\n\n9.  Set the configuration to **Active** and click **Save**.\n\n\n## Result\n\nYour 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.\n\n**Related topics**  \n\n\n[Parser config fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/healthcare-life-sciences/hl7-parser-config-fields.md)\n\n[Test a parser configuration with a sample payload](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/healthcare-life-sciences/hl7-parse-sample-payload.md)\n\n"}}