Andrew & Ogi,
openEHR Templates are not Forms, they are aggregations of archetypes with
further constraints. The scope of an openEHR template can be compared with
a form but define the data structure of that form. However openEHR
Templates can be used to drive the design and generation of forms a
> implementation spaces. Archetypes as clinical model exist independent of
> their potential use. Templates are the visual forms created for particular
> applications. Thus it would be possible to create different versions serving
> the same purpose - in this case the visual representation of a CCR
The reason why it is important to distinguish between archetypes and
templates is to why we insist on the separation between the design and
implementation spaces. Archetypes as clinical model exist independent of
their potential use. Templates are the visual forms created for particular
applica
Andrew,
I understand the limitation of no specifications for templates. Archetypes
are more than data structures, they are semantic structures. A CCR is a
data structure defined by a particular organisation but has no true
semantics in health, where as a discharge or referral is a common concept
> The CCR would not be implemented as a composition archetype but as a
> template.
Some of us haven't seen the template spec which makes it hard to
see where the line between openehr archetypes and openehr templates
lies.
> Obviously there will be a composition archetype required and
> several s
Andrew,
The CCR would not be implemented as a composition archetype but as a
template. Obviously there will be a composition archetype required and
several section archetypes but they would not be specifically designed for
CCR. The same archetypes should be able to be used in Australia
(HealthCon
Gerard Freriks wrote:
> My try.
>
>
> Template: It is the interoperable information part of a contract
> between two or more communicating actors.
Gerard,
that is a very nice functional definition. In some cases, the actors are
the GUI application user, and other users, whose previously persiste
Heath Frankel wrote:
> Andrew & Ogi,
> openEHR Templates are not Forms, they are aggregations of archetypes with
> further constraints. The scope of an openEHR template can be compared with
> a form but define the data structure of that form. However openEHR
> Templates can be used to drive the d
I bet you can...even better implement one that is compatible with CDAr2
CCR implementation; they have some implementation guides with detail;
CDA is supposedly mappable to a composition any way ;) (ask Heath
Frankel and Dipak Kalra, or Sam)..
Then go sell the idea to the NHS for mega$$
-Origi
Hi Heath,
I am interested in this aspect of archetypes/templates as well. I am
currently working with the Scottish National Clinical Datasets program to
see how we might integrate archetypes and templates into their data
standards development process i.e essentially as a design-time tool rather
th
e - in this case the visual representation of a CCR
> form.
>
> Ogi Pishev
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20070220/00d01228/at
Has anyone looked at making an openehr
composition archetype(s) corresponding to
the ASTM continuity of care record (CCR)?
I don't have access to the ASTM standard
but I was just looking at the HL7 document
describing how CCR maps into CDAr2 and
was thinking that it would be a good test of
the pow
12 matches
Mail list logo
