Using Event Capture

+ Using Event Capture +

+ Overview + The event capture module allows users to register events that occurred at a particular + time and place. In DHIS2,time and place correspond, respectively, to period and organisation + units. However, since events are treated as random occurrences there is no such thing as + period for them, rather a date the event has occurred. + +

+ Program definition + In order to capture events, it is mandatory for users to first define the nature of the + event using the Program/Attribute module. Below is a guiding step for this: + + Go to Programs/Attributes module + + + Select Program + + + Click Add new and fill in the necessary details. Under Program + details make sure Type is "Single event without + registration". Below is a snapshot to depict this. + + + + Example single event program creation + + + + + + Once a single event program is created, the system automatically creates a single + program stage. The stage can be accessed from the context menu of the program created. + Clicking "Edit" from the context menu of the program stage + takes to the detail view of the program stage, similar to the one shown below. + + Example single event program stage creation + + + + + + As can be seen from the program stage screen shot above, users have the chance to + define what to collect during event capture. This is possible by selecting a list of data + elements from "Available data elements" to "Selected data elements". Under selected data elements, please pay + attention for the following check boxes: + + Compulsory: whether it is mandatory or not to + collect the element during event capture + + + Allow provided elsewhere: this is to define if + the data element can be collected by the selected organisation unit while it has + occurred elsewhere. For example, from the figure, it is possible for "mnch Blood + pressure" to be measured in another facility but reported in the selected facility where + these is no blood pressure measuring device. + + + Display in reports: this decides if the data + element can appear in reports or not. If there are many data elements to be collected + during event capture, it makes more sense to prioritize which ones to show in report by + default. + + + Date in future: this is only for those date type + data elements and to decide if it is possible to allow collect future dates or + not. + + + In addition to defining program and program stage, another important step to complete + before event capturing is associating programs with organization units. This can be done + through "Assign program to organisation units" button from + the context menu of the selected program. +

+ Operations + Event capturing is possible by selecting an organisation unit and a program. The moment a + program is selected the system displays existing events. Events are displayed in a tabular + fashion as shown in the figure below. From the figure, each row corresponds to an event and + the columns are event details (data elements). + + Example event list + + + + + + + All event related operations are accessible from the screen shown above. The operations + currently available are: + + Capturing - this available by clicking the "Register New Event" button. + + + Column show/hide - this is to allow users decide which columns to show/hide. This + feature is especially important when we have a long list of data elements assigned to a + program stage. + + + Editing - the rows in the table are clickable. Clicking them shows three menus - + Edit, Edit in grid + and Remove. The difference between edit and edit in + grid is that, Edit takes to a new page with an opportunity to edit all the data elements + of the selected event. However, edit in grid allows to edit the selected event within + the table but only those columns (data elements) visible in the grid. If more columns + are required, it is possible to add using the "Show/Hide columns" button. + + + Sorting - this is possible by clicking the text of each column header. + + + Filtering - this is possible by clicking the small search icon shown to the right of + each column header. Clicking them provides an input field to type a filtering criteria. + The moment a user types a filter, the system starts applying. During filtering it is + possible to define start and end dates for date type data elements and lower and upper + limits for number types. For the rest, it is just a text. + + + Paging - using the links at the bottom of the table, it is possible to have some + paging interactions. + + +