Create custom EDI definition in Altova MapForce
To make Altova MapForce accept your file, create a new EDI collection with a modified file 837l.config.
- Copy the folder HIPAA.X12.5010A2 to HIPAA.XYZ.
- Remove the read-only attribute for the HIPAA.XYZ folder.
-
Delete unnecessary files from the
HIPAA.XYZ folder. Keep only the following files:
-
ParserErrors.Config
-
X12.Codelist
-
EDI.Collection
-
X12.Segment
-
837I.Config
-
Envelope.Config
-
-
Edit the EDI.Collection file in a text editor and delete all Message nodes except for the node with
File="837I.Config".
<?xml version="1.0" encoding="utf-8"?> <Messages Version="3"> <Meta> <Release>5010</Release> <Agency>X12</Agency> </Meta> <Root File="Envelope.Config" /> <Message Type="837-Q3" File="837I.Config" Description="Health Care Claim: Institutional" /> </Messages>
-
Edit the file 837I.Config in a text editor and make the F1315 field optional (add
minOccurs="0").
<Data ref="F1315" minOccurs="0" info="Admission Type Code" />
-
Copy the
HIPAA.XYZ folder to the
MapForceEDI directory. You should have administrator rights to perform this, because the destination
folder is write-protected.
Now, when you browse EDI collections in Altova MapForce, you can find the newly defined collection HIPAA.XYZ with a single message type "837-Q3 Health Care Claim: Institutional". This modified EDI collection can be used to build the EDI type (schema and mapping files) for KC Plug-In.