Changes

After the desired [[Principles for Managing the Data Inventory Manager|data elements]] and [[Principles for Standardizing Data Entry Forms|Data Entry Form templates]] are customised and published, the next step is to define and document the information workflow for each type of Data Entry Form. This is a critical step for ensuring the quality of the data stored in {{IMSMANG}}. It involves combining the workflow rules identified in Chapter 1 with the Data Entry Form templates defined in Chapter 2 to create a set of workflows that can be documented as instructions or SOPs for entering and reconciling data in IMSMA^NG{{IMSMANG}}. Each workflow and SOP should include rules for:

Creating a programme-specific user guide is a critical step in communicating information management concepts and decisions to IMSMA^NG {{IMSMANG}} users, particularly because IMSMA^NG {{IMSMANG}} is so customisable. With a programme-specific user guide information managers can:

*provide an easy reference for data entry personnel and users of IMSMA^NG {{IMSMANG}} information

The guide should document the programme-specific customisations of IMSMA^NG{{IMSMANG}}. It should provide straightforward, task-specific guidance and avoid complicated discussions of possible options and conditions. Ideally, the guide is an intermediate document that bridges the gap between the goals, objectives and terms of reference of information management and the specific “how-to” instructions in the IMSMA^NG {{IMSMANG}} User Guide.

The Overview section should cover basic information about the guide, its purpose and intent and about information management responsibilities. It should describe the overall workings of IMSMA^NG including the configuration of the IMSMA^NG {{IMSMANG}} system within the programme as well as the number of users and basic roles and responsibilities.

In this section, information managers should define each item and process that will be tracked in IMSMA^NG{{IMSMANG}}. Following the recommendations in XXX, this This information should include:

*description of each item category and subcategory that will be used (see Items)*definition of what each item category and subcategory will be used for (see Items)*list of key data elements including custom-defined fields (see Items)*description of the relationships among items (see Assigning and Linking)*list of the status values for each item (see Status Changes)*direction for how locations will be used (see Location)*description for how tasking will be used (see Tasking Tool)