Uploaded image for project: 'Specification PR tracker'
  1. SPECPR-54

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

    Details

    • Type: Problem Report
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects versions: RM Release 1.0.2
    • Fix versions: RM Release 1.0.3
    • Components: RM Demographic model
    • Labels:
      None

      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

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                Rong Chen
                Reporter:
                Sebastian Iancu
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: