Technical Specification for Medical Claims Electronic Data Transfer (MCEDT) Service via Electronic Business Services (EBS)

EBS-EDT SOAP Specifications


Date: August 2017

Version 4.3

See also: Version 4.2


Table of Contents



Glossary

Claim Submission Number (CSN) aka Billing Number
A unique identifier that is assigned to a Health Care Provider who is registered with MOHLTC for the purpose of submitting claims for insured services.

The identifier is alphanumeric and is between 5 and 6 characters long. Group billing numbers must begin with a leading zero and adhere to this format: 0[A-Z0-9]{4}.
MCEDT Service Schedule
A Service Schedule to the Master Service agreement that forms part of the Agreement between the Service Requestor and MOHLTC and captures the roles and responsibilities that relate to the MCEDT via EBS.
Health Care Provider (HCP)
Individual, group or facility licensed to provide health care services to eligible residents of Ontario.
Health Information Custodian (HIC)
Health Information Custodian in or under Personal Health Information Privacy Act (PHIPA).
Identity Provider (IDP)
A party or organization that creates, maintains, and manages identity information for principals and performs principal authentication for other parties or organizations.
Master Services Agreement
The binding legal agreement through which MOHLTC accepts the identity of an end user at face value based on authenticating the end user's organization at the time of the service request.
MOHLTC
The Ontario Ministry of Health and Long-Term Care.
MOHLTC Electronic Business Services (EBS)
The Electronic Business Service is a framework which provides an electronic business gateway that exposes MOHLTC services to the Broader Health Sector and provides a full featured IAM suite of provisioning, business enrolment, business and IT federation agreements, technical specifications and terms of acceptable use governance.
Message Transmission Optimization Mechanism (MTOM)
A method of efficiently sending binary data to and from web services. For more information refer to:
SOAP Message Transmission Optimization Mechanism
Output (Response) Message Fields
Output (Response) Message fields are those fields which are returned by the Medical Claims Electronic Data Transfer web service.
Service Provider (SP)
Throughout this document, Service Provider refers exclusively to MOHLTC, as the provider of the Medical Claims Electronic Data Transfer service via EBS.
Simple Object Access Protocol (SOAP)
Simple Object Access Protocol: an Extensible Markup Language (XML)-based protocol for exchanging structured information between computer systems.
Stakeholder Number (SN)
A unique identifier that is assigned to stakeholders of interest who are registered with the MOHLTC. The unique identifier is either 7 digits long or 8 digits long depending on the type of stakeholder to which it belongs.
UUID
A version 4 Universally Unique Identifier (UUID).
Web Services Description Language (WSDL)
Web Services Description Language: an XML-based language for describing web services and how to access them.

Back to top


Notice and Disclaimer

All possible measures are exerted to ensure accuracy of the contents of this manual; however, the manual may contain typographical, printing or other errors. The reader is cautioned against complete reliance upon the contents of the manual without confirming the accuracy and currency of the information contained in it. The Crown in Right of Ontario, as represented by the Ministry of Health and Long-Term Care (MOHLTC), assumes no responsibility for errors or omissions in any of the information contained in this manual, or for any person's use of the material therein, or for any costs or damages associated with such use. In no event shall the Crown in Right of Ontario be liable for any errors or omissions, or for any damages including, without limitation, damages for direct, indirect, incidental, special, consequential or punitive damages arising out of or related to the use of information contained in this manual.

This technical specification is intended only to assist and guide the development of software to access the Medical Claims Electronic Data Transfer (MCEDT) web service via the MOHLTC Electronic Business Service (EBS).

Revisions to the specification will be made as required. The ministry will make every effort to give as much advance notice as possible for future revisions. It is essential that software developers keep current regarding any changes to this specification. The current version of the technical specification will be available for download.

For further details about MCEDT via EBS service including enrolment criteria please refer to the MCEDT Reference Manual.

This document does not describe the technical specifications of the specific files that can be uploaded and downloaded by the MCEDT application. For information on specific file format specifications please refer to the individual technical specification (EBS-EDT SOAP Specifications).

