Join the DHIS2 team and HISP Rwanda for the next webinar in our DHIS2 for immunization series! This webinar will provide an overview of the new Immunization Registry and Vital Events Notification packages and experts from the Rwandan Ministry of Health will share their real-world implementation experiences. This webinar took place on Wednesday, 8 September, from 14:00-15:30 Oslo time (GMT+2).
You can watch a recording of this webinar on the DHIS2 YouTube channel. The slides from this presentation are also available for download.
Feel free to reply to this thread to ask questions or add comments for the presenters.
Learn more about the DHIS2 immunization toolkit: visit website
Browse DHIS2 downloadable metadata packages: visit website
Starting in three minutes! @community make sure you write your questions here for the presenters to answer!
Hi, My name is Kose from Juba South Sudan. Am a Software Developer. Looking forward to the insights from the program.
Hi all – I’m so sorry if this is a dumb question – but if a child is registered to the CRVS and a unique ID is assigned by the national authority – is this ID# persisted across all programmes (including the immunization programme) as a “golden thread” for this child?
Thanks so much,
Hello, is this tracker to be used at point of care (in front of the patient during consultation), or to be encoded at the end of the day? Thanks.
Hi Vini! This program is optimized to support a point of care workflow with built-in decision support (such as warnings, etc), but it also can be used for “end of day” data entry. The DHIS2 metadata package is designed to be flexible and countries may adopt into the workflow that is best suited to their context. It could also be a hybrid where some facilities are able to use the EIR at point of care, while others may not. The same package can be used.
Will the slides and the recording be made available?
Hi @Amaiga, enjoying the live stream on the CoP?
Welcome to the Community of Practice @kose, @Ritz, @vinifardhdiani, and @Alfakeir!
Hi Derek, great question. Indeed if a child is registered into the CRVS and already has a Unique ID from the national authority, this can be added to the child’s record (the “tracked entity attribute” in DHIS2 terms) and this will persist across programmes. In the case that the child is registered first in the EIR and later receives a national ID, their record can be update to include this information. Since many countries maintain multiple levels and types of identifiers (e.g. health facility identifiers, programme identifiers specific to EPI, or national identifiers) these can all be attached to the child’s record as appropriate, and persist across programmes depending on the configuration. In this way, DHIS2 Tracked Entity Attributes can be used to accommodate multiple identifiers.
Hi again – and (again) sorry if this is obvious to everyone but me – but will the blocker work across all the DHIS2 programmes (e.g. all persons registered across all programmes), or are we only looking for blockers (duplicates) on a single programme?
Thanks and warmest regards,
PS: sorry for all the apologies… I’m Canadian.
Hi @AnabelAA – the slides and recording of this webinar will be shared here on the Community of Practice, and on our YouTube channel: DHIS2 - YouTube
Hi Derek, no worries! If by the “blocker” you mean, “must it be unique across all programmes”, the answer is yes, the attribute can be configured to be unique to the system, and thus cannot be duplicated regardless of which programme. The system will block you from duplicating that ID if it is configured to be unique in the system. Did I understand the question right?
From your friendly neighbor to the south.
Hello Everyone, hoping to learning more and explore DHIS2 and would love to connect with everyone here. Have a great day.
Thanks so much, Rebecca – and howdy neighbour!
I saw that the blocker was looking for duplicates based on name. Is that test against same-name across all programmes??
Welcome to the community @Mehkan_Ali!
Hi… sorry for so many questions… but I didn’t notice that the vaccine batch# was logged at the time of the transaction. Did I miss it (or is it entered somewhere else)?
Thanks so much for this really great demo.