David,
sorry, you are right, I misread you. As usual, you were writing
precisely, and I was reading imprecisely ;)
- thomas
On 02/12/2016 13:45, David Moner wrote:
2016-12-02 14:22 GMT+01:00 Thomas Beale <[email protected]
<mailto:[email protected]>>:
I see the case of Silje from a different perspective. What she is
asking is if we can document the participants of each Element
inside the Entry. So far this is not possible, as Entries have
been always seen as a whole clinical statement, with all
participants assigned to that level.
From a realist perspective, the phrase 'participants of an
Element' doesn't completely make sense - an Element is just an
atom of information that is part of something else. You can only
participate in an 'activity' (an Activity that has been performed
in openEHR is an Action; an activity that generates information is
usually an Observation, with the protocol part indicating how it
was done), and to express the activity generally takes 1..N
Elements in some sort of structure, including timing etc. If two
different activities are being reported inside the same Entry,
there are two possible conclusions:
1. it should really be two Entries
2. they are just considered detailed items within the larger
activity documented by he Entry.
I think we need to be more careful on the meanings of the
primitives in the RM - in any RM in fact - they are regularly
abused within all RMs I see, including CDA, FHIR, even HL7v2. It
always seems OK from a human perspective, but we say good-bye to
computable information when we do that.
That was exactly my point ;-)
I was not advocating for including participations at the ELEMENT
level. On the contrary, I was remembering that it can only be done at
the ENTRY level.
In the case of Silje, the histopathology findings archetype that can
be found at the CKM is a CLUSTER
(http://www.openehr.org/ckm/#showArchetype_1013.1.2680). So, it is not
possible to add there the participation information to inform about
who did the macro or micro findings as she wanted. The alternative I
proposed without modifying the current RM is, as you also said, to
create two different ENTRYs.
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
