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

Clarify how workflow actors are notified - PRO #13

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Patient Reported Outcomes (PRO) (FHIR)
    • STU3
    • FHIR Infrastructure
    • overview [deprecated]
    • 1.3 Abstract Model,
    • Hide

      For this project, How an EHR keeps track of responses and notifies providers, researchers is out-of-scope. This will change from EHR to EHR and from organization to organization.

      Will add a paragraph about subsequent sharing that identifies there are various mechanisms by which downstream consumers can receive the information (subscription, polling, pushing documents/bundles, messaging, etc.) with links to the relevant parts of the core spec.

      Show
      For this project, How an EHR keeps track of responses and notifies providers, researchers is out-of-scope. This will change from EHR to EHR and from organization to organization. Will add a paragraph about subsequent sharing that identifies there are various mechanisms by which downstream consumers can receive the information (subscription, polling, pushing documents/bundles, messaging, etc.) with links to the relevant parts of the core spec.
    • Nagesh Bashyam/Ana Kostadinovska: 12-0-0
    • Enhancement
    • Non-substantive

    Description

      Comment:

      It is not clear from the spec how does the EHR or Care Delivery Health IT System know that there are responses available. It is as well not clear how do reasearchers, care teams, providers know that there are responses available. Please specify

      Summary:

      Clarify how workflow actors are notified

      Attachments

        Activity

          People

            Unassigned Unassigned
            ana_kostadinovska Ana Kostadinovska
            Ana Kostadinovska
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: