NamingSystem constraint nsd-2 overly restrictive

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • NamingSystem
    • Hide

      Change the nsd-2 constraint expression to take period (including time zone considerations) into account for the preferred identifier for a type.  The operation will need to address this consideration - the default would be to return the preferred identifier at the present time.  Will add an additional input parameter 'effective' (dateTime) to the $preferred-id operation to specify other than the 'current' time.

      Show
      Change the nsd-2 constraint expression to take period (including time zone considerations) into account for the preferred identifier for a type.  The operation will need to address this consideration - the default would be to return the preferred identifier at the present time.  Will add an additional input parameter 'effective' (dateTime) to the $preferred-id operation to specify other than the 'current' time.
    • Rob Hausam/Carmela Couderc: 7-0-2
    • Enhancement
    • Compatible, substantive

      There is a period attached to NamingSystem.uniqueId which means that different identifiers of the same type can both be preferred.

      This scenario violates the constraint nsd-2 and also poses problems for the operation $preferred-id which can only return a single identifier. There is no mechanism for the client to specify the point in time that they are interested in.

            Assignee:
            Unassigned
            Reporter:
            Michael Lawley
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: