2015May sdc #127 - Why is options a reference rather than a list of embedded content

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • Questionnaire
    • 4.26.8
    • Hide

      ValueSet is used in many places, not just Questionnaire. Because there are use-cases for it to be independent, it must be defined to allow independence. The alternative would be to have Questionnaire support both inline codes and a ValueSet reference which would impose even more complexity on systems.

      We will add guidance about how to use ValueSet as a contained resource

      Show
      ValueSet is used in many places, not just Questionnaire. Because there are use-cases for it to be independent, it must be defined to allow independence. The alternative would be to have Questionnaire support both inline codes and a ValueSet reference which would impose even more complexity on systems. We will add guidance about how to use ValueSet as a contained resource
    • Russell/Laura: 6-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: Questionnaire

      Comment:

      options is only a reference; why is this not embedded, or with a structure with an optional reference to an external value set? It appears that the 80% (more like 95%) case for forms are localy defined lists of <choice> items, not a <choice> type linking to a external valueset. Why is this not an embedded QuestionnaireAnsers resource?

            Assignee:
            Unassigned
            Reporter:
            Ted Klein
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: