CRM Taskforce Meeting Minutes - 5 April 2012

From CIMI
Jump to: navigation, search

Attendees

  • Linda Bird (Ministry of Health Holdings, Singapore)
  • Stan Huff (Intermountain Healthcare)
  • Richard Kavanagh (NHS Connecting for Health)
  • Josh Mandel (SMArt)
  • Michael van der Zel (Results4Care)
  • Gerard Freriks (EN13606 Association)
  • Thomas Beale (Ocean Informatics)
  • Galen Mulrooney, ONC, U.S.A.
  • Grahame Grieve (Health Intersections)
  • Cecil Lynch (Accenture) - CIMI Clinical Modelling Taskforce
  • Dipak Kalra (UCL) - Guest

Apologies

Agenda

  • Welcome to Cecil Lynch and brief update of CIMI Clinical Modelling taskforce
  • Brief update from Tom and Grahame on planned datatype work
  • Presentation from Dipak on UCL datatypes work
  • Tooling requirements
  • Core CIMI Reference Model – discussion
  • Clinical Modelling Layers (including clinical patterns)
  • Plan / Actions

Brief Summary

  • Welcome to Cecil Lynch and brief update of CIMI Clinical Modelling taskforce
    • Clinical modelling taskforce to meet next week
    • Will start with a small set of clinical models at mindmap level
    • Cecil and Linda to start cross-attending meetings to support collaboration
  • Brief update from Tom on planned datatype work with Grahame
    • To start with openEHR datatypes and use Grahame’s (FHIR) work as a more uptodate source of evidence to update openEHR datatypes as required.
    • Will consider the appropriateness of some data types, such as ‘Reference Range’
    • Will consider data types using example models
  • Presentation from Dipak on UCL datatypes work
    • How they approached the problem
    • Considered versioning, null flavour
    • Some datatypes (e.g. addresses) may be better as archetypes
    • Profile was slim/lean/mean set of datatypes
  • Datatype discussion following presentation
    • Should we be establishing a pattern of versioning instances?
    • Modelling of semantic links between 2 instances of data may require pointing to a specific instance version.
    • We should be modelling semantics around clinical data, but not transactional semantics around update
    • ISO18308 defines high level data type requirements. If time permits, these requirements could be elaborated on with more current evidence
  • Tooling requirements
    • 1: Taskforce Deliverable: One or more UML class diagrams, which together represent the candidate CIMI reference model:
      • Requirements:
        • Enable the specification of UML 2.0 Class diagrams
        • Import and generate XMI 2.3
        • Display and share UML 2.0 class diagrams
        • Affordably priced, and industry accepted
      • Candidate Tools:
        • BOUML – cheap (50 Euro per seat), generates XMI 2.3
        • Enterprise Architect (EA) – industry accepted, affordable, import/exports XMI 2.3, commonly used (Michael, Galen, Linda, Cecil)
      • Actions:
        • Consider EA - Check the XMI output generation is solid
    • 2: Taskforce Deliverable: An implementation of the candidate CIMI reference model that enables a set of initial clinical models to be created based on this reference model (preferably using ADL 1.5):
      • Requirements:
        • Based on CIMI RM
          • Adapt to CIMI RM as it changes (either hard-coded or customizable)
          • Including clinical patterns
        • Create and update clinical models
          • Based on CIMI RM
          • Define constraints on all parts of CIMI RM
          • Specialisation, Terminology binding
        • Version, review, import and publish clinical models (in ADL 1.5/ADL:XML)
        • Goal state: Export/Import models from openEHR, ISO13606-1, CEML, XMI, HL7 etc
        • Goal state: Generate documentation for review
        • User roles: e.g. model developer, reviewer
      • Candidate Tools:
        • openEHR Workbench Editor – Supports any reference model; Will be first to generate ADL 1.5; Question: When will editor be ready for use?
        • Existing archetype editor + Text Editor (to edit for ADL 1.5 and revised reference model
        • Spreadsheet with ADL generator
    • 3: Other CIMI Tooling: Not a taskforce deliverable, but required by CIMI
      • Clinical model repository: including download, review, read
      • Terminology workbench: Edit/maintain CIMI reference terminology
      • Terminology server: Share CIMI reference terminology and support binding to clinical models
  • Core CIMI Reference Model – discussion
    • <Discussion deferred to next week>
  • Clinical Modelling Layers (including clinical patterns)
    • <Discussion deferred to next week>
  • Plan / Actions
    • Finalise tooling requirements (Michael, Linda)
    • Test EA UML XMI generation (Tom, Linda, Galen)
    • Datatype work (Tom, Grahame, Alan)
    • Collaboration with Clinical Modelling Taskforce
    • Consider core reference model issues

Actions

  • Distribute minutes to taskforce (including CIMI wiki): Linda
  • Tooling Requirements: Michael, Linda
  • Test UML XMI generation: Galen, Tom, Linda
  • DataType work: Tom, Grahame, Alan
  • Collaboration with Clinical Modelling taskforce: Linda, Stan
  • Core reference model issues: All
  • Update from CIMI IEC: Stan