Hi Matiass,

Mattias Forss wrote:
>
> Archetype A and archetype B will have 'correct archetype paths 
> according to where the fragment was put', but will they refer to the 
> same paths? When I talked about data I meant what was stored in the 
> EHR system and when I talked about values I meant what was entered in 
> the template.
>
> I tried to ask if there is some way to make two or more archetypes 
> manipulate exactly the same data in an EHR system, meaning that the 
> archetypes probably must refer to the same paths - otherwise the data 
> will be manipulated at different places and the system must know that 
> the data at the different places are actually the same. Consider this 
> example:
>
> Archetype A is used in a template to create data about a patient's 
> weight and archetype B is used in another template and will also 
> create data about the weight. However, if the weight data was already 
> entered in the EHR system, is there a way (to create archetypes) which 
> make the system know that it deals with the same data no matter if it 
> came from archetype A or archetype B and fetch the last entered value 
> to any of the templates that need the weight information?
Ah, I understand where you are coming from now. Archetypes and templates 
don't know anything about which data instances they have created; it is 
the other way round. A given template could be used to create 20 
measurements of weight of the patient, which might be reasonable if the 
patient happens to be an infant, the measurements might be every few 
weeks from birth for say 18 months. The data of each of those 20 
measurements (Observations inside distinct Compositions) knows that such 
and such an archetype and template was used to create the data. So if 
the application retrieves one of the older measurements, the kernel will 
know which archetypes and template to apply, However, this would not 
occur unless someone was correcting wrongly entered values; normally 
previous data are just viewed, e.g. in a graph or similar, which doesn't 
require the kernel, just archetype-aware display components.

There is also a question of whether certain data could be compatible 
with more than one template or archetype. It can certainly be compatible 
with more than one template, since templates re-use archetypes. It can 
also be used with parents of specialised archetypes. We have already 
tested ,more generic archetypes (and no archetypes) being used with data 
archetyped with specific specialised archetypes, and it works fine for 
display.

does this help?

-  thomas

_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical



Reply via email to