Exercise 7.1 - Mapping From EDI - Online Resource Center

Purpose:

To practice transforming EDI X12 files to an XML Format.

Create a Route

1. From the eiConsole File Management screen, select the Add Route button.
2. In the dialog that appears, enter the name EDI to People XML and select OK.
3. The Route should now appear in the table on the screen. Double-click it to open it.

Document Source System

1. Select the Source System stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Change the System Name to EDI File.
3. Select the Choose Source Icon button, and scroll down to select one of the EDI icons.

Configure the Listener

1. Select the Listener stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Select Directory/File from the Listener Type selection box. Optionally, click the … button to open the Module Search Dialog, which provides a faster way to find the module you’re looking for.
3. Assign a polling directory, using the … button to open the file selector. The polling directory should NOT be the directory with all the sample files, since files will be moved/deleted by the Listening process.

Add Source Format for EDI Transformation

1. Select the Source Transform stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Click the Add Format button. In the dialog that appears, name the format EDI to People, and click OK. The transformation configuration panel will appear below.
3. On the left-hand side, in the Transformation Module Configuration panel, select the EDI transformer. Its configuration panel will appear below.
4. Check the box, Use X12 Table Data for Enhanced Functionally.
5. Add the 837-Q1 directory.
6. Set the Version to 5010.On the Enhancements tab, under Friendly Naming, select Add to element name from the drop-down.
7. On the right-hand side, in the XSLT To XML configuration panel, uncheck the Use Direct Relay button. The options in that panel will now be enabled.
8. Click the New button beneath the checkbox to open the Data Mapper.

Load Source and Target Formats

1. Use the Open Source Format button above the Source Format panel to open the Select Format dialog. Choose XML from the Format Reader selection box.
2. In the select format dialog, browse and select 837_5010.xml, then click Read Format.
3. Click on the icon to expand it so you can see the sub-elements.
4. Use the Open Target Format button above the Target Format panel to open the Select Format dialog. Choose XML from the Format Reader selection box again.
5. Remove the existing sample file and add People.xml, then click Read Format.
6. Check the box Show Friendly Names in all Mapper Trees Where Available.
7. The Source and Target format panels should now be populated.

Map the Root Nodes and Add Iteration

1. Select the XCSData Node that is the root of the tree in the Source panel to the left. Drag it onto the center panel and drop it on the stylesheet node that’s already there.
2. Select the People node that is the root of the tree in the Target panel to the right. Drag it onto the center panel and drop it on the XCSData node that was just dropped there.
3. Above the center mapping panel is the Extensions panel. The currently displayed tab, Filter by Pattern, has a text field called Pattern. Type for-each into that field.
4. A single item should be present in the panel. This item should also be called for-each. Select and drag it onto the People node in the center mapping panel.
5. In the Source tree, expand the node called Interchange/Group/Transaction/Loop_2000B_SubscriberHierarchicalLevel/Loop_2010BA_SubscriberName. This element represents a loop with a named entity, which can be used to identify a subscriber(patient) according to the NM1_SubscriberName field.
6. Drag the found Interchange/Group/Transaction/Loop_2000B_SubscriberHierarchicalLevel/Loop_2010BA_SubscriberName element onto the @select node beneath the for-each node in the center mapping panel.
7. Next, we’ll need to modify this mapping to conditionally select Interchange/Group/Transaction/Loop_2000B_SubscriberHierarchicalLevel/Loop_2010BA_SubscriberName elements with a child NM1_SubscriberName/NM101_EntityIdentifierCode having a value of IL subscriber (patient).
8. Double-click on the @select element you mapped the for each onto; this will enable you to edit the XPath expression.
9. You should have: Interchange/Group/Transaction/Loop_2000B_SubscriberHierarchicalLevel/Loop_2010BA_SubscriberName.
10. We’ll modify this by adding this to the end of the expression: [NM1_SubscriberName/NM101_EntityIdentifierCode = ‘IL’] the line should look like this Interchange/Group/Transaction/Loop_2000B/Loop_2010BA [NM1_SubscriberName/NM101_EntityIdentifierCode = ‘IL’] when completed.
11. This is a predicate; it’s effectively saying, “find the Interchange/Group/Transaction/Loop_2000B/Loop_2010BA with a child element, NM1_SubscriberName/NM101_EntityIdentifierCode, with a value of ′IL′ “.
12. In the Target tree, select the Person node that is a child of the People node and drag it onto the for-each node in the center mapping panel.

Finish the Mapping

1. Select all of the nodes that are children of the Person node in the Target format panel and drag them onto the center panel dropping them onto the Person node.
2. Click the + button next to the Name and Address Nodes in the Target format panel to expand them to show their child nodes and drag them onto the center mapping panel as well.
3. Now that the whole Target format has been configured in the center panel, it’s time to map the Source format to it. Map the nodes in the following way (all source nodes are children of the Interchange/Group/Transaction/Loop_2000B_SubscriberHierarchicalLevel/Loop_2010BA_SubscriberName Source node):
  1. Source: NM1_SubscriberName/NM104_SubscriberFirstName -> Target: Name/First
  2. Source: NM1_SubscriberName/NM103_SubscriberLastName -> Target: Name/Last
  3. Source: NM1_SubscriberName/NM109_SubscriberPrimaryIdentifier -> Target: SSN
  4. Source: DMG_SubscriberDemographicInformation/DMG03_SubscriberGenderCode -> Target: Gender
  5. Source: DMG_SubscriberDemographicInformation/DMG02_SubscriberBirthDate -> Target: BirthDate
  6. Source: N3_SubscriberAddress/N301_SubscriberAddressLine -> Target: Address/Line1
  7. Source: N3_SubscriberAddress/N302_SubscriberAddressLine -> Target: Address/Line2
  8. Source: N4_SubscriberCityStateZIPCode/N401_SubscriberCityName -> Target: City
  9. Source: N4_SubscriberCityStateZIPCode/N402_SubscriberStateCode -> Target: Address/State
  10. Source: N4_SubscriberCityStateZIPCode/N403_SubscriberPostalZoneOrZIPCode -> Target: Address/Zip
4. Now that the mapping is complete click the Save icon in the toolbar above the tree. When prompted for a name, use the default, transform.
5. Click the X button in the top right corner to close the Data Mapper and return to the Route Editing Grid.

Configure the Transport

1. Select the Transport stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Select Directory/File from the Transport Type selection box. Optionally, click the … button to open the Module Search Dialog, which provides a faster way to find the module you’re looking for.
3. Select the Target Directory, using the … button to open the file selector.
4. Set edi-people-output as the Target File Name.
5. Set xml as the Target File Extension.

Document the Target System

1. Select the Target System stage in the Route Editing Grid. The configuration panel will appear at the bottom.
2. Change the System Name to People XML File.
3. Select the Choose Target Icon button and scroll down to select one of the XML icons.

Prepare to Test

1. In the menu bar at the top, select Mode -> Testing Mode. Make sure the changes to the Route are saved.
2. Copy the file named 837_5010.edi from the Samples directory provided into the directory chosen as the polling directory.

Perform the Test

1. At the top of the Testing Mode screen, select the Execute Test button.
2. If the Route was configured successfully, all the Stages should light up with green checkmarks.
3. In the OS File Explorer, open the directory selected as the Target Directory. The file edi-people-output.xml should be there, with the transformed contents produced by the XSLT.

Output Files

1. Compare the results from the exercise with the following example output files to see if they are correct.
  1. edi-people-output.xml

Structured Data

Exercise 7.1 – Mapping From EDI