Data bundles of arbitrary size
PATHCOPY is closely related to the hierarchical data formats such as HL7, UN/EDIFACT, NCPDP, and X12. PATHCOPY also adds the ability to move and relocate fields for FRL and VRL message formats.
PATHCOPY can replicate a datum into fields and subfields for HRL, FRL, and VRL messages.
Points to remember
- With PATHCOPY, you can use
partial- or full-path specifiers as parameters. These parameters designate how
data is moved between IN, input record messages, and OUT, output record
messages.
- Full-path specifiers to a field can be used for both input records and output records. The result is the same as having used a standard COPY operation to perform the move of the field or component.
- A full-path specifier that goes to a single atomic datum, or the specification of a constant such as null, can be used in the input record. That datum or constant is replicated into each location for data elements. This is indicated by the output record path designator.
- If partial-path specifiers are used for both input records and output records, then they must designate similar data entities. For example, PID segment to PID segment.
- Partial path for HL7, UN/EDIFACT, NCPDP, and X12 is any path that goes to at least a group. For example, 0, 0(1), 0(0).PID, 0(0).PID(1). Use BULKCOPY for full message to full message copy for all messages. PATHCOPY of a group to a group can be equivalently used in some instances.
- Partial path for FRL and VRL is a path to a field.
- Full path for HL7, UN/EDIFACT, NCPDP, and X12 is any path that goes to at least a field.
- Full path to atomic datum is any path that resolves to an individual data
element.
- In HL7, UN/EDIFACT, NCPDP, and X12, this is a path to a single subcomponent.
- In VRL, this is usually a path to a single sub-subcomponent.
- In FRL, this is usually a path to a single subcomponent.
- With PATHCOPY, you can relocate a data entity. For example, you can move a segment from one position of an input record to another position for an entity within the output record hierarchy. For example, a segment may be moved between nested groups in HL7.
- PATHCOPY follows the established behaviors of BULKCOPY and COPY for moving data between HL7, UN/EDIFACT, NCPDP, and X12 message variants.
- Multiple path designators can be entered into Source and Destination of the GUI. They can also be entered into the IN, input record, and OUT, output record, keyed lists of the PATHCOPY scripted configuration file. The sense of these multiple entries is that of pairing, where the first Source argument applies to the first Destination argument. Extraneous, unpaired entries are ignored.
- PATHCOPY can be used within and in conjunction with ITERATE translation blocks. The designation of entities to be iterated within a PATHCOPY path parameter is the same as that used for other actions such as COPY.
- PATHCOPY can be used for automatic, implied iteration copies. To perform automatic iteration, leave an explicit repetition designator off of the end of the input record or output record partial path.
- PATHCOPY can be used within and in conjunction with IF-ELSE translation blocks.
- PATHCOPY can be used to move data between related formats, such as FRL/VRL or HL7/X12. Movement of more than atomic data elements between unlike formats, such as FRL/HL7, is undefined.