Hi Ian,
Thanks for the answer. I think having "process" & "etc" in the specs makes a
little difficult to understand what values are allowed in the category field.
BTW, in the Terminology.xml file, "process" is also present:
http://www.openehr.org/releases/1.0.2/architecture/computable/terminology/terminology.xml
<Concept Language="en" ConceptID="431" Rubric="persistent"/><Concept
Language="en" ConceptID="432" Rubric="Composition category"/><Concept
Language="en" ConceptID="433" Rubric="event"/><Concept Language="en"
ConceptID="434" Rubric="process"/>
--
Kind regards,
Ing. Pablo Pazos Guti?rrez
LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos
From: ian.mcnic...@oceaninformatics.com
Date: Wed, 3 Oct 2012 00:57:24 +0100
Subject: Re: Question about Composition.category
To: openehr-technical at lists.openehr.org
Hi Pablo
The only current allowed values are event and persistent. I am not quite sure
what process might mean in this context. This was clearly some philosophical
musing when the spec was written but I have not come across a need for this
when modelling so far. I have requested a change to allow a persistent
composition to have a context attribute , currently disallowed. Episodic care
such as hospital admission does throw up the need for persistent compositions
to carry the context of the episode but persist throughout that episode. eg a
problem list for the current admission.
Ian
Dr Ian McNicollClinical modelling consultant Ocean InformaticsMobile +44 (0)
775 209 7859Skype imcnicoll
On 3 Oct 2012, at 00:00, pablo pazos <pazospablo at hotmail.com> wrote:
Hi all,
As usual I'm reviewing the specs & the openEHR terminology.I understand the
"event" and "persistent" values for the Composition.category property.
There is also a "process" value, but I don't understand the difference between
"event" and "process". The specs are not clear here:
"Indicates what broad category this Composition is belogs to, e.g. ?persistent?
- of longitudinal validity, ?event?, ?process? etc."
Any thoughts?
--
Kind regards,
Ing. Pablo Pazos Guti?rrez
LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos
_______________________________________________
openEHR-technical mailing list
openEHR-technical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________
openEHR-technical mailing list
openEHR-technical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121004/a4203ffc/attachment.html>
