Clarify usage of lookupQuestionnaire

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium High
    • Structured Data Capture (SDC) (FHIR)
    • current
    • FHIR Infrastructure
    • (NA)
    • 12.45.1
    • Hide

      The text should be changed from "(if the Reference is to a Questionnaire)" to "(if the Reference is to a QuestionnaireResponse)".

      Will also add some examples of how this might be used - e.g. being able to fill in a blood pressure with an Observation-linked Questionnaire or filling in a FamilyMemberHistory using FHIRPath approach

      Show
      The text should be changed from "(if the Reference is to a Questionnaire)" to "(if the Reference is to a QuestionnaireResponse)". Will also add some examples of how this might be used - e.g. being able to fill in a blood pressure with an Observation-linked Questionnaire or filling in a FamilyMemberHistory using FHIRPath approach
    • Paul Lynch/Don Langlois: 6-0-0
    • Correction
    • Non-substantive

      The current description says:
      "For items of type reference, the reference can be populated either by picking an existing entity or by creating a new one. In the latter case, this Questionnaire allows specifying the Questionnaire to use in creating the target instance.This can be direct (if the Reference is to a Questionnaire) or indirect via mapping if the Reference is to some other sort of resource."

      The "direct" case (where the Reference is of type Questionnaire) needs clarification, or perhaps removal. It seems to me that if the question's answer is a reference to a Questionnaire, and the user is responding by creating a new Questionnaire (using the lookupQuestionnaire to do it), you would still need the mapping just as you would for any other resource type.

            Assignee:
            joeegarcia
            Reporter:
            Paul Lynch
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: