# Runtime references to other archetypes?
**URL:** https://discourse.openehr.org/t/runtime-references-to-other-archetypes/12414
**Category:** Technical (archive)
**Created:** [28 May 2007 16:44 UTC](https://discourse.openehr.org/t/runtime-references-to-other-archetypes/12414 "2007-05-28T16:44:12Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)
#### Post date: [28 May 2007 16:44 UTC](https://discourse.openehr.org/t/runtime-references-to-other-archetypes/12414/1 "2007-05-28T16:44:12Z")
Hi!
Do I understand correctly that (at least) the following two archetypes
refer to specific parts (selected by paths) of other archetypes, and
that these references will be created/selected by clinicians at
runtime?
[http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-INSTRUCTION.monitoring.v1draft.html](http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-INSTRUCTION.monitoring.v1draft.html)
Concept: Archetype
Description: The id of the archetype(s) to be filled as part of this monitoring
Type: Text
[http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-EVALUATION.goal.v1.html](http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-EVALUATION.goal.v1.html)
Concept: Archetype + path
Description: The archetype and path to the node that is to be measured
Type: URI - resource identifier
Why different data types?
What should the text respectively URI look like? (Examples welcome.)
What is the optimal type?
Any other archetypes using this kind of cross referencing?
Best regards,
Erik Sundvall
[http://www.imt.liu.se/~erisu/](http://www.imt.liu.se/~erisu/)
---
### Author:  [@Sam](https://discourse.openehr.org/u/Sam)
#### Post date: [30 May 2007 04:12 UTC](https://discourse.openehr.org/t/runtime-references-to-other-archetypes/12414/2 "2007-05-30T04:12:23Z")
Hi Erik
> ```auto
> Do I understand correctly that (at least) the following two archetypes
> refer to specific parts (selected by paths) of other archetypes, and
> that these references will be created/selected by clinicians at
> runtime?
>
> ```
Yes - or in the template.
> ```auto
> [http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-INSTRUCTION.monitoring.v1draft.html](http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-INSTRUCTION.monitoring.v1draft.html)
> Concept: Archetype
> Description: The id of the archetype(s) to be filled as part of this monitoring
> Type: Text
>
> [http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-EVALUATION.goal.v1.html](http://svn.openehr.org/knowledge/archetypes/dev/html/en/openEHR-EHR-EVALUATION.goal.v1.html)
> Concept: Archetype + path
> Description: The archetype and path to the node that is to be measured
> Type: URI - resource identifier
>
> ```
Yes - the idea is that there is a statement about the archetype and path of the attribute that is to be ‘monitored’ or what is the ‘target’. These are the basis for a query that will enable the system to show that a particular measurement must be carried out or a record created as part of the instruction.
So if the goal is the to lose weight the target might be the weight measurement in the weight archetype:
openEHR-EHR-OBSERVATION.body\_weight.v1 and the path to the weight measurement itself. (It could be the blood pressure measurement and the systolic blood pressure for example.
> ```auto
> Why different data types?
>
> ```
Historical reasons - URI - which will allow a path statement is correct.
> ```auto
>
> ```
> ```auto
> What should the text respectively URI look like? (Examples welcome.)
>
> ```
//openEHR-EHR-OBSERVATION.body\_weight.v1/data/event[at0002]/item[at0003]
(I did not check if this is the correct path but you get the idea.
> ```auto
> What is the optimal type?
>
> ```
Possibly DV\_EHR\_URI - what we are really expressing is a query rather than a link to any particular instance.
> ```auto
> Any other archetypes using this kind of cross referencing?
>
> ```
Complication (problem) as an optional URI or DV\_TEXT. We may need archetyping of links soon as many are asking for this - just making it visible to the modellers will help. Also, DV\_TEXT has a hypertext link to allow soft linkage to another problem for example.
Cheers, Sam