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

NamingSystem Duplicate Guidance

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Terminology Infrastructure
    • STU
    • NamingSystem
    • 4.11.5.3
    • Hide

      Change the existing text:  

      In some cases, the same code or identifier system might accidentally be created more than once in a registry, for example because someone failed to check for an existing entry before adding a new one or knows the same concept with a different name. If this occurs, one of the system entries should be deleted and the remaining entry should have its uniqueId updated to include any identifiers present on the original entry (and possibly have its descriptive information modified to include additional information from the duplicate entry).

      To this:

      In some cases, the same code or identifier system might accidentally be created more than once in a registry, for example because someone failed to check for an existing entry before adding a new one or if they didn't recognize that their addition replicates another. If this occurs, the system publisher should be contacted for guidance.  

      Show
      Change the existing text:   In some cases, the same code or identifier system might accidentally be created more than once in a registry, for example because someone failed to check for an existing entry before adding a new one or  knows the same concept with a different name.  If this occurs,  one of the system entries should be deleted and the remaining entry should have its  uniqueId  updated to include any identifiers present on the original entry  (and possibly have its descriptive information modified to include additional information from the duplicate entry). To this: In some cases, the same code or identifier system might accidentally be created more than once in a registry, for example because someone failed to check for an existing entry before adding a new one or  if they didn't recognize that their addition replicates another. If this occurs, the system publisher should be contacted for guidance.  
    • Peter Jordan/Rob Hausam: 2-0-0
    • Correction
    • Non-substantive
    • R5

    Description

      The existing text:  

      In some cases, the same code or identifier system might accidentally be created more than once in a registry, for example because someone failed to check for an existing entry before adding a new one or knows the same concept with a different name. If this occurs, one of the system entries should be deleted and the remaining entry should have its uniqueId updated to include any identifiers present on the original entry (and possibly have its descriptive information modified to include additional information from the duplicate entry).

       

      Is most likely outdated. Shouldn't the NamingSystem  that is the loser be retired or deprecated?  

      1st sentence has some awkward text that could be changed.

      In some cases, the same code or identifier system might accidentally be created more than once in a registry, for example because someone failed to check for an existing entry before adding a new one or if they didn't recognize that their addition is the same as another because the name is different. 

      I

      Attachments

        Activity

          People

            Unassigned Unassigned
            carmela_couderc Carmela A. Couderc
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: