CRM Taskforce RM Starting Point - Voting Results

Jump to: navigation, search

Purpose of Vote

To select a starting point for the core CIMI reference model. It is anticipated that the selected reference model will then be modified, as required, to better meet the CIMI reference model requirements.

Period of Vote

Friday 23rd March – Wednesday 28th March 2012

Voting Process

Each member of the taskforce was asked to rank, in order of preference (from 5 to 1), the following reference models:

  • ISO 13606-1 (or variation)
  • openEHR Reference Model
  • openEHR/ISO13606-1 Harmonisation
  • DCM2010 (ISO13972 conformant)
  • EN13606 Association Proposal

Based on the votes received, the option with the fewest points was eliminated. Round 2 votes were then determined by reallocating the points (from 5 to 2) for the remaining 4 options, in the original order of preference. This process of elimination and reallocation of points was repeated, until 2 options remained. The option with the highest number of points was then selected.

Voting Outcome

The openEHR reference model has been selected as the starting point for the CIMI reference model (by 6 of the 9 members of the taskforce).

Summary of Reasons and Discussion

The reasons given by the taskforce members for selecting the openEHR reference model included:

  • The range of existing archetypes, tooling, infrastructure, methodology and documentation;
  • Established reference model tested by multiple authoring participants;
  • Can benefit from lessons learned by many implementations;
  • Able to start designing clinical models straight away;
  • Demonstrable use within a two-level modelling architecture;
  • Specification is freely available on the web to read and redistribute without cost;
  • Willingness of the organisation to work with CIMI and make changes as needed to meet CIMI’s needs

However, it should be noted that the following concerns and issues were also raised:

  • Concern about the complexity in the current openEHR reference model - a simplified model is preferred;
  • There are a few areas where some debate is required to bridge the gap between the model and the requirements;
  • Requires us to work together to simplify and improve
  • It is not a standard, and there are IP concerns relating to the specifications
  • Requires work to develop a UML-based profile and editing environment