Hi Heather, Purely technically, I think the answer is "false" - since assumed values are an available independent of their context (e.g. data or state). But for all practical modelling I think the answer is "true" - assumed_value should really be used for protocol/state, but not data. As for the tooling, there's always a bit of tension between these two, i.e. how generic such tools can and should be, what should be exposed to the UI and what maybe not.
Sebastian Von: openEHR-clinical <openehr-clinical-boun...@lists.openehr.org> Im Auftrag von Heather Leslie Gesendet: Montag, 8. Oktober 2018 12:17 An: For openEHR clinical discussions <openehr-clini...@lists.openehr.org> Cc: For openEHR technical discussions <openehr-technical@lists.openehr.org> Betreff: Seeking clarification regarding Assumed value Hi everyone, Assumed value - https://www.openehr.org/releases/AM/latest/docs/AOM1.4/AOM1.4.html#_assumed_value I've spoken to Sam Heard on many occasions and I have understood him to say that the intent for an assumed value to only be relevant for 'State' in an OBSERVATION. But never in 'Data'. This is what I've always taught modellers. The original Ocean Archetype Editor, had this implemented. In more recent years 'assumed value' was implemented across all of the parts of the OBSERVATION. Incorrectly, as I understand it, but the code was never reviewed nor updated. We are now debating how this should be implemented in the new ADL Designer, and I'm seeking clarification. It makes sense to be able to potentially have an assumed value for 'State' - for example the position of the patient if it is always the same in 99% of use cases. The theory, as I understand it, is that in this situation the position will only be recorded if the assumed value is modified from the assumed value. (Mind you, if the assumed value is excluded/zero occurrence in an implemented template, it will not necessarily be a valid assumption, but let's keep that argument about whether assumed values are reasonable at all for later). The discussion is often further compounded by confusion about default vs assumed values. I don't think that it makes any sense to allow an 'assumed value' for actual data values eg a Systolic Blood Pressure measurement - especially if, as per the specs link (above), "The notion of assumed values is distinct from that of 'default values'. The latter is a local requirement, and as such is stated in templates; default values do appear in data, while assumed values don't." My question to the list: Data values need to be recorded explicitly and should never be assumed - True or False? Thanks Heather Dr Heather Leslie MB BS, FRACGP, FACHI, GAICD M +61 418 966 670 Skype: heatherleslie Twitter: @atomicainfo, @clinicalmodels & @omowizard www.atomicainformatics.com [cid:image001.jpg@01D45F0A.CBC67680]
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
