EDI Translate now supports writing multiple transaction sets within a single interchange
EDI Translate now supports writing multiple transaction sets within a single interchange
EDI Translate now supports writing multiple transaction sets within a single interchange
EDI Translate now supports writing multiple transaction sets within a single interchange
Nov 18, 2022
Nov 18, 2022
Nov 18, 2022
Nov 18, 2022
Every EDI message contains an interchange envelope, with one or more transaction sets nested inside the interchange. The transaction set contains the actual content of the message.
Previously, customers using EDI Translate to generate EDI from a JSON payload could only generate a single transaction set inside of an interchange. Now, customers who want to “batch” multiple transaction sets inside a single interchange can do so using the same API by passing an array of transaction sets in the JSON payload.
There is no additional charge for generating EDI with multiple transaction sets, you only pay for the request and the data processed (see pricing).
Every EDI message contains an interchange envelope, with one or more transaction sets nested inside the interchange. The transaction set contains the actual content of the message.
Previously, customers using EDI Translate to generate EDI from a JSON payload could only generate a single transaction set inside of an interchange. Now, customers who want to “batch” multiple transaction sets inside a single interchange can do so using the same API by passing an array of transaction sets in the JSON payload.
There is no additional charge for generating EDI with multiple transaction sets, you only pay for the request and the data processed (see pricing).
Every EDI message contains an interchange envelope, with one or more transaction sets nested inside the interchange. The transaction set contains the actual content of the message.
Previously, customers using EDI Translate to generate EDI from a JSON payload could only generate a single transaction set inside of an interchange. Now, customers who want to “batch” multiple transaction sets inside a single interchange can do so using the same API by passing an array of transaction sets in the JSON payload.
There is no additional charge for generating EDI with multiple transaction sets, you only pay for the request and the data processed (see pricing).
Every EDI message contains an interchange envelope, with one or more transaction sets nested inside the interchange. The transaction set contains the actual content of the message.
Previously, customers using EDI Translate to generate EDI from a JSON payload could only generate a single transaction set inside of an interchange. Now, customers who want to “batch” multiple transaction sets inside a single interchange can do so using the same API by passing an array of transaction sets in the JSON payload.
There is no additional charge for generating EDI with multiple transaction sets, you only pay for the request and the data processed (see pricing).
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.
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.
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.
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.