Hi Dileep,
the identification section of the AOM2 spec
<https://specifications.openehr.org/releases/AM/latest/AOM2.html#_archetype_identification>
gives a reasonable explanation. In ADL2/AOM2, a template is just an
archetype, not something different, so all the archetype rules apply.
More on ADL2 templates here
<https://specifications.openehr.org/releases/AM/latest/AOM2.html#_templates>.
ALl of the rules for ADL2/AOM2 should be the same for .oet / ADL 1.4
based templates (e.g. when is a new UID required etc).
hope this helps.
- thomas
On 18/06/2019 21:05, Dileep V S wrote:
Hi,
Please see a snippet from an OPT that we have. I see that there are 3
different pieces of identification - UID, template_id & concept.
Template_id seems to have been picked up automatically from the
template file name and UID automatically generated by the template
designer.
The concept is something that the person creating the template can
optionally give and can be different from the template_id.
<uid>
<value>0c8e4361-ed54-4555-b2d9-9680c1f2bb46</value>
</uid>
<template_id>
<value>EHRN Medication summary.v0</value>
</template_id>
<concept>EHRN Medication summary.v0</concept>
What are the intended purpose of each of these? Can we have two
templates with different sets of these data without creating a
conflict? For example can I have two versions of the same template
with different UIDs and template_id, but same concept? How about two
with different UIDs and same template_id or two with same UID and
different template_ids.
What situations can cause a conflict on the server?
regards
Dileep V S
/Founder/
HealtheLife Ventures LLP
m: +91 9632888113
a: 106, Innovation Centre, IIIT, Electronics City, Bangalore 560100
w: <http://ayushehr.com>ehr.network, <http://ehr.network>ayushehr.com
<http://ayushehr.com> <http://ayushehr.com> e: dil...@healthelife.in
<mailto:dil...@healthelife.in>
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Project, Intermountain Healthcare
<https://intermountainhealthcare.org/>
Management Board, Specifications Program Lead, openEHR Foundation
<http://www.openehr.org>
Health IT blog <http://wolandscat.net/> | Culture blog
<http://wolandsothercat.net/> | The Objective Stance
<https://theobjectivestance.net/>
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
