Da Vinci Unsolicited Notifications
1.1.0-preview - STU 1.1 Preview United States of America flag

Da Vinci Unsolicited Notifications, published by HL7 International / Infrastructure And Messaging. This guide is not an authorized publication; it is the continuous build for version 1.1.0-preview built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-alerts/ and changes regularly. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Base Da Vinci Notification Profiles

These define the base constraints on FHIR resources for systems conforming to this implementation guide. Other Da Vinci Notification Profiles are based on them.

Da Vinci Notifications Bundle Profile

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

Da Vinci Notifications MessageHeader Profile

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.

Da Vinci Admission/Discharge/Transfer Notification Profiles

Operations associated with CDex admission/discharge/transfer notifications

Da Vinci Admit Notification MessageHeader Profile

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.

Da Vinci Admit/Discharge/Transfer Notification Condition Profile

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.

Da Vinci Admit/Discharge/Transfer Notification Coverage Profile

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.

Da Vinci Admit/Discharge/Transfer Notification Encounter Profile

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.

Da Vinci Discharge Notification MessageHeader Profile

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.

Da Vinci Transfer Notification MessageHeader Profile

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.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Da Vinci Notification Admit Event ValueSet

Concepts describing Da Vinci Unsolicited Admit Notification notification events.

Da Vinci Notification Discharge Event ValueSet

Concepts describing Da Vinci Unsolicited Notification discharge notification events.

Da Vinci Notification Event ValueSet

Concepts describing the purpose of the Da Vinci Unsolicited Notification.

Da Vinci Notification Transfer Event ValueSet

Concepts describing Da Vinci Unsolicited Notification transfer notification events.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide. The code systems defined here are not part of the base FHIR specification and future versions of this guide will migrate them to VSAC or another standard centralized US Realm terminology authority.

Da Vinci Event CodeSystem Notification

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.

Bundle Examples

These are Bundle example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Admit Notification Intermediate Translate Bundle

Admit Notification Intermediate Translate Bundle example

Admit Notification Intermediate Transmit Bundle

Admit Notification Intermediate Transmit Bundle example

Admit Notification Message Bundle 01

Admit Notification Message Bundle example

Admit Notification Message Bundle 02

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

Discharge Notification Message Bundle

Discharge Notification Message Bundle example

Transfer Notification Message Bundle

Transfer Notification Message Bundle example

CapabilityStatements

There are 3 Capability Statements defining computable definitions of FHIR conformance expectations of the RESTful transactions and specific profiles for each of the Da Vinci Notification Roles. They provide the base conformance rules that may be used for system compatibility testing, code generation, or as the basis for a conformance assessment.

The following table summarizes how these CapabilityStatements applies to the Da Vinci Notification Roles

Role server-mode client-mode
Sender - Da Vinci Notification Sender
Intermediary Da Vinci Notification Receiver Da Vinci Notification Forwarder
Recipient Da Vinci Notification Receiver -
Notification Forwarder CapabilityStatement

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

Notification Receiver CapabilityStatement

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.

Notification Sender CapabilityStatement

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

Terminology: Concept Maps

These define transformations to convert between codes by systems conforming with this implementation guide.

Direct ADT to Da Vinci Alerts ConceptMap

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.