Da Vinci Unsolicited Notifications Implementation Guide CI Build

Da Vinci Unsolicited Notifications, published by HL7 International - Infrastructure and Messaging Work Group. This is not an authorized publication; it is the continuous build for version 0.2.1). This version is based on the current content of https://github.com/HL7/davinci-alerts/ and changes regularly. See the Directory of published versions

Change notes

The Da Vinci Unsolicited Notifications Implementation Guide was developed under the Davinci Project

Changes and Updates for version 0.2.0

  1. This Implementation Guide was originally named Da Vinci Alerts Implementation Guide - after review by several HL7 workgroups, it was felt that the term “alerts” has a specific meaning to many people that was not the same as the contents of this guide. Therefore the title of this IG has been changed to Da Vinci Unsolicited Notifications Implementation Guide. Be aware that there are several technical artifacts such as the canonical base, the npm package name and the history page url that cannot be changed and still retain the word “alerts” in their paths.
  2. Implemented FHIR Messaging paradigm instead of using a custom operation to transact notifications.
    1. Replaced the Da Vinci Alert Bundle Profile with a message bundle, the Da Vinci Notifications Bundle.
    2. Replaced the $notify custom operation with the FHIR $process-message operation to transact the Da Vinci Notifications Bundle directly to Recipients and Intermediaries.
    3. Replaced existing Profiles with Profiles, MessagedDefinitions and GraphDefinition to support FHIR messaging and the Admit/Discharge use case.
    4. Replaced existing examples to support FHIR messaging and the Admit/Discharge use case.
    5. Replaced existing CapabilityStatements to support FHIR messaging and the Admit/Discharge use case.
    6. Various changes and updates to the documentation and figures to provide specific guidance for using FHIR messaging and implementation of the Admit/Discharge use case.

Changes and Updates for version 0.1.0

  • DEPRECATED: Note that this version (0.1.0) should not be used, it was pulled from the ballot after publication and has been replaced by version 0.2.0.