Dear Koray, According to SIAMM:
Any thing can be negated (or better it is declared that something is absent. Since each ENTRY archetype is a named process that is: ordered, executed, assessed or summarised after termination, we can describe: - that there is no order, no execution, no assessment or perception of the summary after termination of a specific named Action, Protocol, Clinical Pathway. - in addition it is possible that as the result of a query specific data is not found. (e.g. No recording of any Blood Glucose, no recording of Blood Glucose: > 12 mMol/L) This Presence/Absence indicator is NOT a boolean data type but a fixed text: Present/Absent In addition, after long debates, it had been decided in the CEN/ISO Task Groups that in the RM we have one flag that indicates that something is 'fishy'. It is the 'Attention' attribute in the ENTRY class. Gerard Freriks +31 620347088 gfrer at luna.nl On 15 jul. 2013, at 09:41, Thomas Beale <thomas.beale at oceaninformatics.com> wrote: >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20130715/f6dfd00d/attachment-0001.html>
