JEDI 2.0 format is now available in production
Jan 6, 2022
Until now, the new JEDI 2.0 format was in "beta" as it stabilized. As of today, JEDI 2.0 is now ready for production use and comes with long-term support and commitment to no breaking changes.
You can read more about the JEDI@2.0 format here.
Below is an example of a JEDI 2.0 file.
{ "interchanges": [ { "interchange_control_header_ISA": { "authorization_information_qualifier_01": "no_authorization_information_present_no_meaningful_information_in_i02_00", "authorization_information_02": "", "security_information_qualifier_03": "no_security_information_present_no_meaningful_information_in_i04_00", "security_information_04": "", "interchange_id_qualifier_05": "mutually_defined_ZZ", "interchange_sender_id_06": "", "interchange_id_qualifier_07": "mutually_defined_ZZ", "interchange_receiver_id_08": "", "interchange_date_09": "210902", "interchange_time_10": "1200", "repetition_separator_11": "/", "interchange_control_version_number_code_12": "00801", "interchange_control_number_13": "123456789", "acknowledgment_requested_code_14": "interchange_acknowledgment_requested_ta1_1", "interchange_usage_indicator_code_15": "test_data_T", "component_element_separator_16": ":" }, "groups": [ { "functional_group_header_GS": { "functional_identifier_code_01": "ocean_shipment_information_304_311_317_319_322_323_324_325_326_361_SO", "application_senders_code_02": "00", "application_receivers_code_03": "00", "date_04": "20210902", "time_05": "1200", "group_control_number_06": "987654321", "responsible_agency_code_07": "accredited_standards_committee_x12_X", "version_release_industry_identifier_code_08": "008010" }, "transaction_sets": [ { "heading": { "transaction_set_header_ST": { "transaction_set_identifier_code_01": "326", "transaction_set_control_number_02": "0000" }, "transaction_set_trailer_SE": { "number_of_included_segments_01": "2", "transaction_set_control_number_02": "0000" } }, "type": "326" } ], "functional_group_trailer_GE": { "number_of_transaction_sets_included_01": "1", "group_control_number_02": "987654321" } } ], "interchange_control_trailer_IEA": { "number_of_included_functional_groups_01": "1", "interchange_control_number_02": "123456789" }, "delimiters": { "element": "*", "segment": "~", "sub_element": ":", "repetition": "/" } } ] }
Until now, the new JEDI 2.0 format was in "beta" as it stabilized. As of today, JEDI 2.0 is now ready for production use and comes with long-term support and commitment to no breaking changes.
You can read more about the JEDI@2.0 format here.
Below is an example of a JEDI 2.0 file.
{ "interchanges": [ { "interchange_control_header_ISA": { "authorization_information_qualifier_01": "no_authorization_information_present_no_meaningful_information_in_i02_00", "authorization_information_02": "", "security_information_qualifier_03": "no_security_information_present_no_meaningful_information_in_i04_00", "security_information_04": "", "interchange_id_qualifier_05": "mutually_defined_ZZ", "interchange_sender_id_06": "", "interchange_id_qualifier_07": "mutually_defined_ZZ", "interchange_receiver_id_08": "", "interchange_date_09": "210902", "interchange_time_10": "1200", "repetition_separator_11": "/", "interchange_control_version_number_code_12": "00801", "interchange_control_number_13": "123456789", "acknowledgment_requested_code_14": "interchange_acknowledgment_requested_ta1_1", "interchange_usage_indicator_code_15": "test_data_T", "component_element_separator_16": ":" }, "groups": [ { "functional_group_header_GS": { "functional_identifier_code_01": "ocean_shipment_information_304_311_317_319_322_323_324_325_326_361_SO", "application_senders_code_02": "00", "application_receivers_code_03": "00", "date_04": "20210902", "time_05": "1200", "group_control_number_06": "987654321", "responsible_agency_code_07": "accredited_standards_committee_x12_X", "version_release_industry_identifier_code_08": "008010" }, "transaction_sets": [ { "heading": { "transaction_set_header_ST": { "transaction_set_identifier_code_01": "326", "transaction_set_control_number_02": "0000" }, "transaction_set_trailer_SE": { "number_of_included_segments_01": "2", "transaction_set_control_number_02": "0000" } }, "type": "326" } ], "functional_group_trailer_GE": { "number_of_transaction_sets_included_01": "1", "group_control_number_02": "987654321" } } ], "interchange_control_trailer_IEA": { "number_of_included_functional_groups_01": "1", "interchange_control_number_02": "123456789" }, "delimiters": { "element": "*", "segment": "~", "sub_element": ":", "repetition": "/" } } ] }
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.