Using Event Capture

- 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). + Capturing events + To capture an event, the first step is to select an organisation unit from the left-side + organisation unit tree. After selecting an org unit, the list of programs will display the + programs which have been associated with the selected organisation unit and which have been + given access to the current user through user roles. Events are displayed in a tabular fashion + as shown in the figure below. As seen in the screenshot, each row corresponds to an event. The + columns display information about the events, more specifically they display data for data + elements which are part of the program. Example event list @@ -98,36 +32,45 @@ 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. + Capturing data: 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. + Showing/hiding colums: this is to allow users decide which columns to show/hide in + the table of events. 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. + and Remove. The edit function takes you to a new page + where information for the selected event can be updated. The edit in grid function + allows you 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 to speficy which columns should be displayed in the + list. + + + Sorting: this can be done by clicking the text of each column header. + + + Filtering: this is done 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 + system starts applying the filter the moment a user starts to type. During filtering it + is possible to define start and end dates for date type data elements and lower and + upper limits for number types. + + + Paging: The list of events can be paged by using the paging section at the bootom of + the list. Paging allows you to quickly move between pages of events and to change the + page size, i.e. the number of events per page. + The event capture module works offline, in the sense that if Internet connectivity drops + during your working session, you can continue to capture events which will be stored locally + in your web browser (client). When connectivity has returned the system will ask you to upload + your locally stored data, which sends the data to the Web server where it is stored. Note that + if you close your Web browser while being disconnected from the Internet, you cannot return to + your working session; however your data will still be saved locally and can be uploaded to the + Web server the next time your are online and log into the system.