You may have mentioned this already. Are SMS’s sent directly from the Tracker to the registered number for a Missed Appointment…Does the Tracker integrate to any Community Based Systems used by Case Workers for example to notify a missed appointment. Also, is there a Defaulter report for missed appointments?
Another question about integration to the CVRS system. Is this Bi-directional? Can the National ID be pulled in from the CVRS to the Tracker?
The batch number has been included sometimes in the package and removed sometimes. It is not in this current version, but can be added. The question to consider for any given country is if the person adding the data has the batch number / if the batch number is already recorded elsewhere, such as the supply chain reports / and if it is worth adding bar code scanning or some other approach for including it.
Is the NIDA Database the CRVS system in Rwanda that the Tracker interoperates with?
Hi @AnabelAA ! Welcome to the CoP.
By default, SMS reminder to the patient’s primary contact are scheduled to send 2 days before the scheduled appointment visit. Unfortunately, DHIS2 does not currently have “missed appointment” notification feature, so you would need a custom script to check for appointments that have been missed yesterday, and then send a message through DHIS2 or the SMS gateway.
There is a "missed appointment’ working list for care providers, which I think is what you mean by “Defaulter Report”.
As for Community based systems this is certainly a valuable adaptation, but greatly depends on local context: what type of system is used, how it could push data into / out of DHIS2, and how it would be used by case workers.
Yes, that test is against all programs (all TEIs in the system, to identify potential duplicate TEIs that were enrolled in another program, but not yet in EIR for example).
Good question. Bi-directional integration technically is possible but it likely would present a complex workflow. That would really depend on context. For example, if the CRVS needs to ‘search’ the Tracked Entities (children) in DHIS2 to assign the national UID, how would it do so (e.g. based on name, surname, date of birth and ensure no duplicates). Or perhaps it could be part of the ‘notification’ of the birth to CRVS, then the CRVS would send back based on that record the ID, which would be a quite interesting use case but we have not yet encountered it! We’d love to hear more if you have a use case/work flow in mind for your context.
We have heard quite a few use cases of countries using their civil registration systems to “pre-populate” DHIS2 with TEIs (individuals) for the COVID-19 vaccine rollouts. This allows the user to simply search their name or ID in DHIS2 (once pre-loaded) and then complete the data for their vaccination record, without losing time to enroll the individual into the program. We have a lot to learn from these innovative work flows, but see a lot of value in linkages between these systems.
There are many ways to configure the search results: which org units (clinics) a user has access to search across, which attributes are shared across programs, which ones must be unique, etc. The demo search was for first name, which is a “non-unique attribute”, without a last name, and thus showed an alert for the possible duplicate. When both first name and last name were entered, no duplicates were found.
More details on search attributes are found here: Home - DHIS2 Documentation
Does the Tracker implementation in Rwanda integrate with the RHIE (Shared Client record) for example?
Can you also talk about how Adverse Event monitoring is done?
If you would like to learn about some additional DHIS2 tools that you can deploy to support your immunization programs, join us for our webinar on the DHIS2 Scorecard, Bottleneck Analysis and Action Tracker Apps. This webinar will take place on Wednesday, 13 October at 14:00 Oslo time.
You can register for this event through our online form.
Thanks for a great presentation!
Thank you. lovely presentations
This was a great session. Thank you for the opportunity