CIMI group goes with openEHR archetypes & UML profile

14/12/2011

The Clinical Information Modelling Initiative (CIMI) group led by Dr Stan Huff (Intermountain Health, Utah) met here in London 29 Nov – 1 Dec to make a final decision on formalism, from the two remaining – openEHR archetypes and various forms of UML (previous posts on CIMI: DCMs & RM, on formalisms). Instead of simply choosing one, the group made a more strategic choice of designating openEHR ADL/AOM 1.5 as the core formalism, with a corresponding profile of UML being developed to enable the more numerous UML-based developers (e.g. VA, NHS etc) to use archetypes within their UML toolchains.

Here is the public announcement resulting from this meeting.

Read the rest of this entry »


CIMI: purpose-built or jury-rigged?

14/11/2011
In recent weeks, the Clinical Information Modelling Initiative (CIMI), led by Stan Huff, has followed its stated process and is nearing a voting process in which a shared health domain modelling formalism is chosen. Proponents of each of the candidate formalisms have been asked to post arguments supporting their work.
A supporting statement for openEHR archetypes as the optimal formalism is posted here, on the CIMI wiki. We have not included any beautiful tool-based views, nor even the ‘latest and best clinical models’, following Stan’s request for the ‘raw’ technical view of the syntax. Accordingly, the only thing with even any colour in it is these screenshots of an ADL archetype in a raw text editor, with syntax highlighting on.
Read the rest of this entry »

DCM – Data Types and Reference Model considerations

11/09/2011

Following the DCM meeting convened by Dr Stan Huff (Intermountain Healthcare) in Washington in July, reported in an earlier blog post, there is a further meeting this week in San Diego, which will discuss the issues of ‘data types’ and ‘reference models’ for the purpose of DCM (detailed clinical models).

I created two slideshows to explain my views on these matters (DCM_and_data_types and DCM_and_reference_model [both PDF]). Below is an extract of my arguments in these slideshows, based on experience, for adopting a particular approach to data types and reference model within the stated mission the DCM forum, which is to find formalism and attendant models in which to express universally shareable detailed clinical models. Naturally, my view on ‘the answer’ to that question is ‘openEHR (ADL/AOM) archetypes, templates and terminology’, but what I am providing below is not an argument supporting that, but one proposing how to proceed with respect to the ‘underlying models’.
Read the rest of this entry »


Information models, DCMs and Archetypes

07/07/2011

I will be attending a ‘Fresh Look’ meeting in Washington next week. The idea is to make some progress on the topic of  ‘detailed clinical models’ (DCMs). Some of the goals include setting up a repository of DCMs, establishing governance, and defining a roadmap for tooling. Underlying all this is a huge list of formalisms and models, including OWL, UML, ADL, HL7 MIF, XSD, LRA, RMIMs, CDA templates, greenCDA and so on. Read the rest of this entry »


DCMs – can they look good AND be computable?

08/06/2011

Let’s talk about mindmaps and archetypes. Mindmaps seem to be fuzzy and friendly – we need them because they are incredibly efficient at transmitting information to humans. Archetypes seem über-mathematical, but we need them to do proper model-based computing.

Read the rest of this entry »


Detailed Clinical Models (DCMs) – some basic facts

03/06/2011

The New Zealand e-health programme architecture task-force has published its Working Interoperability Reference Architecture blueprint document. With respect to the document and the comments posted (I tried to post myself,  but the comment disappeared), it seems worth making a couple of points on DCMs, of whatever flavour. If a DCM is to be expressed in a way useful to building and managing health IT infrastructure, there are two possibilities. Read the rest of this entry »


The crisis in e-health standards II

01/10/2009

Prev: The crisis in e-health standards
Next: The crisis in e-health standards IIa

In my last post I made three basic points:

  1. that the committee-based process used by official standards organisations is not designed to be used for standards development and will not generate the required outcomes in e-health;
  2. that the process of  ‘choosing standards’ by governments (or anyone else) will not result in an integrated set of specifications on which widespread e-health interoperability can be based.
  3. a new way of producing standards for e-health is needed.

Although for most engineering and other technical people, these points are obvious, it is nevertheless reasonable to present some evidence. Read the rest of this entry »


Follow

Get every new post delivered to your Inbox.

Join 55 other followers