My organization has been tasked with parsing raw EDI 271 messages into JSON strings in order to feed a downstream application. A few key details about the task:
- The raw EDI 271 will be coming across as a standard format from a single outbound upstream system
- The EDI 271 messages adhere to the 5010 standard
- We do not need EVERY field from the EDI message, only a select number of fields. However some of the fields we need (e.g. coverage details) are dynamic in size and will be variable in # of segments both on the EDI side as well as the receiving JSON side.
- We will be looking to build one incoming business operation for the stream of 271 messages which will then be parsed into Medicare and non-Medicare
- The JSON output has a static format per class of payor (sample can be referenced below for both Medicare and non-Medicare payors):
Medicare Example JSON:
Non-Medicare Example JSON:
Our ask to the community: has anyone tackled a similar situation like this before? If so, can you provide some guidance on how you went about working through this challenge?
Please let me know if any further information would be helpful.