Model CEN/TC251 13606
Gerard Several points: 1.Specifically, openEHR proposes a number of Reference Models, supplemented by Archetype Models. 2. You seem to use the word 'Kernel' as a synonym for Reference Model. If this is not so, please will you explain your use of the word Kernel? 3. The Reference Models proposed by openEHR are just sufficient to meet the set of published requirements (e.g. ISO 18308) for an EHR and apply to _any_ EHR. It is necessary to delineate various levels in the Architecture in order to be able to place Classes, Attributes, and Functions appropriately to meet the requirements. 4. The Reference Models are indeed generic, in the usual sense that they are not prescriptive about what _information_ must be in an EHR, but make possible the representation of all those kinds of information known to exist in (or be necessary for future) EHRs. 5. For each Reference Model there will be a corresponding Archetype Model (only the Data Types Archetype model has so far been released). Authors of actual Archetypes, conforming to the Archetype models, will be able to impose the required constraints of their domains to guide the construction of instances of EHRs. 6. To my way of thinking, everything about the Reference Models is _generic_. Archetypes provide the means of using the models to construct EHRs for particular, i.e. non-generic, domains. I hope this helps to resolve what appears to be a fundamental difference between us! With best wishes David At 21:02 02/12/2002 +0100, you wrote: Dear colleagues, The last week I had a discussion with some colleagues of me at TNO. They studied the OpenEhr proposal for a model for the EHR. It is their opinion, and I agree with it, that the Kernel is not generic enough because it contains things like the structure of the document (folder, transaction, etc) Even things like an organiser archetype must become a real archetype and be not a part of the kernel. With regards, Gerard -- private -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands +31 252 544896 +31 654 792800 - If you have any questions about using this list, please send a message to d.lloyd at openehr.org * David S.L. Lloyd, Technical Consultant * CHIME - Centre for Health Informatics and Multiprofessional Education, at UCL * E-Mail: d.lloyd at chime.ucl.ac.uk Tel: +44 (0)20 7288 3364 * Web: www.chime.ucl.ac.uk/~rmhidsl#contact - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
Subject of care
Hi, S.o.C can mean many things: One person One mother or foetus Any body part in or outside the body And any grouping of items mentioned above. A S.o.C indicates the participation in activities. Gerard On 2002-12-01 23:38, Sam Heard sam.heard at bigpond.com wrote: Dear all I have been reviewing the subject of care - over family history. It is clear that the following information is potentially useful: 1. The name of the person so you can refer to them as so-and-so 2. The relationship (father, mother) this might or might not include their genetic relationship (adoptive) - at present I have this in the genetic relationship boolean value of the family history problem. I think this is the most appropriate as it is the only time when it is essential to know it?? 3. The ID of the person in the demographic server - allowing contact details etc. Can others think of other issues with identifying the subject of an entry in the EHR - (not the ehr itself!) Times when this is likely are around the birth of a child and for family history problems. Cheers, Sam Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-2, Standards Australia Hon. Senior Research Fellow, UCL, London 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838 808 sam.heard at bigpond.com www.openEHR.org www.HL7.org __ Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-2, Standards Australia Hon. Senior Research Fellow, UCL, London 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838 808 sam.heard at bigpond.com www.openEHR.org www.HL7.org __ - If you have any questions about using this list, please send a message to d.lloyd at openehr.org -- private -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands +31 252 544896 +31 654 792800 - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
Subject of care
Sam Heard wrote: Dear all I have been reviewing the subject of care - over family history. It is clear that the following information is potentially useful: 1. The name of the person so you can refer to them as so-and-so but not in the EHR as such - in some places like Norway, it is not allowed to have patient name or some other kinds of identifying information in the EHR. So it has to be in the demographic server, ad referenced from the EHR by meaningless ids. On the screen this will of corse be invisible. - thomas beale - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
Archetype rules (invariants) in openEHR RM?
Dario Liberman wrote: Well, In this case, I recommend to add a kind of actor, that may be de aggregation of other actors. The administrator may decide which capabilities or roles this new actor may have, since it doesn't necessarily need to have anything in common with the aggregation of the capabilities of each of the actors it aggregates. I have added this to a list of change requests, but there is more thinking to be done - we may need to differentiate between workgroups which exist in and of themselves, e.g. cardiology team (?), versus groups which are formed around a patient, e.g. a diabetic care team, which is a particualr grouping of people likely to exist only for a particular patient (i.e. they are not constituted as any formal team). Would the latter be identified as a group? Where? We have the concept of PARTY, ACTOR etc in the demographic model for things which exist regardless of context, and PARTICIPATION for context-specific participations of PARTYs in activities around the patient. - thomas beale - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
