CodeSystem$lookup OperationDefinition.parameter.property.value type mismatch

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • OperationDefinition
    • Hide

      This is an issue with the publication tooling not propagating what's in the spreadsheet defining the operation into the parameters of the formal operation definition.

      Auto-approved. FHIR-I thinks this should be fixed for R4.

      UPDATED RESOLUTION:

      In R4, update define an extension on OperationDefinition.parameter for subtypes of an abstract type, and update the $lookup operation to use this extension.

      In R5, add a OperationDefinition.parameter.subtype property to enable this without extensions, and update the docs to indicate that .type can be used to specify an abstract type, with .subtype defining which concrete types are allowed. In the absence of a .subtype value, any concrete subtype of the .type value can be used.

      Show
      This is an issue with the publication tooling not propagating what's in the spreadsheet defining the operation into the parameters of the formal operation definition. Auto-approved. FHIR-I thinks this should be fixed for R4. UPDATED RESOLUTION: In R4, update define an extension on OperationDefinition.parameter for subtypes of an abstract type, and update the $lookup operation to use this extension. In R5, add a OperationDefinition.parameter.subtype property to enable this without extensions, and update the docs to indicate that .type can be used to specify an abstract type, with .subtype defining which concrete types are allowed. In the absence of a .subtype value, any concrete subtype of the .type value can be used.
    • Grahame Grieve / Rob Hausam: 6-0-0
    • Correction
    • Non-substantive

      The FHIR docs for CodeSystem$lookup define the property.value (and property.subproperty.value) field as a type-choice (code | Coding | string | integer | boolean | dateTime | decimal). However, when you look at the formal JSON definition, it's defined as code.

            Assignee:
            Unassigned
            Reporter:
            zrsmith92
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: