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

Allow $lookup to query CodeSystem supplement content

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Terminology Infrastructure
    • CodeSystem
    • Hide

      For CodeSystem/$lookup we will:

      1. add a new parameter for explicitly mentioning additional supplements to use
        1. 'useSupplement' canonical 0..*
        2. referenced supplements must be for the same CodeSystem
      2. by default, supplements for the code system are not automatically included except where they provide additional designations that may be indicated by, for example, the displayLanguage parameter
      3. in the $lookup output, return the url of the supplement that the parameter value was sourced from as:
        1. 'property.source' canonical 0..1
        2. 'property.subproperty.source' canonical 0..1

       

      Show
      For  CodeSystem/$lookup  we will: add a new parameter for explicitly mentioning additional supplements to use 'useSupplement' canonical 0..* referenced supplements must be for the same CodeSystem by default, supplements for the code system are not automatically included except where they provide additional designations that may be indicated by, for example, the displayLanguage parameter in the $lookup output, return the url of the supplement that the parameter value was sourced from as: 'property.source' canonical 0..1 'property.subproperty.source' canonical 0..1  
    • Michael Lawley/Reuben Daniels: 5-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      For CodeSystem/$lookup we either need to

      1. add an extra parameter for explicitly mentioning additional supplements to use,
      2. automatically include all known (to the server) supplements for the code system, or
      3. relax the restriction on the supplement's URI being used as the system parameter.

      These are not (all) mutually exclusive options.

      In any case, it would be very useful to have a sanctioned, consistent, and clear mechanism for including supplement-sourced properties in the $lookup result so that the client can determine the provenance of the additional values. This should probably also work for supplemented designations.

      See related Zulip thread https://chat.fhir.org/#narrow/stream/179202-terminology/topic/CodeSystem.20Supplements.20with.20SNOMED

       

      Attachments

        Activity

          People

            abdullah.rafiqi Abdullah Rafiqi
            mjlawley Michael Lawley
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: