Last updated: 15 September 2023
At the request of the PAHO Regional Office, the UiO presents this document for review and validation which is a detailed compilation of the information required for the design and development of the new Surveillance system, which will replace the current ISIS system, as a regional platform and eventually, to be available for countries that want to implement it at the national level.
PAHO's Immunization Program needs to develop strategies for monitoring, control, and elimination of vaccine-preventable diseases in the Latin American region. To do this, it is necessary to have tools that facilitate Member States the process of reporting on progress in this regard as well as allowing PAHO to take different actions, such as providing feedback to countries on data received, preparing periodic bulletins and sharing information with other instances, like WHO.
The UiO team has been working jointly with the Department of Family, Health Promotion and Life Course Immunization team in the requirements gathering process, which was initiated in October of 2022.
The solution proposed is aligned with the objectives and scope of assignments indicated in the TORs, that:
- It´s focused but not limited to Measles / Rubella, CRS and Polio A web-based platform. This is one of the most relevant characteristics of the solution since other diseases will be able to be included/configure in the future if required
- It has customizable data entry interface
- It has interoperable capabilities
- It has the capacity to access the platform offline or where the internet connection is not good or not available at all. This is feasible using the mobile Android DHIS2 App. It will be demonstrated to the PAHO team when required.
- It has administration tools
- It´s administrable and manageable. This will be possible due the Capacity Building activities included in the whole process
| Aggregate Data Sets | Description | Level (OU assignment) | Period | User Groups |
|---|---|---|---|---|
| Population UN | UN population data estimates UN births UN <15 UN Total | Level 2 (Country/Pais) | Annual | PAHO VPD - Admins |
| Population - country data Poblacion - pais | Country population data Country’s births Country <15 estimate Country total | Level 3, maybe Level 4 | Annual | Country users (data focal point) |
| Ontime reporting/notificacion negativa | Contains 2 DEs: OT-Base (total reporting units) OT-ReportsOnTime Used to provide reporting rate calculations (inlcuding ‘zero reporting’ | Level 2 (Country/Pais) | Weekly | PAHO - VPD Admins? |
| Congenital Rubella Syndrome (CRS) | ~7 DEs suspected/confirmed/discarded SRC -includes last Epi year/Epi week for last case confi | Level 2 (Country) or lower depending on country reporting | Annual | Country users |
| Programs | Description | Level (OU assignment) | User Groups |
|---|---|---|---|
| Measles/Rubella Sarampion | Level 4 (municipality/municipalidad) | ||
| VPD - Polio | Country population data | Level 4 (municipality/municipalidad) |
The OU hierarchy follows the structure already in place for PAHO’s regional system (ISIS), which only goes to the Municipality level.
All organisation units have shapefiles (where available); municipalities at L4 also use polygons (no coordinates).
The following custom attributes have been created for the PAHO implementation, these are used for importing shapefiles and ensuring they are assigned to the right levels.
- ADM1Name
- ADM2Name
- CountryID
- CountryName
- Country Code
Org unit groups are used to group countries (and their children) in sub-regions, which are often used in regional bulletins or visualizations. Each group contains the respective countries and subdivisions.
- AND
- CAP
- LAC
- NORTH AMERICA
- MEXICO
- SOC
The OUGS ‘Regions’ is used as a data dimension to slice the data in the analytics tools.
Note that org units within an OUGS *must* be exclusive (that is, one OU cannot belong to more than one OUG within the same OUGS)
The VPD-SMART system has 9 types of user roles, each serving different purposes in data capture and management processes. These roles are distributed as follows:
- Administrators
- SuperAdmin:
- Permissions:
- Available app authorities: With this role, users can access any application installed in the DHIS2 system.
- Available tracker authorities: This role allows users to perform the following actions:
- Search Tracked Entity Instance in All Org Units
- Ignore validation of required fields in Tracker and Event Capture
- Delete enrollment and associated events
- View event analytics
- Delete tracked entity instance and associated enrollments and events
- Administer program dashboard configuration
- Tracker importer (experimental)
- Merge tracked entity instances
- Mark events as incomplete
- Available import/export authorities: Similarly, users can perform data migration processes with the following actions:
- Import events
- Export data
- Skip data import audit
- Import data
- Import metadata
- Export events
- Export metadata
- Available system authorities: This role also includes full authority to modify metadata, data, and other actions in the system.
- Permissions:
- VPD-Admin:
- Permissions:
- Available app authorities: This role grants access to applications such as Tracker, data import/export, and system configurations.
- Available tracker authorities: This role allows users to perform the following actions:
- Merge tracked entity instances
- Search Tracked Entity Instance in All Org Units
- Delete enrollment and associated events
- View event analytics
- Manage program rule
- Delete tracked entity instance and associated enrollments and events
- Administer program dashboard configuration
- Available import/export authorities: Not applicable.
- Available system authorities: Not applicable.
- Permissions:
- SuperAdmin:
- Data Entry Personnel
- VPD-MR-VIG LIMITED AUTHORITIES (Lab data): This role is designed for capturing laboratory data in the Final Result, Sequencing, Intratypic Differentiation, and Viral Isolation stages (program rule "IisAMNKD7VW").
- Other features: Not applicable.
- VPD-MR-LAB LIMITED AUTHORITIES (Lab data): This role permits data capture only in the Specimen section for fields: Date sent to process, Type of Sample, Date of sample collection, and Sample Number.
- Other features: Not applicable.
- VPD - Data entry:
- Available app authorities: This role provides access to applications such as Data Entry (Beta), Event Visualizer, Event Reports, Messaging, and Dashboard.
- Available tracker authorities: Not applicable.
- Available import/export authorities: Not applicable.
- Available system authorities: Not applicable.
- VPD - Data capture:
- Available app authorities: This role grants access to applications like Browser Cache Cleaner, Capture, and Dashboard.
- Available tracker authorities: This role allows users to perform the following actions:
- Search Tracked Entity Instance in All Org Units
- Merge tracked entity instances
- View event analytics
- Update tracked entities
- Administer program dashboard configuration
- Available import/export authorities: Not applicable.
- Available system authorities: Not applicable.
- VPD-AFP-VIG LIMITED AUTHORITIES (Lab data): With this role, users can only capture data from the Specimen and Type of sample sections.
- Fields: Specimen, Type of sample, Sample Number, Date of sample collection, Date sent, Laboratory name, Date received, Internal sample code 1.
- Other features: Not applicable.
- VPD-AFP-LAB LIMITED AUTHORITIES (Lab data): This role is specifically for capturing information in sections such as Genotyping (Rubella), Viral Detection (Rubella), Genotyping (Measles), Viral Detection (Measles), and positive tests for other viruses (Rubella and Measles).
- Other features: Not applicable.
- VPD-MR-VIG LIMITED AUTHORITIES (Lab data): This role is designed for capturing laboratory data in the Final Result, Sequencing, Intratypic Differentiation, and Viral Isolation stages (program rule "IisAMNKD7VW").
- Data Analysts
- VPD - Analytics: This role is solely for visualizing and generating data reports.
- Other features: Not applicable.
- Available app authorities:
- Interpretation app
- EpiWeek app
- Event Reports app
- Data Visualizer app
- Dashboard app
- Information app
- Browser Cache Cleaner app
- Linelisting app
- HMIS Dictionary app
- Maps app
- Available tracker authorities:
- View event analytics
- Available import/export authorities: Not applicable.
- Available system authorities: Not applicable.
- VPD - Analytics: This role is solely for visualizing and generating data reports.
The user groups implemented in the VPD system play a crucial role in managing access and modification permissions for metadata based on specific user requirements. Below is a detailed explanation of the functionality of each group:
-
VPD - Admins Member: This group is intended for country-level administrators who need the ability to modify metadata and captured data within the system. It grants them authority over administrative processes without requiring super administrator privileges.
-
VPD - Dashboards Users: Users in this group have restricted privileges to review and modify analytical reports derived from collected data. This restriction ensures that only designated users can access and manipulate analytical resources as needed.
-
VPD - Email Users Alerts: Key users in this group are selected to receive notifications based on predefined validation rules. These alerts are crucial for cases that require review and follow-up, typically due to specific classifications or unique characteristics.
-
VPD - Email Users Alerts Prod: Similar to the previous group, this segment identifies and notifies key users regarding cases that require prompt review and follow-up actions based on predefined rules and criteria.
-
VPD - English Speaking Users: This group manages translations related to CORS and other specific needs as requested by the VPD-PAHO team, ensuring seamless communication and understanding among English-speaking users.
-
VPD - Lab Users: Access to data capture is restricted to authorized users specifically assigned to laboratory modules. This restriction ensures data integrity by preventing unauthorized modifications in fields outside the designated laboratory context.
-
VPD - Measles Users: Users in this group are restricted to accessing and capturing information exclusively related to the Measles program. This limitation ensures that only designated users can interact with and review data and metadata pertinent to the Measles program.
-
VPD - Polio Users: Structured similarly to the Measles Users group, this segment restricts access and modification permissions to information specifically related to the Polio program, maintaining data integrity and program-focused management.
-
VPD - Regional Users: This group facilitates broader access to metadata, enabling users to conduct comprehensive reviews of analytical data at a regional level. It supports informed decision-making and strategic planning by providing access to detailed analytical insights.
-
VPD - Spanish Speaking Users: Specific translations related to CORS and other identified needs are implemented for this user group based on requirements specified by the VPD-PAHO team. This ensures effective communication and utilization of the system among Spanish-speaking users.
These user groups are meticulously designed to align with organizational roles and operational requirements, ensuring secure and efficient management of data access and manipulation within the VPD system.
To facilitate filtering and to make it easier for the user to identify what they are analyzing, the following prefixes are used on long names to distinguish between Measles/Rubella (MR) and AFP/Polio (POL):
- MR - Name
- POL - Name
-
Programs ( Disease data collection forms)
Tracker programs will be created for Measles and Rubella, and another for Polio. This is the type of Program in DHIS2 that provides follow up and to track the entity defined, Cases
A list of main characteristics by alternatives presented in this document, has been included at the end of this section.
- Program Stages
The stages is a mechanism of the DHIS2 Tracker Program that allows replication within the system, the data capture workflow, in a way, that according to it, one or several stages can be included in a program. . The concept of Program Stage has been included in the Glossary of Terms section in this document. In a Tracker Program at least one Stage has to be defined. Using more than one it depends on the workflow and the different steps in this latter and also the users permissions and role in each step. For instance, in the Measles program, it is intended to have
- A Registration process, called Enrolment in DHIS2– to capture all the personal information required by the case. This is a one-time process and intends to create an enrolment per patient per Program. This step also applies if using Case as an Entity.
Specifically, the stages for each Program identified are listed below. Take note that those can be adjusted or changed during the configuration process and according to the use cases that can be identified during the testing and validation process. At this point the stages suggested for the diseases of Polio and Measles/Rubella are:
- Clinical information: Vaccination History, Trips, Clinical data.
- Laboratory: Information about specimens, laboratory tests and results
- Final classification.
Vaccination history and clinical data
-
Data Set - Aggregates
In DHIS2 it is also possible to enter data in a more aggregated level. This is, instead of case by case, identifying the patient(or case), there is a data entry application, called Data Set, that allows to enter totals, disaggregated by some criterion if necessary, for example:
-
Sex
-
Age Range
For the solution proposed, the following Data sets would be created
-
The Population data entry, in order to calculate the rates in the system.
-
The CRS data entry
-
Site notification for negatives
[If there is any potential for misunderstanding or necessity of explanation, please include any kind of justification of the way the package and its modules/stages have been designed]
The program rules were created according to the requirements document delivered by the VPD team. The original document is the following:
https://docs.google.com/spreadsheets/d/11UGKPPbvufY\_06Oz5MqRafIG5WFsV3EZ/edit?gid=219032170\#gid=219032170
The rules created can be found in the following document:
https://docs.google.com/spreadsheets/d/15MJJM1s46rE-OcIfguYJuLnMzTOW-kR\_/edit?gid=1679012049\#gid=1679012049
Name:AFP - Confirmed Case
Id: MCmIOixZNdu
Subject template:Caso confirmado de Sarampion en V{org_unit_name}
Message template: "Se ha registrado un caso confirmado de Polio en V{org_unit_name} en la semana A{MPZ1QsldiKH} - A{BJOIp2AWzaD}.
Por favor verifique el caso:
Numero del caso: A{kR6TpjXjMP7}
Nombre del paciente: A{sLfTm5aHAAy} A{gE9Z5IijE5J}
Edad: A{uiI2pR0ia32} anios, A{WelU0kd868C} meses
Acceda al caso en el siguiente link:
https://vpd-test.paho-dhis2.org/dhis-web-capture/index.html\#/enrollment?enrollmentId=V{enrollment\_id}\&orgUnitId=V{enrollment\_org\_unit\_id}\&programId=V{program\_id}\&teiId=V{tracked\_entity\_id}"
notifyParentOrganisationUnitOnly: TRUE
Recipient user group: mEyOeS62c5D
The columns and query parameters available in the working list are the following:
Case ID
Patient’s full name
Epi week onset
Epi week year onset
Sex
Date of birth
Id number
Age (months) rash onset
Age (years) rash onset
Epi week notification
Type of ID
ID Number
Registration code
Name of the institution notifying
Type of institutional sector
Investigation or home visit date
Municipality of residence
Laboratory
Investigation
Clinical data and Vaccination
The program rules were created according to the requirements document delivered by the VPD team. The original document is the following:
[/business_rules_measles.md)
The rules created can be found in the following document:
https://docs.google.com/spreadsheets/d/15MJJM1s46rE-OcIfguYJuLnMzTOW-kR\_/edit?gid=1679012049\#gid=1679012049
For now only a notification when a confirmed case appears:
Name: MR Confirmed Case
Id: mEyOeS62c5D
Subject template:Caso confirmado de Sarampion en V{org_unit_name}
Message template: "Se ha registrado un caso confirmado de Sarampion en V{org_unit_name} en la semana A{MPZ1QsldiKH} - A{BJOIp2AWzaD}.
Por favor verifique el caso:
Numero del caso: A{kR6TpjXjMP7}
Nombre del paciente: A{sLfTm5aHAAy} A{gE9Z5IijE5J}
Edad: A{uiI2pR0ia32} años, A{WelU0kd868C} meses
Acceda al caso en el siguiente link:
https://vpd-dev.paho-dhis2.org/dhis-web-capture/index.html#/enrollment?enrollmentId=V{enrollment_id}&orgUnitId=V{enrollment_org_unit_id}&programId=V{program_id}&teiId=V{tracked_entity_id}"
notifyParentOrganisationUnitOnly: TRUE
Recipient user group: mEyOeS62c5D
The columns and query parameters available in the working list are the following:
Case ID
Patient’s full name
Epi week onset
Epi week year onset
Id number
Sex
Age (months) rash onset
Epi week notification
Registration code
Detected by
Name of the institution notifying
Investigation or home visit date
Municipality of residence
Script
- Assign EPI week & EPI Year based on the Enrollmment date
- For Polio: enrollment date is the date of initiation of paralysis
- For Measles: enrollment date is the date of initiation of rash
- Therefore, Epi week and Epi year assignment are based on the date of initiation of symptoms in both cases
Custom form
- Polio Tracker Program: makes the columns show left and right for inputting data on location of paralysis on the body
Polio program indicators:
| DHIS2 ID | Name | Description |
|---|---|---|
| AIkMDhKOYUr | AFP basis for discarding (Blanco/Pendiente) | Count of cases where basis for discarding is blank/pending or does not have a value Número de casos de AFP descartados en blanco o pendientes |
| PwHSPYIjr6N | AFP basis for discarding (Guillain-Barré) | Count of cases where basis for discarding is Guillain-Barre |
| rzeecgw8Mlg | AFP basis for discarding (Other diagnosis) | Count of cases discarded on the basis of 'Other diagnosis' |
| H82ztFRHdzD | AFP basis for discarding (Transverse Myelitis) | Count of cases discarded on the basis of 'Transverse myelitis' |
| rlExQ2LJVZ1 | AFP basis for discarding (Traumatic Neuritis) | Count of cases discarded on the basis of 'Traumatic neuritis' |
| n9iHvI72gYY | AFP basis for discarding (Traumatic Neuritis) | Count of cases discarded on the basis of 'Tumor' |
| WFGDF1imvJK | AFP basis for discarding (Unknown) | Count of cases discarded with basis listed as 'unknown' where final classification is not null. |
| IJmaRGyafK8 | AFP cases reported <15 anos | Numero de casos de Polio reportados en menores de 15 anos |
| ZZaL8I7Qxmn | AFP cases reported < 15 years | AFP cases reported between 0 and 15 years; AND has enrollment date (date of paralysis onset) |
| SmORkb5P3J7 | AFP cases reported (total) | Number of AFP cases reported |
| QwAWrymF4sT | AFP cases with lab sample | Count of AFP cases with lab sample (of any type) |
| Ln29J1581mo | AFP cases with lab sample date received and result date reported | Cases with 'date of lab sample received' and 'date of lab result' reported |
| JCTw0HAjUVT | AFP cases with result | Count of cases where Result Isolation has value reported |
| jv9LE1FrokI | AFP cases with sample received <= 14 days, pending result | Count of cases where sample received by lab, but does not yet have a lab result |
| ZiyjfMjblk2 | AFP cases with sample received > 14 days, pending result | Cases with sample received by lab >15 days from date of sample collection, pending lab result |
| jlX1QA39IBo | AFP final classification (Discarded) | Count of AFP cases with final classification 'Discarded' |
| rslSBpFiYr7 | AFP final classification (Pending)/under investigation | Count of AFP cases where final classification is 'Pending' or has no value. |
| f8MEvUkWZct | AFP final classification (Polio compatible) | Count of AFP cases with final classification 'Polio compatible' |
| uQsWJAojbLF | AFP final classification (Polio vaccine associated) | Count of AFP cases with final classification of 'Polio vaccine associated' |
| UIUyFxVWpCv | AFP final classification (Polio vaccine derived) | Count of cases with final classification 'Polio vaccine derived' |
| iydKhL8lc1Y | AFP final classification (Polio wild) | Count of AFP cases with final classification 'Polio Wild' |
| eQ5HSx7oInk | AFP result inadequate | Count of AFP cases where Result Isolation is inadequate |
| qLQhodbzI1v | AFP result negative | Count of AFP cases where Result Isolation is negative |
| hprvggE6Xk5 | AFP result NPEV only | Count of cases where AFP Result Result isolation are non-polio enterovirus (NPEV) only |
| H1DUimdbEp4 | AFP result other virus | Count of AFP cases where Result Isolation is other virus |
| pxeiIP6hkMP | AFP result poliovirus | AFP - with Result / Poliovirus |
| nDFPbpT3WuC | AFP result Poliovirus & NPEV | Count of cases where AFP Result Result isolation is polio AND non-polio enterovirus (NPEV) only |
| nOfIH6vVDko | AFP result received <= 14 days | Number of cases where days between recorded 'Date of results isolation' and recorded 'Date received isolation' <= 14 |
| LB84VlDx2sB | AFP samples not yet received by lab | Count of lab events with type of sample and date of sample collection, but no data for date of result isolation or sample received by lab |
| ysDUAzCxZ7x | AFP samples received by lab (among cases <= 15 yrs) | Need to check. Type of sample has a reference to option code that doesn't exist within the option set. Laboratorio\.VPD-AFP-Type of sample == '1' && isNotNull(Laboratorio\.VPD-AFP-Sample number) && isNotNull(Laboratorio\.VPD-AFP-Date received isolation) && Edad en años al inicio del exantema <= 15 |
| uSzNHNqVHC5 | AFP Under investigation - no borrar | |
| kMmm8EII8SV | AFP samples collected (among <=15 yrs) | Number of samples collected among AFP cases <15 years old |
| W3hSZGU6Jbn | POL -Caso Caliente Criterio <3 vacunas | |
| l6oIP9MdMat | POL -Caso Caliente Criterio <5 años | |
| T3vazQlG04O | POL -Caso Caliente Criterio Fiebre Prodrómica | |
| qBwQ7bDwH4d | POL -Caso Caliente Criterio Parálisis asimétrica | |
| qcSb1M7gLfJ | POL -Caso Caliente Criterio Progresión Rápida | |
| ksCxf7nqbUd | POL -Caso Caliente todos los criterios | |
| KyZWtS28Q0A | AFP case notification rate in country population <15 years (annual) x100,000 | Annual case notification rate: number of AFP cases reported / population <15 years old, as reported by country |
| v3nR1BZtw2m | AFP case notification rate in total country population (annual) per 100,000 | Number of AFP cases reported / total population, per 100,000 |
| lJ2abhsbipD | AFP cases reported (total) | Number of AFP cases reported |
| ZbauSZPweVA | AFP cases with lab result | Count of all AFP/polio enrollments that have lab results: Poliovirus + Poliovirus & NPEV + NPEV + Negativo + Inadecuado |
| jMWUSQJfhMs | AFP cases with result NPEV (%) | Numerator: total number of cases where result isolation is 'NPEV (only)' OR 'NPEV & Poliovirus' Denominator: total cases where Result Isolation has been reported |
| utpDdjGkdT1 | AFP expected cases (annual) based on country population | Annual expected AFP cases based on country reported population <15 years and 1 expected case per 100,000 inhabitants. Calculated annually as country population <15 / 100,000 |
| cmz6jDllc3L | AFP final classification (Polio compatible) | Number of AFP cases with final classification 'Polio compatible' |
| zmvgZrJQVs4 | AFP final classification (Polio vaccine associated) | Number of AFP cases with final classification 'Vaccine associated' |
| atuGRBRBIbP | AFP final classification (Polio vaccine derived) | Number of AFP cases with final classification 'Polio vaccine derived' |
| hxwlaxAj1P6 | AFP final classification (Polio wild) | Number of AFP cases with final classification 'Polio wild' |
| YCCYOIm3jeQ | AFP results received <= 14 days (%) | Numerator: Number of cases where days between recorded 'Date of results isolation' and recorded 'Date received isolation' <= 14 Denominator: Number of cases with lab sample date received and result date reported |
Indicators
Number of expected AFP cases
- Based on population <15 years
- Maybe need another dataset (weekly) to divide the data across weeks & then configure a cumulative indicator
| DHIS2 ID | Name | Description |
|---|---|---|
| MXMj8wM62v6 | MR Adequate Sample taken <= 30 days of Onset of Rash (%) | Numerator: Number of cases with adequate sample taken <= 30 days from Onset of Rash. Denominator: Number of cases with lab sample collected. MRIndic_AdeqSample (Fecha de toma de muestra y fecha de inicio de sÃntomas de exantema <=30) |
| wrUp6qvQguS | MR Adequate Sample taken <= 30 days of Onset of Rash | Number of cases with adequate sample taken <= 30 days from Onset of Rash. |
| dFx4DoBjzzl | MR - %Age range 10 - 14 years | |
| FH7s0YBE3rB | MR - %Age range 12 - 23 months | |
| Nu8EXorhUzD | MR - %Age range 15 - 19 years | |
| JOyI5c3tzgo | MR - %Age range 20 - 24 years | |
| VqBp57GRJE0 | MR - %Age range 2 - 4 years | |
| azOVzdbHsnR | MR - %Age range 25 - 29 years | |
| nM86SgmNG5b | MR - %Age range 30 - 34 years | |
| QGgLo4N44m1 | MR - %Age range 35 - 39 years | |
| HeENUT0TkoO | MR - %Age range >= 40 years | |
| zO9lny7wecc | MR - %Age range 5 - 9 years | |
| aOZLxBMurUo | MR - %Age range 6 - 11 months | |
| Yigo4lxnHE0 | MR - %Age range <6 months | |
| wBtFWReulkj | MR case notification rate (x100,000) population reported by country | Case notification rate: suspected cases of measles/rubella reported x 100,000 population (using country reported population) |
| R7l6fk0wxJ2 | MR cases pending final classification (%) | Cases pending final classification / total suspected cases reported x 100 |
| DmPZBnByDce | MR cases with adequate investigation (%) | Numerator: Suspected cases with date of investigation <= 2 days since date of local notification (incident date) AND have data for the following variables: 1. Nombre de Paciente (First Name, Middle Name,First Last Name,Second Last Name) 2. Identificador (Case ID) 3. Lugar de residencia (Address variables: Address coordinates ó Address ó Municipality) 4. Sexo (Sex) 5. Edad o fecha de nacimiento(AgeYearAtOnset, AgeinmonthsAtOnset) 6. Fecha de Notificación (dtReportedLocal) 7. Fecha de Investigación (dtInvestigation) 8. Fecha de Inicio de rash (dtRashOnset) 9. Fecha de toma de muestra (dtSampleCollection) 10. Presencia de fiebre (Fever) 11. Fecha de última vacuna (dtLastDoseMeaslesRubella) (si el paciente se encuentra en edad de ser vacunado y si el paciente se encuentra vacunado) Denominator: total number of suspected cases repotted |
| yS92BbQVc7w | MR Cases with blood samples received <= 5 days from collection | Number of suspected cases where <=5 days between date of sample collection and date of sample received by lab; calculation based on first lab sample (muestra=1) |
| h3WZe3KpJUb | MR Cases with blood samples received <= 5 days from collection (%) | Numerator: Cases with <=5 days between date of lab sample collection and date received by lab Denominator: Cases with blood sample collected Porcentaje de casos con muestras que se recibieron en el laboratorio en menos o igual a 5 dÃas desde el dÃa de la toma de esta. |
| HU2LkYFPlC1 | MR Cases with blood samples received >= 6 days from collection | Count of cases where blood samples were received by lab 6 days or more after the date of sample collection |
| JAaDlqMe4G9 | MR Cases with IgM results reported <= 4 days from date of sample received (%) | Numerator: number of cases where IgM result reported <=4 days from the date lab sample received Denominator: number of cases where a blood (serum) sample was collected Porcentaje de casos con muestra de sangre que reportaron un resultado IgM positivo en menos o igual a 4 dÃas (MRIndic_ResultLT4days) |
| bq0EDCIUGUk | MR - %Cases with lab result >= 15 days | |
| uiSs9iEVcAe | MR_Cases with lab result >= 15 days | |
| oa1Q1sFSDYM | MR - %Cases with lab result 5-14 days | |
| KBNksDz6uW5 | MR_Cases with lab results 5-14 days | |
| QcubTynGBj6 | MR Cases with PCR result reported <= 4 days from date of sample collection | Cases with PCR results reported <= 4 days from date of sample collection |
| b97dVuO5RAH | MR cases with PCR results reported ≤ 4 days from date of sample collection (%) | Numerator: suspected cases with PCR results reported ≤ 4 days from date of sample collection Denominator: all suspected cases with any type of lab sample collected |
| g2TjH2zEMlO | MR discarded allergic reaction (%) | Percentage of cases discarded on the basis of allergic reaction among all cases discarded (based on final classification) |
| BH8BvzjZBmm | MR discarded based on final classification (%) | Percentage of total suspected reported cases that were discarded (based on final classification) |
| LexCg5u7wLF | MR discarded dengue (%) | Percentage of cases discarded on the basis of dengue among all discarded cases (based on final classification) |
| mmCNLs22zKP | MR discarded Herpes 6 (%) | Percentage of MR cases discarded on the basis of 'Herpes 6' among all cases discarded (based on final classification) |
| HF1ILDlzeDD | MR discarded IgmNeg (%) | Percentage of MR cases discarded on the basis of 'IgM negative' among all cases discarded (based on final classification) |
| yf4o87uITey | MR discarded Other diagnosis (%) | Percentage of MR cases discarded on the basis of 'other diagnosis' among all cases discarded (based on final classification) |
| Nal9lKd6jT4 | MR discarded parvovirus (%) | Percentage of cases discarded on the basis of parvovirus among all discarded cases (based on final classification) |
| uAgeR6bXVmo | MR discarded vaccine-related reaction (%) | Percentage of cases discarded on the basis of vaccine-related reaction among all cases discarded (based on final classification) |
| iGhPbP1vCsa | MR - % Household visit within 48 hrs | Household visit within 48 hrs (MR Total cases Investigation <= 48 hrs) |
| uuTY6xFbaKK | MR_Household visit within 48 hrs | Household visit within 48 hrs (MR Total cases Investigation <= 48 hrs) |
Number of expected suspected measles cases
- Based on total population
- Maybe need another dataset (weekly) to divide the data across weeks & then configure a cumulative indicator
- [How many dashboards are included? Provide name and any specific info if required
- Screenshot initial part of dashboard and provide description of content for each dashboard + supplementary screenshots for any item that might require further explanation]
Standard reports can be used to (Victor Bryan)
- To pull reports in the same format as the bulletin
- To count cases correctly in EpiWeek and EpiYear
- Expected & reported cases