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

Clarify the specific use of NamingSystem

    XMLWordPrintableJSON

Details

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

      A NamingSystem resource manages identifiers of a code system or identifier system, identifier metadata (e.g. type), and limited code system or identifier system specific metadata (e.g. publisher and description). A CodeSystem resource represents a code system, its key properties, and may include the content, identifiers, and other metadata.  

      There is known overlap between the CodeSystem and NamingSystem resource elements. However, the key differences between the resources are as follows:

      • CodeSystem resources may include the concept and property content of the code system, whereas NamingSystem resources do not. CodeSystem resources also allow identifiers to be supplemented by specific metadata. The metadata are supported with extensions. 
      • NamingSystem resources allow the identifiers for code systems or identifier systems to be supplemented by metadata specific to the identifiers. For example: preferred, authoritative, and validity period.
      Show
      A  NamingSystem  resource manages identifiers of a code system or identifier system, identifier metadata (e.g. type), and limited code system or identifier system specific metadata (e.g. publisher and description). A  CodeSystem  resource represents a code system, its key properties, and may include the content, identifiers, and other metadata.   There is known overlap between the CodeSystem and NamingSystem resource elements. However, the key differences between the resources are as follows: CodeSystem resources may include the concept and property content of the code system, whereas NamingSystem resources do not. CodeSystem resources also allow identifiers to be supplemented by specific metadata. The metadata are supported with extensions.  NamingSystem resources allow the identifiers for code systems or identifier systems to be supplemented by metadata specific to the identifiers. For example: preferred, authoritative, and validity period.
    • Reuben Daniels/Rob Hausam: 4-0-1
    • Clarification
    • Non-substantive
    • R5

    Description

      Current text for Boundaries and Relationships section is unclear as to the sspecific use of NamingSystem. In particular it seems to indicate that when a set of concepts or codes is in use but there is no clear or willing authority available, someone can make a NamingSystem instead of a CodeSystem.

      The troublesome sentence is:

      NamingSystem resources, on the other hand, are frequently defined by 3rd parties that encounter the code system in use, and need to describe the use, but do not have the authority to define the features and content.

      Suggest at least change that sentence to be the following if NamingSystem is to be restricted to providing additional identifiers.

      NamingSystem resources, on the other hand, are frequently defined by 3rd parties that encounter the code system in use, and need to describe the use, but do not have the authority to define new identifiers.

      Attachments

        Activity

          People

            marc.duteau Marc Duteau
            Rob_McClure Rob McClure
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: