Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 1 of 44
eMedNY CORE Web
Services
Connectivity Guide
3/28/2014
Version 1.0
EMEDNY CORE WEB SERVICES
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 2 of 44
TABLE OF CONTENTS
1. Introduction ..................................................................................................................................................... 4
2. Requirements and Limitations ........................................................................................................................ 5
3. Envelope Specifications ................................................................................................................................... 6
4. Inbound Transaction Types ............................................................................................................................. 7
5. Responses to Inbound Files ............................................................................................................................. 8
5.1 Real-Time ................................................................................................................................................................ 8
5.2 Batch ....................................................................................................................................................................... 8
6. Retrieving eMedNY-Generated Files ............................................................................................................... 9
7. URL for CORE Web Services ........................................................................................................................... 10
8. Useful Links .................................................................................................................................................... 11
8.1 CAQH-CORE Standards for Web Services .............................................................................................................. 11
8.2 Web Portal Links ................................................................................................................................................... 11
8.2.1 Assistance enrollment in the Web Portal and activation of a “System User” .................................................................... 11
8.2.2 The Web Portal .................................................................................................................................................................. 11
8.3 X12 Information Links ........................................................................................................................................... 11
8.3.1 Information on the eMedNY X12 envelope (ISA and GS) ................................................................................................... 11
8.3.2 eMedNY Companion Guide for 270/271 and 276/277 ...................................................................................................... 11
8.3.3 eMedNY Companion Guide for the 835/820 ..................................................................................................................... 11
8.3.4 eMedNY Companion Guide for the 835S & 820S ............................................................................................................... 11
8.3.5 Washington Publishing Company ...................................................................................................................................... 12
8.4 Production URL for eMedNY CORE Web Services ................................................................................................. 12
8.5 Useful eMedNY Forms .......................................................................................................................................... 12
8.5.1 Certification Statement/Instructions for Existing ETINs .................................................................................................... 12
8.5.2 Electronic Remittance Advice Request .............................................................................................................................. 12
9. Change Log .................................................................................................................................................... 13
10. Appendix I – SOAP Web Services Description Language (WSDL) Updated 6/10/2014 ............................. 13
11. Appendix II – Web Services Schema Definition Updated 6/10/2014 ........................................................ 19
12. Appendix III - SOAP XML Request and Response Samples – updated 1/7/2020 ...................................... 27
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 3 of 44
12.1 Real-Time Examples .............................................................................................................................................. 27
12.1.1 SOAP XML Real-Time Request Example ......................................................................................................................... 27
12.1.2 SOAP XML Real-Time Response Example ...................................................................................................................... 28
12.2 Batch Examples ..................................................................................................................................................... 28
12.2.1 SOAP XML Batch Request Example with MTOM ........................................................................................................... 28
12.2.2 SOAP XML Batch Response Example with MTOM ......................................................................................................... 29
13. Appendix IV – Web Services MIME Request and Response Samples ........................................................ 30
13.1 eMedNY-Generated Response File Examples ....................................................................................................... 30
13.1.1 MIME Request File List 835 Example ............................................................................................................................. 30
13.1.2 X12 835 File List Response 005010X221A1 ................................................................................................................... 31
13.1.3 MIME Request 835 file .................................................................................................................................................. 33
13.1.4 X12 835 Response 005010X221A1 ................................................................................................................................ 34
14. Appendix V - Systems Changes due to migration ...................................................................................... 36
14.1 SOAP Responses .................................................................................................................................................... 36
14.1.1 SOAP MTOM Response .................................................................................................................................................. 37
14.2 MIME Responses ................................................................................................................................................... 39
For eMedNY Billing Guideline questions, please contact the eMedNY Call
Center through the contact information at the end of this document.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 4 of 44
1. Introduction
The eMedNY CORE Web Service is designed to facilitate the exchange of X12 270/271 Health Care Eligibility Benefit
Inquiry and Response information, and 276/277 Health Care Claim Status Request and Response information, for
interactive (real-time) transactions and batch files according to CORE standards. eMedNY CORE Web services can also
be used to retrieve both 835 and 820 remittance advice files.
CORE standards require the use of Hypertext Transfer Protocol Secure (HTTPS) over the public Internet. The X12
payload is required to be enclosed within a message envelope that meets the CORE standards for the following two
protocols:
• HTTP MIME Multipart
• SOAP + WSDL
The purpose of this document is to supply the needed data to connect to eMedNY’s CORE Web Services that adhere to
these standards. The general CORE Standards can be found at the following website:
http://www.caqh.org/pdf/CLEAN5010/270-v5010.pdf
All questions regarding connectivity and billing will go through the eMedNY Call Center at 1-800-343-9000. If necessary,
a ticket will be escalated to a call back unit.
Important Note: It is solely the responsibility of the submitter or user to develop or create their CORE Web Services
compliant application. eMedNY will in no way support the end user application, therefore it is strongly
recommended that the Trading Partner take appropriate action to have available technical support.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 5 of 44
2. Requirements and Limitations
The user will need a client that is compliant with the CORE Standards outlined on the CAQH-CORE website. eMedNY
cannot assist the user in coding this client, nor does eMedNY have sample code available.
In order to connect to eMedNY CORE Web Services, the user will need to obtain a “System User” Username and
Password from the eMedNY Web Portal. Enrollment in the Web Portal is explained in this document:
https://www.emedny.org/selfhelp/ProviderPortal/Enrolling_in_Web_Portal.pdf
Once you are enrolled in the Web Portal, use the following guide to create a System User:
https://www.emedny.org/selfhelp/ProviderPortal/CORE_Web_Services_Enrollment.pdf
The Username and password for eMedNY Core Web Services Transactions are sent in the envelope (MIME or SOAP) of
the transaction – this supplies the required authentication. The Web Services URL will not allow a transaction without a
correct Username and password.
eMedNY CORE Web Services will be available 24 hours a day, 7 days a week barring an outage or maintenance.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 6 of 44
3. Envelope Specifications
The envelope of the transaction must conform to CORE Version 2.2.0 standards as outlined on the CAQH-CORE website.
eMedNY has samples of the envelope for the supported transactions in the Appendix section of this document. Please
see Appendix II for SOAP + WSDL samples, and Appendix III for HTTP/MIME samples. The following items are specific to
eMedNY Web Services
• The Username and Password are the respective Username and Password of the System User sending the
transaction. A System User is set up via the Web Portal – see the links in Chapter 2 for more details.
• The eMedNY ReceiverID is “eMedNY.” Please note this instruction applies only to the envelope (SOAP or MIME)
of the transaction. The receiver ID within the X12 transaction should still meet eMedNY specifications as noted
in the eMedNY Trading Partner Information Standard Companion Guide
.
• The Payload ID conforms to CORE standards – for Batch transactions it is then used to retrieve the responses to
the inbound file.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 7 of 44
4. Inbound Transaction Types
Please refer to the eMedNY Transaction Information Standard Companion Guide CAQH - CORE Companion Guide for
additional information that is specific to New York State Medicaid.
eMedNY CORE Web Services will accept the following inbound Transaction types:
• eMedNY Interactive 270 – Real-Time Eligibility Inquiry
• eMedNY Interactive 276 – Real-Time Claim Status Inquiry
• eMedNY Batch 270 – Batch Eligibility Inquiry
• eMedNY Batch 276 – Batch Claim Status Inquiry
The envelope needs to contain a properly formatted X12 transaction in either 270 or 276 format. The X12 coding of
batch files sent through the File Transfer Service are exactly the same as for other transmission methods. Please refer to
the ASC X12 Standard Implementation Guides from Washington Publishing
to obtain the correct file and record formats
for inbound and outbound eMedNY transactions. The eMedNY Transaction Information Standard Companion Guide
CAQH - CORE Companion Guide supplies details specific to eMedNY 270 and 276 requests.
At this time, eMedNY CORE Web Services is limited to 1 Real-Time Transaction per second and two batch files per
minute. Batch files are limited in size according to the transaction limits in the Implementation guide from Washington
Publishing. eMedNY places no further limits on batch files. However, please keep in mind that the larger the file is the
longer it will take to process in full.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 8 of 44
5. Responses to Inbound Files
When a file is transmitted through eMedNY CORE Web Services, an immediate response will be generated. Other
responses may be available, depending on the type of inbound file. Please see below for specifics.
5.1 Real-Time
The immediate response to a Real-Time Transaction will be the last level of validation for the inbound file. If there is an
issue with the envelope (e.g. improper formatting or an issue with the Username and password,) the response will
contain an envelope fault (SOAP or MIME.) If the X12 packet fails the front-end editing, the response will contain a TA1
or Front-end rejection response. If the X12 packet fails syntax validation, the response will contain the 999. If the X12
packet passes, the response will be the information requested – either a 271 for an inbound 270, or a 277 for an
inbound 276.
5.2 Batch
The immediate response to a Batch Transaction will be either an envelope error or a notification that the transaction
was received. All of the other responses must be requested through Web Services – if they are available they will be
returned as the response to the request. eMedNY uses the Payload ID from the request to correspond to the Payload
ID in the original inbound file – it is incumbent on the user to know the Payload ID of their inbound files.
If the User submits multiple Functional Groups (GS-GE) in the inbound inquiry, we will return the responses (999 and
271 or 277) as MTOM attachments. Each Functional Group will be its own attachment.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 9 of 44
6. Retrieving eMedNY-Generated Files
eMedNY CORE Web Services can be utilized in retrieving a provider’s X12 Remittance Advice (835 for most providers,
820 for managed care plans) and certain Managed Care encounter data files. If the provider designates their files to be
sent through eMedNY Core Web Services, the following types of files will be sent through this method:
• 820 Premium Payment Advice (820 File)
• 820 Premium Payment Advice Suppliment (820S File)
• 835 Remittance Advice (835 File)
• 835 Remittance Advice Supplement (835S File)
• 834 Benefit Enrollment and Maintenance (834 File)
• Managed Care Roster (834R File)
• Managed Care Organizations Data File (DWPX)
• Data Warehouse First Fill File (DWXF)
• Data Warehouse Adherence Report (DWXA)
Remittance files (820/820S and 835/835S) will be enclosed within a .tar file. This .tar file can include multiple files, and
will include all files of that type sent to the Web Services User Name for that cycle. The X12 formatting of this file is
exactly the same as those retrieved by other methods. Please refer to the ASC X12 Standard Implementation Guides
from Washington Publishing to obtain the correct file and record formats for 835 and 820 files. The
eMedNY
Transaction Information Standard Companion Guide X12 supplies details specific to eMedNY 835 and 820 files. The
Pended Claims Report: Specification supplies information on the formatting of the 835S and the Managed Care
Capitation Premium Pended and Denied Claims Report: Specification supplies information on the formatting of the
820S.
In order to designate these files to be sent to the eMedNY CORE Web Services System User Name, the provider will need
to fill out the following form to designate the routing:
https://www.emedny.org/info/ProviderEnrollment/ProviderMaintForms/700201_ELECRMTREQ_ERa_PDF_Remit_Form.
pdf
The Web Portal has a copy of this form that can be transmitted electronically.
To download an eMedNY-Generated response file, the user will send a “Request File List <payload tpe>” transaction to
retrieve a list of available files. They then can download the specific available files with “Request <payload type>”
transactions. See the Appendices for samples.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 10 of 44
7. URL for CORE Web Services
The URL for eMedNY CORE Web Services follows
https://caqh.emedny.org/eMedNY/EDIGateway
This URL is for Production transactions only. At this time, there are no means of sending Test files through CORE Web
Services. If a Test file is sent to the above URL it will receive a Front End or TA1 rejection for “Invalid Test Indicator.”
Providers wishing to test their connectivity can use a Test Indicator with the intent of getting a rejection.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 11 of 44
8. Useful Links
Most of the below links appear elsewhere in the document, this is a compilation of links the user may need for the
system.
8.1 CAQH-CORE Standards for Web Services
http://www.caqh.org/sites/default/files/core/phase-ii/policy-rules/270-v5010.pdf
8.2 Web Portal Links
8.2.1 Assistance enrollment in the Web Portal and activation of a
“System User”
https://www.emedny.org/selfhelp/ProviderPortal/Enrolling_in_Web_Portal.pdf
https://www.emedny.org/selfhelp/ProviderPortal/CORE_Web_Services_Enrollment.pdf
8.2.2 The Web Portal
https://portal.emedny.org/provider
8.3 X12 Information Links
8.3.1 Information on the eMedNY X12 envelope (ISA and GS)
https://www.emedny.org/HIPAA/5010/transactions/eMedNY_Trading_Partner_Information_CG.pdf
8.3.2 eMedNY Companion Guide for 270/271 and 276/277
https://www.emedny.org/HIPAA/5010/transactions/eMedNY_Transaction_Information_CAQH-
CORE_CG_X12_version_5010.pdf.
8.3.3 eMedNY Companion Guide for the 835/820
https://www.emedny.org/HIPAA/5010/transactions/eMedNY_Transaction_Information_CG_X12_version_5010.pdf
8.3.4 eMedNY Companion Guide for the 835S & 820S
https://www.emedny.org/HIPAA/5010/transactions/Pended_Claims_Report_Specifcation.pdf
https://www.emedny.org/HIPAA/5010/transactions/MCO_Premium_Claims_Pend_and_Deny%20Report_Specifcation.p
df
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 12 of 44
8.3.5 Washington Publishing Company
http://www.wpc-edi.com/
8.4 Production URL for eMedNY CORE Web Services
https://caqh.emedny.org/eMedNY/EDIGateway
8.5 Useful eMedNY Forms
8.5.1 Certification Statement/Instructions for Existing ETINs
The ETIN must be kept current for any kind of electronic transaction
https://www.emedny.org/info/ProviderEnrollment/ProviderMaintForms/401103_ETINDFLT_Default_ETIN_Selection_Fo
rm.pdf
8.5.2 Electronic Remittance Advice Request
This form determines the routing of all eMedNY-Generated responses for the stated ETIN
https://www.emedny.org/info/ProviderEnrollment/ProviderMaintForms/401103_ETINDFLT_Default_ETIN_Selection_Fo
rm.pdf
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 13 of 44
9. Change Log
Date
Ver
Modification
6/23/2014
1.1
Initial Version
9/3/2014
1.2
Minor revisions to the language of the document, changed company name, updated links.
4/12/2017
1.3
Added 834 files to file types. Changed some language on the end page.
1/17/2020
1.4
Updated all the samples to reflect an update in the responses. Added Appendix V to give
“before” and “after” examples of the code changes due to a server migration. Added this Change
Log.
5/15/20
1.5
Made more changes to the samples to reflect the responses from the new system– removed a
few samples as they can be extrapolated from the CAQH-CORE information.
2/14/23
1.6
Altered a few entries in 6. “Pharmacy Carve-out Report (DWPX)” was replaced with “Managed
Care Organizations Data File (DWPX,)” and the following entries were added: “Data Warehouse
First Fill File (DWXF,)” “Data Warehouse Adherence Report File (DWXA,)” “Managed Care Roster
(834R File)”. In 11 the file types “MEDA” and”MEDS” were removed and the above were
inserted.
10. Appendix I – SOAP Web Services Description
Language (WSDL) Updated 6/10/2014
The Web Services Description Language (WSDL) for SOAP follows:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions name="eMedNYCORERule"
targetNamespace="http://emedny.org/CORERule.wsdl"
xmlns:tns="http://emedny.org/CORERule.wsdl"
xmlns:sch="http://emedny.org/CORERule.xsd"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsp="http://www.w3.org/ns/ws-policy"
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsdl:documentation>
eMedNY CORE Rule
Version: 1.1
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 14 of 44
Change History:
09/16/13 -- Peter Futerko - Original Version 1.0 (CORE Rule Version 2.2.0)
11/22/13 -- Peter Futerko - Version 1.1
Added Generic Transactions
</wsdl:documentation>
<!-- ================================================================= -->
<!-- TYPE DEFINITIONS -->
<!-- List of types participating in this BPEL process . -->
<!-- The BPEL Designer will generate default request and response -->
<!-- types but you can define or import any XML Schema type and use -->
<!-- them as part of the message types. -->
<!-- ================================================================= -->
<wsdl:types>
<xsd:schema>
<xsd:import namespace="http://emedny.org/CORERule.xsd" schemaLocation="eMedNYCORERule.xsd"/>
</xsd:schema>
<xsd:schema targetNamespace="http://emedny.org/CORERule.wsdl">
<xsd:element name="invokeFault">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="invokeFault" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<!-- ================================================================= -->
<!-- MESSAGE TYPE DEFINITION -->
<!-- Definition of the message types used as part of the port type -->
<!-- type definitions -->
<!-- ================================================================= -->
<wsdl:message name="RealTimeRequestMessage">
<wsdl:part name="body" element="sch:COREEnvelopeRealTimeRequest"/>
</wsdl:message>
<wsdl:message name="RealTimeResponseMessage">
<wsdl:part name="body" element="sch:COREEnvelopeRealTimeResponse"/>
</wsdl:message>
<wsdl:message name="BatchSubmissionMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchSubmission"/>
</wsdl:message>
<wsdl:message name="BatchSubmissionResponseMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchSubmissionResponse"/>
</wsdl:message>
<wsdl:message name="BatchSubmissionAckRetrievalRequestMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchSubmissionAckRetrievalRequest"/>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 15 of 44
</wsdl:message>
<wsdl:message name="BatchSubmissionAckRetrievalResponseMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchSubmissionAckRetrievalResponse"/>
</wsdl:message>
<wsdl:message name="BatchResultsRetrievalRequestMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchResultsRetrievalRequest"/>
</wsdl:message>
<wsdl:message name="BatchResultsRetrievalResponseMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchResultsRetrievalResponse"/>
</wsdl:message>
<wsdl:message name="BatchResultsAckSubmissionMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchResultsAckSubmission"/>
</wsdl:message>
<wsdl:message name="BatchResultsAckSubmissionResponseMessage">
<wsdl:part name="body" element="sch:COREEnvelopeBatchResultsAckSubmissionResponse"/>
</wsdl:message>
<wsdl:message name="invokeFault">
<wsdl:part name="parameters" element="tns:invokeFault"/>
</wsdl:message>
<!-- ================================================================= -->
<!-- PORT TYPE DEFINITION -->
<!-- A port type groups a set of operations into a logical service -->
<!-- unit. -->
<!-- ================================================================= -->
<wsdl:portType name="CORETransactions">
<wsdl:operation name="RealTimeTransaction">
<wsdl:input message="tns:RealTimeRequestMessage"/>
<wsdl:output message="tns:RealTimeResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
<wsdl:operation name="BatchSubmitTransaction">
<wsdl:input message="tns:BatchSubmissionMessage"/>
<wsdl:output message="tns:BatchSubmissionResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
<wsdl:operation name="BatchSubmitAckRetrievalTransaction">
<wsdl:input message="tns:BatchSubmissionAckRetrievalRequestMessage"/>
<wsdl:output message="tns:BatchSubmissionAckRetrievalResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
<wsdl:operation name="BatchResultsRetrievalTransaction">
<wsdl:input message="tns:BatchResultsRetrievalRequestMessage"/>
<wsdl:output message="tns:BatchResultsRetrievalResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
<wsdl:operation name="BatchResultsAckSubmitTransaction">
<wsdl:input message="tns:BatchResultsAckSubmissionMessage"/>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 16 of 44
<wsdl:output message="tns:BatchResultsAckSubmissionResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
<wsdl:operation name="GenericBatchSubmissionTransaction">
<wsdl:input message="tns:BatchSubmissionMessage"/>
<wsdl:output message="tns:BatchSubmissionResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
<wsdl:operation name="GenericBatchRetrievalTransaction">
<wsdl:input message="tns:BatchResultsRetrievalRequestMessage"/>
<wsdl:output message="tns:BatchResultsRetrievalResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
<wsdl:operation name="GenericBatchReceiptConfirmationTransaction">
<wsdl:input message="tns:BatchResultsAckSubmissionMessage"/>
<wsdl:output message="tns:BatchResultsAckSubmissionResponseMessage"/>
<wsdl:fault name="fault" message="tns:invokeFault"/>
</wsdl:operation>
</wsdl:portType>
<!-- ================================================================= -->
<!-- BINDING DEFINITION -->
<!-- ================================================================= -->
<wsdl:binding name="CoreSoapBinding" type="tns:CORETransactions">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="RealTimeTransaction">
<soap:operation soapAction="RealTimeTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="BatchSubmitTransaction">
<soap:operation soapAction="BatchSubmitTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="BatchSubmitAckRetrievalTransaction">
<soap:operation soapAction="BatchSubmitAckRetrievalTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="BatchResultsRetrievalTransaction">
<soap:operation soapAction="BatchResultsRetrievalTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 17 of 44
</wsdl:operation>
<wsdl:operation name="BatchResultsAckSubmitTransaction">
<soap:operation soapAction="BatchResultsAckSubmitTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="GenericBatchSubmissionTransaction">
<soap:operation soapAction="GenericBatchSubmissionTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="GenericBatchRetrievalTransaction">
<soap:operation soapAction="GenericBatchRetrievalTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
</wsdl:operation>
<wsdl:operation name="GenericBatchReceiptConfirmationTransaction">
<soap:operation soapAction="GenericBatchReceiptConfirmationTransaction" style="document"/>
<wsdl:input><soap:body use="literal"/></wsdl:input>
<wsdl:output><soap:body use="literal"/></wsdl:output>
<wsdl:fault name="fault"><soap:fault name="fault" use="literal"/></wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<!-- ================================================================= -->
<!-- SERVICE DEFINITION -->
<!-- ================================================================= -->
<wsdl:service name="CoreService">
<wsdl:port name="CoreSoapPort" binding="tns:CoreSoapBinding">
<soap:address location="https://caqh.emedny.org/eMedNY/EDIGateway"/>
</wsdl:port>
</wsdl:service>
<!-- ================================================================= -->
<!-- SECURITY POLICY DEFINITION -->
<!-- ================================================================= -->
<wsp:Policy>
<sp:SupportingTokens>
<wsp:Policy>
<sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-
securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:WssUsernameToken11/>
</wsp:Policy>
</sp:UsernameToken>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 18 of 44
</wsp:Policy>
</sp:SupportingTokens>
</wsp:Policy>
</wsdl:definitions>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 19 of 44
11. Appendix II – Web Services Schema Definition
Updated 6/10/2014
The XML Web Services Schema Definitions follow:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
targetNamespace="http://emedny.org/CORERule.xsd"
xmlns:sch="http://emedny.org/CORERule.xsd">
<xsd:annotation>
<xsd:documentation>
eMedNY CORE Rule
Version: 1.1
Change History:
09/16/13 -- Peter Futerko - Original Version 1.0 (CORE Rule Version 2.2.0)
01/16/14 -- Peter Futerko - Version 1.1
Added payload types for retrieval of remittance advice, premium payment advice,
835 supplemental, 820 supplemental, encounters, and pharmacy carve-out.
</xsd:documentation>
</xsd:annotation>
<!--##########################################################-->
<!--# #-->
<!--# Root Nodes #-->
<!--# #-->
<!--##########################################################-->
<xsd:element name="COREEnvelopeRealTimeRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="sch:SubmissionPayloadType" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:RealTimeMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 20 of 44
<xsd:element name="COREEnvelopeRealTimeResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:RealTimeMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:string" minOccurs="0" maxOccurs="1"/>
<xsd:element name="ErrorCode" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ErrorMessage" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeBatchSubmission">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="sch:SubmissionPayloadType" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="1" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="1" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeBatchSubmissionResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="0" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="0" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="0" maxOccurs="1"/>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 21 of 44
<xsd:element name="ErrorCode" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ErrorMessage" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeBatchSubmissionAckRetrievalRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="sch:AcknowledgementRetrievalPayloadType" minOccurs="1"
maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="0" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="0" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeBatchSubmissionAckRetrievalResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="0" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="0" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="0" maxOccurs="1"/>
<xsd:element name="ErrorCode" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ErrorMessage" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeBatchResultsRetrievalRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="sch:ResultsRetrievalPayloadType" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 22 of 44
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="0" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="0" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeBatchResultsRetrievalResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="0" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="0" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="0" maxOccurs="1"/>
<xsd:element name="ErrorCode" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ErrorMessage" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeBatchResultsAckSubmission">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="sch:AcknowledgementSubmissionPayloadType" minOccurs="1"
maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="0" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="0" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 23 of 44
<xsd:element name="COREEnvelopeBatchResultsAckSubmissionResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadLength" type="xsd:int" minOccurs="0" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CheckSum" type="sch:Sha1Checksum" minOccurs="0" maxOccurs="1"/>
<xsd:element name="Payload" type="xsd:base64Binary" minOccurs="0" maxOccurs="1"/>
<xsd:element name="ErrorCode" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ErrorMessage" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="COREEnvelopeError">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PayloadType" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ProcessingMode" type="sch:BatchMode" minOccurs="1" maxOccurs="1"/>
<xsd:element name="PayloadID" type="sch:IsoUuid" minOccurs="1" maxOccurs="1"/>
<xsd:element name="TimeStamp" type="xsd:dateTime" minOccurs="1" maxOccurs="1"/>
<xsd:element name="SenderID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ReceiverID" type="sch:CoreString" minOccurs="1" maxOccurs="1"/>
<xsd:element name="CORERuleVersion" type="sch:CoreRuleVersion" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ErrorCode" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="ErrorMessage" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<!--##########################################################-->
<!--# #-->
<!--# Simple Types #-->
<!--# #-->
<!--##########################################################-->
<xsd:simpleType name="IsoUuid">
<xsd:annotation>
<xsd:documentation>
ISO UUID standard (described at ftp://ftp.rfc-editor.org/in-notes/rfc4122.txt),
with hexadecimal notation, generated using a combination of local timestamp
(in milliseconds) as well as the hardware (MAC) address, to ensure uniqueness.
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 24 of 44
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}"></xsd:pattern>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="Sha1Checksum">
<xsd:annotation>
<xsd:documentation>
Algorithm is SHA-1, Encoding is Hex. Checksum must be computed only on the payload
and not on the metadata.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9a-fA-F]{40}"></xsd:pattern>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CoreString">
<xsd:annotation>
<xsd:documentation>
Maximum length 50 characters.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="50"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="CoreRuleVersion">
<xsd:annotation>
<xsd:documentation>
CORE Rule Version = 2.2.0.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="2.2.0"></xsd:pattern>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="RealTimeMode">
<xsd:restriction base="xsd:string">
<xsd:pattern value="RealTime"/>
</xsd:restriction>
</xsd:simpleType>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 25 of 44
<xsd:simpleType name="BatchMode">
<xsd:restriction base="xsd:string">
<xsd:pattern value="Batch"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="SubmissionPayloadType">
<xsd:annotation>
<xsd:documentation>
Submission payload types.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:enumeration value="X12_270_Request_005010X279A1"></xsd:enumeration>
<xsd:enumeration value="X12_276_Request_005010X212"></xsd:enumeration>
<xsd:enumeration value="X12_005010_Request_BatchSubmissionMixed"></xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="AcknowledgementRetrievalPayloadType">
<xsd:annotation>
<xsd:documentation>
Acknowledgement retrieval payload types.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:enumeration value="X12_999_RetrievalRequest_005010X231A1"></xsd:enumeration>
<xsd:enumeration value="X12_TA1_RetrievalRequest_00501X231A1"></xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ResultsRetrievalPayloadType">
<xsd:annotation>
<xsd:documentation>
Results retrieval payload types.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:enumeration value="X12_005010_Request_Batch_Results_271"></xsd:enumeration>
<xsd:enumeration value="X12_005010_Request_Batch_Results_277"></xsd:enumeration>
<xsd:enumeration value="X12_005010_Request_BatchResultsMixed"></xsd:enumeration>
<xsd:enumeration value="X12_999_RetrievalRequest_005010X231A1"></xsd:enumeration>
<xsd:enumeration value="X12_820_Request_005010X218A1"></xsd:enumeration>
<xsd:enumeration value="X12_835_Request_005010X221A1"></xsd:enumeration>
<xsd:enumeration value="Request_820S"></xsd:enumeration>
<xsd:enumeration value="Request_834R"></xsd:enumeration>
<xsd:enumeration value="Request_835S"></xsd:enumeration>
<xsd:enumeration value="Request_DWPX"></xsd:enumeration>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 26 of 44
<xsd:enumeration value="Request_DWXA"></xsd:enumeration>
<xsd:enumeration value="Request_DWXF"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_820"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_835"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_820S"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_834R"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_835S"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_DWPX"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_DWXA"></xsd:enumeration>
<xsd:enumeration value="Request_File_List_DWXF"></xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="AcknowledgementSubmissionPayloadType">
<xsd:annotation>
<xsd:documentation>
Acknowledgement submission payload types.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:enumeration value="X12_999_SubmissionRequest_005010X231A1"></xsd:enumeration>
<xsd:enumeration value="X12_TA1_SubmissionRequest_00501X231A1"></xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 27 of 44
12. Appendix III - SOAP XML Request and Response
Samples – updated 1/7/2020
General examples can be found at the following link:
http://www.caqh.org/sites/default/files/core/phase-ii/policy-rules/270-v5010.pdf
The following are actual samples from the eMedNY Instance of CAQH/CORE:
12.1 Real-Time Examples
The following are examples of Real-Time transactions. The examples are 270/271, but a 276 can be sent by changing the
payload type.
12.1.1 SOAP XML Real-Time Request Example
POST /eMedNY/EDIGateway HTTP/1.1
Content-Type: application/soap+xml; action="RealTimeTransaction"
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
soap:mustUnderstand="true">
<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-
1.0.xsd" wsu:Id="UsernameToken-21621663">
<wsse:Username>******</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-
1.0#PasswordText">******</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soap:Body>
<cor:COREEnvelopeRealTimeRequest xmlns:cor="http://emedny.org/CORERule.xsd">
<cor:PayloadType>X12_270_Request_005010X279A1</cor:PayloadType>
<cor:ProcessingMode>RealTime</cor:ProcessingMode>
<cor:PayloadID>60000000-0000-0000-0000-000000000005</cor:PayloadID>
<cor:TimeStamp>2007-08-30T10:20:34Z</cor:TimeStamp>
<cor:SenderID>HospitalA</cor:SenderID>
<cor:ReceiverID>eMedNY</cor:ReceiverID>
<cor:CORERuleVersion>2.2.0</cor:CORERuleVersion>
<cor:Payload><![CDATA[ISA*00…~]]></cor:Payload>
</cor:COREEnvelopeRealTimeRequest>
</soap:Body>
</soap:Envelope>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 28 of 44
12.1.2 SOAP XML Real-Time Response Example
HTTP/1.1 200
Content-Type: application/soap+xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Tue, 12 May 2020 19:23:41 GMT
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body>
<ns3:COREEnvelopeRealTimeResponse xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-utility-1.0.xsd" xmlns:ns2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
1.0.xsd" xmlns:ns3="http://emedny.org/CORERule.xsd" xmlns:ns5="http://emedny.org/CORERule.wsdl">
<ns3:PayloadType>X12_271_Response_005010X279A1</ns3:PayloadType>
<ns3:ProcessingMode>RealTime</ns3:ProcessingMode>
<ns3:PayloadID>60000000-0000-0000-0000-000000000005</ns3:PayloadID>
<ns3:TimeStamp>2020-05-12T19:23:41Z</ns3:TimeStamp>
<ns3:SenderID>eMedNY</ns3:SenderID>
<ns3:ReceiverID>HospitalA</ns3:ReceiverID>
<ns3:CORERuleVersion>2.2.0</ns3:CORERuleVersion>
<ns3:Payload><![CDATA[ISA*00…~]]></ns3:Payload>
<ns3:ErrorCode>Success</ns3:ErrorCode>
<ns3:ErrorMessage>None</ns3:ErrorMessage>
</ns3:COREEnvelopeRealTimeResponse>
</soap:Body>
</soap:Envelope>
12.2 Batch Examples
The following are examples of Batch transactions. The examples are 270/271, but a 276 can be sent by changing the
payload type.
12.2.1 SOAP XML Batch Request Example with MTOM
POST /eMedNY/EDIGateway HTTP/1.1
Content-Type: multipart/related; type="application/xop+xml"; start="<A1>"; start-info="application/soap+xml";
action="GenericBatchRetrievalTransaction"; boundary="MIMEBoundaryAbCd"
--MIMEBoundaryAbCd
Content-Type: application/xop+xml; type="application/soap+xml"
Content-Transfer-Encoding: binary
Content-ID: <A1>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>******</wsse:Username>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 29 of 44
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-
1.0#PasswordText">******</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soap:Body>
<cor:COREEnvelopeBatchResultsRetrievalRequest xmlns:cor="http://emedny.org/CORERule.xsd">
<cor:PayloadType>Request_File_List_DWPX</cor:PayloadType>
<cor:ProcessingMode>Batch</cor:ProcessingMode>
<cor:PayloadID>AAA00000-0000-0000-0000-000000000000</cor:PayloadID>
<cor:TimeStamp>2020-03-30T10:20:34Z</cor:TimeStamp>
<cor:SenderID>HospitalA</cor:SenderID>
<cor:ReceiverID>eMedNY</cor:ReceiverID>
<cor:CORERuleVersion>2.2.0</cor:CORERuleVersion>
</cor:COREEnvelopeBatchResultsRetrievalRequest>
</soap:Body>
</soap:Envelope>
--MIMEBoundaryAbCd--
12.2.2 SOAP XML Batch Response Example with MTOM
HTTP/1.1 200
Date: Tue, 31 Mar 2020 13:06:04 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips mod_auth_gssapi/1.5.1 mod_nss/1.0.14
NSS/3.28.4 PHP/5.4.16 mod_wsgi/3.4 Python/2.7.5
Content-Type: multipart/related; type="application/xop+xml"; boundary="uuid:cf568db6-d575-412b-a6fb-
acd4cb00efd1"; start="<root.message@cxf.apache.org>"; start-info="application/soap+xml"
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
--uuid:cf568db6-d575-412b-a6fb-acd4cb00efd1
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
Content-Transfer-Encoding: binary
Content-ID: <r[email protected]pache.org>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body>
<ns3:COREEnvelopeBatchResultsRetrievalResponse xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-
200401-wss-wssecurity-utility-1.0.xsd" xmlns:ns2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-secext-1.0.xsd" xmlns:ns3="http://emedny.org/CORERule.xsd"
xmlns:ns5="http://emedny.org/CORERule.wsdl">
<ns3:PayloadType>Response_File_List_DWPX</ns3:PayloadType>
<ns3:ProcessingMode>Batch</ns3:ProcessingMode>
<ns3:PayloadID>AAA00000-0000-0000-0000-000000000000</ns3:PayloadID>
<ns3:PayloadLength>72</ns3:PayloadLength>
<ns3:TimeStamp>2020-03-31T13:06:04Z</ns3:TimeStamp>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 30 of 44
<ns3:SenderID>eMedNY</ns3:SenderID>
<ns3:ReceiverID>HospitalA</ns3:ReceiverID>
<ns3:CORERuleVersion>2.2.0</ns3:CORERuleVersion>
<ns3:CheckSum>62bb53f35ff9649155bff5f4bf9baf753517b70f</ns3:CheckSum>
<ns3:Payload>
<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:abc54148-29fd-43d9-96fd-
8daed0429f52-[email protected]"/>
</ns3:Payload>
<ns3:ErrorCode>Success</ns3:ErrorCode>
<ns3:ErrorMessage>None</ns3:ErrorMessage>
</ns3:COREEnvelopeBatchResultsRetrievalResponse>
</soap:Body>
</soap:Envelope>
--uuid:cf568db6-d575-412b-a6fb-acd4cb00efd1
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <abc54148-29fd-43d9-96fd-8daed0429f52-45@emedny.org>
<list><payloadid>20190802-0900-4600-0000-000000000001</payloadid></list>
--uuid:cf568db6-d575-412b-a6fb-acd4cb00efd1--
13. Appendix IV – Web Services MIME Request and
Response Samples
General examples can be found at the following link:
http://www.caqh.org/sites/default/files/core/phase-ii/policy-rules/270-v5010.pdf
The following are actual samples from the eMedNY Instance of the system:
13.1 eMedNY-Generated Response File Examples
These are examples of requesting a file list of and requesting an eMedNY-Generated response file. The examples use an
835 file, but this can be varied by changing the payload type.
13.1.1 MIME Request File List 835 Example
POST /eMedNY/EDIGateway HTTP/1.1
Content-Type: multipart/form-data; boundary="MIMEBoundaryAbCd"
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="PayloadType"
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 31 of 44
Request_File_List_835
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="ProcessingMode"
Batch
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="PayloadID"
20190802-0901-4600-0000-000000000001
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="TimeStamp"
2007-08-30T10:20:34Z
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="UserName"
******
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="Password"
******
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="SenderID"
HospitalA
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="ReceiverID"
eMedNY
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="CORERuleVersion"
2.2.0
--MIMEBoundaryAbCd--
Response
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D--
13.1.2 X12 835 File List Response 005010X221A1
HTTP/1.1 200
Server: nginx
Date: Tue, 12 May 2020 18:42:23 GMT
Content-Type: multipart/form-data; boundary=lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D;charset=UTF-8
Transfer-Encoding: chunked
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 32 of 44
Connection: keep-alive
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="PayloadType"
Content-Type: text/plain;charset=UTF-8
Content-Length: 22
Response_File_List_835
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="ProcessingMode"
Content-Type: text/plain;charset=UTF-8
Content-Length: 5
Batch
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="PayloadID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 36
20190802-0901-4600-0000-000000000001
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="PayloadLength"
Content-Type: text/plain;charset=UTF-8
Content-Length: 2
13
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="TimeStamp"
Content-Type: text/plain;charset=UTF-8
Content-Length: 20
2020-05-12T18:42:19Z
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="SenderID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 6
eMedNY
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="ReceiverID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 9
HospitalA
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="CORERuleVersion"
Content-Type: text/plain;charset=UTF-8
Content-Length: 5
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 33 of 44
2.2.0
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="CheckSum"
Content-Type: text/plain;charset=UTF-8
Content-Length: 40
2ae0811dcbdcf48b1e31a5cbbbf60e2c29328a26
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="Payload"
Content-Type: text/plain;charset=UTF-8
Content-Length: 13
<list></list>
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="ErrorCode"
Content-Type: text/plain;charset=UTF-8
Content-Length: 7
Success
--lwbkInuxo8setmgQs28mTjVG9_zwL2ors5CnSD4D
Content-Disposition: form-data; name="ErrorMessage"
Content-Type: text/plain;charset=UTF-8
Content-Length: 4
None
13.1.3 MIME Request 835 file
POST /eMedNY/EDIGateway HTTP/1.1
Content-Type: multipart/form-data; boundary="MIMEBoundaryAbCd"
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="PayloadType"
X12_835_Request_005010X221A1
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="ProcessingMode"
Batch
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="PayloadID"
20190802-0901-4600-0000-000000000001
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="TimeStamp"
2007-08-30T10:20:34Z
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 34 of 44
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="UserName"
******
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="Password"
******
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="SenderID"
HospitalA
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="ReceiverID"
eMedNY
--MIMEBoundaryAbCd
Content-Disposition: form-data; name="CORERuleVersion"
2.2.0
--MIMEBoundaryAbCd--
13.1.4 X12 835 Response 005010X221A1
HTTP/1.1 200
Content-Type: multipart/form-data; boundary=WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd;charset=UTF-8
Transfer-Encoding: chunked
Date: Tue, 12 May 2020 19:15:54 GMT
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="PayloadType"
Content-Type: text/plain;charset=UTF-8
Content-Length: 29
X12_835_Response_005010X221A1
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="ProcessingMode"
Content-Type: text/plain;charset=UTF-8
Content-Length: 5
Batch
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="PayloadID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 36
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 35 of 44
20190802-0901-4600-0000-000000000001
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="PayloadLength"
Content-Type: text/plain;charset=UTF-8
Content-Length: 5
10240
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="TimeStamp"
Content-Type: text/plain;charset=UTF-8
Content-Length: 20
2020-05-12T19:15:54Z
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="SenderID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 6
eMedNY
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="ReceiverID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 9
HospitalA
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="CORERuleVersion"
Content-Type: text/plain;charset=UTF-8
Content-Length: 5
2.2.0
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="CheckSum"
Content-Type: text/plain;charset=UTF-8
Content-Length: 40
4fb722c683f49b035241f7cc731004e2f646ef5e
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="Payload"; filename="R160629150126.2025.835-.tar"
Content-Type: application/x-tar
Content-Length: 10240
R160629150116.2025.835.0000.x12...
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="ErrorCode"
Content-Type: text/plain;charset=UTF-8
Content-Length: 7
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 36 of 44
Success
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd
Content-Disposition: form-data; name="ErrorMessage"
Content-Type: text/plain;charset=UTF-8
Content-Length: 4
None
--WCEXufLrZ8MpOyxDWa7bkyco6U3jidwO-jhLd--
14. Appendix V - Systems Changes due to migration
In early 2020 the system was updated to use HTTP/1.1. As a result, there were minor changes to the generated
responses. The above examples represent the information after the change, the below examples explicitly show the
“before” and “after” code so that a user experiencing issues can accommodate the changes in the file responses.
Changes are highlighted.
14.1 SOAP Responses
Before Update
Http/1.0 200
Content-Type: application/soap+xml; action="RealTimeTransaction"
Content-Length: 1269
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:cor="http://emedny.org/CORERule.xsd">
<soap:Body>
<cor:COREEnvelopeRealTimeResponse>
<cor:PayloadType>X12_277_Response_005010X212</cor:PayloadType>
<cor:ProcessingMode>RealTime</cor:ProcessingMode>
<cor:PayloadID>f81d4fae-7dec-11d0-a765-00a0c91e6bf6</cor:PayloadID>
<cor:TimeStamp>2013-10-09T20:32:22Z</cor:TimeStamp>
<cor:SenderID>eMedNY</cor:SenderID>
<cor:ReceiverID>HospitalA</cor:ReceiverID>
<cor:CORERuleVersion>2.2.0</cor:CORERuleVersion>
<cor:Payload><![CDATA[ISA*00* *00* *ZZ*NEHEN780 *ZZ*NEHEN003 ...IEA*1*000000031]]></cor:Payload>
<cor:ErrorCode>Success</cor:ErrorCode>
<cor:ErrorMessage>None</cor:ErrorMessage>
</cor:COREEnvelopeRealTimeResponse>
</soap:Body>
</soap:Envelope>
After Update
HTTP/1.1 200
Content-Type: application/soap+xml;charset=UTF-8
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 37 of 44
Transfer-Encoding: chunked
Date: Tue, 12 May 2020 19:23:41 GMT
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body>
<ns3:COREEnvelopeRealTimeResponse xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-utility-1.0.xsd" xmlns:ns2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-
1.0.xsd" xmlns:ns3="http://emedny.org/CORERule.xsd" xmlns:ns5="http://emedny.org/CORERule.wsdl">
<ns3:PayloadType>X12_271_Response_005010X279A1</ns3:PayloadType>
<ns3:ProcessingMode>RealTime</ns3:ProcessingMode>
<ns3:PayloadID>60000000-0000-0000-0000-000000000005</ns3:PayloadID>
<ns3:TimeStamp>2020-05-12T19:23:41Z</ns3:TimeStamp>
<ns3:SenderID>eMedNY</ns3:SenderID>
<ns3:ReceiverID>HospitalA</ns3:ReceiverID>
<ns3:CORERuleVersion>2.2.0</ns3:CORERuleVersion>
<ns3:Payload><![CDATA[ISA*00…~]]></ns3:Payload>
<ns3:ErrorCode>Success</ns3:ErrorCode>
<ns3:ErrorMessage>None</ns3:ErrorMessage>
</ns3:COREEnvelopeRealTimeResponse>
</soap:Body>
</soap:Envelope>
14.1.1 SOAP MTOM Response
Before Update
HTTP/1.0 200 OK
Content-Ty
pe: multipart/related; type="application/xop+xml"; start="<A1>"; start-info="application/soap+xml";
action="BatchResultsRetrievalTransaction"; boundary="2903E661-F811-90E8-2C77-8C079ED24ECB"
Content-Length: 3604
--2903E661-F811-90E8-2C77-8C079ED24ECB
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
Content-Transfer-Encoding: binary
Content-ID: <A1>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body>
<cor:COREEnvelopeBatchResultsRetrievalResponse xmlns:cor="http://emedny.org/CORERule.xsd">
<cor:PayloadType>X12_271_Response_005010X279A1</cor:PayloadType>
<cor:ProcessingMode>Batch</cor:ProcessingMode>
<cor:PayloadID>60000000-0000-0000-0000-000000000001</cor:PayloadID>
<cor:PayloadLength>629</cor:PayloadLength>
<cor:TimeStamp>2019-08-30T15:50:26Z</cor:TimeStamp>
<cor:SenderID>eMedNY</cor:SenderID>
<cor:ReceiverID>HospitalA</cor:ReceiverID>
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 38 of 44
<cor:CORERuleVersion>2.2.0</cor:CORERuleVersion>
<cor:CheckSum>5a48861ac54f5d06e4a824520252392af5d3ced8</cor:CheckSum>
<cor:Payload>
<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:A2"/>
<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:A3"/>
<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:A4"/>
</cor:Payload>
<cor:ErrorCode>Success</cor:ErrorCode>
<cor:ErrorMessage>None</cor:ErrorMessage>
</cor:COREEnvelopeBatchResultsRetrievalResponse>
</soap:Body>
</soap:Envelope>
--2903E661-F811-90E8-2C77-8C079ED24ECB
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <A2>
ISA*00* *00* *ZZ*EMEDNYBAT *ZZ*0PR *190807*1541...~
--2903E661-F811-90E8-2C77-8C079ED24ECB
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <A3>
ISA*00* *00* *ZZ*EMEDNYBAT *ZZ*0PR *190807*1541...~
--2903E661-F811-90E8-2C77-8C079ED24ECB
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <A4>
ISA*00* *00* *ZZ*EMEDNYBAT *ZZ*0PR *190807*1542...~
--2903E661-F811-90E8-2C77-8C079ED24ECB—
After Update
HTTP/1.1 200
Date: Tue, 31 Mar 2020 13:06:04 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips mod_auth_gssapi/1.5.1 mod_nss/1.0.14
NSS/3.28.4 PHP/5.4.16 mod_wsgi/3.4 Python/2.7.5
Content-Type: multipart/related; type="application/xop+xml"; boundary="uuid:cf568db6-d575-412b-a6fb-
acd4cb00efd1"; start="<root.message@cxf.apache.org>"; start-info="application/soap+xml"
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
--uuid:cf568db6-d575-412b-a6fb-acd4cb00efd1
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
Content-Transfer-Encoding: binary
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 39 of 44
Content-ID: <root.message@cxf.apache.org>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body>
<ns3:COREEnvelopeBatchResultsRetrievalResponse xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-
200401-wss-wssecurity-utility-1.0.xsd" xmlns:ns2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-secext-1.0.xsd" xmlns:ns3="http://emedny.org/CORERule.xsd"
xmlns:ns5="http://emedny.org/CORERule.wsdl">
<ns3:PayloadType>Response_File_List_DWPX</ns3:PayloadType>
<ns3:ProcessingMode>Batch</ns3:ProcessingMode>
<ns3:PayloadID>AAA00000-0000-0000-0000-000000000000</ns3:PayloadID>
<ns3:PayloadLength>72</ns3:PayloadLength>
<ns3:TimeStamp>2020-03-31T13:06:04Z</ns3:TimeStamp>
<ns3:SenderID>eMedNY</ns3:SenderID>
<ns3:ReceiverID>HospitalA</ns3:ReceiverID>
<ns3:CORERuleVersion>2.2.0</ns3:CORERuleVersion>
<ns3:CheckSum>62bb53f35ff9649155bff5f4bf9baf753517b70f</ns3:CheckSum>
<ns3:Payload>
<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:abc54148-29fd-43d9-96fd-
8daed0429f52-[email protected]"/>
</ns3:Payload>
<ns3:ErrorCode>Success</ns3:ErrorCode>
<ns3:ErrorMessage>None</ns3:ErrorMessage>
</ns3:COREEnvelopeBatchResultsRetrievalResponse>
</soap:Body>
</soap:Envelope>
--uuid:cf568db6-d575-412b-a6fb-acd4cb00efd1
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <abc54148-29fd-43d9-96fd-8daed0429f52-45@emedny.org>
<list><payloadid>20190802-0900-4600-0000-000000000001</payloadid></list>
--uuid:cf568db6-d575-412b-a6fb-acd4cb00efd1--
14.2 MIME Responses
Before Update
Content-Type: multipart/form-data; boundary="A847AD50-9F55-07FD-C0D3-2934F27F870B"
Content-Length: 1694
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="PayloadType"
X12_277_Response_005010X212
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="ProcessingMode"
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 40 of 44
RealTime
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="PayloadID"
f81d4fae-7dec-11d0-a765-00a0c91e6bf6
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="TimeStamp"
2013-10-09T20:52:55Z
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="SenderID"
eMedNY
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="ReceiverID"
HospitalA
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="CORERuleVersion"
2.2.0
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="Payload"
ISA*00* *00* *ZZ*NEHEN780 *ZZ*NEHEN003 ...IEA*1*000000031
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="ErrorCode"
Success
--A847AD50-9F55-07FD-C0D3-2934F27F870B
Content-Disposition: form-data; name="ErrorMessage"
None
--A847AD50-9F55-07FD-C0D3-2934F27F870B—
After Update
HTTP/1.1 200
Content-Type: multipart/form-data; boundary=-VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA;charset=UTF-8
Transfer-Encoding: chunked
Date: Tue, 07 Jan 2020 17:39:24 GMT
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="PayloadType"
Content-Type: text/plain;charset=UTF-8
Content-Length: 29
X12_271_Response_005010X279A1
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 41 of 44
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="ProcessingMode"
Content-Type: text/plain;charset=UTF-8
Content-Length: 8
RealTime
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="PayloadID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 36
f81d4fae-7dec-11d0-a765-00a0c91e6bf6
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="TimeStamp"
Content-Type: text/plain;charset=UTF-8
Content-Length: 20
2020-01-07T17:39:24Z
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="SenderID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 6
eMedNY
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="ReceiverID"
Content-Type: text/plain;charset=UTF-8
Content-Length: 9
HospitalA
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="CORERuleVersion"
Content-Type: text/plain;charset=UTF-8
Content-Length: 5
2.2.0
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="Payload"; filename=”R160629150126.2025.835-.tar”
Content-Type: application/x-tar
Content-Length: 10240
ISA*00...~IEA*1*000000320~
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="ErrorCode"
Content-Type: text/plain;charset=UTF-8
Content-Length: 7
Success
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 42 of 44
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA
Content-Disposition: form-data; name="ErrorMessage"
Content-Type: text/plain;charset=UTF-8
Content-Length: 4
None
---VzUw7Ii8qgRhv_Ty28_HjOqVwvKfexA--
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 43 of 44
For eMedNY Billing Information:
Institutional: 1-800-343-9000
Clinics, hospitals, rate-based; ordered/referred ambulatory
Practitioner: 1-800-343-9000
MDs, RNs, dentists
Professional: 1-800-343-9000
others (DME, non-MDs - phys. Therapy, etc.)
Business hours are Monday through Friday from 7:00 a.m. to 6:00 p.m..
Version 1.6 eMedNY CORE Web Services User Guide 2/14/2023
Page 44 of 44
eMedNY is the name of the electronic New York State Medicaid system. The eMedNY system allows
New York Medicaid providers to submit claims and receive payments for Medicaid-covered
services provided to eligible clients.
eMedNY offers several innovative technical and architectural features, facilitating the
adjudication and payment of claims and providing extensive support and convenience for its
users.
The information contained within this document was created in concert by eMedNY and DOH.
More information about eMedNY can be found at www.emedny.org.