Da Vinci Clinical Data Exchange (CDex)
2.1.0-preview - CI Build United States of America flag

Da Vinci Clinical Data Exchange (CDex), published by HL7 International / Payer/Provider Information Exchange Work Group. This guide is not an authorized publication; it is the continuous build for version 2.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-ecdx/ and changes regularly. See the Directory of published versions

CapabilityStatement: cdex-capabilitystatement-inline-example

Official URL: http://hl7.org/fhir/us/davinci-cdex/CapabilityStatement/cdex-capabilitystatement-inline-example Version: 2.1.0-preview
Standards status: Informative Computable Name:
Other Identifiers: OID:2.16.840.1.113883.4.642.40.21.13.1

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

R4 example of a CapabilityStatement advertising support for CDex Task Update topic-based subscription

Raw OpenAPI-Swagger Definition file | Download

  • Implementation Guide Version: 2.1.0-preview
  • FHIR Version: 4.0.1
  • Intended Use: requirements
  • Supported Formats: json;
  • Published: 2024-05-16
  • Published by: HL7 International / Payer/Provider Information Exchange Work Group
  • Status: active
  • Copyright:

    Used by permission of HL7 International all rights reserved Creative Commons License


Description:

R4 example of a CapabilityStatement advertising support for CDex Task Update topic-based subscription


Support and Requirements for Other Artifacts

Instantiates other capabilities: Supports other guides:

Jump to:


FHIR server RESTful Capabilities

System-wide server Capabilities

Summary of Resource/Profile Capabilities

Resource Type Supported Interactions Supported Profiles Supported Searches Supported _includes Supported _revincludes Supported Operations
Subscription read, create, update, delete, R4/B Topic-Based Subscription, url, status, $status $events $get-ws-binding-token
Patient read, create, update, delete,
Encounter read, create, update, delete,
Observation read, create, update, delete,

RESTful server Capabilities by Resource/Profile:

Subscription

Conformance Expectation:

Supported Profiles:

Subscription Interaction Summary:

  • read, create, update, delete,

Modify Criteria:

  • A server (conformance expectation undefined) be capable of a create interaction creating a Subscription resource using: POST [base]/Subscription/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of updating a existing Subscription resource using: PUT [base]/Subscription/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of deleting a Subscription resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A server (conformance expectation undefined) be capable of a read interaction returning a Subscription resource using: GET [base]/Subscription/[id]

Search Parameter Summary:

Conformance Parameter Type Example
(conformance expectation undefined) url uri GET [base]/Subscription?url=[uri]
(conformance expectation undefined) status token GET [base]/Subscription?status=[system]|[code]

Patient

Conformance Expectation:


Modify Criteria:

  • A server (conformance expectation undefined) be capable of a create interaction creating a Patient resource using: POST [base]/Patient/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of updating a existing Patient resource using: PUT [base]/Patient/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of deleting a Patient resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A server (conformance expectation undefined) be capable of a read interaction returning a Patient resource using: GET [base]/Patient/[id]

Encounter

Conformance Expectation:


Modify Criteria:

  • A server (conformance expectation undefined) be capable of a create interaction creating a Encounter resource using: POST [base]/Encounter/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of updating a existing Encounter resource using: PUT [base]/Encounter/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of deleting a Encounter resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A server (conformance expectation undefined) be capable of a read interaction returning a Encounter resource using: GET [base]/Encounter/[id]

Observation

Conformance Expectation:


Modify Criteria:

  • A server (conformance expectation undefined) be capable of a create interaction creating a Observation resource using: POST [base]/Observation/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of updating a existing Observation resource using: PUT [base]/Observation/[id]{?_format=[mime-type]}
  • A server (conformance expectation undefined) be capable of deleting a Observation resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A server (conformance expectation undefined) be capable of a read interaction returning a Observation resource using: GET [base]/Observation/[id]