Changes

Additionally, information managers can customise the subcategories so that unused subcategories can be removed and other subcategories added. The same is true for all top-level items within IMSMA^NG, which lets information managers specify their exact information model, including the relationships among item categories, and adjust the model as their needs change over time. To accurately map the information model for a programme, it’s helpful to evaluate the available item subcategories and determine if changes to the information model in IMSMA^NG are required. While these values can be customized after system setup, understanding the types of information for each item is critical to implementing an effective workflow in IMSMA^NG. Table 5 shows examples of the possible subcategories of IMSMA^NG items.

* data elements to be collected and managed in IMSMA^NG

* data elements to be collected and managed in IMSMA^NG

The rationale for each relationship or link should also be documented so the meaning is understood. For example, a hazard reduction may be conducted on a hazard and an accident may be a result of a hazard or produce a victim. These relationships are used when entering data to ensure that the links between items are available for searching and reporting, like when searching for all hazards that have clearances linked to them.