Changes

==Data Types==__NOEDITSECTION__===Core Data===__NOEDITSECTION__In the IMSMA^NG {{IMSMANG}} information model, items are the containers for core data, such as mine action core data. An item is an area, activity or event that a mine action programme records information about and stores in IMSMA^NG{{IMSMANG}}. There are six categories of items, which are described in the table below. Each category can be characterized characterised by a type that reflects whether the item is designed to track process or activity information or the object or product of an activity. 

| HazardLand| Information about an area affected by a hazard

| Hazard reduction activityActivity| Information about an activity , such as efforts to survey, clear, or reduce the threat of a hazard

| Information about an accidental event involving a hazard

| Information about a person injured or affected by a hazardan accident

| Mine Risk Assistance| Information about assistance for a person injured or affected by an accident| Process/Activity|-| Education (MRE) activity| Information about an activity designed to inform or educate people about hazards(e.g. Risk Education or Victim rights)| ObjectProcess/ProductActivity

| Information about an quality-improvement activity , such as an effort to control and monitor the clearance and/or reduction of hazards land or hazard reduction activities| ObjectProcess/ProductActivity

Items are entered into IMSMA<supcenter>NG</sup> by means of a field report. Typically, each category of items has its own field report template for recording information specific to that category. When entered into IMSMA^NG, all field report items must be assigned to a location, which is tied to the country’s gazetteer, or political or administrative structure. The items can then be traced back to the country structure so that users can easily report data such as the number and size of hazards within a particular province. Part of defining and documenting an information model includes defining the useful information attributes for each IMSMA^NG item. IMSMA^NG comes with more than 1,000 data elements already defined as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data elements are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data elements that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data elements may be collected for each IMSMA^NG item, some elements may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.  

|+ Item Subcategories

! Subcategory Category Examples

| HazardLand

* Battle area* Dangerous area* MinefieldSHA

* UXO spotEOD Spot Task* Ammunition Storage

| Hazard reduction activityActivity

Each [[Image:Understanding IMSMA Information Model - Example of the six categories of items can be divided into subcategories or types so users can collect information for each subcategoryDocumented Land. For example, users can specify different types png|center|300px]]<div align="center">''Example of hazards such as dangerous areas, confirmed hazardous areas (CHAs), minefields and battle areas and manage each kind of hazard differently. Using subcategories, information managers can:documentation''</div>

* create separate workflows ===Auxiliary Data===__NOEDITSECTION__In addition to defining the required information for {{IMSMANG}} items, it is important to define the relevant information to be collected about Auxiliary data. This includes defining and documenting the [[Standardising_Auxiliary_Data#Country_Structure|Country Structure]], [[Standardising_Auxiliary_Data#Ordnance Classification | Ordnance classification]], [[Standardising_Auxiliary_Data#Organisations |Organisation]] and [[Standardising_Auxiliary_Data#Places|Place]], such as military bases, hospitals and cultural sites; any additional CDFs that should be created; and any subcategories for each type of hazard* create and manage separate the Auxiliary data entry forms* differentiate between item categories on the maptypes.

Additionally, information managers can customise the subcategories so that unused subcategories can be removed and other subcategories added{{New_6.0 | In version 6. The same is true 0 two classifications used for all top-level items within IMSMA^NG, which lets information managers specify their exact information model, including the relationships among item categories, Victim; Cause and adjust the model as their needs change over time. To accurately map the information model for a programmeNeeds assessment, 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 Assistance classification used for each item is critical to implementing an effective workflow in IMSMA^NGAssistance have been added. Table 5 shows examples of the possible subcategories of IMSMA^NG itemsAll three are hierarchy tree-structures using levels.}}

{{note|<b>Document the following decisions about itemsAuxiliary data:</b>

* data elements to be collected and managed in IMSMA^NG{{IMSMANG}}* data elements fields that are not predefined already configured in IMSMA^NG {{IMSMANG}} and should can be created as CDFs* particularly important, or key, data elements for the programme* relevant subcategories for each itemdata type* status values }}  [[Image:Understanding IMSMA Information Model - Example of Documented Auxiliary Data ver2.png|center|300px]]<div align="center">''Example of Documented Auxiliary Data''</div> ==Data Entry Forms and Summary items==__NOEDITSECTION__A '''Data Entry Form''' is a template used for data entry of information e.g. about a victim. The Data Entry Form(s) for each itema specific object (e.g. the Victim ''Jane Doe'') are summarised and displayed in a '''Summary'''.

Below With this approach, users can collect and store multiple Data Entry Forms about the same item over time so that the entire history of the item is an example preserved in the system. The approach also provides a complete [[Audit log | audit trail]] of a fully-documented hazard.all changes made to any information so that information managers can answer the question, "What did we know and when did we know it?"

[[Image:Understanding IMSMA Information Model Understanding_IMSMA_Information_Model_- Example of Documented Hazard_Updating_CVs ver2.png|center|500px|''Example of Documented Hazard''400px]]

''Example of Documented HazardUpdating Summary items''

===Auxiliary Data===In addition to defining the required Entry Form #1 collects some initial information for IMSMA^NG items, it is important to define about a Land. It sets the relevant information priority to be collected about auxiliary data. This includes defining "Medium" and documenting specifies that the [[Country Structure]], [[Explosive Ordnance]], [[Organisation]] land contains AP mines and [[Place]]is 25, such as military bases, hospitals and cultural sites; any additional CDFs that should be created; and any subcategories for each of the auxiliary data types000 sqm.

<b>Document Data Entry Form #3 updates the following decisions about auxiliary data:</b>land area's size and status after clearance operations are complete. The figure above shows how the land area's Summary is updated after all three reports are entered into the system.

* data elements to be collected and managed in IMSMA^NG* data elements {{Warning| A Data Entry Form that is changing existing information must have a Date of information that is later than the Data Entry Form that it is updating the calculation of the Summary item(s) are based on Date of Information. When the date is earlier or the '''same''', the Summary item will '''not already configured ''' be updated.}} ===Location ===__NOEDITSECTION__A country's official administrative structure, also known as Gazetteer, should be the base for the Country Structure used in IMSMA^NG {{IMSMANG}}. Sometimes the official administrative structure has not been updated for a long time or it is not detailed enough using it for a geographical placeholder, worksite, for the Mine Action programme and can that is why the item Location has been introduced in {{IMSMANG}}. Two fundamental decisions to make when customising {{IMSMANG}} is to decide what Country Structure level Locations will be created as CDFs* relevant subcategories for each data typeconsistently linked to and what concept Locations will represent. Typical concepts that a Location is used to represent include:

Below Using Locations, users can group data that belongs together or is an example of associated with each other and in that way get a fully-documented placebetter overview, facilitate searching and creating reports.The Locations is the link between the Country Structure, whether at the province, district or town level and the Mine Action data. As shown in the figure below, data in {{IMSMANG}} are governed by two simple rules:

[[Image:Understanding IMSMA Information Model - Example of Documented Auxiliary Using Locations to Link Mine Action Datato the Country Structure.png|center|500px|''Understanding IMSMA Information Model - Example of Documented Auxiliary Data'']]

''Understanding IMSMA Information Model - Example of Documented Auxiliary Using Locations to Link Mine Action Datato the Country Structure''

==Field Reports and Current Views==A {{note|<b>field reportDocument the following decisions about Locations:</b> is a data entry form used * what concept Locations will represent* what Country Structure level Locations will be linked to record and store information about an item.}}

A ===Assigning and Linking===__NOEDITSECTION__<b>current viewAssigning</b> is refers to the assignment of an item to a summary Location for the purposes of all the grouping information collected about an item on field reports. All items must be assigned a Location.

<b>ReconciliationLinking</b> is refers to the association between items for the process purposes of assigning the information in a field report analysis. Linking is optional, for example, when linking Activities to Accidents but linking is very important to an existing item or creating a new item/current viewdo so effective reporting will be possible.

All mine action The example below shows how users can build a workflow of relationships among items to model the information management process for their Mine Action Programmes. The figure shows how the Summary changes with each activity that is entered into IMSMA^NG via linked to the original Land. # The Land starts its life-cycle as ''SHA'' with a field report, a data entry form used to collect information about an itemstatus of Open in this example. # When a field the clearance starts and the first Progress report is completedlinked to the Land, it is either reconciled the status should be changed to an existing item (that is''Worked On''. # Finally, it is determined to after linking the Completion Report the land's status should be information about an item that already exists in IMSMA^NG) or it is reconciled as new (that is, it is determined updated to be information about an item that does not already exist in IMSMA^NG)''Closed''.

With this approach, users can collect and store multiple field reports about the same item The result is one Land whose information is updated over time so that by the entire history of the item is preserved in three Activities linked to the systemland. The approach also provides a complete audit trail of all changes made This way to any mine action information so that track information managers can answer be used to represent the questioninformation management process and status rules accurately for a Land Release, Risk management or other process model. [[Image:Understanding IMSMA Information Model - Example of How Current View Statuses Change.png|center|400px]]<div align="What did we know and when did we know it?center">''Example of How Summary Statuses Change''</div>

IMSMA^NG also provides a constantly updated current view of the item which represents the sum of information about the item at any given time. As subsequent The {{IMSMANG}} information model is collected about a specific attribute of an item, IMSMA^NG updates flexible enough for each Mine Action Programme to customise the item’s current view on an attribute-by-attribute basissystem to support its needs. For example, Field Report #1 collects some initial implementations that do not cover Education activities do not need to complete information about a hazard. It sets the priority to "Medium" Education activities, and specifies that they still retain full utility of the hazard contains AP mines and is 25system. Similarly,000 sqm. Field Report #2 updates information about the hazard after a subsequent assessment. The report sets the priority to "High" implementations that only cover Victim tracking and specifies the presence of AP Education activities only can disregard Land and AT mines, but it does not change the size or the status Activities without any loss of the hazard. Field Report #3 updates the hazard’s size and status after clearance operations are complete. The figure below shows how the hazard’s current view is updated after all three reports are entered into the systemutility.

[[Image:Understanding_IMSMA_Information_Model_Understanding IMSMA Information Model -_Updating_CVsExample Relationships Among Items.png|center|500px|''Example of Updating Current Views''550px]]

''Example of Updating Current ViewsNote: Connections to Country Structure and Location have been omitted from the example''

Current view calculations are based on the date of the field reportFor data quality purposes, so it is possible to enter important that the data into is adequately checked. With multiple permission levels for the system out of chronological order (that isApproval, different users can be assigned different permissions, allowing Mine Action Programmes to collect past information about an item) without disrupting the current view. For example, if implement a fourth field report were collected and dated data-entry workflow that distinguishes between Field Report #1 data '''entry''' and Field Report #2, it would have no effect on the current view as all information in the example was updated with Field Report #2 or laterdata '''verification''' roles.===Mapping the Workflow======Business Rules Updating Structure======Progress Reporting Structure===