Meeting on DHIS2, PMORALG and HFR lists
Darcy, Niamh
Dear everyone,
I took the Access DB that Scott shared with us, and did some comparisons with the latest DHIS2 list we had received – see the attached Excel sheet. We need a way forward to resolve these differences, and am hoping we can get this on to the agenda for the next HFR meeting.
As you can see, there are some council names that need to be updated in DHIS2 I believe to match PMORALG/HFR, there are some additional councils that need to be added into the HFR, and facilities that belong to these new councils moved from the old council. Some of these came up in training, such as the separating out Lushoto DC into both Lushoto DC and Bumbuli DC, adding Msalala DC and Ushetu DC to Shinyanga (split from Kahama DC). Bariadi DC splitting into Bariadi TC and DC.
Also, there are some councils mentioned in PMORALG list that are not in HFR or DHIS2 and we should sync up on whether we need to create these or not?
This is really important for us to work on as we are approving facilities at this time and hope to make the system content live at some point in the near future.
It would be great to get UCC and UDSM folks together again into another meeting here, which Wengaa could help arrange if that is ok, so that we can move forward here on making these needed updates to the HFR.
Thanks, Niamh
emse...@yahoo.com
Thanx Niamh we are going to work for this |
From: Darcy, Niamh <nda...@rti.org>;
To: hfr...@googlegroups.com <hfr...@googlegroups.com>;
Subject: [ HFR TZ ] Meeting on DHIS2, PMORALG and HFR lists
Sent: Sun, Jun 22, 2014 10:13:15 PM
Darcy, Niamh
Thanks Esther,
Much appreciated. Please let me know what Wengaa and I can do to assist here also and if there are questions on the spreadsheet I had sent. Scott can also assist here as he is the one who did the original comparison between the DHIS2 data Senyni/Ismail provided and the current Curation Tool dataset.
Thanks, Niamh
--
You received this message because you are subscribed to the Google Groups "hfr-tz" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
hfr-tz+un...@googlegroups.com.
To post to this group, send email to hfr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Scott Teesdale
- Determine who is the empowered source (programmatically and technically) of the administrative hierarchy data and help them to use the appropriate tools to manage that. (i.e., This groups uses a particular tool like a terminology service or otherwise). An analogy could be drawn with the facility registry process here... specifically that the MOH owns the implementation and is implemented by the working group, UCC is the tech partner and they are deploying a specific set of software tools to facilitate the requirements. If we were to remove the FR component and actors and replace them for managing code sets in Tanzania, what would replace those roles for how admin hierarchies and other sets of codes are managed? I can suggest things based on what I have heard but ultimately you will know much better than I will.
- Then, also start to reconcile the administrative hierarchy differences between tools... For example this council is spelled wrong here or missing from this other tool over here. From what I saw in my quick comparison on the FR and DHIS, things are close but there are a few details to resolve.
- Establish workflows to keep code sets standardized/updated. Another common one related to this will be types of services.
- Then, carryout standardizing these code sets across systems and pointing to the source that maintains them moving forward.