Hi There has been some discussion on what sort of tools we need and I am interested in how to approach the whole problem. It seems to me that messages define and information model for each transfer and that each message has to be agreed in advance. The problem space is message definition and HL7 is filling this space at the moment.
If we have a candidate EHR reference model and archetypes to enable the development of clinical models which can be shared post hoc, then everyone can develop a 1:1 transform to this space. The technical detail comes in understanding the set of archetypes, which we hope will be developed in chunks that mean they are relatively stable (with development through the specialisation and revision approachs) and only come up as candidates for a redesign that would break existing software very infrequently (versioning). We now have considerable experience in the breadth of the openEHR RM and its ability to cope with systems that are out there - hospital and primary care. We have only limited experience in managing the archetype space, but our new archetype development environment is coming on well and will address another generation of recording requirements in what we hope will be a solution for the next 20 years or so. The simple description of the new approach is: Information is divided into DATA - information for clinical care HISTORY - timing and time scope of the data STATE - information about the person or thing being measured that is required for interpretation of results PROTOCOL - how the information was derived, basis of measurement To use the old blood pressure DATA - systolic and diastolic readings HISTORY - a one-off or reading, a series, an average over a period, maximum or minimum over a period, variation in a series etc (This will include 0, 5 min and 10 minute readings, a change between readings (postural drop) etc) STATE - patient position, exercise etc PROTOCOL - sphygmomanometer, intra-arterial Our analysis at the moment is that the following configurations are useful: [ ] = optional DATA +/- PROTOCOL DATA + STATE +/- PROTOCOL HISTORY + DATA +/- PROTOCOL HISTORY + DATA + STATE +/- PROTOCOL DATA +/- PROTOCOL HISTORY+DATA + HISTORY+STATE +/- PROTOCOL This is relatively easy to support from an archetype point of view and the new prototypes Tom has announced will make this approach come alive. We should have some example archetypes and the GUI tool available shortly... CHeers, Sam Heard > -----Original Message----- > From: owner-openehr-technical at openehr.org > [mailto:owner-openehr-technical at openehr.org]On Behalf Of Bill Walton > Sent: Tuesday, 29 July 2003 12:14 PM > To: lakewood at copper.net; openehr-technical at openehr.org > Subject: Re: certification and verification of OpenEHR > > > /big snip/ > > > OPINION: Would like to see a tool that can access/breakdown different > types > > of EHRs, support information transfer and synthesis of > additional records, > > even a modified EHR. > > > > Are there others on the list interested in this topic? > > > > -Thomas Clark > > Definitely. > > Best regards, > Bill > > - > If you have any questions about using this list, > please send a message to d.lloyd at openehr.org - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
