When do I need to use the Vaccination Data Model?
The Vaccination Data Model relates to biological preparations that provides active acquired immunity to a particular disease. A vaccine typically contains an agent that resembles a disease-causing microorganism and is often made from weakened or killed forms of the microbe, its toxins, or one of its surface proteins. Another name for a vaccination is an immunization.
The Vaccination Data Model is usually triggered at administration, not ordering. Therefore, it is most useful for applications that want to know when a patient has been administered a vaccination.
When and where can the Vaccination Data Model be supported?
Vaccinations are most commonly administered in outpatient settings. Additionally, supporting transactions between the EHR and immunization registries was one of the three possible public health components in Meaningful Use 2. As a result, EHRs with an ambulatory focus oftentimes have developed support for vaccination interfaces to meet the MU criteria, generally through HL7v2 VXU messages.
What other Data Models is Vaccination similar to?
- Both follow a similar workflow where they are ordered by a physician and administered to a patient.
- Vaccinations are proactive, in that they are given prior to an infection occurring. Medications may be given proactively or retroactively (after illness symptoms have occurred)
- Vaccinations are dead versions of a micro-organism. Medications are generally compounds that hurt or fight micro-organisms or disease symptoms.