Convert Event based program to Tracker based program in DHIS2 2.27

Support - Assistance technique
1

I want to convert our Event based program to Tracker. Can someone tell me how to accomplish this task. And also to ensure that the data continues as well

2

@Collin.Dosunmu Firstly, there is not a direct method in DHIS2 to simply convert an Events program to a Tracker Program.
However, if your current situation requires that you make this change, note that converting a an Event program to a Tracker program is a significant change (generally: data management problem, specifically: data migration) and should be carefully planned and executed.

The main difference between Event programs and Tracker programs is that Tracker programs involve registration and can have multiple stages, while Event programs are simpler and don’t require registration.

Here are some key points to consider when converting your program:

  1. Program Structure Analysis: Analyze your current Event program structure and determine how it fits into the Tracker program model. As described in the Tracker Data Model Session Summary, a Tracker program consists of:

  • Tracked Entity Type

  • Tracked Entity Attributes

  • Enrollment

  • Program Stages (which can be repeatable or non-repeatable)

  1. Tracked Entity Type Definition: Define the Tracked Entity Type for your new Tracker program. This could be a “Person”, “Case”, or any other relevant entity as per your program requirements.

  2. Program Configuration: Create a new Tracker program following the steps outlined in the Learner’s guide to Creating a Multiple Stage Tracker Program. This includes:

  • Defining program details

  • Setting up enrollment details

  • Adding attributes to the program

  • Creating program stages (including one that mimics the current Events program)

  1. Data Mapping: Map your existing Event program data to the new Tracker program structure. Determine which data elements from your Event program will become:

  • Tracked Entity Attributes (for registration)

  • Data elements in the enrollment stage

  • Data elements in program stages
    Here are a few questions to guide you during this mapping:
    Considering the structure of a Tracker program; tracked entity attribute, enrollment stage, program stage(s), where will the current event program fit? Is the event data more or less like an entity-based data that you’ll like to fit into the enrollment stage of the new Tracker Program or this events data can be better describes as follow-ups to an entity(s)?

  1. Data Migration Strategy: Based on your data mapping, develop a strategy for migrating data: a. If your Event data represents entity-based information:

  • Import the Event data as enrollments in the new Tracker program

  • Use program stages for future follow-ups b. If your Event data represents follow-up information:

  • Create a list of entities with their attributes

  • Import this list as enrollments in the Tracker program

  • Map and import the related Event data as events in the appropriate program stages

  1. Implementation:

  • Use the DHIS2 API or available import tools to execute your data migration strategy

  • Ensure proper data validation and integrity checks during the migration process

Let me know if this helps!

1 Like