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 →

3M EDI Invoice Specification Guidelines 3M EDI Invoice notes provide separate comments of the data segments sent in 3M’s EDI invoices (ASC X12 transaction set 810). 3M can send many valid ACS X12 data segments and elements in 3M EDI Invoice; however, these guidelines refer to some of the most commonly sent. 3M EDI Invoice ASC X12 version is 004010. If you cannot receive invoices in version Read More →

837 Institutional Healthcare Claim Testing: Set-up, Directory and File Naming 837 Institutional Healthcare Claim Testing should be followed by requesting information on establishing connections through the SFTP server. Upon completion of 837 Institutional Healthcare Claim set-up, providers will receive additional instructions on SFTP usage. SFTP Directory Naming Convention There would be two categories of folders under Trading Read More →

837 Institutional Healthcare Claim Testing (Washington State Health Care Authority (HCA)) Procedure 837 Institutional Healthcare Claim Testing completion  must occur prior to submitting electronic transactions in production to Washington State Health Care Authority ProviderOne. 837 Institutional Healthcare Claim Testing is conducted to ensure the following levels of HIPAA compliance: Level 1 – Syntactical integrity: Testing of Read More →

 HIPAA Dental COB Claim Mapping Exercise Example HIPAA Dental COB Claim example and exercise represent how to generate HIPAA Dental COB Claim file for processing by the destination payer. HIPAA Dental COB Claim Scenario Patient PUFFY DOG is seen a dentist DONALD D, DUCK in the office INFINITE ENDODONTICS. The payer of the HIPAA Dental COB Claim is Read More →

837 Dental Transaction Mapping Exercise Example 837 Dental Transaction Mapping exercise gives a scenario of working with a 837 Dental Transaction file to complete the claim and send it to processing. 837 Dental Transaction Mapping exercise will be useful for insurance companies, providers and HIPAA specialists. Scenario: Patient MINI DUCK dependent son of DONALD DUCK goes to the Read More →