Da Vinci Unsolicited Notifications Implementation Guide (Release 0.2.0 STU1 Ballot)

This page is part of the Da Vinci Unsolicited Notifications (v0.2.0: STU 1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

Downloads: CapabilityStatement: (XML, JSON),OpenAPI-Swagger Definition file

Notification Receiver CapabilityStatement

  • Implementation Guide Version: 0.1.0
  • FHIR Version: 4.0.0
  • Supported formats: xml, json
  • Published: 2019-11-15
  • Published by: HL7 International - Infrascture and Messaging Work Group

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.

FHIR RESTful Capabilities

Da Vinci Notifications Receiver SHALL:

  1. Support at least one use case defined in this Guide and listed in the Scenarios Section.
  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 xml source formats for all Da Vinci Notification interactions.
  2. 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.