We're updating the issue view to help you get more done. 

Conflict between PARTY_RELATIONSHIP.type() requirements and item-path specification

Description

The [Type_validity: type = name] invariant of PARTY_RELATIONSHIP cannot be satisfied in the context of a ROLE without breaking the item-path specification, where it is stated the name must be unique among siblings (see http://www.openehr.org/releases/1.0.2/architecture/overview.pdf , Chapter 11 - Paths and locators).

Example:
===================================
ROLE = <
name/value = 'HC consumer'
identities = ....
relationships = (Set<PARTY_RELATIONSHIP>) <
[at0002] = <
name/value = 'Insurance'
details = ....
time_validity = 1/jan/1992 - 20/jan/2011
>
[at0003] = <
name/value = 'Patient'
details = ....
time_validity = 1/jan/1992 - 20/jan/1992
>
[at0003] = <
name/value = 'Patient'
details = ....
time_validity = 1/dec/2002 - 20/dec/2002
>
...
>
===================================

The [type() = name] is not only a PARTY_RELATIONSHIP issue, but applies to other classes from demographic package. In a way it was also reported by Sergio Freire on the mailinglist: http://lists.chime.ucl.ac.uk/mailman/private/openehr-technical/2010-August/005308.html

Environment

None

Status

Reporter

Sebastian Iancu

Labels

None

Components

Affects versions

RM Release 1.0.2

Priority

Minor