Minimum Cases Per Month Upload Requirement:
Due to the time and effort required to initiate and maintain extraction on behalf of the EMS agency, ePCR vendor, and CARES, an agency must meet the minimum requirement of at least 10 CARES-qualifying cases per month for upload. If your agency is approved to move forward with the upload process and you are an existing registry participant, the current method of desktop data entry must be continued until electronic upload to the CARES production site is activated. If you have any questions or concerns, please contact your CARES liaison.
Important notes to all vendor IT developers/programmers:
Please ONLY use the XML Data Dictionary for reference in developing your XML Import file, rather than the CARES (Clinical) Data Dictionary PDF which is ONLY for CARES end users and coordinators. Required elements that must be passed in the XML file for CARES purposes are CARES Elements 1-11, 13-22, 25-27, and 29-32. Optional elements to pass in the XML file are CARES Elements 12, 23-24, 28, 33-46, and 60-69. If the agency is a CARES/HeartRescue site, all CARES Required and Optional elements 1-46 and 60-69 must be passed. To view PDFs of the CARES elements, please refer to "CARES Required Elements" and/or "CARES Required and Optional Elements" links on the Upload Resources for V3 Submissions page.
PARSING NOTES: If an XML file contains a call that already exists in the system with the same Date of Arrest and Incident Number for a given agency (eArrest.14 or Custom element servicedate and eResponse.03), the file will not parse and none of the records within the XML file will be processed.
Test data sent to the Beta server should not contain any PHI.
myCARES Web Services
myCARES now accepts both REST and SOAP requests. Our REST web service is the traditional method vendors have been using for some time. Now, we have added a SOAP web service that allows vendors to use the same functionality they have developed for NEMSIS compliant data submission. See the NEMSIS website for more information about SOAP submissions and NEMSIS requirements.
Both REST submissions and SOAP messages include a way to indicate which XSD to use (NEMSIS 3.3.4, 3.4.0 or 3.5.0). myCARES validation does not include a CARES-specific XSD.
When data is submitted using REST or SOAP, an XML file is created on one of our servers for that submission. Each file is then processed as follows:
- There is a finite list of items that will cause file rejection in early processing - namely the absence of these custom elements: AgencyID, FormID, ImportVersion, ImportMethod.
- Regardless of how that file was submitted, the file is checked against the NEMSIS XSD. If the XML is not well-formed or XSD validation fails, the file is rejected.
- If the file passes steps 1 and 2, it is then validated against the NEMSIS schematron. This check produces informational data, since there is no case where the file will be rejected.
- The file is validated against the CARES schematron. Any of the custom elements, if present, must pass a proper value or the file will be rejected. Since the file will be rejected at the database level in these cases, we are now stopping processing prior to that. Otherwise, the record will be parsed. The CARES schematron is a dynamic file, please check back frequently under the desired v3 Upload Resources pages below.
- XSD failures and schematron results are available in the File Upload Validation Report, accessed via account login at mycares.net
- XSD/Schematron validations are file-based. The validation information is tied to the agency credentials in your submission. For example, if you are sending a file that contains records for one to multiple agencies, the validation information will only be available in the File Upload Validation Report for the agency (credentials) used to submit the file.
Agency Identification Process:
When a file passes validation and enters the final review before posting to the database, myCARES will cross-check the file for two levels of agency identification accuracy:
- An AgencyID in the eCustomConfiguration.AgencyID XML field that matches the database AgencyID and
- dAgency.01 and dAgency.02 values from the XML file matching these respective values entered in the database, along with dAgency.04.
Should there be any changes to the dAgency.01 or dAgency.02 values for an agency at any time, please notify Monica Rajdev (firstname.lastname@example.org) immediately so that myCARES may be updated. If the AgencyID and dAgency value combinations of an individual Patient Care Report do not match the values entered into myCARES, that incident will not upload to the database.