EDI Payer Initiated Eligibility/Benefit Transaction (Washington State Medicaid) Additional Guides EDI Payer Initiated Eligibility/Benefit Transaction transmission must be secure in accordance with 45 CFR Parts 160, 162, and 164 Health Insurance Reform: Security Standards. Control segments/envelopes EDI Payer Initiated Eligibility/Benefit Transaction conforms to ASC X12 Control Segments / Envelopes (ISA-IEA, GS-GE, and ST-SE) for Version Read More →

PIE Transaction (Payer Initiated Eligibility/Benefit) Washington State Medicaid Testing Requirements PIE Transaction should be submitted by the trading partner through the Washington State Medicaid ProviderOne Secure File Transfer Protocol (SFTP). The trading partner downloads acknowledgements for the test file from the ProviderOne SFTP HIPAA ACK folder. If the ProviderOne system generates a positive TA1 and Read More →

PIE (PAYER INITIATED ELIGIBILITY/BENEFIT): Requirements of The Deficit Reduction Act Scope (Washington State Medicaid) PIE (Payer Initiated Eligibility/Benefit) transaction was developed to deliver membership and benefit information in one single, unsolicited transaction. The PIE (Payer Initiated Eligibility/Benefit) Transaction uses the same identifiers as the ASC X12 271 response transaction and therefore mirrors the format of the Read More →

Payer Initiated Eligibility/Benefit (PIE) Within The Requirements of The Deficit Reduction Act Scope (Washington State Medicaid) Payer Initiated Eligibility/Benefit (PIE) electronic transaction can be used by health plans to transmit eligibility and benefit information to Washington State Medicaid. basic guidelines given below are to assist State Medicaid agencies and payers in implementing the Payer Initiated Eligibility/Benefit (PIE) Transaction. Read More →

834 Benefit Enrollment and Maintenance HIPAA Basic Guides (Washington State Medicaid HCA) 834 Benefit Enrollment and Maintenance should be used by trading partners in conjunction with the ASC X12 TR3 834 Benefit Enrollment and Maintenance version 005010X220A1. When transmitting 834 Benefit Enrollment and Maintenance transactions, HCA follows standards developed by ASC X12. These standards involve Interchange (ISA/IEA) Read More →

Shipping Schedule Transaction Set (862) Basic Data Contents Shipping Schedule Transaction Set (862) can be used by supplier, and is intended to supplement the Planning Schedule Transaction Set (830). The Shipping Schedule Transaction Set will supersede certain shipping and delivery information transmitted in a previous Planning Schedule Transaction, but it does not replace the 830 transaction set. The Shipping Schedule Transaction Read More →

Volvo EDI Invoice Requirements For Automotive Products (AP) Suppliers Volvo EDI Invoice version for Automotive Products (AP) Suppliers is D03A version (Global standard) of the Edifact INVOIC message. ANSI X12 810 message is used by Volvo suppliers/partners in North America. Global Invoice is an initiative of the joint Automotive Industry and covers all types of EDI invoices Read More →

810 EDI Invoice Recommendations For 3M Suppliers 810 EDI Invoice recommendations provide basic description and some data segments technical lay-out comments for creating 3M 810 EDI Invoice (EDI ASC X12 transaction set 810). 3M can accept many valid ASC X12 data segments and elements in 810 EDI Invoice, however, we mention only those that are most commonly used. The ASC X12 version of Read More →

3M 820 Payment/Remittance Advice Specification Comments 3M 820 Payment/Remittance Advice comments given below provide recommendations for use when creating 3M 820 Payment/Remittance Advice (ASC X12 transaction set 820 for 3M). 3M can send many valid ACS X12 data segments and elements in 3M 820 Payment/Remittance Advice; however, these guidelines refer to some of the most commonly sent. 3M 820 Payment/Remittance Advice ASC X12 version is 004010. Read More →