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

CapabilityStatement: Notification Receiver CapabilityStatement

Official URL: http://hl7.org/fhir/us/davinci-alerts/CapabilityStatement/notification-receiver Version: 1.1.0-preview
Standards status: Trial-use Maturity Level: 2 Computable Name: NotificationReceiverCapabilityStatement
Other Identifiers: OID:2.16.840.1.113883.4.642.40.47.13.2

Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License

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.

Raw OpenAPI-Swagger Definition file | Download

SHOULD Support the Following Implementation Guides:

SHOULD Implement All Or Parts Of The Following Capability Statements:

FHIR RESTful Capabilities

Da Vinci Notifications Receiver SHALL:

  1. Support the notification framework defined in this Guide.
  2. Implement the RESTful behavior according to the FHIR specification.
  3. Support json source formats for all Da Vinci Notification interactions.
  4. Declare a CapabilityStatement identifying the scenarios, transactions and profiles supported.

Da Vinci Notifications Receiver SHOULD:

  1. Support the admission/discharge use case defined in this Guide.
  2. Support xml source formats for all Da Vinci Notification interactions.
  3. Identify the Da Vinci Notification or US Core profiles supported as part of the FHIR meta.profile attribute for each instance.

Security:

  1. For general security consideration refer to the Security and Privacy Considerations.
  2. For security considerations specific to this guide refer to the Security page for requirements and recommendations.
  3. A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.

Summary of System Wide Operations

  • SHALL support the $process-message operation.

    • The Recipient or Intermediary SHALL process the $process-message operation.