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

Questionnaire.item.type cannot be deferred to item.definition

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      R4
    • Work Group:
      FHIR Infrastructure
    • Related Artifact(s):
      Questionnaire
      StructureDefinition
    • Related Page(s):
      ElementDefinition
    • Related Section(s):
      2.37.5.5, 2.37.8
    • Grouping:
    • Resolution Description:
      Hide

      We will add item.text  as mapping to ElementDefinition.label

      We will note that extensions that allow a context of both Questionnaire.item and ElementDefinition should propagate.

      We will remove item.type as something that can be automatically populated, but will note the correspondence and indicate that the mappings should align - and note that the target profiles for Reference or canonical should propagate to the appropriate Questionnaire.item extension.

      We will add language warning about the use of definition in that client systems won't necessarily recognize/process the definition and thus may not render or capture data against the questionnaire correctly.  We will also define a new optional 0..1 extension on Questionnaire and mark it as 'mustSupport' in our base SDC profile that indicates that the Questionnaire relies on definitions to populate some of its item properties (and thus that clients that can't retrieve the definitions can't safely handle the Questionnaire).

      Show
      We will add item.text  as mapping to ElementDefinition.label We will note that extensions that allow a context of both Questionnaire.item and ElementDefinition should propagate. We will remove item.type as something that can be automatically populated, but will note the correspondence and indicate that the mappings should align - and note that the target profiles for Reference or canonical should propagate to the appropriate Questionnaire.item extension. We will add language warning about the use of definition in that client systems won't necessarily recognize/process the definition and thus may not render or capture data against the questionnaire correctly.  We will also define a new optional 0..1 extension on Questionnaire and mark it as 'mustSupport' in our base SDC profile that indicates that the Questionnaire relies on definitions to populate some of its item properties (and thus that clients that can't retrieve the definitions can't safely handle the Questionnaire).
    • Resolution Vote:
      Grahame Grieve/Paul Lynch: 9-0-0
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive

      Description

      The definition of Questionnaire.item.definition (and similar explanatory text for Questionnaire) indicates that if the definition "is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value: ... type (ElementDefinition.type)."

      However, Questionnaire.item.type has cardinality 1..1, so it can't have no value.

      Remove Questionnaire.item.type from the list of derived attributes.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lloyd Lloyd McKenzie
              Reporter:
              esilver Elliot Silver
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: