HIPAA Transaction Standard Companion Guide ASC X X212A1 Health Care Claim Status Request and Response (276/277)

Size: px
Start display at page:

Download "HIPAA Transaction Standard Companion Guide ASC X X212A1 Health Care Claim Status Request and Response (276/277)"

Transcription

1 HIPAA Transaction Standard Companion Guide ASC X X212A1 Health Care Claim Status Request and Response (276/277) Disclosure Statement This companion guide for real-time and batch 276/277 follows the CAQH CORE Phase I and Phase II guidelines. February 2017

2 This Companion Guide is prepared for use by trading partners affiliated with Kaiser Foundation Health Plan of Washington. This Companion Guide is to be used with, and not as a replacement for, the ASC X12N 5010 version of the HIPAA Transaction Technical Report Type 3 (TR3). The TR3 s for each transaction are available electronically from the WPC website at This Companion Guide is considered a living document, and as such, the information provided herein will be subject to change. A copy of the document and any changes to the document will be posted via the Kaiser Foundation Health Plan of Washington website located at: kp.org/wa/ provider.ghc.org/open/billingandclaims/claimsprocedures/index.jhtml Kaiser Foundation Health Plan of Washington is committed to maintaining the integrity and security of health care data in accordance with applicable laws and regulations. Preface The Health Insurance Portability and Accountability Act (HIPAA) requires all health insurance payers to comply with the Electronic Data Interchange (EDI) standards for health care as established by the Department of Health and Human Services. This Companion Guide to the v5010 ASC X12N Implementation Guide (or TR3) and associated errata, adopted under HIPAA, clarifies the data content used when exchanging claim status data electronically with Kaiser Foundation Health Plan of Washington. Transmissions based on 2013 Group Health Cooperative 2

3 this Companion Guide, used in tandem with the ASC X12 276/277 and the ASC X TR3s, are compliant with both X12 syntax and the TR3. This Companion Guide is intended to convey information that is within the framework of the ASC X12 Implementation Guides adopted for use under HIPAA. The document further specifies the requirements to be used when preparing, submitting, receiving and processing electronic health care administrative data. The document supplements, but does not contradict, disagree, oppose, or otherwise modify the HIPAA Implementation Guide in a manner that will make its implementation by users to be out of compliance. Using this Companion Guide does not mean that a claim will be paid Group Health Cooperative 3

4 1 TABLE OF CONTENTS REFERENCES GETTING 2.1 WORKING WITH OUR HEALTH TRADING PARTNER AND TESTING 6 3 TESTING WITH THE 4 CONNECTIVITY WITH THE 9 A. SOAP: Real-time 9 B. MIME Multipart: Real-time C. SOAP: Batch D. MIME Multipart: Batch E. HTTP Error Messages F. Envelope Errors G. Batch Response and Retrieval H. Connectivity Information to the SFTP server CONTACT INFORMATION EDI CONTROL 7 PAYER SPECIFIC BUSINESS RULES AND PROCESS SPECIFIC SERVICE AAA CORE LEVEL OF CERTIFICATION TRADING PARTNER 10 TRANSACTION SPECIFIC INFORMATION APPENDICES 8 PROCEDURES... 8 A. CHECKLIST B. BUSINESS...20 C. EXAMPLES D. CHANGE SUMMARY E. SFT SET UP F. LOSSARY Group Health Cooperative 4

5 Revision History Date Version Description Author New Release G. Schulte 2.1 Updated realtime response restrictions G. Schulte Update real time response requirements G. Schulte Update Name Reviewers Date Version Reviewers Role & Responsibility & G. Schulte Lead Integration Architect Gladys Jones Jack Hempel Sergio Angarita Pete Schneider Health Plan IT Consultant Integration Architect Integration Architect Integration Developer Approvers Date Version Approver Role & Responsibility Gladys Jones Health Plan IT Consultant 11/22/ Gladys Jones Health Plan IT Consultant 10/22/ Gladys Jones Health Plan IT Consultant 02/04/ Gladys Jones Health Plan IT Consultant 5

6 1 INTRODUCTION 1.1 OVERVIEW The purpose of this document is to introduce and provide information about Kaiser Foundation Health Plan of Washington CAQH/CORE solution for submitting real time and batch 276/277 transactions. This document will cover the Phase II operating rules requirements for the claim status transaction. The 276 and 277 transactions are used in tandem: the 276 transaction is used to request the status of a health care claim(s) and the 277 to respond with the information regarding the specified claim(s). These transactions can be real-time or batch. Kaiser Foundation Health Plan of Washington supports both real-time and batch transactions; and returns detailed claim status information on the 277 Response. 1.2 SCOPE Providers, clearing houses, and other trading partners are advised to refer to the v5010 ASC X12 Implementation Guide for submitting the claim status inquiries. This companion guide should be used to clarify and find more information about the CORE requirements and rules regarding batch and real-time transactions, i.e. acknowledgments, connectivity, response time, system availability, and data content. 1.3 REFERENCES ASC X12 Version 5010A1 Implementation Guides: CAQH/CORE: WSDL: SOAP: MIME Multipart: CORE XML Schema: ADDITIONAL INFORMATION Kaiser Foundation Health Plan of Washington currently supports both batch and real-time transactions. Kaiser Foundation Health Plan of Washington has adopted the two envelope standards mandated in CORE Phase II. 1. HTTP MIME Multipart 2. SOAP + WSDL Kaiser Foundation Health Plan of Washington has chosen the use of X.509 certificates for authentication. The external partner that wants to connect with Kaiser Foundation Health Plan of Washington will issue a X.509 certificate signed by a known certificate authority (CA) i.e. VeriSign, etc. Once the certificate is issued, the external partner will provide Kaiser Foundation Health Plan of Washington with the Distinguished Name (DN) for Kaiser Foundation Health Plan of Washington to verify the external partner s identity when they connect to our Gateway. 6

7 2 GETTING STARTED 2.1 WORKING WITH OUR HEALTH PLANS Providers, billing services and clearinghouses interested in submitting 276 inquiries and receiving 277 responses for either real-time or batch to/from for Kaiser Foundation Health Plan of Washington should contact the EDI team at 2.2 TRADING PARTNER REGISTRATION Trading partner registration is required in order to submit 276 requests and receive 277 responses. Please find attached in appendices the submit request form which will initiate the registration process. (Refer to Appendix F) 2.3 CERTIFICATION AND TESTING OVERVIEW Kaiser Foundation Health Plan of Washington requires submitting at least one test transaction to ensure data transfer is successful with connectivity using the certificate. The testing URLs are given below: HTTP MIME QA RealTime Test Request : HTTP MIME QA Batch Test Request : SOAP QA RealTime Test Request Request: SOAP QA Batch Test Request Request: WSDL: 3 TESTING WITH THE PAYER Listed below are steps to follow when testing: Provide the Distinguished Name for X509 Certification to Kaiser Foundation Health Plan of Washington EDI Support An EDI coordinator will be assigned to work with you on the registration and testing Create test transactions (preferably good and bad requests) based on Companion Guide/Implementation Guide specifications and submit via the testing URL, either real-time or batch or both, as necessary ( Refer to Appendix C for transaction example) Retrieve, review, and validate the appropriate response (277 or 999) Submit confirmation to determine production readiness Move to production upon consensus 7

