The Da Vinci Notifications Bundle Profile constrains the FHIR Bundle resource to the Da Vinci notification messaging framework.

The Da Vinci Notifications MessageHeader Profile sets minimum expectations for the FHIR MessageHeader resource to record the necessary context for Da Vinci notification messaging using FHIR resources. It references the focus of the use case event or request as well as other information related to the action typically transmitted in a Bundle resource in which the MessageHeader resource instance is the first resource in the Bundle.

The Da Vinci Admit Notification MessageHeader Profile builds on the Da Vinci Notifications MessageHeader Profile and sets minimum expectations for the FHIR MessageHeader resource to record the necessary context for Da Vinci admit notification messaging scenario. The event code is "notification-admit" and the focus of the event is the Encounter.

The Da Vinci Admit/Discharge/Transfer Notification Condition Profile is based on the US Core Condition Encounter Diagnosis Profile and and complies with US Core versions 3.1.1, 6.1.0, and 7.0.0. It adds the mandatory Condition.encounter element which references the Da Vinci Admit/Discharge/Transfer Notification Encounter Profile in the same message Bundle.

The Da Vinci Admit/Discharge/Transfer Notification Coverage Profile is based on the HRex Coverage Profile and constrains the Patient resource referenced by the Coverage.beneficiary element to be found in the same message Bundle. The Da Vinci Admit/Discharge/Transfer Notification Coverage Profile is based on the US Core Coverage Profile and complies with US Core versions 6.1.0, and 7.0.0. It constrains the resources referenced by the Coverage.beneficiary element to the US Core Patient Profile. It also constrains the referenced resource to be an entry in the message Bundle that it populates.

The Da Vinci Admit/Discharge/Transfer Notification Encounter Profile is based on the US Core Encounter Profile and complies with US Core versions 3.1.1, 6.1.0, and 7.0.0. It constrains the resources referenced by the Encounter.Subject to the US Core Patient Profile ,Encounter.participant.individual to the US Core Practitioner Profile and Encounter.Location to the US Core Location Profile. It also constrains these referenced resources to be entries in the message Bundle that it populates.

The Da Vinci Discharge Notification MessageHeader Profile builds on the Da Vinci Notifications MessageHeader Profile and sets minimum expectations for the FHIR MessageHeader resource to record the necessary context for Da Vinci discharge notification messaging scenario. The event code is "notification-discharge" and the focus of the event is the Encounter.

The Da Vinci Transfer Notification MessageHeader Profile builds on the Da Vinci Notifications MessageHeader Profile and sets minimum expectations for the FHIR MessageHeader resource to record the necessary context for Da Vinci transfer notification messaging scenario. The event code is "notification-transfer" and the focus of the event is the Encounter.

Concepts describing Da Vinci Unsolicited Admit Notification notification events.

Concepts describing Da Vinci Unsolicited Notification discharge notification events.

Concepts describing the purpose of the Da Vinci Unsolicited Notification.

Concepts describing Da Vinci Unsolicited Notification transfer notification events.

Concepts describing the purpose of the Da Vinci Unsolicited Notification. Note these concepts are 'pre-coordinated' to represent the concept of notification message AND the event that triggers the notification.

Admit Notification Intermediate Translate Bundle example

Admit Notification Intermediate Transmit Bundle example

Admit Notification Message Bundle example

This Admit Notification Message Bundle example illustrates referencing a Device for the author and sender in the MessageHeader.

Discharge Notification Message Bundle example

Transfer Notification Message Bundle example

This CapabilityStatement describes the expected capabilities of a Da Vinci Intermediary when forwarding Unsolicited Notifications transacted with the $process-message in the client mode.

This CapabilityStatement describes the expected capabilities of a server that is capable of receiving a Da Vinci Unsolicited Notification transacted with the $process-message operation.

This CapabilityStatement describes the expected capabilities of a Da Vinci Sender when sending Unsolicited Notifications transacted with the $process-message in the client mode.

Since May 1, 2021 CMS requires that hospitals send notifications electronically for admit, transfer and discharge events to the patient's care team members, for which most implementations currently use V2 ADT messages. As a result DirectTrust, a consensus body of forty organizations and individuals representing the care continuum, collaborated in creating an Implementation Guide using Direct Secure Messaging for both senders and receivers. The Event Notifications via the Direct Standard® defines the necessary data element to cover the CMS rules, maps those to the V2 elements in several ADT message structures and provides the value sets for coded elements.

These V2 elements have been mapped them to their respective location in this DaVinci FHIR IG for the Admit-Transfer-Discharge Use case. In addition, the value set concepts between the two product families have been mapped, where possible.

This ConceptMap summarizes the Direct ADT message to the Da Vinci Notification Terminology Mappings. Complete mappings can be downloaded as an excel file at https://hl7.org/fhir/us/davinci-alerts/tables/DirectToDaVinciMap.xlsx.