XMLWordPrintableJSON

Details

    • Icon: Comment Comment
    • Resolution: Considered - No action required
    • Icon: Highest Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • (many)
    • 2.1.4
    • Hide

      The current approach is a compromise between between sending everything and sending a minimal message. (e.g., just the Encounter ) in which all Receivers would need to query back for more information. Will continue with this approach and review feedback from implementers on whether more or less data is needed for the use case.

      Also based on Da Vinci Guidelines Document: (see attached) "The requester should limit the request for information to that required to address the specific, stated purpose" . Therefore providing the minimum necessary to: provide enough information to understand what the notification is about and to enable the Recipient to determine if and what additional steps they need to take in response to the notification.

      Show
      The current approach is a compromise between between sending everything and sending a minimal message. (e.g., just the Encounter ) in which all Receivers would need to query back for more information. Will continue with this approach and review feedback from implementers on whether more or less data is needed for the use case. Also based on Da Vinci Guidelines Document: (see attached) "The requester should limit the request for information to that required to address the specific, stated purpose" . Therefore providing the minimum necessary to: provide enough information to understand what the notification is about and to enable the Recipient to determine if and what additional steps they need to take in response to the notification.

    Description

      Per comment on 2.1.3-the bundle should, to the degree possible, contain actionable information and not require the user to track down additional information to respond-i.e should be self sufficient

      Existing Wording:

      There is no expectation that the data submitted represents all the data required by the Notification Recipient/Intermediary, only that the data is known to be relevant to the triggering event. The Notification Recipient/Intermediary can optionally fetch additional information from the patient’s medical record using FHIR RESTful searches. The endpoint for this search may be known or supplied via the $process-message operation payload.

      Attachments

        Activity

          People

            Unassigned Unassigned
            klsalzman Keith Salzman
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: