EDI Inspector & Reference
Jan 31, 2022
EDI Inspector: ability to download EDI file and improved data rendering
You can now save an EDI file from the Inspector editor.
We also improved data rendering format making the EDI file more human-readable:
Dates previously displayed as 20210901 now are shown as Sep 1, 2021.
Prior to the change, X12 elements that had a paired relational constraint were displayed as two separate entries. Example:
Communication Number Qualifier: Internet Email Address <> EA Communication Number: team@stedi.com
We now combine these into a single entry, with the qualifier as the label. You can click on either of these values to see the relevant reference information.
Internet Email Address <> EA : team@stedi.com
EDI Reference: Human-readable conditions
The EDI Reference has been updated to display a human-readable interpretation of relation condition code (ex. P0304: If either PER-03 or PER-04 is present, then the other is required). Before the enhancement, only the relation condition code was provided, which was difficult to parse (ex. P0304).See example
EDI Inspector: ability to download EDI file and improved data rendering
You can now save an EDI file from the Inspector editor.
We also improved data rendering format making the EDI file more human-readable:
Dates previously displayed as 20210901 now are shown as Sep 1, 2021.
Prior to the change, X12 elements that had a paired relational constraint were displayed as two separate entries. Example:
Communication Number Qualifier: Internet Email Address <> EA Communication Number: team@stedi.com
We now combine these into a single entry, with the qualifier as the label. You can click on either of these values to see the relevant reference information.
Internet Email Address <> EA : team@stedi.com
EDI Reference: Human-readable conditions
The EDI Reference has been updated to display a human-readable interpretation of relation condition code (ex. P0304: If either PER-03 or PER-04 is present, then the other is required). Before the enhancement, only the relation condition code was provided, which was difficult to parse (ex. P0304).See example
Changelog
Changelog
View Stedi's full changelog.
Get started with Stedi
Get started with Stedi
Automate healthcare transactions with developer-friendly APIs that support thousands of payers. Contact us to learn more and speak to the team.
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.