Please direct any questions to the Service Support Contact Centre at 1-800-262-6524 or SSContactCentre.MOH@ontario.ca

Back to top


Intended Audience for this Technical Specification Document

This document is intended for use by developers of applications and products that support communication with MOHLTC's MCEDT via EBS (web service interface) a service provided by the ministry to support electronic data transfer. This service is built to the web services standards detailed in this document.

The ministry does not provide any support for automation of the public MCEDT web page.

This document is also intended to be read in the context of either a service agreement between the ministry and the Service Requestor or through an accepted IDP. The service agreement is defined by a Master Service Agreement and an MCEDT Service Schedule between the ministry and the Service Requestor (SR).

This technical specification is also targeted to vendors of various software applications and products that have or plan to have modules that support MCEDT through a web service interface within the province of Ontario in Canada.

The document describes the web service, the SOAP message specification and aims to guide the users in the development of client application to integrate with this web service.

It is assumed that the reader has knowledge of web services and related protocols, SOAP and XML message formats/processing, relevant interoperability profiles and identity assertions and has read the ‘MOHLTC EBS - Generic Security SOAP Specification' document.

Back to top


About this Document

The Ministry of Health and Long-Term Care Medical Claims Electronic Data Transfer service allows health care providers (HCP) to send and receive electronic data with the ministry.

This document is an extension of the "MOHLTC EBS – Generic Security SOAP Specification" document and is intended to provide the reader with sufficient information to implement service requestor software that can use the service.

The MCEDT service will only support the IDP security model in its first release

The introduction provides an overview of the MCEDT service and provides a glossary of the terminology used throughout the document. Additional functional information and overview of the MCEDT process is provided in the MCEDT reference manual.

The Simple Object Access Protocol (SOAP) Message Section provides the technical specifications of the SOAP message including:

  • Message Web Services Description Language;
  • Validation message schema including the request and the response;
  • Data specifications for fields; and
  • MTOM will be used to transfer all attachments.

Back to top


Introduction

The Medical Claims Electronic Data Transfer service adheres to the EBS security models. As such, it requires that the unique ministry identifier for Service Requestor (SR) be a Stakeholder Number (SN), and for Service User (SU) be either a SN or a Claim Submission Number (CSN).

Although the ministry does provide a simple user interface for MCEDT all program to program interfaces MUST use this web service and should never interface to the user interface. The user interface can and will change time to time without notification.

Medical Claims Electronic Data Transfer

The MCEDT service is a framework which allows electronic file processing to and from the ministry's adjudication and reporting systems. Service users who are authenticated to the MCEDT service can upload (send) files to the ministry for processing. Related reports can also be retrieved through this information technology channel by authorized users or their agents (designates). Service users and their agents must first register and enroll for a set of new security credentials before they can be authenticated to the MCEDT service before they can upload (send) or download (receive) reports or files.

The contents and format of files remain exactly as transmitted from the service user or from the ministry's information technology systems.

For more information refer to the MCEDT Reference manual.

Web Service Interface for MCEDT Service

The Province of Ontario, via the Ministry of Health and Long-Term Care, offers MCEDT via EBS for users through third party or client software.

Back to top


Technical Interface

The Province of Ontario is responsible and accountable for the service provider component.

The service interface uses the SOAP protocol for communication and the WS-Security (WSS) protocol for transaction security. There are several implementations of the WSS protocol available and it is suggested that one of those be used where possible. The following sections assume appropriate headers are included as defined by the "EBS – Generic Security SOAP Specification".

The response message will be signed using the EBS certificate and the results object of the response will be encrypted using the AES128-CBC encryption algorithm and will need to be decrypted by the caller before using the returned data.

SOAP Message:

SOAP is an XML-based standard protocol that defines a message specification for transmitting XML documents via a network. Since this message specification does not depend on a particular programming language or operating system (OS), data transfer can be conducted among and between systems that use different languages or operating systems.

All attachments will be sent and received using the MTOM attachment protocol.

The Message WSDL

A WSDL is a specification for coding web services-related information (access point and interface specifications, etc.) in XML. Note that while WSDL does not define a protocol when sending/receiving messages, the ministry is using SOAP via HTTPS as the protocol for message transmission.

WSDL Definitions Table

The WSDL includes the following standard elements:
Access EDT Web Service URL
Internet Access Electronic Data Transfer Web Service1443/EDTService/EDTService
ENA Access Electronic Data Transfer Web Service1443/EDTService/EDTService

The complete EBS-EDT Message WSDL is available upon request.

Back to top


Validation Message Schema

The MCEDT message schema includes definitions of both the request and the response elements. Schema elements are described below, and the full schema is available upon request.

Data Specifications for Fields

The fields described in the message specification are necessarily generic in order to follow the XML data typing standards. However, in order to pass validation, some of the fields must be presented in the format expected by the ministry.

WS-Security will be used to encrypt the returning data. All returning attachments will be encrypted with the public key of the callers signing certificate. For more information please refer to the ‘MOHLTC EBS – Generic Security Specification’ document. For information on the currently supported file/resource types refer to the ‘MCEDT CURRENTLY SUPPORT FILE/RESOURCE TYPES’ addendum.

The maximum attachment size that will be accepted by MCEDT is 10 megabytes.

Methods

Upload

The operation will be used to upload one or up to 5 documents from external users. Each attachment has a maximum size of 10 megabytes.

Input (Request) Message Fields
name="content" type="xs:base64Binary"

The content of the file being uploaded. The content is sent as an attachment using the MTOM protocol. The maximum attachment size of 10 megabytes.

name="description" type="xs:string"

A custom description (name) of the file. The maximum length is 50 characters.

name="resourceType" type="xs:string"

A resource type as specified by the getTypeList method.

Output (Response) Message Fields

name="auditID" type="xs:string" pattern= "
[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier (UUID). A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="description" type="xs:string"

The description (name) sent in the input data for the file. The maximum length is 50 characters.

name="resourceID" type="xs:integer"

The EDT Identification of the resource uploaded.

name="code" type="xs:string"

The response code for the request.

Code Description
IEDTS0001 Success
EEDTS0003 Resource Type Not Found
EEDTS0010 File Upload Failed
EEDTS0012 MOH ID not Valid
EEDTS0061 User does not have permission to perform this action
ECLAM0002 Mal Formed Header
ECLAM0003 Missing Billing Number in the header
ECLAM0005 Mal Formed Trailer. Claim Header – 1 header count does not match number of Claim Header – 1 headers in batch
ECLAM0006 Mal Formed Trailer. Claim Header – 2 header count does not match number of Claim Header – 2 headers in batch
ECLAM0007 Mal Formed Trailer. Item Record count does not match number of Item Records in batch
ECLAM0008 Claim File must be 79 bytes;
EOBEC0002 OBEC File is an invalid length
EOBEC0003 Mal Formed Header. The ‘OBE’ in the transaction code field is invalid.
EOBEC0004 OBEC Health Number length invalid.
EOBEC0005 OBEC Health Number is not numeric.

NOTE: Specific error response codes can be returned based on the type of file being uploaded. The error codes for specific file types can be found as addendums to this technical specification.

name="msg" type="xs:string"
The response code message for the request.

name="status" type=" tns:resourceStatus"
The current status of the resource. i.e. UPLOADED

Submit

The operation submits a list of documents to be processed by the ministry.

Input (Request) Message Fields

maxoccurs="100" minOccurs="1" name="resourceIDs" type="xs: integer"
The list of file ids to submit.

Output (Response) Message Fields

name="auditID" type="xs:string" pattern=
"[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier (UUID). A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="description" type="xs:string"
The custom description (name) sent when the resource was uploaded or updated. Maximum length is 50 characters.

name="resourceID" type="xs:integer"
The file id of the file submitted.

name="code" type="xs:string"
The response code for the request.

Code Description
IEDTS0001 Success
EEDTS0012 MOH ID not Valid
EEDTS0050 User not Allowed
EEDTS0051 No Data for Processing
EEDTS0052 Data Processing failed
EEDTS0054 User that is submitting the resource is not the same as the user that uploaded it.
EEDTS0055 The resource is not in the upload status so cannot be submitted
EEDTS0056 The resource id specified cannot be found.

name="msg" type="xs:string"
The response code message for the request.

name="status" type=" tns:resourceStatus"
The current status of the resource. i.e. SUBMITTED.

Download

The operation downloads a list of up to 5 documents from the ministry.

Input (Request) Message Fields

maxoccurs="5" minOccurs="1" name="resourceIDs" type="xs:integer"
The list of file ids to download.

Output (Response) Message Fields

name="auditID" type="xs:string" pattern=
"[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier. A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="content" type="xs:base64Binary"
The content of the file being downloaded. The content is received as an attachment using the MTOM protocol.

name="resourceID" type="xs:integer"
The file id of the file dowloaded.

name="resourceType" type="xs:string"
A resource type as specified by the getTypeList method.

name="description" type="xs:string"
The description (name) sent in the input data for the file. The maximum length is 50 characters.

name="code" type="xs:string"
The response code for the request.

Code Description
IEDTS0001 Success
EEDTS0012 MOH ID not Valid
EEDTS0050 User not Allowed
EEDTS0051 No Data for Processing
EEDTS0052 Data Processing failed
EEDTS0054 User that is submitting the resource is not the same as the user that uploaded it.
EEDTS0056 The resource id specified cannot be found.

name="msg" type="xs:string"
The response code message for the request.

List

The operation returns a list of document references and attributes as specified by the search criteria of the caller. The results are broken into pages of up to 50 items each. The default sort order of the output response is by createTimestamp descending, then resourceType ascending.

Input (Request) Message Fields

Optional Fields

name="resourceType" type="xs:string"
A resource type as specified by the getTypeList method.

name="status" type=" tns:resourceStatus"
The current status of the resource. One of UPLOADED, SUBMITTED, WIP, DOWNLOADABLE, APPROVED, DENIED.

name="pageNo" type=" xs:interger"
The page number of the results page that is to be returned. Page numbers are 1 based and this should be 1 for the initial request.

Output (Response) Message Fields

name="auditID" type="xs:string" pattern=
"[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier. A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="createTimestamp" type="xs:dateTime" The timestamp when the file was created.

name="description" type="xs:string" The description (name) sent in the input data when the file was uploaded. The maximum length is 50 characters.

name="resourceType" type="xs:string" A resource type as specified by the getTypeList method.

name="modifyTimestamp" type="xs:dateTime" The timestamp when the file was last modified.

name="resourceID" type="xs:integer" The file id of the file uploaded/submitted.

name="code" type="xs:string" The response code for the request.

Code Description
IEDTS0001 Success
EEDTS0012 MOH ID not Valid
EEDTS0003 Resource Type Not Found
EEDTS0050 User not Allowed

name="msg" type="xs:string"
The response code message for the request.

name="status" type=" tns:resourceStatus"
The current status of the resource. One of UPLOADED, SUBMITTED, WIP, DOWNLOADABLE, APPROVED, DENIED.

name="resultSize" type="xs:integer"
This represents the total number of pages in the request.

Info

The operation returns a list of document attributes for the specified document ids.

Input (Request) Message Fields

maxoccurs="100" minOccurs="1" name="resourceIDs" type="xs:integer"
The list of file ids to get info on.

Output (Response) Message Fields

name="auditID" type="xs:string" pattern=
"[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier (UUID). A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="createTimestamp" type="xs:dateTime"
The timestamp when the file was created.

name="description" type="xs:string"
The description (name) sent in the input data for the file when uploaded. The maximum length is 50 characters.

name="resourceType" type="xs:string"
A resource type as specified by the getTypeList method.

name="modifyTimestamp" type="xs:dateTime"
The timestamp when the file was last modified.

name="resourceID" type="xs:integer"
The file id of the file uploaded/submitted.

name="code" type="xs:string"
The response code for the request.

Code Description
IEDTS0001 Success
EEDTS0012 MOH ID not Valid
EEDTS0050 User not Allowed
EEDTS0051 No Data for Processing
EEDTS0056 The resource id specified cannot be found

name="msg" type="xs:string"
The response code message for the request.

name="status" type=" tns:resourceStatus"
The current status of the resource. One of UPLOADED, SUBMITTED, WIP, DOWNLOADABLE, APPROVED, DENIED.

Delete

The operation will delete the specified documents from the MCEDT system. Files can only be deleted if they have been uploaded and/or updated but not submitted. Downloadable files cannot be deleted.

Input (Request) Message Fields

maxoccurs="100" minOccurs="1" name="resourceIDs" type="xs:integer"
The list of file ids to delete.

Output (Response) Message Fields

name="auditID" type="xs:string" pattern=
"[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier. A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="description" type="xs:string"
The description (name) sent in the input data for the file when uploaded. The maximum length is 50 characters.

name="resourceID" type="xs:integer"
The file id of the file deleted.

name="code" type="xs:string"
The response code for the request.

Code Description
IEDTS0001 Success
EEDTS0012 MOH ID not Valid
EEDTS0050 User not Allowed
EEDTS0051 No Data for Processing
EEDTS0052 Data Processing failed
EEDTS0056 The resource id specified cannot be found
EEDTS0057 The resource is not in the upload status so cannot be deleted
EEDTS0058 User that is deleting the resource is not the same as the user that uploaded it

name="msg" type="xs:string"
The response code message for the request.

name="status" type=" tns:resourceStatus"
The current status of the resource. i.e. DELETED

Update

The operation will replace up to 5 documents with the contents and attributes specified.

Input (Request) Message Fields

name="content" type="xs:base64Binary"
The content of the file being uploaded. The content is sent as an attachment using the MTOM protocol.

name="resourceID" type="xs:integer"
The file id of the file updated.

Output (Response) Message Fields

name="auditID" type="xs:string" pattern=
"[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier. A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="description" type="xs:string"
The description (name) sent in the input data for the file when uploaded. Maximum length 50 characters.

name="resourceID" type="xs:integer"
The file id of the file updated.

name="code" type="xs:string"
The response code for the request.

Code Description
IEDTS0001 Success
EEDTS0012 MOH ID not Valid
EEDTS0050 User not Allowed
EEDTS0051 No Data for Processing
EEDTS0052 Data Processing failed
EEDTS0053 Data Not Processed
EEDTS0054 User that is submitting the resource is not the same as the user that uploaded it.
EEDTS0056 The resource id specified cannot be found.
EEDTS0059 The resource is not in the upload status so cannot be updated
EEDTS0060 User that is updating the resource is not the same as the user that uploaded it
ECLAM0002 Mal Formed Header
ECLAM0003 Missing Billing Number in the header
ECLAM0005 Mal Formed Trailer. Claim Header – 1 header count does not match number of Claim Header – 1 headers in batch
ECLAM0006 Mal Formed Trailer. Claim Header – 2 header count does not match number of Claim Header – 2 headers in batch
ECLAM0007 Mal Formed Trailer. Item Record count does not match number of Item Records in batch
ECLAM0008 Claim File must be 79 bytes
EOBEC0002 OBEC File is an invalid length
EOBEC0003 Mal Formed Header. The ‘OBE‘ in the transaction code field is invalid.
EOBEC0004 OBEC Health Number length invalid.
EOBEC0005 OBEC Health Number is not numeric.

name="msg" type="xs:string"
The response code message for the request.

name="status" type=" tns:resourceStatus"
The current status of the resource. i.e. UPLOADED.

getTypeList

The operation will return the list of resources a caller can access. This will provide information on how the resource is used. One of UPLOAD, DOWNLOAD or BOTH processes. It will also specify if additional Primary Group information is also required as part of those processes.

Input (Request) Message Fields

NA

Output (Response) Message Fields

name="auditID" type="xs:string" pattern=
"[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}"

The audit UID is an identifier created by the service for each SOAP message processed. The UID returned is a version 4 Universally Unique Identifier (UUID). A UUID is a 16-byte (128-bit) number. In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters (32 digits and 4 hyphens).

name="access" type=" tns:resourceAccess"
The access permissions of the resource type. One of UPLOAD, DOWNLOAD, BOTH.

name="groupRequired" type="xs:boolean"
Set to true if a group claim submission number is required to use this file.

name="descriptionEn" type="xs:string"
name="descriptionFr" type="xs:string"
The description of the resource type specified in the "resource Type" field below.

name="resourceType" type="xs:string"
The resource type being definded. Maximum of 3 characters in length. See MCEDT CURRENTLY SUPPORTED FILE/RESOURCE TYPES ADDENDUM: for a list of the currently supported types.

name="csns" type="tns:csnData"
A list of csn/group pairs that represent what the user must specify to use the resource. A solo claim submission number will always be provided. A group will only be provided if access has been restricted to a specific group identity by a Service User.

name="code" type="xs:string"
The response code for the request.

Code Description
EEDTS0012 MOH ID not Valid
EEDTS0050 User not Allowed

name="msg" type="xs:string"
The response code message for the request.

Testing

Conformance testing must be completed for MCEDT. For more details please refer to the Testing section in the MOHLTC EBS – Generic Security SOAP Specification' document or Section 9 Conformance Testing in the Medical Claims Electronic Data Transfer Reference Manual.

Back to top


Appendix A: Error Codes

Character based error codes are returned as well as textual descriptions of the error. All ministry specific error codes are 9 characters.

The following are the ministry specific error codes that may be returned within an EBS Fault accompanied by brief explanations.

EBS Fault Code Error Comment
SMIDL0100 System not initialized correctly; contact your technical support or software vendor.
SMIDL0203 Service is not available; contact your technical support or software vendor.
SMIDL0204 General System Error; contact your technical support or software vendor.

MCEDT Currently Supported Status Types Addendum

Status Type Description
UPLOADED File has been uploaded
SUBMITTED File has been submitted and ready to be processed
WIP File has been sent for processing
DOWNLOADABLE File is available for download
DELETED File has been logically deleted
APPROVED Stale Dated Claim has been approved
DENIED Stale Dated Claim has been denied

MCEDT Currently Supported File/Resource Types Addendum

Inbound

File Type Description
CL Claims
OB OBEC
SDC Stale Dated Claims
RHB Reciprocal Hospital Billing
File Type Description
OO OBEC Response
ER Error Reports
ES Error Report Extract
RA Remittance Advice
RS Remittance Advice Extract
BE Batch Edit
AH Academic Health Governance Report
Code Description
CO EC Outside Use report
CS EC Summary report
NS Northern Specialist APP Governance
MR Claims Mail File Reject Message
OR OBEC Mail File Reject Message
GCM General Ministry Communications
PSP Payment Summary Report PDF
PSX Payment Summary Report XML
RCP Roster Capitation Report PDF
RCX Roster Capitation Report XML
VAP ADP Vendor Report PDF
VHP Home Oxygen Vendor Report PDF
VAX ADP Vendor Report Excel
VHX Home Oxygen Vendor Report Excel

Claim and Stale Dated Claim File Upload Error Codes Addendum

Returned Error Code Description
ECLAM0002 Mal Formed Header
ECLAM0003 Missing Billing Number in the header
ECLAM0005 Mal Formed Trailer. Claim Header –  1 header count does not match number of Claim Header – 1 headers in batch
ECLAM0006 Mal Formed Trailer. Claim Header – 2 header count does not match number of Claim Header – 2 headers in batch
ECLAM0007 Mal Formed Trailer. Item Record count does not match number of Item Records in batch
ECLAM0008 Claim File must be 79 bytes

OBEC File Upload Error Codes Addendum

Returned Error Code Description
EOBEC0002 File is an invalid length
EOBEC0003 Mal Formed Header. The ‘OBE’ in the transaction code field is invalid.
EOBEC0004 OBEC Health Number length invalid.
EOBEC0005 OBEC Health Number is not numeric.

Back to top


Image:Pdf icon.gif To view PDF format files, you need to have Adobe Acrobat® Reader installed on your computer.
You can download this free software from the Adobe Web site.

For More Information

Call the Service Support Contact Centre (SSCC) at: 1-800 262-6524
Hours of operation: 8:00 a.m. – 5:00 p.m. Monday – Friday, except holidays
E-mail: SSContactCentre.MOH@ontario.ca