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

Add examples and conformance statements to card launch of DTR App

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • 1.0.0 [deprecated]
    • Financial Mgmt
    • Supported Hooks
    • 4.3.4.2.7
    • Hide

      In the section where we deal with "recommend launching DTR" we will indicate that this might mean launching a SMART app or launching equivalent internal EHR functionality.

      Because we're no longer using a SMART cards to pass back a request for DTR, there's no longer anything special about CRD-specific SMART launch.  No SMART app URL comes back and no context comes back other than the extension added to the order as part of the system action.  (There's already an example of the extension in the spec.)  DTR launch will now always be stand-alone, passing in either the context of an order, an existing QuestionnaireResponse, or (for CDex) a Task.  There will be examples of these different types of launches in the DTR spec.  (Will review whether these are clearly called out in DTR and, if not, will raise a DTR change request to ensure this occurs.)

      NOTE: we'll need to remove the changes pre-applied for the previous resolution.

      Show
      In the section where we deal with "recommend launching DTR" we will indicate that this might mean launching a SMART app or launching equivalent internal EHR functionality. Because we're no longer using a SMART cards to pass back a request for DTR, there's no longer anything special about CRD-specific SMART launch.  No SMART app URL comes back and no context comes back other than the extension added to the order as part of the system action.  (There's already an example of the extension in the spec.)  DTR launch will now  always  be stand-alone, passing in either the context of an order, an existing QuestionnaireResponse, or (for CDex) a Task.  There will be examples of these different types of launches in the DTR spec.  (Will review whether these are clearly called out in DTR and, if not, will raise a DTR change request to ensure this occurs.) NOTE: we'll need to remove the changes pre-applied for the previous resolution.
    • Bob Dieterle/Jeff Brown: 7-0-1
    • Enhancement
    • Non-compatible
    • 1.1.0-ballot [deprecated]

    Description

      1) clarify that launch of DTR may include "launching" a native EHR application as well as a SMART application

      2) Create examples and conformance language to support the following scenarios

      a) launch native application and pass context

      b) launch provider selected SMART application and pass context (EHR may support more than one SMART application for DTR)

      c) launch payer (responding CDS) specified SMART application and pass context 

      Attachments

        Activity

          People

            Unassigned Unassigned
            rcdieterle Robert Dieterle
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: