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

Alignment and completeness of NamingSystems/terminology pages/OID Registry

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Medium Medium

    Description

      For any FHIR implementer, the terminology-systems pages that list the System URIs and connections to OID where applicable. Secondly there is a Bundle of NamingSystems that helps you prevent screen scraping that information from HTML. (E.g. http://hl7.org/fhir/R4/namingsystem-terminologies.xml and http://hl7.org/fhir/R4/namingsystem-registry.xml)

      The relationship between the NamingSystems and the terminology pages is unclear. Things are missing from the NamingSystems that could have been in there, see GF#20329 for example. This ticket focuses on information missing from both sources:

      The connection between the V3/V2 OIDs and the FHIR URIs. The columns in the terminology pages are empty and the information is missing from the NamingSystems. It is virtually impossible to connect the dots based on what's in the OID Registry.

      My request:

      • Make sure that for every system (code or identifier), that the source-of-truth in FHIR is the NamingSystem bundle
      • Make sure that every FHIR NamingSystem uses the HL7 OID Registry as source-of-truth for OIDs
      • Make sure that the terminology-pages are generated from the NamingSystems so there can be no difference between them
      • Make sure all V2/V3 value set pages also list the relevant OIDs, instead of ??. Using the same NamingSysterms as source this seems doable.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ahenket Alexander Henket
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: