In this series of posts we document how we began the process of modelling our data using mindmaps. The aim is to document our processes in an open and reproducible manner.
In Part 1 we examined the initial stages of mindmapping. Here in Part 2, we look at the next steps, leading up to archetyping in openEHR.
Analysing the data points and identifying overlaps
The 2 images below display the different annotations we can use during the analysis phase. Our convention is to use labels, notes and comments for different functions.
These are added to any datapoint by pressing F3, via the drop down menus at the top of the page (Modify > Label), or by right clicking on a data point (Insert > Label). Only one label can be added per node, but this may contain multiple different tags – these are listed in a box beneath the name of the data point.
For example, in the image above the data point CR0620 has been labelled with the tags “COSDcore” and “Genomics”. This indicates that the data point is present in both the COSD Core dataset and the Genomics dataset. Using the tags therefore allows us to highlight overlaps in datasets.
To keep things simple, please use single words without spaces for the tags (though you can use concatenated words – eg the terms “COSD” & “core” together become “COSDcore”). The tags are separated by commas, as seen in the image above.
- These tags can then be used to search through or filter down the data points, which is why they are so useful.
- The tags are also used for assigning to archetypes – see later.
- XMind automatically reorders the tags into alphabetical order.
These are added to any datapoint by pressing F4, via the drop down menus at the top of the page (Modify > Notes), or by right clicking on a data point (> Notes). A small icon appears to the right of the data point name, when there is a comment attached. Click on the icon to reveal the notes, as on the image below.
The “notes” function is used for longer text notes about the data point. We recommend that you put any codes from other data points in this section (eg in the above image CR0620 in COSD is equivalent to 14944.1 in Genomics).
You may also choose to document information about the field type including value sets (eg Male / Female / Other) in the notes section.
These are added to any datapoint by clicking on the icon in the top toolbar , via the drop down menus at the top of the page (Modify > Comments), or by right clicking on a data point (> Comments). A small icon appears to the right of the data point name, when there is a comment attached. Click on the icon to reveal the comments, as on the image below.
Multiple comments can be added by different people. This section is therefore used for discussion during collaboration.
The comments section should only be used for discussion between different people working on the project. If any aspect of the data point itself needs to be changed, it should be documented using the name field, the labels, comments or markers.
Identification of commonality with existing archetypes
We aim to Identify which data points can be collected using archetypes that are already available, and which cannot.
- Some data points will be completely covered by archetypes that have already been published (full match).
- Some data points will require modification of available archetypes (partial match).
- Some data points will require the development of new archetypes (no match).
To document this process we have created a series of markers which can be used in XMind. The markers can be imported by opening the file “openEHR-infogather.xmp” – a zip file containing the file can be found here. The markers should be used in the following way:
The easiest way to use the markers is to open the Markers window – via the drop down menus at the top of the page (Window > Markers). The imported markers are usually at the bottom of the window, under the heading “openEHR tasks”.
The markers can be inserted by clicking on the node and then clicking on the required marker. The results will look similar to the image below.
The name of a relevant archetype can also be added as a label – see the labels under CR0620 on the following image.
And there you are! An outline of how XMind can be used for modelling in openEHR. A summary of the processes outlined in Parts 1 & 2 can be found in Part 3.