Virginia Elite v3 Data Dictionary Version 126.96.36.199 (Effective date - 07.27.2020)
Posted by Bryan Hodges, Last modified by Bryan Hodges on 16 June 2020 05:18 PM
Important Note regarding the version number: When the previous version was released, there was confusion regarding the version number since Virginia is on NEMSIS v3.4.0. To clarify, the version number of the new dictionary is being adjusted to 188.8.131.52 (the 4th digit will indicate the number of times a new dictionary is produced while on 3.4.0). This change should not be interpreted as any sort of reversal. It is a move forward.
OEMS has revised and is publishing an updated EMS Virginia Data Dictionary (version 184.108.40.206) along with a version change document. The version change document attached to this article (Virginia Data Dictionary Change Log v220.127.116.11) documents the changes made from the previous data dictionary.
The data dictionary changes will not go into effect until 07.27.2020. It is being released early so agencies and vendors will have an opportunity to review the documents and adjust their internal reporting systems if needed.
As in the past, agencies may submit beyond the minimum dataset as outlined in the Virginia Data Dictionary. However, there are considerations to this agencies must adhere to.
If an agency has mapping questions, your vendor should be an agencies first point of contact. While OEMS personnel are available to make mapping recommendations, we cannot instruct agencies on performing those actions in their system. An agency may have outside integrations, such as CAD or Billing, which could be adversely affected if data mappings are handle incorrectly. This is why an agencies software vendor must be the primary resource when making system changes.
OEMS also recommends software vendors contact their customers and make sure they are up to date on Virginia requirements. Many times, OEMS will contact an agency concerning a data issue only to have the agency state their vendor is supposed to be making sure all of this is working correctly. If any agency or vendor needs a recommendation on what values to map to, please contact support and we will be more than glad to assist.
In conjunction with the release of this updated dictionary, new validation rules and a new Schematron file have been produced. For more information on these, please use the below links and refer to those specific articles:
Validation Rules changes (effective 07.27.2020):
Schematron (effective 07.27.2020)
For question concerning any of this, please contact OEMS support via email: email@example.com