EMS regulations require every licensed Virginia EMS agency to submit patient care records with the required minimum dataset on a schedule established by the Virginia Office of EMS (OEMS), as authorized in §32.1-116.1 of the Code of Virginia. The OEMS uses this data to generate an EMS Data Quality Report each month. This report is posted on the OEMS website (below), and is provided to the OEMS Director, the OEMS Division of Regulation and Compliance Enforcement, the OEMS Rescue Squad Assistance Fund grants program, and all Virginia EMS agency superusers, as well as other local, state, and national stakeholders.
Beginning in 2025, the OEMS is now publishing 2 data quality reports.
- EMS Data Quality Report:
- PDF version – This is the same PDF as has been previously published.
- Spreadsheet version – This is a read-only spreadsheet version of the above PDF that allows for filtering.
- EMS Vendor Data Quality Report (PDF) – This PDF contains data quality information broken down by EMS software vendors.
- EMS Vendor Data Quality Report (PDF) - January 2025
- EMS Agency Data Quality Report (PDF) - January 2025
- EMS Vendor Data Quality Report (PDF) - February 2025
- EMS Agency Data Quality Report (PDF) - February 2025
- EMS Vendor Data Quality Report (PDF) - August 2025
- EMS Agency Data Quality Report (PDF) - August 2025
- EMS Vendor Data Quality Report (PDF) - September 2025
- EMS Agency Data Quality Report (PDF) - September 2025
- EMS Vendor Data Quality Report (PDF) - October 2025
- EMS Agency Data Quality Report (PDF) - October 2025
Report Methodology
This report provides the following information:
- EMS Agency number: the license number assigned by the OEMS Division of Regulation, Compliance, and Enforcement
- EMS Agency name: the agency name as it appears on the EMS agency’s license on file with the OEMS Division of Regulation, Compliance, and Enforcement
- Region: the name of the Regional Council in which the agency’s headquarters is located
- NEMSIS version: the NEMSIS version used to report the data
- Of note, the NEMSIS version field is only shown in reports for the months that Virginia EMS agencies are transitioning from NEMSIS v3.4 to NEMSIS v3.5. During a single month, an agency may show data submitted using both NEMSIS versions. This is expected, as agencies typically move from v3.4 to v3.5 mid-month. Should an agency find they are submitting both versions beyond a single month, agencies should contact their EMS software vendor to determine why this is occurring.
- Records Submitted: the total number of records an agency submitted to the Virginia EMS data repository for processing for the month of the report (excluding records with a pending or blank submission status)
- Records Failed: the total number of records that failed validation/Schematron requirements and did not process into the Virginia EMS data repository for the month of the report
- Records Passed: the total number of records that did not fail validation/Schematron requirements and did process into the Virginia EMS data repository for the month of the report
- Data Quality:

-
-
-
- Software Vendor: the EMS software vendor the agency uses to submit data to the Virginia EMS data repository
-
-
†For guidance on the approved method, please contact OEMS support at oems-appsupport@vdh.virginia.gov
‡EMS agencies listed on a report as “Failed to Submit” are encouraged to contact OEMS support at oems-appsupport@vdh.virginia.gov to come up with solutions for your agency.
The OEMS System Optimization Division is committed to working with all EMS agencies and EMS software vendors on data quality–related issues. Our goal is to identify ways to improve data quality with minimal impact on EMS agencies, while also participating in statewide and national data research projects.
Agencies requiring technical assistance related to data quality or Virginia EMS Repository submissions should first contact their Regional EMS Council, which serves as the primary point of contact for agency-level support, including submission issues, data review, and data quality improvement efforts. If additional guidance or technical assistance is needed beyond what the Regional EMS Council can provide, the Council will coordinate directly with the OEMS Division of System Optimization.
Agencies with NO EMS patient care reports (runs) for a given month are required to submit a support ticket via the System Optimization Division Support Request link below indicating that no EMS runs occurred and specifying the applicable reporting month. This notification should be completed within the first 7 calendar days of the new month to ensure accurate reporting and compliance with monthly submission requirements.
If there are validation issues that EMS software vendors cannot help their customers (i.e., EMS agencies) resolve, both the agency and vendor should reach out to the OEMS System Optimization Division for assistance.
For any questions regarding data quality, data submissions, or to submit a "no runs" report, please utilize the request form link below.