Step-up and step-down maps
The step-up and step-down maps provide the basis for mapping simple correspondence in unchanged elements, the changes in positioning of information within the transaction, new or changed segments loops, and other differences, both in the implementation guide changes between the two versions, and the base X12 changes.
The step-up and step-down maps use the Type 2 schemas to map the included transactions from the HIPAA 5010 base to the new 80x0 TR3 format.
The step-up maps have an additional input that uses the IBM Integration Platform native JSON support to provide a way to extend the output 80x0 data with new fields supported in the new draft implementation guides.
Notes for using the step-up and step-down maps:
In addition to loop or segment-specific functional maps and map rules, the following notes apply
to the step-up and step-down maps:
- If an element or composite is not used in 80x0, it is mapped with an =NONE rule, with a comment indicating that it is not used in the 80x0 TR3.
- Loop names in 80x0 schemas and functional map names in the maps reflect an abbreviation of the name in the 80x0 TR3, so they might be different from the loop name in the 5010 schema.
- Where text elements have component rules in the 80x0 schemas to enforce a maximum length, the LEFT function is used in step-down mapping to 5010, if the Type 2 schema enforced the length through type item properties.
- As the schema item properties are set to allow pads, and pad to min content, optional items in the mapping are wrapped in a functional map to prevent spaces to be built on output.
- Data for elements that are present in 5010 data but are no longer used in 80x0 and do not correspond to a different element in 80x0, are discarded in the step-up mapping. Similarly, data for new elements defined for use in the 80x0 TR3 that were not present in the 5010 TR3 are discarded.
- Additional map rules and functional maps are implemented where needed for mapping between the two versions.