This page is part of the Da Vinci Unsolicited Notifications (v1.0.0: STU1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions
CapabilityStatement: Notification Receiver CapabilityStatement
Raw OpenAPI-Swagger Definition file | Download
Notification Receiver CapabilityStatement
- Implementation Guide Version: 1.0.0
- FHIR Version: 4.0.1
- Supported formats: xml, json
- Published: 2020-09-14
- Published by: HL7 International - Infrastructure 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:
- Support the notification framework defined in this Guide.
- Implement the RESTful behavior according to the FHIR specification.
- Support json source formats for all Da Vinci Notification interactions.
- Declare a CapabilityStatement identifying the scenarios, transactions and profiles supported.
Da Vinci Notifications Receiver SHOULD:
- Support the admission/discharge use case defined in this Guide.
- Support xml source formats for all Da Vinci Notification interactions.
- Identify the Da Vinci Notification or US Core profiles supported as part of the FHIR
meta.profile
attribute for each instance.
Security:
- For general security consideration refer to the Security and Privacy Considerations.
- For security considerations specific to this guide refer to the Security page for requirements and recommendations.
- 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.