The archetype constraints the reference model, if something isn't
explicit on the archetype definition the default classes and
attributes from the reference model are assumed
2009/5/7 Stef Verlinden stef at vivici.nl:
I've been working through the demographic AT's that were provided by Sergio.
It's probably due to my lack of technical knowlegde but I can't find where
reverse_relationships are defined in these archetypes. Or it must be
in?openEHR-DEMOGRAPHIC-ROLE.health_consumer.v1 under:
relationships matches {
??? ??? ??? PARTY_RELATIONSHIP[at0010] matches
{??? -- relationship between a health consumer and a third-party
payer
??? ??? ??? ??? details matches { -- we gaan
er klaarblijkelijk vanuit dat er maar 1 relatie kan bestaan met
zorgverzekeraar
??? ??? ??? ??? ??? allow_archetype
CLUSTER[at0011]??? matches { -- identifier used in the relationship
include
??? archetype_id/value matches {/([a-zA-Z0-9_]+)*(identifier)\.v1/}
In that case I probably don't understand how this works. From what I read in
the demographic_im there shoudl be by references to the??HIER_OBJECT_IDs
Can somebody help me to understand this and possible explain how to create
such an reverse_relationship in an AT.
Cheers,
Stef
___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
--
Diego Bosc? Tom?s diebosto at fis.upv.es
yampeku at gmail.com
Grupo IBIME
Instituto ITACA - Universidad Polit?cnica de Valencia
Acceso B
Edificio 8G
Camino Vera s/n
46022 VALENCIA (Spain)
tel: +34 963 875 277
http://ibime.upv.es