Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-13314

NamingSystem.replacedBy assumes NamingSystems have a fixed physical location

    XMLWordPrintableJSON

Details

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

      Remove NamingSystem.replacedBy. We can't come up with a use-case where this would ever be used. Also remove nsd-3

      Show
      Remove NamingSystem.replacedBy. We can't come up with a use-case where this would ever be used. Also remove nsd-3
    • Eric Haas/James Agnew: 10-0-0
    • Enhancement
    • Non-compatible
    • STU3

    Description

      Currently, NamingSystem.replacedBy is a resource reference, referring to the REST endpoint where another namingsystem can be found. We fear this will not work well in situations where NamingSystems are put into registries - when registries each have a copy of the NamingSystem, the receiving registry would have to update this element to point to the NamingSystem within the same registry if it also has a copy of the replaced system.

      Wouldn't it be better for this to be a fixed url, instead of a resource reference, that refers to one of the NamingSystem.uniqueIds?

      Attachments

        Activity

          People

            Unassigned Unassigned
            ewout Ewout Kramer
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: