The X12 library determines which transaction library to load based on either the functional group or transaction set header (GS or ST segments). The current lookup process requires a "strict" match on this version identifier.
For example the snippet below will load the transaction model located within linuxforhealth.x12.v5010.x12_837_005010X222A2
837*0001*005010X222A2
This approach doesn't support the X12 specification's notion of a consolidated guide. For instance the 5010 837 Professional Claim Specification supports the following revisions:
May 2006 005010X222
June 2010 005010X222A1
June 2014 005010X222A2.
We need to update the lookup process to map each supported revision identifier to the recent release.
The X12 library determines which transaction library to load based on either the functional group or transaction set header (GS or ST segments). The current lookup process requires a "strict" match on this version identifier.
For example the snippet below will load the transaction model located within
linuxforhealth.x12.v5010.x12_837_005010X222A2This approach doesn't support the X12 specification's notion of a consolidated guide. For instance the 5010 837 Professional Claim Specification supports the following revisions:
We need to update the lookup process to map each supported revision identifier to the recent release.