Step by Step Guide: Event Programs, Stages and the Capture App
Monthly totals answer how many. They cannot answer who, or how old, or how quickly somebody was treated. This guide builds an event program, gives it the questions asked about each case, and enters real cases in the Capture app.
Everything so far has been totals: one number per facility per month. Case based data is one row per case, which lets you ask questions a total can never answer, such as the age of the people testing positive.
| Aggregate | Case based, event program | |
|---|---|---|
| One record is | A month for a facility | One case, one visit, one test |
| Entered in | The Data Entry app | The Capture app |
| Built from | Data set and form | Program and program stage |
| Good for | Routine monthly reporting | Line lists, outbreak follow up, case investigation |
| Registration | None | Without registration for events, with registration to follow a person over time |
An event program without registration is the simplest case based setup: one record per case, with nobody registered and nothing to follow up.
The stage is the form. Its data elements are the questions asked about each case, and they are ordinary data elements, created exactly as in the data elements topic.
| Question | Answer from |
|---|---|
| How many cases this month | Either model |
| How many were under five | Case based only |
| How many positives got treatment the same day | Case based only |
| National trend over three years | Aggregate, which is far lighter |
| App | What it does with events |
|---|---|
| Line Listing | The raw rows, filtered and downloadable |
| Event Reports | Counts and pivot tables of events |
| Event Visualizer | Charts of the same |
| Maps | An event layer, one dot per case |
| Program indicators | Rates built from events, usable on a dashboard beside aggregate ones |