Hi all,
We are supporting the MoH of Angola to implement this package. One question: do we have the portuguese version?
Thank you,
Att,
1 Like
As far as I know HISP Mozambique has started working on a Portuguese translation of the package. It will be available soon.
1 Like
Hi! just spoke with them. Thank you
2 Likes
Hi Claudia and everyone else interested.
Eduardo Mondlane University - Faculty of Medicine with the Ministry of health in Mozambique made a whole translation to Portuguese.
If you are interested please let me know.
Regards
1 Like
Thank you soo much guys for that effort.
Kind regards,
1 Like
New and updated COVID-19 Surveillance Packages are now released!
Read the announcement here: Additional COVID-19 Data Packages are released!
And find the documentation and download links here: Covid-19 - DHIS2
3 Likes
Thanks Max.
1 Like
Dear All, is the DHIS2 COVID-19 surveillance tracker able to integrate with SORMAS?
1 Like
Dear Dr. Okoye,
SORMAS can report to DHIS2 Tracker, but I don’t believe there is integration with the Tracker module yet. This is one of the reasons we have been documenting what data models are being used by Tracker, SORMAS and others so that we can make them interoperable later. You can see this documentation here:
Data Models for Covid-19 Tools : email cleitner@path.org if you need edit access - Google Sheets
Cheers,
-carl
3 Likes
Dear All,
I installed the COVID packages yesterday on our demo server and was able to enter some data.
As at this morning I and other team member can no longer enter data and this is the error we see on the browser console:
Trying to change this to tabular data entry still throws this error.
Trying to get the logs for this.
Please your help is seriously required.
Thank you.
1 Like
Dear @ifeanyiokoye,
This is most likely this bug that is fixed and issue will be solved in upcoming patch releases: [DHIS2-7865] - Jira
See @sele’s post here: Tracker Program Stage Loads Forever - #7 by sele for a workaround until then.
Best regards,
Karoline
Hi Carl, this is great news! The case-based surveillance package has been updated with metadata coded according to the WHO case reporting data dictionary. We also have the capability to add additional codes to the metadata to enable easier integration i.e. with SORMAS or other as long as we know what the standard is. We will update our metadata coding in the spreadsheet shared.
1 Like
Thanks all for this, really great work.
Wanted to comment on the “COVID-19 case-based surveillance” program.
I would recommend that for cases where, in the “health outcome” stage, “death” is selected, there should be a next stage which is the same as the SMoL program which you previously developed (see https://who.dhis2.org/documentation/#cause-of-death) (or the COVID DHIS2 program should be linked to the SMoL Program if that is already in use to complete the medical certificate of cause of death for that individual). It will be very important to have correct medical certification of cause of death for all individuals who die from COVID-19 (certainly important to have correct medical certification of cause of death for all deaths) – it is not enough to know that the outcome was death, there needs to be a full medical certificate of cause of death. I would say, the link to the SMoL program should only be optional if the country is using another program / software to capture the medical certificate of cause of death (should be WHO 2016 form of medical certification of cause of death – see page 203 (Annexes section 7.1) of ICD volume 2 at https://icd.who.int/browse10/Content/statichtml/ICD10Volume2_en_2016.pdf?ua=1&ua=1).
Would be great if countries exploring the use of the COVID-19 DHIS2 Programs which are already using the SMoL Program could explore the link.
Thanks
4 Likes
Hi Martin,
This is a great use case. As you have mentioned, a Cause of Death data package already exists and could be used in combination with COVID-19 surveillance. In the current design, the Cause of Death program is a separate program. It will be interesting to see if how countries may have implemented this work flow. For example, adding a simple program rule at the Outcome stage if the outcome is “dead” can prompt the user to complete the Certificate of Death. If the country already uses the Cause of Death tracker, the entity can be enrolled in the Cause of Death tracker program to complete the death certificate.
@bratschim I have also heard that @Hannan has been working with MOH in Bangladesh to introduce to the WHO’s new emergency ICD-10 code for COVID-19 and may have experience to share.
Rebecca
1 Like
@Rebecca thanks for this. yes Bangladesh would also be a great setting to test the combination of these DHIS2 programs. indeed WHO is working to provide guidance on the expansion of the ICD-10 dictionary in the SMoL cause of death program to include the ICD-10 codes for COVID-19
1 Like
Dear Colleagues, regarding dhis2 COVID19 module, since we dont know the volume of suspected cases, do we advise countries to use their production system to use case based module which also includes patient followup? or best practice is to have a separate instance dedicated for the COVID19 Cases.
Do we have recommendations on the minimum server capacity before integration to the rest of existing HMIS reports?
1 Like
Hi Andrew,
UiO’s recommendation is to set up a separate instance for COVID-19 tracker programs. As you say, the volume of cases can be unknown and this would minimize risk to the performance and stability of the production HMIS. @bobj has documented set-up guidance that is intended to complement the existing general installation guides on docs.dhis2.org. Hope this helps!
Rebecca
1 Like
Hi Andrew
Its really hard to talk about best practice in these early days. What I would say is that many countries have experienced performance and stability issues with some of their large tracker deployments, so adding these modules into the mix would potentially make supporting specific issues difficult. So definitely from a support perspective, running on a separate instance, preferably with a separate database is the wisest thing to do.
If you have a an existing tracker implementation which is lightly loaded and performing well you could get away with merging this - with the additional risk that the new addition might introduce new instability into the original system.
The key to all of this is of course monitoring. There are far too few country systems which have proper monitoring in place where you can assess the performance of your database in particular, and rapidly identify any problems as they emerge. Because many existing systems are running blind like this it would definitely be safer to run the new modules separate to this.
Regards
Bob
3 Likes