8 4 CONNECTIVITY WITH THE PAYER/COMMUNICATIONS 4.1 PROCESS FLOW Process flow is layered by http process, envelope, and then business process. Only when the inbound transmission has passed the outer layers to the business process will a 999 and/or a 271 response be returned. 4.2 TRANSMISSION/Re-TRANSMISSION ADMINISTRATIVE PROCEDURES Real time 276 inquiries are limited to one status request. A response to the real-time inquiry will not exceed 20 seconds on average 90% of the time for our monthly volume. If a Real time response message is not received within the 60 second response time period, the submitter s system may send a duplicate transaction no sooner than 90 seconds after the original attempt was sent. Batch 276 inquiries are limited to 99 status requests within an ST/SE grouping. A response to the batch inquiry will be provided by 7 a.m. (PST) the following business day for batches received before 9 pm (PST) the previous day. Batch requests submitted after 9 p.m. (PST) will be available by 7 a.m. (PST) two business days following submission. The following links below provide more information on: System Maintenance: Please refer to the respective health plan page for the most up-to-date information on system availability at: kp.org/wa/provider/open/billingandclaims/claimsprocedures/index.jhtml 8

9 System Downtime: All scheduled downtimes and the respective health plan holiday schedules will be published and emergency downtimes will be posted in the below link: kp.org/wa/provider /open/billingandclaims/claimsprocedures/index.jhtml 4.3 COMMUNICATION PROTOCOL SPECIFICATIONS In compliance with Core rules, Kaiser Foundation Health Plan of Washington requires that all SOAP transactions conform to SOAP Version 1.2. The XML schema definition set forth by CORE and used by our EDI is located at: The WDSL definition set forth by CORE and used by our EDI is located at: Connectivity Mode Transaction Request Submission to URL SOAP + WSDL HTTP + MIME Secure Web Service Secure Web Service Secure Web Service Secure Web Service Real-time Time X 12 Batch X12 Real-time Time X12 Batch X12 /service/request /service/request g/service/request /service/request WSDL est?wsdl A. SOAP: Real-time Message Content Details: Payload Type: Payload Type specifies the type of payload included within a request. Valid values are: Request X12_276_Request_005010X212 Response 9

10 X12_277_Response_005010X212 X12_999_Response_005010X231A1 Processing Mode: Processing Mode indicates Real-time processing mode. Valid value is RealTime Payload ID: This is an Identifier that is used to uniquely identify the request submitted. Values are Alphanumeric, may contain hyphen. Timestamp: Time and Date specifying when a message is created and sent to a receiver. Valid value follows standard Universal Time (UTC) Sender ID: Submitter ID/Client ID Valid value is 7 characters alphanumeric as assigned by Kaiser Foundation Health Plan of Washington Receiver ID: Kaiser Foundation Health Plan of Washington s Tax ID Valid value is 11 characters alphanumeric. i.e RT CORE Rule Version: The CORE Rule version that this envelope is using will be Payload: Payload contains compliant X request data. Payload should be encrypted using BASE 64 encode. B. MIME Multipart: Real-time HTTP Headers: For MIME multipart the messages should always contain Content-Type that specifies the boundary used to separate each part of the message. Example: Content-Type: multipart/form-data; boundary=xbcy Message Content Details: Payload Type: Payload Type specifies the type of payload included within a request. Valid values are: Request X12_276_Request_005010X212 Response X12_277_Response_005010X212 X12_999_Response_005010X231A1 Processing Mode: Processing Mode indicates real-time processing mode. Valid value is RealTime 10

11 Payload ID: This is an Identifier used to uniquely identify the request submitted. Values are Alphanumeric, may contain hyphen. Time Stamp: Time and Date specifying when a message is created and sent to a receiver. Valid value follows standard Universal Time (UTC) Sender ID: Submitter ID/Client ID. Valid value is 7 characters alphanumeric as assigned by Kaiser Foundation Health Plan of Washington. Receiver ID: Kaiser Foundation Health Plan of Washington s Tax ID Valid value is 11 characters alphanumeric. i.e RT CORE Rule Version: The CORE Rule version that this envelope is using will be Payload: Payload contains compliant X request data. Payload should be encrypted using BASE 64 encode. Real-time Example: --XbCY Content-Disposition: form-data; name="payloadtype" X12_276_Request_005010X212 --XbCY Content-Disposition: form-data; name="processingmode" RealTime --XbCY Content-Disposition: form-data; name="payloadid" e51d4fae-7dec-11d0-a765-00a0c91e6da6 --XbCY Content-Disposition: form-data; name="timestamp" T10:20:34Z --XbCY Content-Disposition: form-data; name="senderid" HOSPIX9 --XbCY Content-Disposition: form-data; name="receiverid" RT --XbCY Content-Disposition: form-data; name="coreruleversion"

12 --XbCY Content-Disposition: form-data; name="payload" ISA*00* --XbCY-- *00* *ZZ C. SOAP: Batch HTTP Headers: For MTOM the messages should always contain Content-Type that specifies among others the boundary used to separate each part of the message. Example: Content-Type: multipart/related; type="application/xop+xml"; start-info="application/soap+xml"; action="batchresultsacksubmittransaction"; boundary="---- =_Part_0_ " In return, we will also send a Content-Type that specifies among others the boundary used to separate each part of the message. Example: Content-Type: multipart/related; boundary="wmbmime1boundaryurn_uuid_523f992ed9ce810e7f "; start-info="application/soap+xml"; type="application/xop+xml"; start="<0.urn:uuid:523f992ed9ce810e7f @ibm.com>" Message Content Details: Payload Type: Payload Type specifies the type of payload included within a request. Valid values are: Request X12_276_Request_005010X212 X12_999_RetrievalRequest_005010X231A1 X12_005010_Request_Batch_Results_277 X12_999_SubmissionRequest_005010X231A1 Response X12_BatchReceiptConfirmation X12_999_Response_005010X231A1 X12_277_Response_005010X212 X12_Response_ConfirmReceiptReceived Processing Mode: Processing Mode indicates Batch. Valid value is Batch 12

13 Payload ID: This is an Identifier that will be used to uniquely identify the request submitted. Values are Alphanumeric, may contain hyphen. Payload Length: Defines the length of the actual X12 payload in bytes. Timestamp: Time and Date specifying when a message is created and sent to a receiver. Valid value follows standard Universal Time (UTC). Sender ID: Submitter ID/Client ID. Valid value is 7 characters alphanumeric as assigned by Kaiser Foundation Health Plan of Washington EDI team. Receiver ID: Kaiser Foundation Health Plan of Washington s Tax ID Valid value is 9 characters numeric. i.e CORE Rule Version: The CORE Rule version that this envelope is using will be Checksum: An element used to allow receiving site to verify the integrity of the message that is sent. Algorithm is SHA-1, Encoding is Hex. Checksum must be computed only on the payload and not on the metadata. Payload: Payload contains compliant X request data. Payload should be encrypted using BASE 64 encode. D. MIME Multipart: Batch HTTP Headers: For MIME multipart the messages should always contain Content-Type that specifies the boundary used to separate each part of the message. Example: Content-Type=multipart/form-data; boundary=xbcy Message Content Details: Payload Type: Payload Type specifies the type of payload included within a request. Valid values are: Request X12_276_Request_005010X212 X12_999_RetrievalRequest_005010X231A1 X12_005010_Request_Batch_Results_277 X12_999_SubmissionRequest_005010X231A1 Response X12_BatchReceiptConfirmation X12_999_Response_005010X231A1 X12_277_Response_005010X212 X12_Response_ConfirmReceiptReceived 13

14 Processing Mode: Processing Mode indicates Batch. Valid value is Batch Payload ID: This is an Identifier that you will use to uniquely identify the request submitted. Values are Alphanumeric, may contain hyphen. Payload Length: Defines the length of the actual payload in bytes. Timestamp: Time and Date specifying when a message is created and sent to a receiver. Valid value follows standard Universal Time (UTC). Sender ID: Submitter ID/Client ID. Valid value is 7 characters alphanumeric as assigned by Kaiser Foundation Health Plan of Washington. Receiver ID: Kaiser Foundation Health Plan of Washington s Tax ID Valid value is 9 characters numeric. i.e CORE Rule Version: The CORE Rule version that this envelope is using will be Checksum: An element used to allow receiving site to verify the integrity of the message that is sent. Algorithm is SHA-1, Encoding is Hex. Checksum must be computed only on the payload and not on the metadata. Payload: Payload contains compliant X request data. Payload should be encrypted using BASE 64 encode. Batch Example: --XbCY Content-Disposition: form-data; name="payloadtype" X12_999_SubmissionRequest_005010X231A1 --XbCY Content-Disposition: form-data; name="processingmode" Batch --XbCY Content-Disposition: form-data; name="payloadid" f81d4fae-7dec-11d0-a765-00a0d91e6fa6 --XbCY Content-Disposition: form-data; name="payloadlength" XbCY Content-Disposition: form-data; name="timestamp" T10:20:34Z --XbCY Content-Disposition: form-data; name="senderid" 14

15 CLMLGC9 --XbCY Content-Disposition: form-data; name="receiverid" XbCY Content-Disposition: form-data; name="coreruleversion" XbCY Content-Disposition: form-data; name="checksum" 6A3FE XbCY Content-Disposition: form-data; name="payload" SVNBKjAwKiAgICAgICAgICAqMDA= --XbCY-- E. HTTP Error Messages 1. HTTP 200 OK Returned when authentication is valid and request is accepted with the real-time system. 2. HTTP 202 OK Returned when batch file submission has been accepted. 3. HTTP 400 Bad Request Returned for incorrectly formatted HTTP headers. 4. HTTP 403 Forbidden Returned when the user is unauthorized. 5. Server Errors When the real-time production system is not able to process a real-time request due to interface failures or other system unavailability, a standard 5xx series error such as HTTP 500 Internal Server Error or HTTP 503 Service Error will be returned by the application. Resubmission is recommended at a later time. F. Envelope Errors 1. Success Envelope was processed successfully. 2. <FieldName>Illegal Illegal value provided for <FieldName>. 3. <FieldName>Required The field <FieldName> is required but was not provided. 4. Version Mismatch The version of the envelope sent is not acceptable to the receiver. If the SOAP version is not valid at the receiver, a SOAP fault is returned with this fault code. 15

16 5. Checksum Mismatched The checksum value computed on the recipient did not match the value that was sent in the envelope. G. Batch Response and Retrieval All batch requests for claim sataus and batch results acknowledgment will be received by establishing a HTTP connection using CORE rules. The trading partners must submit a request for available responses. Kaiser Foundation Health Plan of Washington provides a list of 277/999 files available for pick up. Kaiser Foundation Health Plan of Washington uses an SFTP server where the files are available for pick up. To connect to this server, the Trading Partner must request an account. All our trading partners as of December 2012 already have an account to connect to this server. For future partners, a form is available online and in Appendix E to request access to the server. The user ID assigned to log into this server is the user ID that has to be sent in the Sender ID field when submitting requests real-time or batch through the HTTP standard connection. H. Connectivity Information to the SFTP server Server name: sft3.ghc.org Port: 22 Folder PROD: my_inboxes/mercator/ Folder TEST: my_test_inboxes/mercator/ Maximum number of real-time and batch transactions per minute per client Real time: 5 Batch: 1 Maximum size of Batch files: Maximum size of a file sent as an attachment to the HTTP request will be 1 MB 5 CONTACT INFORMATION EDI CUSTOMER SERVICE For questions regarding Kaiser Foundation Health Plan of Washington 276/277 real-time and batch transmission, or this guide, please contact: EDI Support Group Monday Friday, 8:00 AM 4:00 PM PST Ph: (206) edisupport@ghc.org For specific questions regarding Subscriber/Plan information, please go the web sites: kp.org/wa/provider /open/billingandclaims/claimsprocedures/index.jhtml 6 CONTROL SEGMENTS/ENVELOPES 16

17 ISA-IEA SEGMENT: Loop ID Segment Type Element Identifier Element Name Attribute Value Header ISA ISA01 Authorization Information Qualifier ID 0 ISA02 Authorization Information AN Security Information ISA03 Qualifier ID 0 ISA04 Security Information AN ISA05 Interchange ID Qualifier ID ZZ ISA06 Interchange Sender ID AN ISA07 Interchange ID Qualifier ID ZZ ISA08(BATCH) Interchange Receiver ID AN ISA08 (REALTIME) Interchange Receiver ID AN RT ISA09 Interchange Date DT ISA10 Interchange Time TM ISA11 Repetition Separator ^ Interchange Control ISA12 Version Number ID 0501 Interchange Control ISA13 Number N0 ISA14 Acknowledgement Requested ID 0 Usage Indicator ISA15 T-Test, P-Production ID T/P Component Element ISA16 Separator AN Loop ID Segment Type Trailer IEA IEA01 Element Identifier Element Name Attribute Value Number of Included Functional Groups Interchange Control IEA02 must match Interchange Control GS-GE SEGMENT: Segment Type Element Identifier Element Name Attribute Value Loop ID Header GS01 Functional Identifier Code ID HS GS02 Application Sender Code AN GS03 Application Receiver Code AN GS04 Date DT GS05 Time TM GS06 Group Control Number N0 GS07 Responsible Agency Code ID X 17

18 GS08 Version Identifier Code AN X212 Segment Type Element Identifier Element Name Attribute Value Loop ID Trailer GE GE01 Number of Transaction Sets Included GE02 Group Control Number ST-SE: Segment Element Loop ID Type Identifier Element Name Attribute Value Header ST ST01 Transaction Set Identifier Code ID 276 ST02 Transaction Set Control Number AN 1 ST03 Implementation Convention Reference AN X212 Segment Element Loop ID Type Identifier Element Name Attribute Value Trailer SE01 Number of Included Segments SE02 Transaction Set Control Number One ISA/IEA may contain more than one Functional Group (GS/GE). The functional group must be an claim status transaction type (005010X212). 7 PAYER SPECIFIC BUSINESS RULES AND LIMITATIONS 7.1 SPECIFIC SERVICE CODES Kaiser Foundation Health Plan of Washington EDI follows the Washington Best Practices guidelines for the Service codes. For more information please, refer to the link below: AAA CODES Not Applicable 7.3. CORE LEVEL OF CERTIFICATION At this time Kaiser Foundation Health Plan of Washington has passed testing for CORE levels 1 and 2 certification. 18

19 8 ACKNOWLEDGEMENTS 8.1 REAL-TIME Following responses can be expected from Kaiser Foundation Health Plan of Washington EDI for a real-time 276 transaction: 8.2 BATCH 277 response transaction indicating the requested member s coverage or benefits (or) 999 acknowledgement (for a 276 Reject) if the 276 transaction contains HIPAA compliancy errors Following responses can be expected from Kaiser Foundation Health Plan of Washington EDI for a batch 276 transaction: 277 response transaction will be available the following day indicating the requested member s coverage or benefits 999 acknowledgement within an hour if the 276 transaction contains HIPAA compliancy errors 9 TRADING PARTNER AGREEMENTS Trading Partner agreement is not required for claim status inquiries but trading partner registration is mandatory. 10 TRANSACTION SPECIFIC INFORMATION Kaiser Foundation Health Plan of Washington EDI follows the standard information in the ASC X12N 276/277(005010X212) Health Care Claim Status Inquiry and Response Implementation Guide Kaiser Foundation Health Plan of Washington 19

20 A. IMPLEMENTATION CHECKLIST Provide the Distinguished Name for X509 Certification to Kaiser Foundation Health Plan of Washington An EDI coordinator will be assigned to work with you on the registration and testing Create test transactions (preferably good and bad requests) based on Companion Guide/Implementation Guide specifications and submit via the testing link, either real-time or batch or both, as necessary ( Refer to Appendices C for transaction example) Retrieve, review, and validate the appropriate response (277 or 999) Submit confirmation to determine production readiness Move to production upon consensus B. BUSINESS SCENARIOS NA C. TRANSMISSION EXAMPLES Kaiser Foundation Health Plan of Washington Health Real Time Transmission Example Sample 276 Transaction ISA*00* *00* *ZZ*YOUR ID *ZZ* RT *100301*1347*!*00501* *1*T*: GS*HR*YOUR ID * RT * *1347* *X*005010X212 ST*276* *005010X212 BHT*0010*13*RAM276TEST* *1425 HL*1**20*1 NM1*PR*2* KAISER FOUNDATION HEALTH PLAN OF WASHINGTON *****PI*98111 HL*2*1*21*1 NM1*41*2*ABC PROVIDER SERVICES*****46* HL*3*2*19*1 NM1*1P*2* ABC PROVIDER SERVICES*****XX* HL*4*3*22*0 DMG*D8* *M NM1*IL*1*CLAIMTEST*MIKE****MI* TRN*1* REF*1K* AMT*T3* DTP*472*RD8* SE*16* GE*1* IEA*1*

21 Sample 277 Transaction ISA*00* *00* *ZZ* RT *ZZ*YOUR ID *121228*1145*^*00501* *0*T*: GS*HN* *YOUR ID* *114513*1*X*005010X212 ST*277* *005010X212 BHT*0010*08* * *114513*DG HL*1**20*1 NM1*PR*2* KAISER FOUNDATION HEALTH PLAN OF WASHINGTON *****PI*98111 HL*2*1*21*1 NM1*41*2* ABC PROVIDER SERVICES*****46* HL*3*2*19*1 NM1*1P*2* ABC PROVIDER SERVICES*****XX* HL*4*3*22*0 NM1*IL*1*CLAIMTEST*MIKE****MI* TRN*2* STC*F1:65* **200*0* REF*1K* REF*BLT*131 DTP*472*RD8* SE*16* GE*1*1 IEA*1* D. CHANGE SUMMARY This is the first companion guide for claim status from Kaiser Foundation Health Plan of Washington for CORE. E. SFT Setup See our web site for the current form F. Glossary ACRONYM ASC X12N CA CAQH CORE DN EDI HIPAA HTTP MIME MTOM SFTP SHA-1 SOAP TR3 Accredited Standards Committee Certificate Authority Council for Affordable and Quality Healthcare Committee on Operating Rules for Information Exchange Distinguished Name Electronic Data Interchange Health Insurance Portability and Accountability Act Hypertext Transfer Protocol Message Transmission Optimization Mechanism Multipurpose Internet Mail Extensions Secure File Transfer Protocol Secure Hash Algorithm Simple Object Access Protocol Technical Reports 21

22 WPC WSDL XML Washington Publishing Company Web Service Definition Language Extensible Markup Language 22

23 23

HIPAA Transaction Standard Companion Guide. Refers to the Implementation Guides Based on ASC X12 version CORE v5010 Companion Guide

HIPAA Transaction Standard Companion Guide. Refers to the Implementation Guides Based on ASC X12 version CORE v5010 Companion Guide Gold Coast Health Plan CORE Companion Guide 270-271 HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 CORE v5010 Companion Guide August 2018

More information

Alameda Alliance for Health

Alameda Alliance for Health Alameda Alliance for Health HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 CORE v5010 Companion Guide October 2015 October 2015 005010 Version

More information

Inland Empire Health Plan

Inland Empire Health Plan Inland Empire Health Plan HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 CORE v5010 Companion Guide March 2016 March 2016 005010 Version

More information

Medical Associates Health Plans and Health Choices

Medical Associates Health Plans and Health Choices Medical Associates Health Plans and Health Choices 270/271 HIPAA Transaction Companion Guide HIPAA V5010X279A1 VERSION: 2.0 DATE: 06/21/2016 1 Disclosure Statement This material contains confidential,

More information

Partnership HealthPlan of California

Partnership HealthPlan of California Partnership HealthPlan of California HIPAA Transaction Companion Guide CORE: 276/277 Health Care Claim Status Request and Response ASC X12 version 005010 Disclosure Statement This document is subject to

More information

Administrative Services of Kansas (ASK)

Administrative Services of Kansas (ASK) Administrative Services of Kansas (ASK) HIPAA 276/277 005010X212 Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 January 2016 1 Disclosure Statement This document

More information

CTMMIS SAFE HARBOR. Connecticut Medical Assistance Program 5010 Companion Guide April 10, 2017

CTMMIS SAFE HARBOR. Connecticut Medical Assistance Program 5010 Companion Guide April 10, 2017 CTMMIS SAFE HARBOR Connecticut Medical Assistance Program 5010 Companion Guide April 10, 2017 Connecticut Department of Social Services (DSS) 55 Farmington Avenue Hartford, CT 06105 DXC Technology 195

More information

/277 Companion Guide. Refers to the Implementation Guides Based on X12 version Companion Guide Version Number: 1.1

/277 Companion Guide. Refers to the Implementation Guides Based on X12 version Companion Guide Version Number: 1.1 5010 276/277 Companion Guide Refers to the Implementation Guides Based on X12 version 005010 Companion Guide Version Number: 1.1 November 26, 2012 1 Disclosure It is the sole responsibility of the provider/vendor

More information

276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions

276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions Companion Document 276/277 276/277 Health Care Claim Status Request/ Response Real-Time This companion document is for informational purposes only to describe certain aspects and expectations regarding

More information

Eligibility Gateway Companion Guide

Eligibility Gateway Companion Guide Eligibility Gateway Companion Guide Conduent EDI Solutions, Inc. ASC X12N 270/271 ASC X12N 276/277 All Payers May 10, 2017 2017 Conduent Business Services, LLC. All rights reserved. Conduent and Conduent

More information

Maryland Health Insurance Exchange (MHBE) Standard Companion Guide Transaction Information

Maryland Health Insurance Exchange (MHBE) Standard Companion Guide Transaction Information A service of the Maryland Health Benefit Exchange Maryland Health Insurance Exchange (MHBE) Standard Companion Guide Transaction Information 999 Implementation Acknowledgments for Health Care Insurance

More information

Electronic Remittance Advice (835) (Refers to the Implementation Guides based on ASC X X221)

Electronic Remittance Advice (835) (Refers to the Implementation Guides based on ASC X X221) HIPAA Transaction Standard EDI Companion Guide Electronic Remittance Advice (835) (Refers to the Implementation Guides based on ASC X12 005010X221) 2 Disclosure Statement: This Companion Guide has been

More information

276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions

276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions Companion Document 276/277 276/277 Health Care Claim Status Request/ Response Real-Time This companion document is for informational purposes only to describe certain aspects and expectations regarding

More information

Administrative Services of Kansas (ASK)

Administrative Services of Kansas (ASK) Administrative Services of Kansas (ASK) HIPAA 834 005010X220A1 Health and Dental Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 Last reviewed July 2018 1 Disclosure

More information

HIPAA Transaction Health Care Claim Acknowledgement Standard Companion Guide (277CA, X214)

HIPAA Transaction Health Care Claim Acknowledgement Standard Companion Guide (277CA, X214) (underwritten by Dean Health Plan) HIPAA Transaction Health Care Claim Acknowledgement Standard Companion Guide (277CA, 005010X214) Instructions related to Transactions based on ASC X12 Implementation

More information

DentaQuest HIPAA Transaction Standard Companion Guide

DentaQuest HIPAA Transaction Standard Companion Guide DentaQuest HIPAA Transaction Standard Companion Guide 837D 005010X224A2 Version 1.0 January 2016 January 18, 2016 1 Disclosure Statement 2015 DentaQuest, LLC. All rights reserved. This document may be

More information

Standard Companion Guide

Standard Companion Guide Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 005010X224A2 Health Care Claim Dental (837D) Companion Guide Version Number 2.0 September 25, 2018 Page 1 of 15 CHANGE LOG

More information

ASC X X220A1)

ASC X X220A1) HIPAA Transaction Standard EDI Companion Guide Benefit Enrollment and Maintenance (834) (Refers to the Implementation Guides based on ASC X12 005010X220A1) 2 Disclosure Statement: This Companion Guide

More information

Assurant Health HIPAA Transaction Standard Companion Guide

Assurant Health HIPAA Transaction Standard Companion Guide Assurant Health HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 270/271 Health Care Eligibility Benefit Inquiry and Response CORE v5010 Master

More information

Blue Cross Blue Shield of Louisiana

Blue Cross Blue Shield of Louisiana Blue Cross Blue Shield of Louisiana Health Care Claim Payment/Advice (835) Standard Companion Guide Refers to the Implementation Guides Based on ASC X12N version: 005010X221A1 October 1, 2013 Version 1.0

More information

Standard Companion Guide. Refers to the Implementation Guide Based on X12 Version X212 Health Care Claim Status Request and Response (276/277)

Standard Companion Guide. Refers to the Implementation Guide Based on X12 Version X212 Health Care Claim Status Request and Response (276/277) Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 005010X212 Health Care Claim Status Request and Response (276/277) Companion Guide Version Number 4.0 June 12, 2018 Change

More information

HIPAA 276/277 Companion Guide Cardinal Innovations Prepared for Health Care Providers

HIPAA 276/277 Companion Guide Cardinal Innovations Prepared for Health Care Providers Cardinal Innovations Prepared for Health Care Providers, February 2017 Table of Contents Preface... 4 1. Transaction Instruction (TI) Introduction... 5 1.1 Scope... 5 1.2 Overview... 5 1.3 References...

More information

Florida Blue Health Plan

Florida Blue Health Plan FLORIDA BLUE HEALTH PLAN COMPANION GUIDE Florida Blue Health Plan ANSI 276/277- Health Care Claim Status Inquiry and Response Standard Companion Guide Refers to the Technical Report Type Three () of 005010X212A1

More information

276/ /277 Health Care Claim Status Request and Response Real-Time. Basic Instructions. Companion Document

276/ /277 Health Care Claim Status Request and Response Real-Time. Basic Instructions. Companion Document Companion Document 276/277 276/277 Health Care Claim Status Request and Response Real-Time Basic Instructions This section provides information to help you prepare for the ANSI ASC X12.316 Health Care

More information

West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270

West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270 West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270 Date of Publication: 01/01/2014 Document Number: Version: 2.0 DISCLAIMER The Molina Healthcare Companion Guide for West Virginia is

More information

Health Care Connectivity Guide

Health Care Connectivity Guide Health Care Connectivity Guide Standard Companion Guide November 2, 2015 Version 2.0 Disclosure Statement The Kansas Department of Health and Environment (KDHE) is committed to maintaining the integrity

More information

USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270

USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270 USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270 Date of Publication: 12/04/2012 Version: 1.1 DISCLAIMER The DXC Technology Companion Guide for USVI Medicaid is subject to change prior

More information

EMBLEMHEALTH HIPAA Transaction Standard Companion Guide

EMBLEMHEALTH HIPAA Transaction Standard Companion Guide EMBLEMHEALTH HIPAA Transaction Standard Companion Guide Refers to the X12N Implementation Guide 005010X222A1: 837P Health Care Claim Professional Transaction HIPAA Readiness Disclosure Statement The Health

More information

EMBLEMHEALTH. HIPAA Transaction Standard Companion Guide

EMBLEMHEALTH. HIPAA Transaction Standard Companion Guide EMBLEMHEALTH HIPAA Transaction Standard Companion Guide Refers to the X12N Implementation Guide 005010X220A1: 834 Benefit Enrollment and Maintenance Transactions EMBLEMHEALTH COMPANION GUIDE HIPAA Readiness

More information

Florida Blue Health Plan

Florida Blue Health Plan FLORIDA BLUE HEALTH PLAN COMPANION GUIDE Florida Blue Health Plan ANSI 270/271- Health Care Eligibility and Benefit Inquiry and Response Standard Companion Guide Refers to the Technical Report Type Three

More information

Claim Status Inquiry and Response (276/277) (Refers to the Implementation Guides based on ASC X X212)

Claim Status Inquiry and Response (276/277) (Refers to the Implementation Guides based on ASC X X212) HIPAA Transaction Standard EDI Companion Guide Claim Status Inquiry and Response (276/277) (Refers to the Implementation Guides based on ASC X12 005010X212) Disclosure Statement: 2 This Companion Guide

More information

Excellus BlueCross BlueShield

Excellus BlueCross BlueShield Excellus BlueCross BlueShield HIPAA Transaction Standard Companion Guide Refers to the HIPAA ANSI ASC X12N Implementation Guides for the following transactions: ASC X12N/005010X279A1 Health Care Eligibility

More information

Sanford Health Plan HIPAA Transaction Standard Companion Guide

Sanford Health Plan HIPAA Transaction Standard Companion Guide Sanford Health Plan HIPAA Transaction Standard Companion Guide Refers to the Technical Report Type 3 (TR3) Implementation Guides Based on ASC X12 Version 005010X279A1 Eligibility Inquiry and Response (270/271)

More information

Standard Companion Guide

Standard Companion Guide Standard Refers to the Implementation Guide Based on X12 Version 005010X223A2 Health Care Claim: Institutional (837) Version Number: 1.0 December 10, 2010 written permission of UnitedHealth Group is prohibited.

More information

270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response

270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Companion Document 270/271 270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Basic Instructions This section provides information to help you prepare for the ANSI ASC X12.281 Eligibility,

More information

ASC X12N 276/277 (005010X212)

ASC X12N 276/277 (005010X212) TRICARE HIPAA Transaction Standard Companion Guide ASC X12N 276/277 (005010X212) Health Care Claim Status Request and Response Version 1.1 March 2013 i DISCLOSURE STATEMENT Please note that the information

More information

Standard Companion Guide

Standard Companion Guide Response (278) Standard Companion Guide Refers to the Implementation Guides Based on X12 version 005010X217E2 Health Care Services Review Request for Review and Companion Guide Version Number: 2.0 October

More information

ANSI ASC X12N 837 Healthcare Claim (Version X222A1-June 2010) Professional Companion Guide

ANSI ASC X12N 837 Healthcare Claim (Version X222A1-June 2010) Professional Companion Guide ANSI ASC X12N 837 Healthcare Claim (Version 005010X222A1-June 2010) Pruitt Health Premier Missouri Medicare Select Signature Advantage September 2015 TABLE OF CONTENTS AT A GLANCE II CHAPTER 1: INTRODUCTION

More information

HIPAA Transaction 278 Request for Review and Response Standard Companion Guide

HIPAA Transaction 278 Request for Review and Response Standard Companion Guide FLORIDA BLUE HEALTH PLAN COMPANION GUIDE HIPAA Transaction 278 Request for Review and Response Standard Companion Guide Refers to the Technical Reports Type 3 Based on ASC X12 version 005010X217 Companion

More information

Integration Guide for Data Originators of Claim Status. Version 1.1

Integration Guide for Data Originators of Claim Status. Version 1.1 Integration Guide for Data Originators of Claim Status Version 1.1 December 23, 2010 Integration Guide for Data Originators of Claim Status Revision History Date Version Description Author November 25,

More information

Sanford Health Plan. HIPAA Transaction Standard Companion Guide. Refers to the Technical Report Type 3 (TR3) Implementation Guides

Sanford Health Plan. HIPAA Transaction Standard Companion Guide. Refers to the Technical Report Type 3 (TR3) Implementation Guides Sanford Health Plan HIPAA Transaction Standard Companion Guide Refers to the Technical Report Type 3 (TR3) Implementation Guides Based on ASC X12 Version 005010X212A1 Health Care Claim Status Request and

More information

Appendix A Vendor Specifications for. State of Idaho MMIS

Appendix A Vendor Specifications for. State of Idaho MMIS Appendix A Vendor Specifications-5010 for State of Idaho MMIS Date of Publication: 1/18/2017 Document Number: TL428 Version: 6.0 Revision History Version Date Author Action/Summary of Changes 1.0 07/01/2011

More information

HIPAA X 12 Transaction Standards

HIPAA X 12 Transaction Standards HIPAA X 12 Transaction Standards Companion Guide 837 Professional/ Institutional Health Care Claim Version 5010 Trading Partner Companion Guide Information and Considerations 837P/837I June 11, 2012 Centene

More information

Vendor Specifications 270/271 Eligibility Benefit Inquiry and Response ASC X12N Version for. State of Idaho MMIS

Vendor Specifications 270/271 Eligibility Benefit Inquiry and Response ASC X12N Version for. State of Idaho MMIS Vendor Specifications 270/271 Eligibility Benefit Inquiry and Response ASC X12N Version 5010 for State of Idaho MMIS Date of Publication: 7/27/2017 Document : TL419 Version: 8.0 Revision History Version

More information

General Companion Guide 837 Professional and Institutional Healthcare Claims Submission Version Version Date: June 2017

General Companion Guide 837 Professional and Institutional Healthcare Claims Submission Version Version Date: June 2017 General Companion Guide 837 Professional and Institutional Healthcare Claims Submission Version 5010 Version Date: June 2017 1 Introduction ************************************************************************

More information

HIPAA X 12 Transaction Standards

HIPAA X 12 Transaction Standards HIPAA X 12 Transaction Standards Companion Guide 837 Professional/ Institutional Health Care Claim Version 5010 Trading Partner Companion Guide Information and Considerations 837P/837I September 19, 2014

More information

Refers to the Technical Reports Type 3 Based on ASC X12 version X223A2

Refers to the Technical Reports Type 3 Based on ASC X12 version X223A2 HIPAA Transaction Standard Companion Guide For Availity Health Information Network Users Refers to the Technical Reports Type 3 Based on ASC X12 version 005010X223A2 837 Health Care Claim Institutional

More information

< A symbol to indicate a value is less than another. For example, 2 < 3. This symbol is used in some BCBSNC proprietary error messages.

< A symbol to indicate a value is less than another. For example, 2 < 3. This symbol is used in some BCBSNC proprietary error messages. Glossary < A symbol to indicate a value is less than another. For example, 2 < 3. This symbol is used in some BCBSNC proprietary error messages. > A symbol to indicate a value is greater than another.

More information

837 Companion Guide. October PR.P.WM.1 3/17

837 Companion Guide. October PR.P.WM.1 3/17 837 Companion Guide Refers to the Implementation Guides based on the HIPAA Transaction ASC X12N. Standards for Electronic Data Interchange X12N/005010x222 Health Care Claim: Professional (837P) and ASC

More information

ACKNOWLEDGMENTS BEST PRACTICE

ACKNOWLEDGMENTS BEST PRACTICE Claim and Remittance ACKNOWLEDGMENTS BEST PRACTICE Prepared by the Minnesota Administrative Uniformity Committee (AUC) This Best Practice is intended for use with the corresponding MN Uniform Companion

More information

837 Health Care Claim Companion Guide. Professional and Institutional

837 Health Care Claim Companion Guide. Professional and Institutional 837 Health Care Claim Companion Guide Professional and Institutional Revised December 2011 Table of Contents Introduction... 3 Purpose... 3 References... 3 Additional information... 4 Delimiters Supported...

More information

837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE

837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE 837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE OCTOBER 19, 2012 A S C X 1 2 N 8 3 7 (0 0 5 0 10 X 222A1) VERSION 3.0 TABLE OF CONTENTS 1.0 Overview 3 2.0 Introduction 4 3.0 Data Exchange

More information

Health Care Claims: Status Request and Response (Version 1.12 January 2007)

Health Care Claims: Status Request and Response (Version 1.12 January 2007) PacifiCare Electronic Data Interchange 276/277 Transaction Companion Guide Health Care Claims: Status Request and Response (Version 1.12 January 2007) 276/277 ANSI ASC X12 276/277 (004010X093) ANSI ASC

More information

BLUE CROSS AND BLUE SHIELD OF LOUISIANA PROFESSIONAL CLAIMS COMPANION GUIDE

BLUE CROSS AND BLUE SHIELD OF LOUISIANA PROFESSIONAL CLAIMS COMPANION GUIDE BLUE CROSS AND BLUE SHIELD OF LOUISIANA Table of Contents I. Introduction...3 II. General Specifications...4 III. Enveloping Specifications...5 IV. Loop and Data Element Specifications...7 V. Transaction

More information

Standard Companion Guide

Standard Companion Guide Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 005010X212 Health Care Claim Status Request and Response (276/277) Companion Guide Version Number 3.0 September 28, 2018

More information

Refers to the Technical Reports Type 3 Based on ASC X12 version X /277 Health Care Claim Status Inquiry and Response

Refers to the Technical Reports Type 3 Based on ASC X12 version X /277 Health Care Claim Status Inquiry and Response HIPAA Transaction Standard Companion Guide For Availity Health Information Network Users Refers to the Technical Reports Type 3 Based on ASC X12 version 005010X212 276/277 Health Care Claim Status Inquiry

More information

BLUE CROSS AND BLUE SHIELD OF LOUISIANA INSTITUTIONAL CLAIMS COMPANION GUIDE

BLUE CROSS AND BLUE SHIELD OF LOUISIANA INSTITUTIONAL CLAIMS COMPANION GUIDE BLUE CROSS AND BLUE SHIELD OF LOUISIANA Table of Contents I. Introduction...3 II. General Specifications...4 III. Enveloping Specifications...5 IV. Loop and Data Element Specifications...7 V. Transaction

More information

834 Companion Document to the 5010 HIPAA Implementation Guide

834 Companion Document to the 5010 HIPAA Implementation Guide Published: 1/3/2012 Updated: 12/15/2014 834 Companion Document to the 5010 HIPAA Implementation Guide Version 3.00.00 Virtual Benefits Administrator Companion Document Audience Companion documents are

More information

Indiana Health Coverage Programs

Indiana Health Coverage Programs Indiana Health Coverage Programs HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 Health Care Services Review Inquiry/Response (278) Companion

More information

Blue Shield of California

Blue Shield of California Blue Shield of California HIPAA Transaction Standard Companion Guide Section 1 Refers to the Implementation Guides Based on X12 version 005010 Companion Guide Version Number: 1.0 June 6,2011 [OCTOBER 2010

More information

837 Health Care Claim Professional, Institutional & Dental Companion Guide

837 Health Care Claim Professional, Institutional & Dental Companion Guide 837 Health Care Claim Professional, Institutional & Dental Companion Guide 005010X222A1 & 005010X223A1 V. 1.2 Created 07/18/14 Disclaimer Blue Cross of Idaho created this companion guide for 837 healthcare

More information

Phase II CAQH CORE 270: Connectivity Rule version March 2011

Phase II CAQH CORE 270: Connectivity Rule version March 2011 Phase II CAQH CORE 270: Connectivity Rule Table of Contents REVISION HISTORY FOR PHASE II CORE CONNECTIVITY RULE... 4 1 BACKGROUND... 5 1.1 Guiding Principles... 5 2 ISSUES TO BE ADDRESSED AND BUSINESS

More information

Electronic Transaction Manual for Arkansas Blue Cross Blue Shield

Electronic Transaction Manual for Arkansas Blue Cross Blue Shield Electronic Transaction Manual for Arkansas Blue Cross Blue Shield HIPAA Transaction Companion Document Guide Refers to the X12N Implementation Guides: 004010X092A1: (270/271) Health Care Eligibility Benefit

More information

It is recommended not to exceed 99 patient requests per Information Receiver Loop (2000B).

It is recommended not to exceed 99 patient requests per Information Receiver Loop (2000B). ASC X12N 270/271 (004010X092A1) Health Care Eligibility Benefit Inquiry and Response Companion Guide Notes The ISA segment terminator, which immediately follows the component element separator, must consist

More information

Electronic Transaction Manual for Arkansas Blue Cross and Blue Shield FEDERALEMPLOYEEPROGRAM (FEP) DentalClaims

Electronic Transaction Manual for Arkansas Blue Cross and Blue Shield FEDERALEMPLOYEEPROGRAM (FEP) DentalClaims Electronic Transaction Manual for Arkansas Blue Cross and Blue Shield FEDERALEMPLOYEEPROGRAM (FEP) DentalClaims HIPAA Transaction Companion Document Guide Refers to the X12N Implementation Guide: 005010X224A2:

More information

WEDI Acknowledgement Recommendations

WEDI Acknowledgement Recommendations Acknowledgement Recommendations For ASC X12N Implementation Guides, Interchange Level through Conformance Checking Version 4.0 July 2008 Enclosure 2 Workgroup for Electronic Data Interchange 12020 Sunrise

More information

Blue Cross Blue Shield of Delaware

Blue Cross Blue Shield of Delaware Highmark Standard Companion Guide Blue Cross Blue Shield of Delaware Instructions related to Employer/Sponsor Transactions based on ASC X12 Implementation Guides, version 005010 Companion Guide Version

More information

Prepared by the Minnesota Administrative Uniformity Committee (AUC)

Prepared by the Minnesota Administrative Uniformity Committee (AUC) Claim and Remittance ACKNOWLEDGMENTS BEST PRACTICE Prepared by the Minnesota Administrative Uniformity Committee (AUC) This Best Practice is intended for use with the corresponding MN Uniform Companion

More information

ANSI ASC X12N 277 Claims Acknowledgement (277CA)

ANSI ASC X12N 277 Claims Acknowledgement (277CA) ANSI ASC X12N 277 Claims Acknowledgement (277CA) Acute Care Long Term Care Encounters COMPANION GUE February 28, 2012 Texas Medicaid & Healthcare Partnership Page 1 of 23 Print Date: 1/10/2013 Table of

More information

835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1

835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1 835 Health Care Claim Payment and Remittance Advice Companion Guide 004010 X091A1 Version 1.3 March 1, 2008 1-March-2008 TABLE OF CONTENTS 1 Introduction... 1 1.1 Purpose... 1 2 Transmission and Data Retrieval

More information

Companion Guide Institutional Billing 837I

Companion Guide Institutional Billing 837I Companion Guide Institutional Billing 837I Release 3 X12N 837 (Version 5010A2) Healthcare Claims Submission Implementation Guide Published December 2016 Revision History Date Release Appendix name/ loop

More information

Companion Guide Benefit Enrollment and Maintenance 834

Companion Guide Benefit Enrollment and Maintenance 834 Companion Guide Benefit Enrollment and Maintenance 834 Private Exchanges X12N 834 (Version 5010) X12N 834 (Version 5010)Healthcare Services Review Benefit Enrollment and Maintenance Implementation Guide

More information

270/271 Benefit Eligibility Inquiry/Response Transactions Companion Guide ANSI ASC X12N 270/271 (Version 4010A)

270/271 Benefit Eligibility Inquiry/Response Transactions Companion Guide ANSI ASC X12N 270/271 (Version 4010A) 270/271 Benefit Eligibility Inquiry/Response Transactions ANSI ASC X12N 270/271 (Version 4010A) State of Washington Department of Social & Health Services Prepared by: CNSI 3000 Pacific Avenue S.E. Suite

More information

Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837

Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837 Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837 Version 1.4 Final RECORD OF CHANGE VERSION NUMBER DATE REVISED DESCRIPTION OF CHANGE PERSONS INVOLVED 1.0 10/25/02 Creation and first view by

More information

EDI Functional Acknowledgment

EDI Functional Acknowledgment EDI 997 - Functional Acknowledgment VERSION: 1.0 FINAL Author: Created: Best Buy E-Business July 09, 2003 12:24 PM 997 EDI X12 4030 Document.rtf 1 For internal only 997 Functional Acknowledgment Functional

More information

837 Superior Companion Guide

837 Superior Companion Guide 837 Superior Companion Guide Refers to the Implementation Guides based on the HIPAA Transaction ASC X12N. Standards for Electronic Data Interchange X12N/005010x222 Health Care Claim: Professional (837P)

More information

General Companion Guide. Version Number: 1.4 September 16, 2003

General Companion Guide. Version Number: 1.4 September 16, 2003 Louisiana Medicaid General Companion Guide Version Number: 1.4 September 16, 2003 2003 CAQH and WEDI "The Companion Guide is the copyrighted work of CAQH and WEDI. More information may be obtained by visiting

More information

Mississippi Medicaid Companion Guide to the X279A1 Benefit Inquiry and Response Conduent EDI Solutions, Inc. ANSI ASC X12N 270/271

Mississippi Medicaid Companion Guide to the X279A1 Benefit Inquiry and Response Conduent EDI Solutions, Inc. ANSI ASC X12N 270/271 Mississippi Medicaid Companion Guide to the 005010X279A1 Benefit Inquiry and Response Conduent EDI Solutions, Inc. ANSI ASC X12N 270/271 OCT 2017 TABLE OF CONTENTS AT A GLANCE II CHAPTER 1: INTRODUCTION

More information

Express permission to use X12 copyrighted materials within this document has been granted.

Express permission to use X12 copyrighted materials within this document has been granted. 837 Companion Guide Refers to the Implementation Guides based on the HIPAA Transaction ASC X12N. Standards for Electronic Data Interchange X12N/005010x222 Health Care Claim: Professional (837P) and ASC

More information

Functional Acknowledgment - 997

Functional Acknowledgment - 997 997 Functional Acknowledgment - 4030 INBOUND Version: 1.0 Author: Modified: 03/06/2006 V4030 1 997 Functional Acknowledgment Functional Group=FA This Draft Standard for Trial Use contains the format and

More information

Streamline SmartCare Network180 EHR

Streamline SmartCare Network180 EHR Last modified 8/28/2016 Network180-Streamline837CompanionGuide20160818.doc Page 1 of 8 Streamline SmartCare Network180 EH HIPAA 837 Companion Guide for Direct Submitters (V 1.0 Updated 08/28/2016) Last

More information

Kentucky HIPAA HEALTH CARE PAYER UNSOLICITED CLAIM STATUS Companion Guide Unsolicited 277. Version 1.1

Kentucky HIPAA HEALTH CARE PAYER UNSOLICITED CLAIM STATUS Companion Guide Unsolicited 277. Version 1.1 Kentucky HIPAA HEALTH CARE PAYER UNSOLICITED CLAIM STATUS Companion Guide Unsolicited 277 Version 1.1 Released August 4, 2004 RECORD OF CHANGE VERSION NUMBER DATE REVISED DESCRIPTION OF CHANGE PERSONS

More information

Cabinet for Health and Family Services Department for Medicaid Services

Cabinet for Health and Family Services Department for Medicaid Services KyHealth Choices 277 Health Care Payer Unsolicited Claim Status (ASC X12N 277) Companion Guide Version 2.3 Version 003070 Cabinet for Health and Family Services Department for Medicaid Services August

More information

Unsolicited 277 Trading Partner Specification

Unsolicited 277 Trading Partner Specification Unsolicited 277 Trading Partner Specification Revision Summary: Revision Date Summary of Changes Number 1.0 3/20/2007 NPI changes in loop 2100C AmeriHealth U277 Unsolicited Health Care Claim Status Notification

More information

Overview. Express permission to use X12 copyrighted materials within this document has been granted.

Overview. Express permission to use X12 copyrighted materials within this document has been granted. 837 Companion Guide Refers to the Implementation Guides based on the HIPAA Transaction ASC X12N. Standards for Electronic Data Interchange X12N/005010x222 Health Care Claim: Professional (837P) and ASC

More information

INTERNET TRANSACTION SERVICES CORE

INTERNET TRANSACTION SERVICES CORE 11.19.2015 INTERNET TRANSACTION SERVICES CORE User Guide Version 1.0.2 CAQH CORE Operating Rules Connectivity Specification v2.2.0 Contents Contents 1 Introduction... 3 2 Specifications... 4 2.1 CORE Connectivity

More information

Guide to the X214 Claim Acknowledgement Conduent EDI Solutions, Inc.

Guide to the X214 Claim Acknowledgement Conduent EDI Solutions, Inc. Mississippi Medicaid Companion Guide to the 005010X214 Claim Acknowledgement Conduent EDI Solutions, Inc. ANSI ASC X12N 277CA October 2017 TABLE OF CONTENTS AT A GLANCE II CHAPTER 1: INTRODUCTION 3 Audience

More information

276/277 Claim Status Request and Response

276/277 Claim Status Request and Response 276/277 Claim Status Request and Response 276 & 277 Health Care Claim Status Request and Response 2 Overview 2 Connectivity Transmission Options 2 System Availability 3 Frequency of Data Exchange 3 Claim

More information

837 Dental Health Care Claim

837 Dental Health Care Claim Companion Document 837D 837 Dental Health Care Claim Basic Instructions This section provides information to help you prepare for the ANSI ASC X12N 837 Health Care transaction for dental claims. The remaining

More information

To: Electronic Data Interchange (EDI) Partners:

To: Electronic Data Interchange (EDI) Partners: To: Electronic Data Interchange (EDI) Partners: Following are our Utility Industry Group compliant EDI 997 version 4010 guidelines for your use in implementing EDI. Page 16 contains a sample 997 for your

More information

837 Professional Health Care Claim. Section 1 837P Professional Health Care Claim: Basic Instructions

837 Professional Health Care Claim. Section 1 837P Professional Health Care Claim: Basic Instructions anthemeap.com Companion Document 837P This companion document is for informational purposes only to describe certain aspects and expectations regarding the transaction and is not a complete guide. The

More information

Quick Start Guide ATRIO HEALTH CARE ELIGIBILITY BENEFIT INQUIRY AND RESPONSE (270/ X279A1)

Quick Start Guide ATRIO HEALTH CARE ELIGIBILITY BENEFIT INQUIRY AND RESPONSE (270/ X279A1) Quick Start Guide ATRIO HEALTH CARE ELIGIBILITY BENEFIT INQUIRY AND RESPONSE (270/271 005010X279A1) PH Tech Version: 1.0 (Beta) I. Introduction PH Tech currently supports access to certain data by 3rd

More information

Gold Coast Health Plan Healthcare Claim: 837 Companion Guide. Versions: X222A X223A2

Gold Coast Health Plan Healthcare Claim: 837 Companion Guide. Versions: X222A X223A2 Gold Coast Health Plan Healthcare Claim: 837 Companion Guide Versions: 005010X222A1 005010X223A2 Updated December 30, 2016 2016 Conduent Business Services, LLC. All rights reserved. Conduent and Conduent

More information

BlueCross BlueShield of Tennessee

BlueCross BlueShield of Tennessee BlueCross BlueShield of Tennessee ASC X12N 270/271 (005010X279A1) Health Care Eligibility Benefit Inquiry and Response BlueCORE Phase II System Companion Guide Version 2.0 November 2011 November 2011 1

More information

ENCOUNTER DATA 101 THURSDAY, AUGUST 7, :00 PM 4:00 PM ET

ENCOUNTER DATA 101 THURSDAY, AUGUST 7, :00 PM 4:00 PM ET ENCOUNTER DATA 101 THURSDAY, AUGUST 7, 2014 3:00 PM 4:00 PM ET 1 Encounter Data Acronyms Acronym CEM EDDPPS EDFES EDIPPS EDPPPS EDPS EDS EODS DMEPOS Terminology Common Edits and Enhancements Module Encounter

More information

Real-Time Connectivity Specifications For. 270/271 and 276/277 Inquiry Transactions

Real-Time Connectivity Specifications For. 270/271 and 276/277 Inquiry Transactions Real-Time Connectivity Specifications For 270/271 and 276/277 Inquiry Transactions United Concordia Dental (UCD) March 22, 2018 1 Contents 1. Overview 2. Trading Partner Requirements 3. Model SOAP Messages

More information

Pennsylvania PROMISe Companion Guide

Pennsylvania PROMISe Companion Guide Pennsylvania Companion Guide Unsolicited 277 Claim Response Version 5010 September 2010 Version 1 Pennsylvania PROMISe Unsolicited 277 Claim Companion Guide This page intentionally left blank. September

More information

Mastering HIPAA 5010 EDI Implementation Guides and EZ-EDI Mapping. Christian Ulangca (Sr. EDI Analyst) Rini Jose (Product Manager)

Mastering HIPAA 5010 EDI Implementation Guides and EZ-EDI Mapping. Christian Ulangca (Sr. EDI Analyst) Rini Jose (Product Manager) Mastering HIPAA 5010 EDI Implementation Guides and EZ-EDI Mapping Christian Ulangca (Sr. EDI Analyst) Rini Jose (Product Manager) What is HIPAA 5010? The 1996 HIPAA legislation required the US Department

More information

EFS 997 Functional Acknowledgment X12/V4010/997: 997 Functional Acknowledgment Version: 1.3

EFS 997 Functional Acknowledgment X12/V4010/997: 997 Functional Acknowledgment Version: 1.3 EFS 997 Functional Acknowledgment X12/V4010/997: 997 Functional Acknowledgment Version: 1.3 Author: EFS Network Created: June 17, 2003 Modified: 06/18/2003 EFS_997v1.3.ecs 1 For internal use only 997 Functional

More information

Standard Companion Guide

Standard Companion Guide Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 005010X222A1 Health Care Claim Professional (837P) Companion Guide Version Number 4.0 January 5, 2018 Page 1 of 18 CHANGE

More information