EDI Reporting Rules (BWC – Commonwealth of Pennsylvania) BWC uses IAIABC Claims Release 3.0 standards for all EDI submissions. Data format must be in compliance with the standard data format described in the Systems Rules. Required BWC requires the electronic submission of injury reports as part of its EDI Implementation. For all data and information … Read More →
Commonwealth of Pennsylvania EDI Claims Implementation EDI Claims Release provides the electronic transfer of comprehensive injury data and gives significant benefits for Trading Partners and stakeholders. Data submitted through EDI transactions will be integrated with the Workers’ Compensation Automation and Integration System (WCAIS). The WCAIS system provides the Commonwealth of Pennsylvania with the technology to efficiently … Read More →
REQDOC EDIFACT Message (Request For Document) REQDOC EDIFACT Message is used to request the last successful CUSRES of an entry. The LRN and or MRN must be provided in the REQDOC. A CUSRES will be sent to verify if the request can be fulfilled or not followed by the CUSRES in question if available. Note … Read More →
Florida Health Care Plan X12 834 Transaction FHCP processes the ASC X12 834 transaction for Benefit Enrollment and Maintenance. These 834 brief mapping guidelines help FHCP trading partners to supplement the 834 TR3. It briefly describes the global data content, business rules, and characteristics of the 834 transaction. All Segments. Only loops, segments, and data elements valid for … Read More →
ASC X12 (Accredited Standards Committee X12): Uniform Standards For Global EDI ASC X12 was chartered by the Accredited Standards Committee X12 to join North American companies using Electronic Data Interchange under common inter-industry standards. Today ASC X12 standards are supported by approximately half million companies using EDI transactions around the world. ASC X12 is closely … Read More →
Case Study: GS1 Standards Reduce EDI Errors (Seton Family of Hospitals and BD) Seton Family of Hospitals (Ascension Health) manages pricing & product information for 445 locations. In past transactions between Seton Family of Hospitals and BD, both parties were identified with proprietary numbers: Seton Family of Hospitals with a BD-assigned SAP “Ship to” number … Read More →
EDI Consignment Orders (Purchase Order (850)) The Purchase Order (850) not only accommodates standalone, and blanket order business scenarios, the Purchase Order (850) also accommodates consignment order business scenarios. Consignment order business scenarios have a lot in common with stand-alone Purchase order in that the use or inclusion of GTIN and GLN can be accommodated … Read More →
EDI Direct Ship Orders And “Ship to Mark for” Orders A Purchase Order (850) may be an original, or it may be an update or confirmation of one already communicated to the seller or broker. It may also be used to express distribution requirements for receiving location(s), such as a Direct Ship Order. Direct Ship … Read More →
Map Use of GLN And GTIN in Order-to-Cash Transactions The use of GLN in a transaction will occur in the N1 loop. The N1 loop is used to identify organizational entities associated with the transaction. The N1 loop can be repeated to add more than one entity, and/or more than one identifier per entity. The N1 … Read More →
EDI GLN Account Hierarchies (Parties and Locations) GLNs are designed to support unique and unambiguous identification of parties/locations in business processes, which is essential for efficient communication between trading partners. The GLN can be used to identify a functional entity (like a hospital pharmacy or accounting department), a physical location (like a warehouse or hospital … Read More →