Templates, node identifiers and data instances

[Gerard Freriks]

Safari worked fine

GF

Gerard Freriks
+31 620347088
gfrer at luna.nl




On 19 Nov 2010, at 16:55, Sebastian Garde wrote:

> Hi Seref,
> 
> I have the same problem sometimes with PDFs from the openEHR space in Firefox.
> Often it works, but sometimes I get the error you experience.
> 
> Regards
> Sebastian

Templates, node identifiers and data instances

[Sebastian Garde]

An HTML attachment was scrubbed...
URL: 

Templates, node identifiers and data instances

[Seref Arikan]

Did anybody else experience the following problem trying to follow Thomas's
link? In my firefox 3.6.12 under win xp with Adobe reader, I get a blank,
black tab at first, and a refresh pops up a window that says a dict object
is expected. Right clicking on the link and saving it works..

Best Regards
Seref


On Fri, Nov 19, 2010 at 12:38 PM, Thomas Beale <
thomas.beale at oceaninformatics.com> wrote:

>
> David,
>
> this document
> talks
> more about this topic. In my view the data should record both the template
> id, and the template at-code, i.e. at0001.1 or whatever. Note that querying
> will normally be driven off archetypes, so in reality what is like to happen
> is that the data will carry a code like at0001.3.2 from some template, whose
> parent is an archetype having at0001.3 as the code on the same node; the AQL
> query would be constructed using the at0001.3, and will pick up any
> at0001.3.2, at0001.3.3, at0001.3.0.1 etc from any number of conforming
> templates - exactly the intended effect of the query.
>
> - thomas
>
>
> On 19/11/2010 12:07, David Moner wrote:
>
> Dear all,
>
>  I have a doubt about templates defined as an archetype specialization.
> The updated specs say that templates are just a further specialized
> archetype. So, any change made at that level (remove or define mandatory
> nodes, slot filling, etc.) also means a new level at the node identifier.
> For example, if I have a node with "at0001" and I constraint something of it
> at the template level, we should generate a new "at0001.1" for that node.
>
>  The question is, data instances that will be generated should use the
> clinical archetype node id (at0001) or the template node id (at0001.1) as
> archetype identifier? Or phrased differently, for the second case, if I
> communicate the instance, should I also share the template definition to
> better describe it or would be enough by sharing only the clinical
> archetype?
>
>  David
>
> *
> *
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 

Templates, node identifiers and data instances

[Tim Cook]

On Fri, 2010-11-19 at 16:55 +0100, Sebastian Garde wrote:
> Hi Seref,
> 
> I have the same problem sometimes with PDFs from the openEHR space in
> Firefox.
> Often it works, but sometimes I get the error you experience.

Works for me w/Firefox 3.6.12 on Ubuntu

--Tim


-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: 

Templates, node identifiers and data instances

[David Moner]

Dear all,

I have a doubt about templates defined as an archetype specialization. The
updated specs say that templates are just a further specialized archetype.
So, any change made at that level (remove or define mandatory nodes, slot
filling, etc.) also means a new level at the node identifier. For example,
if I have a node with "at0001" and I constraint something of it at the
template level, we should generate a new "at0001.1" for that node.

The question is, data instances that will be generated should use the
clinical archetype node id (at0001) or the template node id (at0001.1) as
archetype identifier? Or phrased differently, for the second case, if I
communicate the instance, should I also share the template definition to
better describe it or would be enough by sharing only the clinical
archetype?

David

-- 
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es

Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part --
An HTML attachment was scrubbed...
URL: 

Templates, node identifiers and data instances

[Thomas Beale]

David,

this document 
talks
 
more about this topic. In my view the data should record both the 
template id, and the template at-code, i.e. at0001.1 or whatever. Note 
that querying will normally be driven off archetypes, so in reality what 
is like to happen is that the data will carry a code like at0001.3.2 
from some template, whose parent is an archetype having at0001.3 as the 
code on the same node; the AQL query would be constructed using the 
at0001.3, and will pick up any at0001.3.2, at0001.3.3, at0001.3.0.1 etc 
from any number of conforming templates - exactly the intended effect of 
the query.

- thomas

On 19/11/2010 12:07, David Moner wrote:
> Dear all,
>
> I have a doubt about templates defined as an archetype specialization. 
> The updated specs say that templates are just a further specialized 
> archetype. So, any change made at that level (remove or define 
> mandatory nodes, slot filling, etc.) also means a new level at the 
> node identifier. For example, if I have a node with "at0001" and I 
> constraint something of it at the template level, we should generate a 
> new "at0001.1" for that node.
>
> The question is, data instances that will be generated should use the 
> clinical archetype node id (at0001) or the template node id (at0001.1) 
> as archetype identifier? Or phrased differently, for the second case, 
> if I communicate the instance, should I also share the template 
> definition to better describe it or would be enough by sharing only 
> the clinical archetype?
>
> David
*
*
-- next part --
An HTML attachment was scrubbed...
URL: