Dear All
We are adding constraints on participation to the Archetype Editor. Participations can be recorded at two levels, the Composition and at the level of the Entry. Remember that the reference model knows who was the author of the composition - which is mandatory. There is a special participation on each entry called provider which is just the identification of the source of the information.
If we see archetypes as the shared maximal data set we never want to constrain something in a way that would mean other people collecting the same information would have to use another structure - this means we do not want to put any constraints in the archetype that might be use specific. All such constraints go into the templates where everyone can do as they wish (always keeping to the model expressed in the archetype). Archetypes are what we agree on to enable interoperability.
Attestation or signing is dealt with using another mechanism, so there is no need to bring that into this discussion.
The next release of the archetype editor will have a participations tab. At the level of the entry this will allow:
-
The ability to make the provider of the information mandatory. While this is not a general requirement, in cases like consent and some other issues it is good to have this in a computable form rather than just as text - this is possible through the PARTY_PROXY which allows formal statements such as SELF, related parties with relationship and with or without identification and demographic identifier and also identified party again with or without demographic identifier. (I actually think this part of the openEHR model is extremely elegant but I am biased and it did take about 10 years to get to this point!)
-
Add participations with occurrences set and possibly
- restricted modes - this is an openEHR termset that describes the mode and includes telemedicine, written notes, email…and of course face to face.
- function - this is a DV_TEXT and may be limited to a term set in an external terminology or build a termset within the archetype (internal codes). Both of these are unlikely at present in the archetype, but the time is coming. It does mean that for procedures we can have the operator, assistant etc if this is appropriate.
- Force the date time interval of the participation to be recorded - ie make it mandatory as it is optional in the model.
Please have a look at the UML
Lets hear if there are any concerns…
Cheers, Sam