openEHR "Silver" Model

Hi All,

I know this is probably a very politically sensitive topic, but I am
wondering what the path forward for harmonization of openEHR with CEN
13606. I was talking to Peter Schloeffel yesterday and Peter mentioned
that there are three options:
- the "bronze" option, which involved fixing a couple of things in the
  existing CEN model and adding archetypes to it.
- the "silver" option, which simplifies and modifies openEHR and uses that
  as a basis for the new CEN model
- the "gold" option, which uses the full openEHR model as the basis for
  the new CEN model

Peter also mentioned to me that it was highly likely that the "silver"
option would be the most successful.

My question to the list is, what would you simplify or modify in the
openEHR model?

My gut feeling is to remove everything not required by ISO 18308, but I am
not sure what that would entail or the side effect of that.

Any thoughts?

cheers, Andrew

  _-_|\ Andrew Goodchild
/ * DSTC Pty Ltd
\_.-._/ Brisbane, Australia
      v http://staff.dstc.edu.au/andrewg/

Hi,

My personal thoughts are:

This discussion is trivial.

CEN decided to:
- renew the ENV 13606
- use the two model approach
- produce a standard that can be used to produce: messages, documents and
implementable objects

My preference is the platinum model :slight_smile:
But I go for the gold one.

And as long as we can show that one is able to map to the silver one or the
bronze one, I see no problem. Mapping means that we are able to produce an
Archetype that fulfils the requirements of all those models.

A consequence of the decision taken by CEN is that the Kernel (including the
data types) plus the Archetype model must be stable and as complete as
possible. The various degrees of granularity (that equals the number of
concepts and equals the number of archetypes and complexity of it) will be
outside of the control of the standardisation organisation. It will be in
the hands of the domain experts/user communities.
Each user community that wants to exchange information will use the Kernel
and Archetype Model plus the set of agreed archetypes it needs to use.

So we must provide all proponents of the bronze and silver options
archetypes that fulfil their requirements.

My option is the Patinum one :wink:

Gerard

Ps:
A likewise argument can be made for the data type problem.
We have the PT41 proposal, the HL7 one and the OpenEHR one.

Possibly we have to show that all three are mappable and therefore equally
correct and interchangeable.

This discussion is trivial.

Except for the fact that I may learn from it.

CEN decided to:
- renew the ENV 13606
- use the two model approach
- produce a standard that can be used to produce: messages, documents and

That has been shown to work in abundance.

implementable objects

This is what fills me with new hope. And hopefully it will go
from implementable objects to implemented objects.

Karsten

Dear Andrew and others,

I must take responsibility for the metaphor of gold, silver, bronze (platinum is Gerard's addition!). My intention was not to indicate a first, second, third quality of achievement as in the olympics, but really to indicate level of completeness/sophistication. I did not wish to imply that simple models are inferior, they just serve different purposes from complex ones. I would like to have found an alternative metaphor but could not think of one when I was writing to Peter several days ago. I would still be grateful for suggestions.

Andrew, you do raise an important point about what can be cut out. I will copy here a paragraph I have just sent around the Reference Model Task of the CEN Task Force on this.

"Through openEHR David Lloyd and I have been working to build on a decade of practical EHR experience from GEHR, EHCR-SupA, Synapses, SynEx and 6WINIT resulting in a working ENV13606-like record server using a dual model approach, combining this with a similarly rich experience in Australia and catering for new requirements in areas such as text and language processing, decision support and bioinformatics, to arrive at a “best of breed” approach to the Reference Model and Archetype Model, ready for a new wave of implementation and validation. We recognise that the openEHR models now therefore contain some features that need new evaluation, but many features are fairly well tested approaches that could be adopted for standardisation."

We must accept that, whilst we believe the openEHR models to be the best basis on which to build the next generation of EHR servers, we do not have implementation experience to back all parts of it. It is likely that some refinements will emerge as necessary in the light of implementation deployment and live clinical use. I therefore suggested that, whilst openEHR has a legitimate desire and drive to evaluate next-generation solutions, a legislative standard ought to build on those aspects which are most solid and can be regarded as reasonably stable. openEHR needs to be free rapidly to evolve on the basis of new requirements and implementation experience. The openEHR approach and models exist in their own right, and can be taken up by any vendor or demonstrator without endorsement from CEN.

The new CEN standard (for EHR communication) does need to be compatible with openEHR, and it should be possible for a standards-conformant vendor easily to migrate from new-CEN to full openEHR, but I don't think we will do CEN or openEHR a service by seeking to have these two exactly tied together at any one point in time.

However, if you accept that premise (and you are welcome to disagree) the question remains about how to derive a suitable candidate for standardisation from openEHR. David and I have begun working in this area, with offer of help from Tom. I think we would welcome ideas from the broader openEHR community about the methodology we should pursue.

With best wishes,

Dipak