Choosing the Right DHIS2 Data Entry Form: Default, Section, or Custom? | DHIS2 Metadata Series

[Mayamiko (Mayamiko Z Mendamenda)]

In my previous video, What are Datasets in DHIS2?, I introduced datasets as one of the fundamental concepts in DHIS2 and explained how they support the aggregate data collection process.

As a follow-up, this short video looks at the forms that users interact with when entering data into those datasets.

Watch the video here:

DHIS2 Data Entry Forms Explained: Default vs Section vs Custom #dhis2 #datasets #dataentry

In this video, I compare the three data entry form options available in DHIS2:

• Default Forms
• Section Forms
• Custom Forms

I also share why Section Forms are generally my preferred option for most implementations, particularly due to their simplicity, maintainability, and compatibility with the DHIS2 Android Capture app.

If you missed the previous video on datasets, you can find it here:

What are datasets in DHIS2 ? | DHIS2 Metadata Series

Once you have your indicators in order as shown here It would be important to start working on our form. To do that, you need to create a dataset. In this video, explain what datasets are in DHIS2 and how they support the aggregate data collection process. The video uses a simple analogy based on mathematical sets to make the concept easier for beginners to understand. I hope this may be useful for anyone new to DHIS2 or supporting onboarding and training activities. Short d…

I hope this may be useful for anyone designing datasets or configuring data collection workflows in DHIS2.

But please tell me, what data entry form option do you use in your implementation, and how did you arrive at that decision?

Do you primarily use Default Forms, Section Forms, or Custom Forms?

I’d be interested to hear about your experience, the trade-offs you considered, and what has worked well in your context.

[Gassim (AL-Gassim Sharaf Addin)]

We almost never have issues from the default ones on the CoP so I’d recommend sticking to those if ‘section & custom’ aren’t needed. However, if you want more fun, go for the latter: ‘section’ for fun without so much risk, and ‘custom’ for fun with a little risk.

I think with AI assisting with the DHIS2 apps, there’s a potential for people to create custom apps/plugins in a much preferred way than the custom forms, what do you think @Mayamiko?

Again, thanks for these topics and discussions. I’m trying to keep track of these myself.

[Mayamiko (Mayamiko Z Mendamenda)]

That is a helpful observation, especially from the CoP side on the Default forms. If they solve the problem, there is definitely value in keeping things simple.

You are also spot on about AI making Custom forms a bit more approachable for those willing to take some risks . You can get quite creative with them, but if you do not have some familiarity with HTML and CSS, it can still be difficult to get the layout exactly how you envision it. So I would still recommend using them wisely.

What I find interesting about your point is the possibility that AI could shift people away from custom forms altogether and towards lightweight custom apps or plugins. That may end up being a much cleaner and more maintainable approach for advanced use cases.

And for me, one of the strengths of Section forms right now is their compatibility with the Android Capture app. They give you more control over the layout than Default forms without losing that cross-platform support, which is a nice balance.