> Hi everyone, Hi koray, how do you want to do this? We decided against absence / exclusion in th RM a long time ago, because it is not a simple negation in general, but a complex (i.e. archetyped) statement.
-thomas > > This is to do with my long standing issue about recording absence of info. In > endoscopy models the "Presence" of endoscopic findings was represented as a CLUSTER where a special ELEMENT (that is internally referenced many times for each finding thereafter) captured "Presence" of a finding and also if/why information about a particular finding was not available. This I thought was a quick and dirty fix to a larger problem which I reckon applies to all data structures and types including ENTRY Class itself. > > I came across this in NEHTA medication archetypes: > > COMPOSITION.Medication_List has "Absent Info slot filled by openEHR-EHR- EVALUATION.absence.v1 (and specialisations) that has only one ELEMENT which captures absence (free or coded text) > > Description says: Positive statement that no information is available about > medication use. > > While this approach solves the current problem in the long term and in order > to enable a global scale interoperability it seems to be another quick & dirty fix. To me this is a crystal clear pattern for clinical information (and potentially administrative too) - shouldn't this be handled in RM? > > Sorry if this has already been dealt with - I haven't been able to read all > discussions for a while. > > Cheers, > > -koray > > Koray Atalag, MD, PhD, FACHI > > Senior Research Fellow > > Description: Description: Description: cid:image001.png at 01CD2460.A69C1680 > > School of Population Health, The University of Auckland > > Private Bag 92019 Auckland 1142, New Zealand > > Email: k.atalag at nihi.auckland.ac.nz<mailto:k.atalag at > nihi.auckland.ac.nz> | Web: www.nihi.auckland.ac.nz<http://www.nihi.auckland.ac.nz/> > > Skype: atalagk Mob: 021 02412096 DDI: +64 9 923 7199 -- Thomas Beale Chief Technology Officer Ocean Informatics
