Support FHIR-based ordering - DTR #40

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci DTR (FHIR)
    • STU3
    • Clinical Decision Support
    • (profiles) [deprecated]
    • Task Creation
    • Hide

      The objective here is to create a "todo" item for the clinician or their staff. The intention is not to create the full order at this point in the workflow - as that would mean a disruption to the current workflow. It is true that a DiagnosticRequest, MedicationRequest or other resource will be needed eventually. However, the DTR system will generally not have enough information to create this and the screens in use at this point in the workflow would not necessarily be conducive to authoring the other type(s) of orders required.

      In a sufficiently capable EHR may be ablt to implement the ability to order within the workflow rather than create a task.

      For SOF app we recognize the importance of simplifying practitioner workflow and that automatically creating orders (or allowing practitioners to complete orders) in context can be a means of doing this. The project will revisit allowing direct creation of certain types of orders in future versions of DTR once we have more experience and a better idea of what scenarios this will work well in.

      Show
      The objective here is to create a "todo" item for the clinician or their staff. The intention is not to create the full order at this point in the workflow - as that would mean a disruption to the current workflow. It is true that a DiagnosticRequest, MedicationRequest or other resource will be needed eventually. However, the DTR system will generally not have enough information to create this and the screens in use at this point in the workflow would not necessarily be conducive to authoring the other type(s) of orders required. In a sufficiently capable EHR may be ablt to implement the ability to order within the workflow rather than create a task. For SOF app we recognize the importance of simplifying practitioner workflow and that automatically creating orders (or allowing practitioners to complete orders) in context can be a means of doing this. The project will revisit allowing direct creation of certain types of orders in future versions of DTR once we have more experience and a better idea of what scenarios this will work well in.
    • Bob Dieterle / Rachael Foerster: 8-0-0

      Existing Wording: To facilitate this, the DTR application should allow users to create tasks. The details of the task should be represented by a FHIR Task resource. The DTR application should communicate the task information to the EHR system using the FHIR create interaction.

      Comment:

      I don't think it's the right approach to say – anything that needs to be done should be done via Tasks. E.g., for the example given, the sleep study, or more likely the referral to sleep medicine, should just be ordered by the provider via a ServiceRequest. So what's needed here is support for ServiceRequest, MedicationRequest, and other FHIR-based ordering mechanisms by EHR systems. Tasks could also be used, but in conjunction with such orders, not as a replacement.

      Summary:

      Support FHIR-based ordering

            Assignee:
            Unassigned
            Reporter:
            Kensaku Kawamoto
            Kensaku Kawamoto
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: