Guidance needed for other launchContext "type"s

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Structured Data Capture (SDC) (FHIR)
    • STU3
    • FHIR Infrastructure
    • (profiles) [deprecated]
    • 12.34.1
    • Hide

      Change binding to be required. Raise new tooling tracker item because 'example' binding shouldn't have been allowed for a 'code' element. Also fix the code system so that 'display' and 'definition' show up in the right place.

      If implementers need new contexts, we can release an updated version of the spec that EHRs and other clients can choose to conform to.

      Show
      Change binding to be required. Raise new tooling tracker item because 'example' binding shouldn't have been allowed for a 'code' element. Also fix the code system so that 'display' and 'definition' show up in the right place. If implementers need new contexts, we can release an updated version of the spec that EHRs and other clients can choose to conform to.
    • Paul Lynch/Nagesh Bashyam: 5-0-0
    • Clarification
    • Non-substantive

      It is not clear what a system is supposed to do with the "type" value from launchContext, if the code that is passed in is not one of the codes listed on the example value set at http://hl7.org/fhir/uv/sdc/2019May/valueset-launchContext.html. Are the off-list codes expected to be resource types? Would it make sense to pass in a code that was not a resource type? The "type" valueCode is just of type "code", so there is no code system, which means anything code-like ("abc") could be passed in.

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

              Created:
              Updated:
              Resolved: