WHO SMART Guidelines - Measles Immunization, published by WHO. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/WorldHealthOrganization/smart-example-immz and changes regularly. See the Directory of published versions
Business Processes
This page describes the business processes included in the WHO Digital Adaptation Kit (DAK): SMART Guidelines for Immunizations (link forthcoming). For full details, see the published DAK content.
A business process, or process, is a set of related activities or tasks performed together to achieve the objectives of the health programme area, such as registration, counselling, referrals. Workflows are a visual representation of the progression of activities (tasks, events, interactions) that are performed within the business process. The workflow provides a “story” for the business process being diagrammed and is used to enhance communication and collaboration among users, stakeholders and engineers.
The DAK for Immunizations focuses on key business processes that are part of routine immunization programmes and mass immunization campaigns.
Overview of Key Business Processes
The following table describes the workflows of the included processes.
| # | Process Name | Process ID | Personas | Objectives |
|---|---|---|---|---|
| Title | ID used to reference this process throughout the DAK | Individuals interacting to complete the process | A concrete statement describing what the process seeks to achieve | |
| A | Facility Registration | IMMZ.A |
IIS Staff Facility Staff |
All facilities (including private sector facilities) that are able to administer vaccines must be registered and uniquely identified to enable appropriate tracking of vaccine coverage and stock. |
| B | Plan Service Delivery | IMMZ.B | Health worker |
To prepare for vaccination session. Ensure sufficient supply, and organise their workload |
| C | Query Client Record | IMMZ.C | Health worker | Correctly locate or identify a client’s immunization record as well as review and update a client’s record to provide a complete immunization history |
| D | Register client | IMMZ.D | Health worker | Start and contribute to the clients’ lifelong vaccine record |
| E | Administer Vaccine | IMMZ.E | Health worker | To determine what vaccines a client needs, administer those, and record the relevant necessary data both in the system as well as on the appropriate paper records |
| F | Client reminder | IMMZ.F | Health worker | To remind clients it is time to return for a vaccine |
| G | Defaulter tracing | IMMZ.G | Health worker | Identify those who are overdue for a vaccine and contact them to have them come to be vaccinated. |
| H | Resolve duplicate client records | IMMZ.H |
Health worker IIS Staff |
To identify duplicate client records and consolidate them into one most accurate/suitable (best) record |
| I | Resolve duplicate vaccine events | IMMZ.I |
Health worker IIS Staff |
To identify duplicate vaccination events within a client record and update into one event. |
| J | Report generation | IMMZ.J |
Health worker IIS Staff |
To provide the ability to access and analyse data and to improve immunization program decision making |
Workflows
The workflows that follow depict processes that have been generalized across different contexts and may not reflect the variability and nuances across different settings. The simplicity of the workflow may not adequately illustrate the nonlinear steps that may occur.
Overview of key immunization process flows
The business processes included in the DAK are shown in the following figure. Processes included in the DAK start with a letter (e.g. "A.") and are shown using the "Activity with sub-process" shape, which includes a plus sign.
A. Facility Registration
Objective: All facilities that are able to administer vaccines must be registered and uniquely identified to enable appropriate tracking of vaccine coverage and stock. There are situations where the locations providing vaccines may not be a permanent physical facility but rather some kind of public health authority (as is the case with some temporary or pop up clinics). These may be included as per local policy or needs.
Many countries have a National Master Facility List (NMFL) also called a facility registry. How this is updated and maintained is not part of this workflow.
Each step can often be done by either the system (automated) or may be performed by an actual person who is responsible for the system, this will depend entirely on how the system is implemented. In some situation it may be automated for certain data (for example a new facility notification may come directly from the NMFL) or manual (for example changes to fridge capacity may come via a paper form and entered by IIS staff).
B. Service Plan Delivery
Objective: The objective is to prepare for an immunization session, either at the facility or done on an outreach basis. The primary difference if done as outreach is that all equipment and vaccines must be properly packaged (cold box) for transport.
Note: There are opportunities to integrate with stock management systems to provide the HW with automated views and stock alerts.
C. Query Client Record
Objective: The objective is to correctly locate or identify a client’s immunization record as well as review and update a client’s record to provide a complete immunization history. This will be used to determine recommended vaccines and due dates, allowing providers to recommend and discuss immunizations with the client. It may also be used if the client record needs to be recreated in case original paper record is lost.
D. Register Client
Objective: The objective is to start or contribute to the client’s lifelong immunization record. This will allow providers and the client/mother to identify what vaccinations have been given. Adult clients requiring a new vaccine (such as COVID-19 vaccines) will typically not be in the system as it may not have been available when they received their childhood vaccines. How this is handled will vary widely. It may be possible to import records from another system (such as a universal health insurance system) or from a list from another source (such as an external scheduling or registration system), or they may all be required to be entered manually. This will depend on local capacity and policy. If starting with a paper record, there are some vaccination records (home-based record) that may require additional security/validation features in the paper record for validation. For more information, please refer to Digital Documentation of COVID-19 Certificates: Vaccination Status (23).
E. Administer Vaccine
Objective: The objective is to determine what vaccines a client needs, administer those, and record the relevant necessary data both in the system as well as on the appropriate paper records. Clients will enter this process in a variety of ways. They may be coming for one in a series of routine childhood vaccines, they may be a healthcare worker requiring a vaccine for work, they may be an adult seeking a vaccine for COVID-19 or an annual flu vaccine, or a student getting a vaccine for HPV at a school vaccination clinic. This will also apply to catch up campaigns, although they will often be conducted as outreach/mobile clinics. Supplementary vaccine campaigns do not follow the process below as they vary widely on what is recorded on an individuals record and determining eligibility (everyone in the age range will be eligible regardless of vaccine status, since the dose is supplemental to any series.
F. Client Reminder
Objective: The objective is to correctly locate or identify a client’s immunization record as well as review and update a client’s record to provide a complete immunization history. This will be used to determine recommended vaccines and due dates, allowing providers to recommend and discuss immunizations with the client. It may also be used if the client record needs to be recreated in case original paper record is lost.![image]
