Tracker Form Design: Register-style data entry vs. repeated events in DHIS2 Capture

[bashanta (Basanta Gaire)]

Hi all.
This post could be against the standard workflow design proposed in Capture app, however, I would like to get valuable suggestions in workflow design in capture app.

Traditionally, in physical registers, health works keep records of each follow up visit in a single row for each client, for instance, if they are providing Depoprovera injection, they keep record in single row of the client with date of injection and follow up date in same row.

However, according to capture app workflow, every time health worker has to create a new event and keep record.

If we designed capture app aligning with register to allow user to edit single programme stage, designe custom view to make UI similar to the register, what possible issues we may face in future in data analysis and processing. It seems more user friendly for the service providers to adopt and conceptualize, ultimately reducing training and capacity building cost of the digitalization process.

I am in conflict, which way to go. Either follow the DHIS2 recommended workflow or go for user friendly custom register-based forms with possible low cost for implementation.

Your suggestions in this regard will be extremely valuable for me.

[Gassim (AL-Gassim Sharaf Addin)]

Hi @bashanta

Thank you for sharing this with the community! To begin with, a similar use-case has been suggested as an idea (Log in with Atlassian account) For more info about what an idea (feature request) is, see ideas !

@bashanta

However, according to capture app workflow, every time health worker has to create a new event and keep record.

It’s possible to choose an ‘auto-generate’ event so that you could have the event auto-generate for the data entry user the next time they’re going to fill in the form.

@bashanta

If we designed capture app aligning with register to allow user to edit single programme stage, designe custom view to make UI similar to the register, what possible issues we may face in future in data analysis and processing. It seems more user friendly for the service providers to adopt and conceptualize, ultimately reducing training and capacity building cost of the digitalization process.

I think that if you’re editing a single event, you’re erasing the previously entered data, so I don’t know why would that be helpful; however, since you are looking into developing a custom UI, you could potentially make it automatically create a new event but display it in the way that your users are used to.

@bashanta

I am in conflict, which way to go. Either follow the DHIS2 recommended workflow or go for user friendly custom register-based forms with possible low cost for implementation

I would suggest to make the UI appear in the desired format (while making it stick to the workflow in the background), would that be an option you could consider?

Thanks!