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

Questionnaire.item.answerOption has inconsistencies regarding Questionnaire.item.type and answerOption.value[x]

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • Questionnaire
    • Hide

      The list of types in the que-5 invariant and the list of types on the answerOption element should be the same.  Will expand both lists to cover the same set of types + uri (i.e. same as initial.value[x] excluding boolean and Attachment).  We will limit the que-5 invariant to answerOption.

      We will define a new invariant similar to que-5 for answerValueSet that limits its use to items of type Coding, string and uri (the set of the 'option' data types normally allowed to be bound to a ValueSet).

      Will add a comment to answerValueSet that says: "For items of type Coding, the value set indicates the allowed code+system matches.  For items of type 'string', the display values in the value set expansion are taken as the allowed values for the item. "

      We will make explicit via another new invariant that the data type of the answerOption.value[x] must match that of the item.type (if options are present).

       

      Show
      The list of types in the que-5 invariant and the list of types on the answerOption element should be the same.  Will expand both lists to cover the same set of types + uri (i.e. same as initial.value [x] excluding boolean and Attachment).  We will limit the que-5 invariant to answerOption. We will define a new invariant similar to que-5 for answerValueSet that limits its use to items of type Coding, string and uri (the set of the 'option' data types normally allowed to be bound to a ValueSet). Will add a comment to answerValueSet that says: "For items of type Coding, the value set indicates the allowed code+system matches.  For items of type 'string', the display values in the value set expansion are taken as the allowed values for the item. " We will make explicit via another new invariant that the data type of the answerOption.value [x] must match that of the item.type (if options are present).  
    • Brian Postlethwaite/Ye Wang: 4-0-0
    • Correction
    • Non-substantive

    Description

      Questionnaire.item.answerOption is currently (after rule que-5) allowed for 8 item-types, but answerOption.value[x] only defines 6 value-choices.

      Missing, corresponding to the 8 item-types, are:
      valueDecimal, valueDateTime, valueQuantity.

      Additionaly answerOption.value[x] allows valueReference, while item.type reference is not allowed to have answerOption/answerValueSet (according to rule que-5).

      Finally there are no restrictions documented for which value-choice should be used for a specific item.type. Meaning at the moment an item with type integer is allowed to have answerOption with valueDate, valueQuantity, ... . An explicit rule expecting type and value to match could speed up understanding the intention of answerOption in R5.

      Attachments

        Activity

          People

            Unassigned Unassigned
            patricksteiger Patrick Steiger
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: