Vendor Interface Specification

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

Alabama Medicaid Vendor Interface Specifications

Eligibility Gateway Companion Guide

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

If a claim was denied (or rejected on a TA1, 997, or 824), do not submit a reversal or replacement claim. Submit a new original claim.

Batch Eligibility Long Term Care claims

WV MMIS EDI File Exchange User Guide Version 1.0 West Virginia Trading Partner Account Electronic Data Interchange (EDI) File Exchange User Guide

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

BULLETIN BOARD SCREENS for HIPAA (BBS) UPDATED JULY 22, Once connected, the first screen displays the node number that you are connected to.

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

Inland Empire Health Plan

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

Indiana Health Coverage Programs

220 Burnham Street South Windsor, CT Vox Fax

PAYER ID NUMBER SPECIAL NOTES. ELECTRONIC REGISTRATIONS Agreements Required SEND ENROLLMENT FORMS TO: ENROLLMENT CONFIRMATION

Electronic Transaction Manual for Arkansas Blue Cross Blue Shield

USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270

MISSISSIPPI MEDICAID DENTAL ELECTRONIC CLAIMS ENROLLMENT REGISTRATION

Health Care Connectivity Guide

835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1

220 Burnham Street South Windsor, CT Vox Fax OREGON MEDICAID DENTAL ELECTRONIC CLAIMS ENROLLMENT REGISTRATION

220 Burnham Street South Windsor, CT Vox Fax

Administrative Services of Kansas (ASK)

EDS Attn: EDI Unit P.O. Box 2991 Hartford, CT

837 Health Care Claim Professional, Institutional & Dental Companion Guide

TRISPAN HEALTH SERVICES ANSI v4010a1

220 Burnham Street South Windsor, CT Vox Fax

MICHIGAN DEPARTMENT OF COMMUNITY HEALTH. ELECTRONIC SUBMISSION MANUAL March 2013

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

Mississippi Medicaid. Mississippi Medicaid Program Provider Enrollment P.O. Box Jackson, Mississippi Complete form and mail original to:

Quick Reference Guide. Online Courier: File Transfer Protocol (FTP) Signing On. Using FTP Pickup

Cabinet for Health and Family Services Department for Medicaid Services

West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270

X D I A L U P. X12 (HIPAA) Dial-up Transmission System. Document Version

This bulletin provides additional information about the change in First Steps (FS) processors as outlined in BT dated February 3, 2006.

Louisiana Medicaid Management Information System (LMMIS)

Connecticut interchange MMIS

ANSI ASC X12N 837 Healthcare Claim Companion Guide

EDI Electronic Funds Transfer (EFT) and Electronic Remittance Advice (ERA) Online Enrollment Instructions

PROVIDER PORTAL. NEW USER/REFRESHER LEARNING PROVIDER PORTAL OVERVIEW Module

Administrative Services of Kansas (ASK)

220 Burnham Street South Windsor, CT Vox Fax

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

ANSI ASC X12N 835 Healthcare Claim Institutional, Professional and Dental Department of Labor-OWCP Companion Guide. May 31, 2017

Change Healthcare ERA Provider Information Form *This form is to ensure accuracy in updating the appropriate account

MoveIT DMZ User Guide

The HTTP protocol. Fulvio Corno, Dario Bonino. 08/10/09 http 1

Real-Time Connectivity Specifications

Billing Workshop for Targeted Case Management (TCM) Non-Contracted Providers

TRADING PARTNER ID ENROLLMENT

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

Trading Partner Account (TPA) Registration and Maintenance User Guide. for. State of Idaho MMIS

MEDICAID MARYLAND PART A (MCDMD) PRE-ENROLLMENT INSTRUCTIONS

Integration Guide for Data Originators of Claim Status. Version 1.1

Blue Cross Blue Shield of Louisiana

MEDICAID MARYLAND PRE-ENROLLMENT INSTRUCTIONS MCDMD

HIPAA 837 Claims EDI Agreement. Agreement. HIPAA 837 Claims EDI Agreement

TRICARE West Region Electronic Data Interchange PO Box Augusta, GA Fax:

BLUE CROSS AND BLUE SHIELD OF LOUISIANA PROFESSIONAL CLAIMS COMPANION GUIDE

Alameda Alliance for Health

Change Healthcare ERA Provider Information Form *This form is to ensure accuracy in updating the appropriate account

Nasuni Data API Nasuni Corporation Boston, MA

Companion Guide Institutional Billing 837I

TRICARE PGBA, LLC Electronic Data Interchange PO Box Augusta, GA Fax: Phone , Option #2

MyCare Ohio Provider Portal User Guide May, 2014

Change Healthcare ERA Provider Information Form *This form is to ensure accuracy in updating the appropriate account

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

1304 Vermillion Street Hastings, MN Ph Fax

TEXAS MEDICARE (TRAILBLAZERS) CHANGE FORM MR085

MEDICAID MARYLAND PRE ENROLLMENT INSTRUCTIONS MCDMD

Easthampton Savings Bank Online Business Banking User Guide

Companion Guide Benefit Enrollment and Maintenance 834

MEDICARE Texas (TRAILBLAZERS) PRE-ENROLLMENT INSTRUCTIONS 00900

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

[MS-INFODCF]: InfoPath Data Connection File Download Protocol. Intellectual Property Rights Notice for Open Specifications Documentation

Nasuni Data API Nasuni Corporation Boston, MA

Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837

Louisiana Medicaid Management Information System (LMMIS)

EDI-ERA Provider Agreement and Enrollment Form (Page 1 of 5)

EZClaim Premier ANSI 837P TriZetto Clearinghouse Manual

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

Appendix A Vendor Specifications for. State of Idaho MMIS

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

HTTPS File Transfer. Specification

Updating Astea Mobile URLs

Optum Clearinghouse (also known as ENS) ICD-10 Testing. February 28, 2014 External Client Document

Meaningful Use Registration System User Guide

98 - Professional (Physician) Visit - Office

220 Burnham Street South Windsor, CT Vox Fax

2. GETTING STARTED A. Secure File Transfer Protocol Procedures

Texas Medicaid EDI CONNECTIVITY GUIDE

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

BUSINESSMAIL X.400 WEB INTERFACE AS2 GATEWAY V2.9

UB-04/ INSTITUTIONAL FALL WORKSHOP 2013

Provider Electronic Solutions Upgrade Instructions

Florida Blue Health Plan

Change Healthcare CLAIMS Provider Information Form *This form is to ensure accuracy in updating the appropriate account

Pennsylvania PROMISe Companion Guide

Louisiana Medicaid Management Information System (LMMIS)

DentaQuest HIPAA Transaction Standard Companion Guide

Transcription:

Connecticut XIX HIPAA Translator Vendor Interface Specification DXC Technology 195 Scott Swamp Road Farmington, CT 06032, USA Page 1 of 31 Version 4.0 -- Approval Date November April 10, 2017

Table of Contents 1. Introduction... 3 1.1. Purpose... 3 1.2. Background... 4 1.2.1. HIPAA Batch Transactions Processing... 4 1.2.2. Web Interface... 5 1.2.3. Client software... 5 1.2.4. Connecting to the server... 5 1.2.5. File Upload... 6 1.2.6. Directory List... 9 1.2.7. Download a File... 13 Appendix A - Revision Log... 16 Appendix B - Current Format / Interchange Format Cross Reference... 17 Page 2 of 31

1. Introduction 1.1. Purpose This document is intended for Software Vendors to use in order to develop applications to interact with the State interchange Medicaid system and upload and download HIPAA compliant transactions in batch mode. Appendix B contains format cross reference material to assist vendors that have software written to interface with the legacy Medicaid system. This appendix identifies the interface specification changes between the existing Medicaid system and the interchange processing system going online January 2008. Note that this document provide specifications for transaction exchange in batch only. Connecticut EDI Department: 1-800-688-0503 Page 3 of 31

1.2. Background 1.2.1. HIPAA Batch Transactions Processing Each State is prepared to accept files in the HIPAA approved formats. However, not all HIPAA transaction types are accepted by the file upload/download process for each state. Other transaction types may be supported in different ways by each state, such as through interactive processing. Refer to the chart below for which transaction types are currently accepted. Note that this chart refers only to batch transaction exchange: State 270 271 276 277 278RQ / 278RS P 820 834 835 837 D 837 I 837P Connecticut A S A S A/S S S S A A A Legend: A The state will accept these transactions S The state will send these transactions N The state will not exchange these transactions Page 4 of 31

1.2.2. Web Interface The web interface is designed to support batch file uploads and downloads. There are two ways to use this interface. The first way is to logon to the secure web site using a trading partner user id and password. This web site has web pages which allow users to upload and download files. The second way is to use a software program that runs on a users PC or on a users server that connects to the secure trading partner web services. This site sends a request using the HTTPS protocol containing information which includes the trading partner user id, password, and the request data. The request data can include a request for a listing of files available for download, a specific file name to downloaded, or a file to upload. The files can be transferred in compressed format or in standards ASCII text format. All data is transferred using the Secure Socket Layer (SSL) which encrypts the data over the network. 1.2.3. Client software The client software can be written in any language that supports HTTPS for communicating with the trading partner web services. The data files transferred from and to the web services are in the HIPAA standard formats. 1.2.4. Connecting to the server To connect to the web application you first must have a network connection that provides access to the public internet. If your connection requires proxy server to connect to the Internet this needs to be configurable in your application. Once connected use the URL in table 1 to establish a connection with the applications. It is recommended that this URL not be hard coded as part of your application and be configurable instead. All of the transactions will require the connection be made using the Secure Socket Layer (SSL). Programming languages such as Visual Basic have other ways to connect using SSL, such as by using the WinInet libraries that are a part of Microsoft Windows. Send test transaction files to the production URL using the standard X12N Test identifier in the transactions file. Table 1. State Connecticut Root URL https://www.ctdssmap.com/ctportal/desktopmodules/ic_portal_pesinterface/ To access the specific web applications append the URL as identified in table 2. Table 2. Web Application File Upload Directory List File Download URL PESUpload.aspx PESFileList.aspx PESGetFile.aspx?sak_download= Page 5 of 31

1.2.5. File Upload The file upload function uses standard HTTPS request. User ID, password and other required parameters must be embedded in the HTTP header. The file is sent in the http request body as data stream. The interface returns a message in XML format. URL: https:// <Root URL>/PESUpload.aspx Table 3. File upload HTTP Header Description Property Name Header Property Description Length Require user_name password filename The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: Xyzuser. This field should be at most 20 characters, and must begin with an alpha character. The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 Format: The password must be between 7 and 30 characters, and must contain at least 3 of these 4 character types: Upper Case letter, Lower Case letter, Nmber and Special Character. The path and name of the file being uploaded. Sample Data: d:\myfile.dat 6-20 Y 6-8 Y 1-256 Y Table 4. File Upload Response XML Message Description Element Attribute Response XML Message Description success passwordexpired Returned as single node in XML format. BatchId is a reference for the file is uploaded. Sample: <success batchid='170516875'/> Returned as single node in XML format. Sample: <passwordexpired /> Page 6 of 31

Element Attribute Response XML Message Description error message If error has occurred during the process, an error message is returned in XML format. Messages: o Invalid ID/password. Please try again. o User account has been disabled. Please call help desk to reset. o User account has been locked. Please call help desk to reset. o An error occurred during the file upload. o Upload URI not found. o PI record not found. o Error determining transaction type. File transfer aborted. Sample: <error message=' Upload URI not found ' /> Page 7 of 31

Sample HTTP file upload request: Accept-Language: en Proxy-Connection: Keep-Alive User-Agent: ecseagle user_name: trade123 password: password01 Host: www.ctdssmap.com ISA*00* *00* *ZZ*100350619A *ZZ*00005 *061011*1049*U*00401*000000183*0*P*:~GS*HC*100350619A*00005*20061011*1049*183*X*004010X098A1~ST*8 37*000000001~BHT*0019*00*PES183*20061011*1049*CH~REF*87*004010X098A1~NM1*41*1*LANE*TESTING****46* KATBLANE~PER*IC*LANE*TE*9726044999~NM1*40*2*KANSAS MEDICAL ASSISTANCE PROGRAM*****46*00005~HL*1**20*1~PRV*BI*ZZ*3747P1801X~NM1*85*1*LANE*TESTING****34*123456789~N3*540 0 LEGACY DR~N4*PLANO*TX*75024~REF*1D*100350619A~HL*2*1*22*0~SBR*P*18*******MC~NM1*IL*1*BONNER*JILL****MI*0 0000041889~N3*1234 5TH ST~N4*MADISON*WI*537130000~DMG*D8*19800525*F~NM1*PR*2*KANSAS MEDICAL ASSISTANCE PROGRAM*****PI*48-6029925~CLM*999*150***11::1*Y*C*Y*Y*B~HI*BK:1111~LX*1~SV1*HC:90050*150*UN*1*11**1~DTP*472*RD8*200 61011-20061011~REF*6R*1~CLM*999*150***11::1*Y*C*Y*Y*B~HI*BK:1111~LX*1~SV1*HC:90050*150*UN*1*11**1~DTP*4 72*RD8*20061010-20061010~REF*6R*1~CLM*999*150***11::1*Y*C*Y*Y*B~HI*BK:1111~LX*1~SV1*HC:90050*150*UN*1*11**1~DTP*4 72*RD8*20061010-20061010~REF*6R*1~CLM*999*150***11::1*Y*C*Y*Y*B~HI*BK:1111~LX*1~SV1*HC:90050*150*UN*1*11**1~DTP*4 72*RD8*20061010-20061010~REF*6R*1~CLM*999*150***11::1*Y*C*Y*Y*B~HI*BK:1111~LX*1~SV1*HC:90050*150*UN*1*11**1~DTP*4 72*RD8*20061010-20061010~REF*6R*1~CLM*999*150***11::1*Y*C*Y*Y*B~HI*BK:1111~LX*1~SV1*HC:90050*150*UN*1*11**1~DTP*4 72*RD8*20061010-20061010~REF*6R*1~SE*56*000000001~GE*1*183~IEA*1*000000183~ Sample HTTP Response from file upload request: HTTP/1.1 200 OK Server: Microsoft-IIS/5.1 Date: Wed, 11 Oct 2006 15:49:45 GMT X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Transfer-Encoding: chunked Cache-Control: private Content-Type: text/html <success batchid='170516875'/> Sample HTTP Response with error from file upload Request: HTTP/1.1 200 OK Date: Fri, 04 Jan 2008 02:01:16 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 58 <error message= 'An error occurred during the file upload.'/> Page 8 of 31

1.2.6. Directory List The directory list message is an XML formatted message sent over HTTPS. The reason for doing a directory list is to get the sak of any available files for downloading. The sak_download key must be specified in the download url as querystring in order to get the file. The interface returns a message in XML format contains all available files in the download directory. URL: https://<root URL>/PESGetFile.aspx?sak_download=1234 Table 5. Directory List HTTP Header Description Property Name Header Property Description Length Require user_name Password The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: xyzuser. This field should be at most 20 characters, and must begin with an alpha character. The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 Format: The password must be between 7 and 30 characters, and must contain at least 3 of these 4 character types: Upper Case letter, Lower Case letter, Nmber and Special Character. 6-20 Y 6-8 Y Table 6. Directory Listing Response XML Description Element Attribute Response XML Message Description file sak_download System generated key that is used to identify the file can be downoaded. Sample Data: 222222222 Format: Numeric filename Name of the file that is stored in the system. Sample Data: 9856_9855_5FCCA113_999X12BATCH_0_100000041. 999 Page 9 of 31

Element Attribute Response XML Message Description shortname cde_identification dte_available dte_downloaded Short name of the transaction type. Sample Data: Functional Ack Code that identifies the document type Required value: 999_X12_BATCH Date and time that the file is made available on the file server. Sample Data: 6/25/2007 12:00:00 AM Format: Numeric Date and time that the file is downloaded Sample Data: 6/25/2007 12:00:00 AM Format: Numeric Table 7. Directory Listing Response Error Message Description Element Attibute Response XML Error Message Description passwordexpired Returned as single node in XML format. Sample: <passwordexpired /> error message If error has occurred during the process, an error message is returned in XML format. Messages: o Invalid ID/password. Please try again. o User account has been disabled. Please call help desk to reset. o User account has been locked. Please call help desk to reset. o An error occurred during the List Files process. Sample: <error message='user account has been locked. Please call help desk to reset.' /> Page 10 of 31

Sample HTTP Request for Directory Listing: Accept-Language: en Proxy-Connection: Keep-Alive User-Agent: ecseagle user_name: trade123 password: password01 Host: www.ctdssmap.com Sample HTTP Response from Directory Listing Request: Accept-Language: en Proxy-Connection: Keep-Alive User-Agent: ecseagle user_name: trade123 password: password01 Host: www.ctdssmap.com <files> <file sak_download="251910" filename="11917_11915_0b828945_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="7/10/2007 12:00:00 AM" dte_downloaded="7/10/2007 10:51:11 PM" /> <file sak_download="251886" filename="11788_11787_2dcd4265_ta1x12batch_0_100000041.ta1" shortname="interchange Ack " cde_identification="ta1_x12_batch" dte_available="7/10/2007 12:00:00 AM" dte_downloaded="7/10/2007 8:41:02 AM" /> <file sak_download="251873" filename="11702_11701_455137d0_ta1x12batch_0_100000041.ta1" shortname="interchange Ack " cde_identification="ta1_x12_batch" dte_available="7/9/2007 12:00:00 AM" dte_downloaded="1/1/1900 12:00:00 AM" /> <file sak_download="251781" filename="11274_11273_15169940_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="7/5/2007 12:00:00 AM" dte_downloaded="7/6/2007 10:20:42 AM" /> <file sak_download="251766" filename="11224_11223_8a6a3e82_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="7/4/2007 12:00:00 AM" dte_downloaded="7/4/2007 4:24:11 PM" /> <file sak_download="251722" filename="10994_10993_dab7a096_ta1x12batch_0_100000041.ta1" shortname="interchange Ack " cde_identification="ta1_x12_batch" dte_available="7/2/2007 12:00:00 AM" dte_downloaded="7/2/2007 11:35:41 PM" /> <file sak_download="251573" filename="10166_10160_db9f5ad3_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="6/27/2007 12:00:00 AM" dte_downloaded="7/3/2007 4:48:37 PM" /> <file sak_download="251572" filename="10165_10159_4e7fdafe_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="6/27/2007 12:00:00 AM" dte_downloaded="7/3/2007 4:48:37 PM" /> <file sak_download="251571" filename="10164_10158_7202d753_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="6/27/2007 12:00:00 AM" dte_downloaded="7/3/2007 4:48:38 PM" /> <file sak_download="251569" filename="10162_10156_da2599f8_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="6/27/2007 12:00:00 AM" dte_downloaded="7/2/2007 11:03:36 PM" /> <file sak_download="251558" filename="10096_10095_386044f9_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="6/26/2007 12:00:00 AM" dte_downloaded="6/28/2007 9:03:19 AM" /> <file sak_download="251557" filename="10094_10092_6bbd6cdb_999x12batch_0_100000041.999" shortname="functional Ack " cde_identification="999_x12_batch" dte_available="6/26/2007 12:00:00 AM" dte_downloaded="7/2/2007 11:07:34 PM" /> </files> Page 11 of 31

Sample HTTP Response with error from Directory Listing Request: HTTP/1.1 200 OK Date: Fri, 04 Jan 2008 02:01:16 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 58 <error message= 'An error occurred during the List Files process.'/> Page 12 of 31

1.2.7. Download a File The download a file message is an HTTP request sent over HTTPS. A file name from the directory listing response is used to request the file to download. SAK_DOWNLOAD must be specified in the download url as querystring in order to get the file. URL: https://<root URL>/ PESGetFile.aspx?sak_download={sak_download} Table 8. Download File Request Message Description Proerty Name Header Property Description Length Require user_name Password The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: Xyzuser. This field should be at most 20 characters, and must begin with an alpha character. The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 Format: The password must be between 7 and 30 characters, and must contain at least 3 of these 4 character types: Upper Case letter, Lower Case letter, Nmber and Special Character. 6-20 Y 6-8 Y QueryString Name Description Length Require sak_download System generated key that is used to indentify the file can be downoaded. Sample Data: 256499 Format: Numeric 9 Y Page 13 of 31

Table 9. Download File Response Error Message Description Element Attribute Response XML Error Message Description passwordexpired Returned as single node in XML format. Sample: <passwordexpired /> error message If error has occurred during the process, an error message is returned in XML format. Messages: o Invalid ID/password. Please try again. o User account has been disabled. Please call help desk to reset. o User account has been locked. Please call help desk to reset. o File to download was not specified in the request. o File to download is not found. o Download URI not found. o Could not download file: {filename} Sample: <error message='download URI not found ' /> Page 14 of 31

Sample HTTP Request for a file download: Accept-Language: en Proxy-Connection: Keep-Alive User-Agent: ecseagle user_name: trade123 password: password01 Host: www.ctdssmap.com Sample HTTP Response from Download file Request: HTTP/1.1 200 OK Date: Fri, 04 Jan 2008 01:37:59 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Content-Disposition: attachment; filename=81593_81592_8c6d1561_999x12batch_0_100000041.999 Transfer-Encoding: chunked Cache-Control: private Content-Type: text/plain ISA*00* *00* *ZZ*123456789 *ZZ*100000041 *071025*1320*U*00401*000000010*0*T*:~GS*FA*445498161*100000041*20071025*13204268*7*X*004010~ST*99 9*7001~AK1*HC*129~AK2*837*000000001~AK5*A~AK9*A*1*1*1~SE*6*7001~GE*1*7~IEA*1*000000010~ Sample HTTP Response with error from Download file Request: HTTP/1.1 200 OK Date: Fri, 04 Jan 2008 02:01:16 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 58 <error message= 'Download URI not found.'/> Page 15 of 31

Appendix A - Revision Log Amendment History - Document Status (e.g. Draft, Final, Release #): Document Version # Approval Date Modified By Section, Page(s)and Text Revised Page 16 of 31

Appendix B - Current Format / Interchange Format Cross Reference This appendix serves as a transition guide to assist software vendors that currently have automated data exchanges in place with the Legacy Medicaid billing system. The intent of the appendix is to highlight the specification changes between the Legacy system and the new Medicaid system. The changes are presented in the following tables. Legacy system specifications are documented under column header Legacy System Interface and the corresponding interchange specification on the right under column header interchange Interface. Table 10. This table documents the changes to the URL were data is uploaded/downloaded Legacy System Interface InterChange Interface State Root URL Root URL Connecticut Production www.ctmedicalprogram.com Test www.ctmedicalprogram.com/test https://www.ctdssmap.com/ctportal/desktopmodules/ic_portal_pesinterface/ Table 11. Documents the name changes to the web application Legacy System Interface InterChange Interface Web Application URL Suffix URL Suffix File Upload /secure/webuploadfromclient PESUpload.aspx Directory List /secure/webdirectorydownloadfromclient PESFileList.aspx File Download /secure/webdownloadfromclient PESGetFile.aspx?sak_download= Version 4.0 -- Approval Date November April 10, 2017 Page 17 of 31

Table 12. File Upload Request Legacy System Interface interchange Interface Element XML Message Description Length Require Property Name Header Property Description Length Require TradingPartnerId The Trading Partner Id is used to identify whom the transaction is for. The Id, along with the User Id and Password, is used to authenticate the user. 3-35 Y n/a Not used Sample Data: 222222222 UserId The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: xyzuser 3-15 Y user_name The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: xyzuser 6-20 Y Password The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 6-8 Y password The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 6-8 Y Page 18 of 31

Function This is the Upload file function name. This value must always be filled with UPLOADFILE to be a valid request. 10 Y n/a Not used Required value: UPLOADFILE FileName The path and name of the file being uploaded. Sample Data: d:\myfile.dat 1-256 Y FileName The path and name of the file being uploaded. Sample Data: d:\myfile.dat 1-256 Y FileSize Specifies the size of the file. The size is compared against the actual size of the file uploaded to ensure no data is lost. If the file is in a zipped format, this is the zipped file size. 8 Y n/a Not used Sample Data: 1022 Format: Numeric Page 19 of 31

Table 12. File Upload Request (continued) Legacy System Interface Element XML Message Description Length Require Property Name MapGroup Specifies the MapGroup name to be passed to the translator that should be used to process the file. This is an situational element and is not required to be sent for HIPAA X12N Transaction Files. If this element is used for HIPAA X12N Transaction Data Files, the value must be entered as X12INPUT (the default value) or the file will not be processed or will be processed incorrectly. For non-hipaa X12N Transaction Data Files, DXC Technology will specify the value to be used. A valid value must be entered as specified by DXC Technology or the file will not be processed or will be processed incorrectly. Default Value if not sent : X12INPUT Sample Data: X12INPUT 1-40 N n/a Not used interchange Interface Header Property Description Length Require Page 20 of 31

Table 12.1. File Upload Response Legacy System Interface interchange Interface Element XML Message Description Length Required Element Attribute Response XML Description n/a Not used success batchid Returned as single node in XML format. BatchId is a reference for the file is uploaded. Sample: <success batchid='170516875'/> passwordexpired n/a Returned as single node in XML format. error message Sample: <passwordexpired /> If error has occurred during the process, an error message is returned in XML format. Messages: o Invalid ID/password. Please try again. o User account has been disabled. Please call help desk to reset. o o o o o User account has been locked. Please call help desk to reset. An error occurred during the file upload. Upload URI not found. PI record not found. Error determining transaction type. File transfer aborted. Page 21 of 31

Table 13. File Listing Request Legacy System Interface interchange Interface Element XML Message Description Lengt h TradingPartnerId UserId Password The Trading Partner Id is used to identify whom the transaction is for. The Id is used to limit the list of files in the directory list to only those belonging to this Trading Partner. The Trading Partner Id is cross validated against the User Id and the User Id must be authorized to submit requests for this Trading Partner Id. Sample Data: 222222222 The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: xyzuser The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 Requi re Property Name 3-35 Y n/a Not used Header Property Description 3-15 Y user_name The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: xyzuser 6-8 Y Password The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 Lengt h 6-20 Y 6-8 Y Requi re Page 22 of 31

Function FilesToReturnCount This is the Directory List function name. This value must always be filled with DIRLIST to be a valid request. Required value: DIRLIST Specifies the maximum number of files to return in the directory list. If not included, then all files are returned. Sample Data: 50 Format: Numeric 7 Y n/a Not used 0-6 N n/a Not used Page 23 of 31

FileType This indicates the types of files you want returned in the directory list. For example, if you only want the 999 functional acknowledgments, you would specify a file type of 999. If you wanted 999 s and the 835 RA s then you specify two file types - one with 999 and the other with 835. Up to 10 file types can be specified at a time. If no file types are specified, then all types are returned. Valid types may be State Specific. Here is a list of possible types: 3 N n/a Not used 271 Eligibility Response 277 Claim Status Response 278 Service Review Request/Response 820 Health Plan Payment 834 Benefit Enrollment 835 Remittance Advice 999 Functional Acknowledgment SUB Submission Accept/Reject Report FileStatus, occurs up to 10 times Indicator to select files based on the following: A = All files N = New files only D = Previously downloaded files only 1 Y n/a Not used Page 24 of 31

FilesCreatedFromDate FilesCreatedToDate The file creation from date is used as a filter to only return files in the directory list which are greater than or equal to this date. If this element is not specified, all files are listed, up through the FileCreatedToDate if specified. Sample Data: 20020701 Format: 4 digit year, 2 digit month, 2 digit day The file creation to date is used as a filter to only return files in the directory list which are less than or equal to this date. If this element is not specified, all files are listed, equal to and greater than the FileCreatedFromDate if specified. If neither the from or to date element is specified, all files are returned in the directory list. Sample Data: 20020731 Format: 4 digit year, 2 digit month, 2 digit day 8 N n/a Not used 8 N n/a Not used Page 25 of 31

Table 14. File Listing Response Legacy System Interface interchange Interface Element XML Message Description Lengt h TradingPartnerId UserId The Trading Partner Id from the request. Sample Data: 222222222 The User Id from the request. Sample Data: xyzuser Requi re 3-35 Y files/file (top n/a element is <files>, child element is 3-15 Y <file>) n/a Element Attribute Response XML Description Function FilesReturnedCount The function from the request. Required value: DIRRESP The number of files returned in the directory listing. Sample Data: 50 Format: Numeric 7 Y n/a 1-6 Y n/a n/a sak_download System generated key that is used to indentify the file can be downoaded. Sample Data: 222222222 Format: Numeric Page 26 of 31

FileName The file name given to the file. This is a system generated name. This is the same name needed to request the file for download. Sample Data: 22222222220020702001 9-40 Y filename Name of the file that is stored in the system. Sample Data: 9856_9855_5FCCA113_999X12BA TCH_0_100000041.999 n/a shortname Short name of the transaction type. Sample Data: Functional Ack FileCreationDate The date the file was created. Sample Data: 20020701 Format: 4 digit year, 2 digit month, 2 digit day 8 Y dte_availa ble Date and time that the file is made available on the file server. Sample Data: 6/25/2007 12:00:00 AM Format: Numeric FileType This is the type of file. Sample Data: 999 3 Y cde_identi fication Code that identifies the document type Required value: 999_X12_BATCH FilesSize The size in bytes of the file in unzipped format. 2-8 Y n/a Sample Data: 50000 Format: Numeric LastDownloadDate The date the file was last downloaded. If the file has not been downloaded this is empty. Sample Data: 20020701 8 N dte_downlo aded Date and time that the file is downloaded Sample Data: 6/25/2007 12:00:00 AM Format: 4 digit year, 2 digit month, 2 digit day. Format: Numeric LastDownloadUserId This is the User Id of the last user to download the file. This is empty if the file hasn t been downloaded yet. 3-15 N n/a password Expired n/a Returned as single node in XML format. Sample: <passwordexpired /> Page 27 of 31

error message If error has occurred during the process, an error message is returned in XML format. Messages: o Invalid ID/password. Please try again. o User account has been disabled. Please call help desk to reset. o o User account has been locked. Please call help desk to reset. An error occurred during the List Files process. Page 28 of 31

Table 15. Download File Request Legacy System Interface interchange Interface Element XML Message Description Length Require Property Name TradingPartnerId UserId Password The Trading Partner Id is used to identify whom the transaction is for. The Trading Partner Id is cross validated against the User Id and the User Id must be authorized to submit requests for this Trading Partner Id. Sample Data: 222222222 The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: xyzuser The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 3-35 Y n/a Not used Header property Description 3-9 Y user_name The User Id is used to authenticate the user submitting the request. The User Id must be authorized to submit for the Trading Partner Id. Sample Data: xyzuser 6-8 Y Password The Password is used in conjunction with the User Id to ensure the validity of the user making the request. Sample Data: jmstp567 Querystring Name appends to the URL. n/a sak_download System generated key that is used to indentify the file can be downoaded. Sample Data: 256499 Format: Numeric Length Require 6-20 Y 6-8 Y 9 Y Page 29 of 31

Function FileName FileFormat This is the File Download function name. This value must always be filled with DOWNLOAD to be a valid request. Required value: DOWNLOAD Specifies the name of the file to download. The name can be found from the directory list request. Sample Data: 000000123 Specifies the file format you want the file downloaded in. Valid Values are: TXT Requests the file in standard ASCII Text format. ZIP Requests the file in zipped format. 8 Y n/a 9-40 N n/a 3 Y n/a Page 30 of 31

Table 15.1. Downlaod File Response Legacy System Interface interchange Interface Element XML Message Description Length Required Element Attribute Response Description passwordexpired n/a Returned as single node in XML format. error message Sample: <passwordexpired /> If error has occurred during the process, an error message is returned in XML format. Messages: o Invalid ID/password. Please try again. o User account has been disabled. Please call help desk to reset. o o o o o User account has been locked. Please call help desk to reset. File to download was not specified in the request. File to download is not found. Download URI not found. Could not download file: {filename} Page 31 of 31

2024 © technodocbox.com Privacy Policy | Terms of Service | Feedback