FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server  |  FHIR Version n/a  User: [n/a]

Resource CapabilityStatement/FHIR Server from package hl7.fhir.us.davinci-cdex#current (172 ms)

Package hl7.fhir.us.davinci-cdex
Type CapabilityStatement
Id Id
FHIR Version R4
Source http://hl7.org/fhir/us/davinci-cdex/https://build.fhir.org/ig/HL7/davinci-ecdx/CapabilityStatement-data-consumer-client.html
Url http://hl7.org/fhir/us/davinci-cdex/CapabilityStatement/data-consumer-client
Version 2.1.0-preview
Status active
Date 2024-05-13T20:40:17.336549-08:00
Name DataConsumerClientCapabilityStatement
Title Data Consumer Client CapabilityStatement
Experimental False
Realm us
Authority hl7
Description This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Consumer in *Client* mode when requesting clinical data from the Data Source during clinical data exchange. The capabilities include one or more of the following interactions: 1. Requesting and Fetching Clinical Data using a FHIR RESTful query 2. Requesting and Fetching Clinical Data using a Task-based query including: - Polling or Subscribing for Task update notifications 3. Requesting Attachments - Requesting Attachments Using Attachments Codes - Requesting Attachments Using Questionnaires
Copyright Used by permission of HL7 International all rights reserved Creative Commons License
Kind requirements

Resources that use this resource

No resources found


Resources that this resource uses

CapabilityStatement
http://hl7.org/fhir/us/core/CapabilityStatement/us-core-client US Core Client CapabilityStatement
http://hl7.org/fhir/us/davinci-hrex/ImplementationGuide/hl7.fhir.us.davinci-hrex Da Vinci Health Record Exchange (HRex)
http://hl7.org/fhir/uv/subscriptions-backport/ImplementationGuide/hl7.fhir.uv.subscriptions-backport Subscriptions R5 Backport
http://hl7.org/fhir/us/davinci-dtr/ImplementationGuide/hl7.fhir.us.davinci-dtr Da Vinci - Documentation Templates and Rules
http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core US Core Implementation Guide
http://hl7.org/fhir/uv/subscriptions-backport/ImplementationGuide/hl7.fhir.uv.subscriptions-backport Subscriptions R5 Backport
http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-patient-demographics CDex Patient Demographics Profile
http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-practitionerrole CDex PractitionerRole Profile
http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-sdc-questionnaireresponse CDex SDC QuestionnaireResponse Profile
http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-signature-bundle CDex Signature Bundle Profile
http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request CDex Task Attachment Request Profile
http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request CDex Task Data Request Profile
http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-questionnaire-adapt DTR Questionnaire for adaptive form
http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-std-questionnaire DTR Standard Questionnaire


Narrative

Note: links and images are rebased to the (stated) source

Data Consumer Client CapabilityStatement

  • Title:Data Consumer Client CapabilityStatement
  • Implementation Guide Version: 2.1.0-preview
  • FHIR Version: 4.0.1
  • Intended Use: Requirements
  • Supported Formats: SHALL support json; MAY support xml;
  • Supported Patch Formats: MAY support application/json-patch+json;
  • Published: 2024-05-13 20:40:17-0800
  • 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:

This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Consumer in Client mode when requesting clinical data from the Data Source during clinical data exchange. The capabilities include one or more of the following interactions:

  1. Requesting and Fetching Clinical Data using a FHIR RESTful query
  2. Requesting and Fetching Clinical Data using a Task-based query including:
    • Polling or Subscribing for Task update notifications
  3. Requesting Attachments
    • Requesting Attachments Using Attachments Codes
    • Requesting Attachments Using Questionnaires

Support and Requirements for Other Artifacts

Instantiates other capabilities: Supports other guides:

Jump to:


FHIR Client RESTful Capabilities

The Da Vinci CDex Data Consumer Client SHALL:

  1. Support at least one of the CDex approaches for exchanging clinical information:
    1. Direct Query
    2. Task-Based Approach
    3. Attachments
  2. Follow the guidelines for Generating and Verifying Signed Resources if signatures are required.
  3. Support JSON source formats for all Da Vinci CDex interactions.
  4. Declare a CapabilityStatement identifying the scenarios, transactions, and profiles supported.

The Da Vinci CDex Data Consumer Client MAY:

  1. Support XML source formats for all Da Vinci CDex interactions.

    Implementers that choose to support XML need to be aware that JSON Web Signatures can only be created and validated in the original native JSON. Transforms to and from XML will invalidate signatures.


Security:

  1. For general security consideration refer to the Security and Privacy Considerations.
  2. For security considerations specific to this guide refer to the Da Vinci HRex Implementation Guide section on Security and Privacy

System-wide Client Capabilities

Interactions

  • MAY support the transaction interaction.
  • MAY support the batch interaction.
  • MAY support the search-system interaction.
  • MAY support the history-system interaction.

Summary of Resource/Profile Capabilities

Resource Type Supported Interactions Supported Profiles Supported Searches Supported _includes Supported _revincludes Supported Operations
Bundle create, search-type, read, vread, update, patch, delete, history-instance, history-type, CDex Signature Bundle Profileversion: {0}2.1.0-preview),
Patient create, search-type, read, vread, update, patch, delete, history-instance, history-type, CDex Patient Demographics Profileversion: {0}2.1.0-preview),
PractitionerRole create, search-type, read, vread, update, patch, delete, history-instance, history-type, CDex PractitionerRole Profileversion: {0}2.1.0-preview),
Provenance create, search-type, read, vread, update, patch, delete, history-instance, history-type,
Questionnaire create, search-type, read, vread, update, patch, delete, history-instance, history-type, DTR Standard Questionnaire, DTR Questionnaire for adaptive form,
QuestionnaireResponse create, search-type, read, vread, update, patch, delete, history-instance, history-type, CDex SDC QuestionnaireResponse Profileversion: {0}2.1.0-preview),
Subscription create, search-type, read, vread, update, patch, delete, history-instance, history-type,
Task create, search-type, read, vread, update, patch, delete, history-instance, history-type, CDex Task Data Request Profileversion: {0}2.1.0-preview), CDex Task Attachment Request Profileversion: {0}2.1.0-preview),

RESTful Client Capabilities by Resource/Profile:

Bundle

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to fetch Clinical Information from data source. SHALL support CDex Signature Bundle Profile for signed Bundles.

Supported Profiles:


Modify Criteria:

  • A Client MAY be capable of a create interaction posting a Bundle resource using: POST [base]/Bundle/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing Bundle resource using: PUT [base]/Bundle/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Bundle resource using: PATCH [base]/Bundle/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Bundle resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHOULD be capable of a search-type interaction fetching Bundle resources matching a search query using: GET [base]/Bundle/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHOULD be capable of a read interaction fetching a Bundle resource using: GET [base]/Bundle/[id]
  • A Client SHOULD be capable of a vread interaction fetching a Bundle resource using: GET [base]/Bundle/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Bundle using: GET [base]/Bundle/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Bundle resources using: GET [base]/Bundle/_history{?[parameters]&_format=[mime-type]}

Patient

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to supply patient demographic data when requesting attachments.

Supported Profiles:


Modify Criteria:

  • A Client MAY be capable of a create interaction posting a Patient resource using: POST [base]/Patient/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing Patient resource using: PUT [base]/Patient/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Patient resource using: PATCH [base]/Patient/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Patient resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client MAY be capable of a search-type interaction fetching Patient resources matching a search query using: GET [base]/Patient/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client MAY be capable of a read interaction fetching a Patient resource using: GET [base]/Patient/[id]
  • A Client MAY be capable of a vread interaction fetching a Patient resource using: GET [base]/Patient/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Patient using: GET [base]/Patient/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Patient resources using: GET [base]/Patient/_history{?[parameters]&_format=[mime-type]}

PractitionerRole

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to supply patient demographic data when requesting attachments.

Supported Profiles:


Modify Criteria:

  • A Client MAY be capable of a create interaction posting a PractitionerRole resource using: POST [base]/PractitionerRole/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing PractitionerRole resource using: PUT [base]/PractitionerRole/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing PractitionerRole resource using: PATCH [base]/PractitionerRole/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a PractitionerRole resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client MAY be capable of a search-type interaction fetching PractitionerRole resources matching a search query using: GET [base]/PractitionerRole/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client MAY be capable of a read interaction fetching a PractitionerRole resource using: GET [base]/PractitionerRole/[id]
  • A Client MAY be capable of a vread interaction fetching a PractitionerRole resource using: GET [base]/PractitionerRole/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a PractitionerRole using: GET [base]/PractitionerRole/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of PractitionerRole resources using: GET [base]/PractitionerRole/_history{?[parameters]&_format=[mime-type]}

Provenance

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to fetch provenance along with clinical information


Modify Criteria:

  • A Client MAY be capable of a create interaction posting a Provenance resource using: POST [base]/Provenance/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing Provenance resource using: PUT [base]/Provenance/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Provenance resource using: PATCH [base]/Provenance/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Provenance resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHOULD be capable of a search-type interaction fetching Provenance resources matching a search query using: GET [base]/Provenance/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHOULD be capable of a read interaction fetching a Provenance resource using: GET [base]/Provenance/[id]
  • A Client SHOULD be capable of a vread interaction fetching a Provenance resource using: GET [base]/Provenance/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Provenance using: GET [base]/Provenance/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Provenance resources using: GET [base]/Provenance/_history{?[parameters]&_format=[mime-type]}

Questionnaire

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to when requesting data or attachments using Questionnaire

Supported Profiles:


Modify Criteria:

  • A Client SHOULD be capable of a create interaction posting a Questionnaire resource using: POST [base]/Questionnaire/[id]{?_format=[mime-type]}
  • A Client SHOULD be capable of putting a existing Questionnaire resource using: PUT [base]/Questionnaire/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Questionnaire resource using: PATCH [base]/Questionnaire/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Questionnaire resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHOULD be capable of a search-type interaction fetching Questionnaire resources matching a search query using: GET [base]/Questionnaire/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHOULD be capable of a read interaction fetching a Questionnaire resource using: GET [base]/Questionnaire/[id]
  • A Client SHOULD be capable of a vread interaction fetching a Questionnaire resource using: GET [base]/Questionnaire/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Questionnaire using: GET [base]/Questionnaire/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Questionnaire resources using: GET [base]/Questionnaire/_history{?[parameters]&_format=[mime-type]}

QuestionnaireResponse

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to fetch completed questionnaires from data source. SHALL support CDex SDC QuestionnaireResponse Profile for signed QuestionnaireResponse.

Supported Profiles:


Modify Criteria:

  • A Client MAY be capable of a create interaction posting a QuestionnaireResponse resource using: POST [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing QuestionnaireResponse resource using: PUT [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing QuestionnaireResponse resource using: PATCH [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a QuestionnaireResponse resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHOULD be capable of a search-type interaction fetching QuestionnaireResponse resources matching a search query using: GET [base]/QuestionnaireResponse/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHOULD be capable of a read interaction fetching a QuestionnaireResponse resource using: GET [base]/QuestionnaireResponse/[id]
  • A Client SHOULD be capable of a vread interaction fetching a QuestionnaireResponse resource using: GET [base]/QuestionnaireResponse/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a QuestionnaireResponse using: GET [base]/QuestionnaireResponse/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of QuestionnaireResponse resources using: GET [base]/QuestionnaireResponse/_history{?[parameters]&_format=[mime-type]}

Subscription

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to subscribe to data source for Task-based requests.


Modify Criteria:

  • A Client SHOULD be capable of a create interaction posting a Subscription resource using: POST [base]/Subscription/[id]{?_format=[mime-type]}
  • A Client SHOULD be capable of putting a existing Subscription resource using: PUT [base]/Subscription/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Subscription resource using: PATCH [base]/Subscription/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Subscription resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHOULD be capable of a search-type interaction fetching Subscription resources matching a search query using: GET [base]/Subscription/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHOULD be capable of a read interaction fetching a Subscription resource using: GET [base]/Subscription/[id]
  • A Client SHOULD be capable of a vread interaction fetching a Subscription resource using: GET [base]/Subscription/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Subscription using: GET [base]/Subscription/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Subscription resources using: GET [base]/Subscription/_history{?[parameters]&_format=[mime-type]}

Task

Conformance Expectation: SHOULD

Resource Specific Documentation:

Required resource type to request and fetch clinical information using Task-based query and for requesting attachments.

  1. If Da Vinci CDex Data Consumer Client supports Task-based query, they SHALL support the CDex Task Data Request Profile.
  2. If Da Vinci CDex Data Consumer Client supports requesting attachments, they SHALL support the following profiles:
    • CDex Task Attachment Request Profile
    • CDex Patient Demographic Profile
    • CDex PractitionerRequest Profile

Supported Profiles:


Modify Criteria:

  • A Client SHOULD be capable of a create interaction posting a Task resource using: POST [base]/Task/[id]{?_format=[mime-type]}
  • A Client SHOULD be capable of putting a existing Task resource using: PUT [base]/Task/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Task resource using: PATCH [base]/Task/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Task resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHOULD be capable of a search-type interaction fetching Task resources matching a search query using: GET [base]/Task/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHOULD be capable of a read interaction fetching a Task resource using: GET [base]/Task/[id]
  • A Client SHOULD be capable of a vread interaction fetching a Task resource using: GET [base]/Task/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Task using: GET [base]/Task/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Task resources using: GET [base]/Task/_history{?[parameters]&_format=[mime-type]}

Source

{
  "resourceType" : "CapabilityStatement",
  "id" : "data-consumer-client",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <!-- TODO \n Jurisdiction \n Prohibited extension - http://hl7.org/fhir/StructureDefinition/capabilitystatement-prohibited -->\n <!-- set include_symbols = false to turn off confonrmance symbols and legen, true to turn on -->\n \n \n <h2 id=\"title\">Data Consumer Client CapabilityStatement</h2>\n <ul>\n <li><b>Title:</b>Data Consumer Client CapabilityStatement</li>\n <li><b>Implementation Guide Version:</b> 2.1.0-preview</li>\n <li><b>FHIR Version:</b> 4.0.1</li>\n <li><b>Intended Use:</b> Requirements</li>\n <li><b>Supported Formats: </b> \n\n \n \n \n <strong>SHALL</strong> support \n \n json;\n \n \n \n <strong>MAY</strong> support \n \n xml;\n \n\n </li>\n \n <li><b>Supported Patch Formats:</b>\n \n \n \n <strong>MAY</strong> support \n \n application/json-patch+json;\n \n </li>\n \n <li><b>Published:</b> 2024-05-13 20:40:17-0800</li>\n \n <li><b>Published by:</b> HL7 International / Payer/Provider Information Exchange Work Group</li>\n <li><b>Status:</b> Active</li>\n <li><b>Copyright:</b> <div><p>Used by permission of HL7 International all rights reserved Creative Commons License</p>\n</div></li>\n </ul>\n <br/>\n\n\n\n \n <strong>Description:</strong> <div><div><p>This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Consumer in <em>Client</em> mode when requesting clinical data from the Data Source during clinical data exchange. The capabilities include one or more of the following interactions:</p>\n<ol>\n<li>Requesting and Fetching Clinical Data using a FHIR RESTful query</li>\n<li>Requesting and Fetching Clinical Data using a Task-based query including:\n<ul>\n<li>Polling or Subscribing for Task update notifications</li>\n</ul>\n</li>\n<li>Requesting Attachments\n<ul>\n<li>Requesting Attachments Using Attachments Codes</li>\n<li>Requesting Attachments Using Questionnaires</li>\n</ul>\n</li>\n</ol>\n</div></div>\n \n <br/>\n \n \n\n\n \n <h3>Support and Requirements for Other Artifacts</h3>\n \n <tr>\n <th>Instantiates other capabilities:</th>\n <td>\n <ul>\n \n <li>\n \n <strong>SHOULD</strong> support \n \n <a href=\"http://hl7.org/fhir/us/core/STU3.1.1/CapabilityStatement-us-core-client.html\">US Core Client CapabilityStatementversion: {0}3.1.1)</a>\n </li>\n \n <li>\n \n <strong>SHOULD</strong> support \n \n <a href=\"http://hl7.org/fhir/us/core/STU6.1/CapabilityStatement-us-core-client.html\">US Core Client CapabilityStatementversion: {0}6.1.0)</a>\n </li>\n \n </ul>\n </td>\n </tr>\n \n \n \n <tr>\n <th>Supports other guides:</th>\n <td>\n <ul>\n \n <li>\n \n <strong>SHOULD</strong> support \n \n <a href=\"http://hl7.org/fhir/us/core/STU3.1.1/ImplementationGuide-hl7.fhir.us.core.html\">US Coreversion: {0}3.1.1)</a>\n </li>\n \n <li>\n \n <strong>SHOULD</strong> support \n \n <a href=\"http://hl7.org/fhir/us/core/STU6.1/ImplementationGuide-hl7.fhir.us.core.html\">US Core Implementation Guideversion: {0}6.1.0)</a>\n </li>\n \n <li>\n \n <strong>SHOULD</strong> support \n \n <a href=\"http://hl7.org/fhir/us/davinci-hrex/STU1/ImplementationGuide-hl7.fhir.us.davinci-hrex.html\">Da Vinci Health Record Exchange (HRex)version: {0}1.0.0)</a>\n </li>\n \n <li>\n \n <strong>SHOULD</strong> support \n \n <a href=\"http://hl7.org/fhir/us/davinci-dtr/STU2/ImplementationGuide-hl7.fhir.us.davinci-dtr.html\">Da Vinci - Documentation Templates and Rulesversion: {0}2.0.1)</a>\n </li>\n \n <li>\n \n <strong>SHOULD</strong> support \n \n <a href=\"http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/ImplementationGuide-hl7.fhir.uv.subscriptions-backport.html\">Subscriptions R5 Backportversion: {0}1.1.0)</a>\n </li>\n \n </ul>\n </td>\n </tr>\n \n \n\n <br/>\n <!-- TODO - Make this a summary of capabilities, including system wide and each paradigm -->\n <p>\n <b>Jump to:</b>\n </p>\n <ul>\n \n <li><a href=\"#Client\">REST Client</a></li>\n \n \n \n </ul>\n\n\n\n <!-- REST Capabilities -->\n \n <br/>\n <a name=\"Client\"> </a>\n <h3 id=\"behavior\">FHIR Client RESTful Capabilities</h3>\n \n <div><div><p>The Da Vinci CDex Data Consumer Client <strong>SHALL</strong>:</p>\n<ol>\n<li>Support at least one of the CDex approaches for exchanging clinical information:\n<ol>\n<li>Direct Query</li>\n<li>Task-Based Approach</li>\n<li>Attachments</li>\n</ol>\n</li>\n<li>Follow the guidelines for <a href=\"signatures.html\">Generating and Verifying Signed Resources</a> <em>if signatures are required</em>.</li>\n<li>Support JSON source formats for all Da Vinci CDex interactions.</li>\n<li>Declare a CapabilityStatement identifying the scenarios, transactions, and profiles supported.\n<ul>\n<li>Follow the guidelines for <a href=\"task-based-conformance.html\">Conforming to CDex Task Based Approach</a> if supporting this exchange.</li>\n<li>Follow the guidelines for <a href=\"attachments-conformance.html\">Conforming to CDex Attachments</a> if supporting this exchange.</li>\n</ul>\n</li>\n</ol>\n<p>The Da Vinci CDex Data Consumer Client <strong>MAY</strong>:</p>\n<ol>\n<li>\n<p>Support XML source formats for all Da Vinci CDex interactions.</p>\n<blockquote>\n<p>Implementers that choose to support XML need to be aware that JSON Web Signatures can only be created and validated in the original native JSON. Transforms to and from XML will invalidate signatures.</p>\n</blockquote>\n</li>\n</ol>\n</div></div>\n \n\n <!-- REST Security -->\n \n <br/>\n <p id=\"security\"><strong>Security:</strong></p>\n \n <div><div><ol>\n<li>For general security consideration refer to the <a href=\"http://build.fhir.org/secpriv-module.html\">Security and Privacy Considerations</a>.</li>\n<li>For security considerations specific to this guide refer to the Da Vinci HRex Implementation Guide section on <a href=\"http://hl7.org/fhir/us/davinci-hrex/security.html\">Security and Privacy</a></li>\n</ol>\n</div></div>\n \n \n \n\n <!-- REST System wide Capabilities -->\n \n <h3>System-wide Client Capabilities</h3>\n \n <!-- REST System wide interactions -->\n \n <h4>Interactions</h4>\n\n <ul>\n \n <li>\n \n <strong>MAY</strong> support the \n \n <code>transaction</code> interaction.</li>\n \n <li>\n \n <strong>MAY</strong> support the \n \n <code>batch</code> interaction.</li>\n \n <li>\n \n <strong>MAY</strong> support the \n \n <code>search-system</code> interaction.</li>\n \n <li>\n \n <strong>MAY</strong> support the \n \n <code>history-system</code> interaction.</li>\n \n </ul>\n \n \n \n \n \n \n \n \n \n \n\n <!-- REST System wide operations -->\n \n\n\n <!-- REST System wide search parameters -->\n \n \n\n\n\n <!-- Resource Capabilities -->\n \n\n <h4>Summary of Resource/Profile Capabilities</h4>\n <!-- TODO need include conformance verb legend -->\n \n <table class=\"grid\">\n <thead>\n <tr>\n <th>Resource Type</th>\n <th>Supported Interactions</th>\n <th>Supported Profiles</th>\n <th>Supported Searches</th>\n <th>Supported <code>_includes</code></th>\n <th>Supported <code>_revincludes</code></th>\n <th>Supported Operations</th>\n </tr>\n </thead>\n <tbody>\n \n <tr>\n <td>\n <a href=\"#Client_Bundle\"><span style=\"white-space: nowrap;\">Bundle</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n <a href=\"StructureDefinition-cdex-signature-bundle.html\">CDex Signature Bundle Profileversion: {0}2.1.0-preview)</a>,\n \n \n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n <tr>\n <td>\n <a href=\"#Client_Patient\"><span style=\"white-space: nowrap;\">Patient</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n <a href=\"StructureDefinition-cdex-patient-demographics.html\">CDex Patient Demographics Profileversion: {0}2.1.0-preview)</a>,\n \n \n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n <tr>\n <td>\n <a href=\"#Client_PractitionerRole\"><span style=\"white-space: nowrap;\">PractitionerRole</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n <a href=\"StructureDefinition-cdex-practitionerrole.html\">CDex PractitionerRole Profileversion: {0}2.1.0-preview)</a>,\n \n \n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n <tr>\n <td>\n <a href=\"#Client_Provenance\"><span style=\"white-space: nowrap;\">Provenance</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n <tr>\n <td>\n <a href=\"#Client_Questionnaire\"><span style=\"white-space: nowrap;\">Questionnaire</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n <a href=\"http://hl7.org/fhir/us/davinci-dtr/STU2/StructureDefinition-dtr-std-questionnaire.html\">DTR Standard Questionnaire</a>,\n \n \n <a href=\"http://hl7.org/fhir/us/davinci-dtr/STU2/StructureDefinition-dtr-questionnaire-adapt.html\">DTR Questionnaire for adaptive form</a>,\n \n \n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n <tr>\n <td>\n <a href=\"#Client_QuestionnaireResponse\"><span style=\"white-space: nowrap;\">QuestionnaireResponse</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n <a href=\"StructureDefinition-cdex-sdc-questionnaireresponse.html\">CDex SDC QuestionnaireResponse Profileversion: {0}2.1.0-preview)</a>,\n \n \n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n <tr>\n <td>\n <a href=\"#Client_Subscription\"><span style=\"white-space: nowrap;\">Subscription</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n <tr>\n <td>\n <a href=\"#Client_Task\"><span style=\"white-space: nowrap;\">Task</span></a>\n </td>\n\n <!-- Supported Interactions -->\n <td>\n \n \n <span style=\"white-space: nowrap;\">create</span>,\n \n <span style=\"white-space: nowrap;\">search-type</span>,\n \n <span style=\"white-space: nowrap;\">read</span>,\n \n <span style=\"white-space: nowrap;\">vread</span>,\n \n <span style=\"white-space: nowrap;\">update</span>,\n \n <span style=\"white-space: nowrap;\">patch</span>,\n \n <span style=\"white-space: nowrap;\">delete</span>,\n \n <span style=\"white-space: nowrap;\">history-instance</span>,\n \n <span style=\"white-space: nowrap;\">history-type</span>,\n \n \n </td>\n\n <!-- Supported Profiles -->\n <td>\n \n <a href=\"StructureDefinition-cdex-task-data-request.html\">CDex Task Data Request Profileversion: {0}2.1.0-preview)</a>,\n \n \n <a href=\"StructureDefinition-cdex-task-attachment-request.html\">CDex Task Attachment Request Profileversion: {0}2.1.0-preview)</a>,\n \n \n \n </td>\n\n <!-- Supported Searches will need to do some sort of mapping instead of join to get the expectations printed out -->\n <td>\n \n </td>\n\n <!-- Supported _includes -->\n <td>\n \n </td>\n\n <!-- Supported _revincludes -->\n <td>\n \n </td>\n\n <!-- Supported Operations -->\n <td>\n \n </td>\n </tr>\n \n </tbody>\n </table>\n <br/>\n\n <h3 id=\"resource-details\" class=\"no_toc\">RESTful Client Capabilities by Resource/Profile:</h3>\n <!-- Each REST Resource Detail -->\n \n <h4 id=\"Client_Bundle\" class=\"no_toc\">Bundle</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to fetch Clinical Information from data source. <strong>SHALL</strong> support CDex Signature Bundle Profile for signed Bundles.</p>\n</div></blockquote>\n\n \n\n <p>Supported Profiles:</p>\n <ul>\n \n <li><strong>SHOULD</strong> support \n <a href=\"StructureDefinition-cdex-signature-bundle.html\">CDex Signature Bundle Profileversion: {0}2.1.0-preview)</a>\n </li>\n \n </ul>\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>create</code> interaction posting a Bundle resource using:\n <code class=\"highlighter-rouge\">POST [base]/Bundle/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>MAY</strong> be capable of putting a existing Bundle resource using:\n <code class=\"highlighter-rouge\">PUT [base]/Bundle/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing Bundle resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/Bundle/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a Bundle resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>search-type</code> interaction fetching Bundle resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/Bundle/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>read</code> interaction fetching a Bundle resource using:\n <code class=\"highlighter-rouge\">GET [base]/Bundle/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>vread</code> interaction fetching a Bundle resource using:\n <code class=\"highlighter-rouge\">GET [base]/Bundle/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a Bundle using:\n <code class=\"highlighter-rouge\">GET [base]/Bundle/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of Bundle resources using:\n <code class=\"highlighter-rouge\">GET [base]/Bundle/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n <h4 id=\"Client_Patient\" class=\"no_toc\">Patient</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to supply patient demographic data when requesting attachments.</p>\n</div></blockquote>\n\n \n\n <p>Supported Profiles:</p>\n <ul>\n \n <li><strong>SHALL</strong> support \n <a href=\"StructureDefinition-cdex-patient-demographics.html\">CDex Patient Demographics Profileversion: {0}2.1.0-preview)</a>\n </li>\n \n </ul>\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>create</code> interaction posting a Patient resource using:\n <code class=\"highlighter-rouge\">POST [base]/Patient/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>MAY</strong> be capable of putting a existing Patient resource using:\n <code class=\"highlighter-rouge\">PUT [base]/Patient/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing Patient resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/Patient/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a Patient resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>search-type</code> interaction fetching Patient resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/Patient/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>read</code> interaction fetching a Patient resource using:\n <code class=\"highlighter-rouge\">GET [base]/Patient/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>vread</code> interaction fetching a Patient resource using:\n <code class=\"highlighter-rouge\">GET [base]/Patient/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a Patient using:\n <code class=\"highlighter-rouge\">GET [base]/Patient/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of Patient resources using:\n <code class=\"highlighter-rouge\">GET [base]/Patient/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n <h4 id=\"Client_PractitionerRole\" class=\"no_toc\">PractitionerRole</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to supply patient demographic data when requesting attachments.</p>\n</div></blockquote>\n\n \n\n <p>Supported Profiles:</p>\n <ul>\n \n <li><strong>SHALL</strong> support \n <a href=\"StructureDefinition-cdex-practitionerrole.html\">CDex PractitionerRole Profileversion: {0}2.1.0-preview)</a>\n </li>\n \n </ul>\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>create</code> interaction posting a PractitionerRole resource using:\n <code class=\"highlighter-rouge\">POST [base]/PractitionerRole/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>MAY</strong> be capable of putting a existing PractitionerRole resource using:\n <code class=\"highlighter-rouge\">PUT [base]/PractitionerRole/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing PractitionerRole resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/PractitionerRole/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a PractitionerRole resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>search-type</code> interaction fetching PractitionerRole resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/PractitionerRole/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>read</code> interaction fetching a PractitionerRole resource using:\n <code class=\"highlighter-rouge\">GET [base]/PractitionerRole/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>vread</code> interaction fetching a PractitionerRole resource using:\n <code class=\"highlighter-rouge\">GET [base]/PractitionerRole/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a PractitionerRole using:\n <code class=\"highlighter-rouge\">GET [base]/PractitionerRole/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of PractitionerRole resources using:\n <code class=\"highlighter-rouge\">GET [base]/PractitionerRole/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n <h4 id=\"Client_Provenance\" class=\"no_toc\">Provenance</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to fetch provenance along with clinical information</p>\n</div></blockquote>\n\n \n\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>create</code> interaction posting a Provenance resource using:\n <code class=\"highlighter-rouge\">POST [base]/Provenance/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>MAY</strong> be capable of putting a existing Provenance resource using:\n <code class=\"highlighter-rouge\">PUT [base]/Provenance/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing Provenance resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/Provenance/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a Provenance resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>search-type</code> interaction fetching Provenance resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/Provenance/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>read</code> interaction fetching a Provenance resource using:\n <code class=\"highlighter-rouge\">GET [base]/Provenance/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>vread</code> interaction fetching a Provenance resource using:\n <code class=\"highlighter-rouge\">GET [base]/Provenance/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a Provenance using:\n <code class=\"highlighter-rouge\">GET [base]/Provenance/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of Provenance resources using:\n <code class=\"highlighter-rouge\">GET [base]/Provenance/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n <h4 id=\"Client_Questionnaire\" class=\"no_toc\">Questionnaire</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to when requesting data or attachments using Questionnaire</p>\n</div></blockquote>\n\n \n\n <p>Supported Profiles:</p>\n <ul>\n \n <li><strong>SHOULD</strong> support \n <a href=\"http://hl7.org/fhir/us/davinci-dtr/STU2/StructureDefinition-dtr-std-questionnaire.html\">DTR Standard Questionnaire</a>\n </li>\n \n <li><strong>SHOULD</strong> support \n <a href=\"http://hl7.org/fhir/us/davinci-dtr/STU2/StructureDefinition-dtr-questionnaire-adapt.html\">DTR Questionnaire for adaptive form</a>\n </li>\n \n </ul>\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>create</code> interaction posting a Questionnaire resource using:\n <code class=\"highlighter-rouge\">POST [base]/Questionnaire/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>SHOULD</strong> be capable of putting a existing Questionnaire resource using:\n <code class=\"highlighter-rouge\">PUT [base]/Questionnaire/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing Questionnaire resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/Questionnaire/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a Questionnaire resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>search-type</code> interaction fetching Questionnaire resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/Questionnaire/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>read</code> interaction fetching a Questionnaire resource using:\n <code class=\"highlighter-rouge\">GET [base]/Questionnaire/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>vread</code> interaction fetching a Questionnaire resource using:\n <code class=\"highlighter-rouge\">GET [base]/Questionnaire/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a Questionnaire using:\n <code class=\"highlighter-rouge\">GET [base]/Questionnaire/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of Questionnaire resources using:\n <code class=\"highlighter-rouge\">GET [base]/Questionnaire/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n <h4 id=\"Client_QuestionnaireResponse\" class=\"no_toc\">QuestionnaireResponse</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to fetch completed questionnaires from data source. <strong>SHALL</strong> support CDex SDC QuestionnaireResponse Profile for signed QuestionnaireResponse.</p>\n</div></blockquote>\n\n \n\n <p>Supported Profiles:</p>\n <ul>\n \n <li><strong>SHOULD</strong> support \n <a href=\"StructureDefinition-cdex-sdc-questionnaireresponse.html\">CDex SDC QuestionnaireResponse Profileversion: {0}2.1.0-preview)</a>\n </li>\n \n </ul>\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>create</code> interaction posting a QuestionnaireResponse resource using:\n <code class=\"highlighter-rouge\">POST [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>MAY</strong> be capable of putting a existing QuestionnaireResponse resource using:\n <code class=\"highlighter-rouge\">PUT [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing QuestionnaireResponse resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a QuestionnaireResponse resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>search-type</code> interaction fetching QuestionnaireResponse resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/QuestionnaireResponse/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>read</code> interaction fetching a QuestionnaireResponse resource using:\n <code class=\"highlighter-rouge\">GET [base]/QuestionnaireResponse/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>vread</code> interaction fetching a QuestionnaireResponse resource using:\n <code class=\"highlighter-rouge\">GET [base]/QuestionnaireResponse/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a QuestionnaireResponse using:\n <code class=\"highlighter-rouge\">GET [base]/QuestionnaireResponse/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of QuestionnaireResponse resources using:\n <code class=\"highlighter-rouge\">GET [base]/QuestionnaireResponse/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n <h4 id=\"Client_Subscription\" class=\"no_toc\">Subscription</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to subscribe to data source for Task-based requests.</p>\n</div></blockquote>\n\n \n\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>create</code> interaction posting a Subscription resource using:\n <code class=\"highlighter-rouge\">POST [base]/Subscription/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>SHOULD</strong> be capable of putting a existing Subscription resource using:\n <code class=\"highlighter-rouge\">PUT [base]/Subscription/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing Subscription resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/Subscription/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a Subscription resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>search-type</code> interaction fetching Subscription resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/Subscription/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>read</code> interaction fetching a Subscription resource using:\n <code class=\"highlighter-rouge\">GET [base]/Subscription/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>vread</code> interaction fetching a Subscription resource using:\n <code class=\"highlighter-rouge\">GET [base]/Subscription/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a Subscription using:\n <code class=\"highlighter-rouge\">GET [base]/Subscription/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of Subscription resources using:\n <code class=\"highlighter-rouge\">GET [base]/Subscription/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n <h4 id=\"Client_Task\" class=\"no_toc\">Task</h4>\n\n <p>Conformance Expectation:\t<strong>SHOULD</strong></p>\n\n <p>Resource Specific Documentation:</p>\n <blockquote><div><p>Required resource type to request and fetch clinical information using Task-based query and for requesting attachments.</p>\n<ol>\n<li>If Da Vinci CDex Data Consumer Client supports Task-based query, they <strong>SHALL</strong> support the <em>CDex Task Data Request Profile</em>.</li>\n<li>If Da Vinci CDex Data Consumer Client supports requesting attachments, they <strong>SHALL</strong> support the following profiles:\n<ul>\n<li><em>CDex Task Attachment Request Profile</em></li>\n<li><em>CDex Patient Demographic Profile</em></li>\n<li><em>CDex PractitionerRequest Profile</em></li>\n</ul>\n</li>\n</ol>\n</div></blockquote>\n\n \n\n <p>Supported Profiles:</p>\n <ul>\n \n <li><strong>SHOULD</strong> support \n <a href=\"StructureDefinition-cdex-task-data-request.html\">CDex Task Data Request Profileversion: {0}2.1.0-preview)</a>\n </li>\n \n <li><strong>SHOULD</strong> support \n <a href=\"StructureDefinition-cdex-task-attachment-request.html\">CDex Task Attachment Request Profileversion: {0}2.1.0-preview)</a>\n </li>\n \n </ul>\n \n \n\n\n <p>\n \n\n \n\n \n\n \n </p>\n\n\n\n\n\n\n <!-- Resource Interactions -->\n \n\n <!-- Resource Operations -->\n \n\n\n\n <!-- TODO Nexted ul items do not appear with a subbullet style -->\n \n <br/>\n <p>Modify Criteria:</p> \n <ul>\n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>create</code> interaction posting a Task resource using:\n <code class=\"highlighter-rouge\">POST [base]/Task/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n <li>\n <!-- TODO change note if server allows putting of a new one (with a specified ID) -->\n A Client <strong>SHOULD</strong> be capable of putting a existing Task resource using:\n <code class=\"highlighter-rouge\">PUT [base]/Task/[id]{?_format=[mime-type]}</code>\n \n </li>\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n <li>\n A Client <strong>MAY</strong> be capable of patching an existing Task resource using:\n <code class=\"highlighter-rouge\">PATCH [base]/Task/[id]{?_format=[mime-type]}</code>\n </li>\n \n\n \n \n\n \n\n \n <li>\n A Client <strong>MAY</strong> be capable of deleting a Task resource using:\n <code class=\"highlighter-rouge\">DELETE [base]//[id]</code>\n \n </li>\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n \n\n \n\n \n\n\n \n\n \n </ul>\n \n\n\n \n <br/>\n <p>Fetch and Search Criteria:</p>\n <ul>\n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>search-type</code> interaction fetching Task resources matching a search query using:\n <code class=\"highlighter-rouge\">GET [base]/Task/[id]{?[parameters]{&amp;_format=[mime-type]}}</code>\n </li>\n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>read</code> interaction fetching a Task resource using:\n <code class=\"highlighter-rouge\">GET [base]/Task/[id]</code>\n \n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>SHOULD</strong> be capable of a <code>vread</code> interaction fetching a Task resource using:\n <code class=\"highlighter-rouge\">GET [base]/Task/[id]/_history/vid</code>\n </li>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-instance</code> interaction fetching a history of a Task using:\n <code class=\"highlighter-rouge\">GET [base]/Task/[id]/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n \n \n \n \n \n \n <li>\n A Client <strong>MAY</strong> be capable of a <code>history-type</code> interaction fetching the history of Task resources using:\n <code class=\"highlighter-rouge\">GET [base]/Task/_history{?[parameters]&amp;_format=[mime-type]}</code>\n </li>\n \n \n\n \n\n \n\n </ul>\n \n\n \n\n <!-- Search Combination -->\n \n \n \n\n \n \n\n\n\n \n\n\n\n\n\n\n\n\n\n <!-- Messaging Capabilities -->\n \n\n <!-- Document Capabilities -->\n \n\n</div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode" : "claims"
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger" : 2,
      "_valueInteger" : {
        "extension" : [
          {
            "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical" : "http://hl7.org/fhir/us/davinci-cdex/ImplementationGuide/hl7.fhir.us.davinci-cdex"
          }
        ]
      }
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode" : "trial-use",
      "_valueCode" : {
        "extension" : [
          {
            "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical" : "http://hl7.org/fhir/us/davinci-cdex/ImplementationGuide/hl7.fhir.us.davinci-cdex"
          }
        ]
      }
    }
  ],
  "url" : "http://hl7.org/fhir/us/davinci-cdex/CapabilityStatement/data-consumer-client",
  "version" : "2.1.0-preview",
  "name" : "DataConsumerClientCapabilityStatement",
  "title" : "Data Consumer Client CapabilityStatement",
  "status" : "active",
  "experimental" : false,
  "date" : "2024-05-13T20:40:17.336549-08:00",
  "publisher" : "HL7 International / Payer/Provider Information Exchange Work Group",
  "contact" : [
    {
      "name" : "HL7 International / Payer/Provider Information Exchange Work Group",
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/claims"
        },
        {
          "system" : "email",
          "value" : "pie@lists.hl7.org"
        }
      ]
    }
  ],
  "description" : "This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Consumer in *Client* mode when requesting clinical data from the Data Source during clinical data exchange. The capabilities include one or more of the following interactions:\n\n1. Requesting and Fetching Clinical Data using a FHIR RESTful query\n2. Requesting and Fetching Clinical Data using a Task-based query including:\n - Polling or Subscribing for Task update notifications\n3. Requesting Attachments\n - Requesting Attachments Using Attachments Codes\n - Requesting Attachments Using Questionnaires",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "urn:iso:std:iso:3166",
          "code" : "US"
        }
      ]
    }
  ],
  "copyright" : "Used by permission of HL7 International all rights reserved Creative Commons License",
  "kind" : "requirements",
  "instantiates" : [
    "http://hl7.org/fhir/us/core/CapabilityStatement/us-core-client|3.1.1",
    "http://hl7.org/fhir/us/core/CapabilityStatement/us-core-client|6.1.0"
  ],
  "_instantiates" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    }
  ],
  "fhirVersion" : "4.0.1",
  "format" : [
    "json",
    "xml"
  ],
  "_format" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHALL"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "MAY"
        }
      ]
    }
  ],
  "patchFormat" : [
    "application/json-patch+json"
  ],
  "_patchFormat" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "MAY"
        }
      ]
    }
  ],
  "implementationGuide" : [
    "http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core|3.1.1",
    "http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core|6.1.0",
    "http://hl7.org/fhir/us/davinci-hrex/ImplementationGuide/hl7.fhir.us.davinci-hrex|1.0.0",
    "http://hl7.org/fhir/us/davinci-dtr/ImplementationGuide/hl7.fhir.us.davinci-dtr|2.0.1",
    "http://hl7.org/fhir/uv/subscriptions-backport/ImplementationGuide/hl7.fhir.uv.subscriptions-backport|1.1.0"
  ],
  "_implementationGuide" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
          "valueCode" : "SHOULD"
        }
      ]
    }
  ],
  "rest" : [
    {
      "mode" : "client",
      "documentation" : "The Da Vinci CDex Data Consumer Client **SHALL**:\n\n1. Support at least one of the CDex approaches for exchanging clinical information:\n 1. Direct Query\n 2. Task-Based Approach\n 3. Attachments\n2. Follow the guidelines for [Generating and Verifying Signed Resources](signatures.html) *if signatures are required*.\n3. Support JSON source formats for all Da Vinci CDex interactions.\n4. Declare a CapabilityStatement identifying the scenarios, transactions, and profiles supported.\n - Follow the guidelines for [Conforming to CDex Task Based Approach](task-based-conformance.html) if supporting this exchange.\n - Follow the guidelines for [Conforming to CDex Attachments](attachments-conformance.html) if supporting this exchange.\n\nThe Da Vinci CDex Data Consumer Client **MAY**:\n\n1. Support XML source formats for all Da Vinci CDex interactions.\n \n > Implementers that choose to support XML need to be aware that JSON Web Signatures can only be created and validated in the original native JSON. Transforms to and from XML will invalidate signatures.",
      "security" : {
        "description" : "1. For general security consideration refer to the [Security and Privacy Considerations](http://build.fhir.org/secpriv-module.html). \n1. For security considerations specific to this guide refer to the Da Vinci HRex Implementation Guide section on [Security and Privacy](http://hl7.org/fhir/us/davinci-hrex/security.html)\n"
      },
      "resource" : [
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "Bundle",
          "supportedProfile" : [
            "http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-signature-bundle|2.1.0-preview"
          ],
          "_supportedProfile" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ]
            }
          ],
          "documentation" : "Required resource type to fetch Clinical Information from data source. **SHALL** support CDex Signature Bundle Profile for signed Bundles.\n",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "Patient",
          "supportedProfile" : [
            "http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-patient-demographics|2.1.0-preview"
          ],
          "_supportedProfile" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHALL"
                }
              ]
            }
          ],
          "documentation" : "Required resource type to supply patient demographic data when requesting attachments.",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "PractitionerRole",
          "supportedProfile" : [
            "http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-practitionerrole|2.1.0-preview"
          ],
          "_supportedProfile" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHALL"
                }
              ]
            }
          ],
          "documentation" : "Required resource type to supply patient demographic data when requesting attachments.",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "Provenance",
          "documentation" : "Required resource type to fetch provenance along with clinical information",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "Questionnaire",
          "supportedProfile" : [
            "http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-std-questionnaire",
            "http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-questionnaire-adapt"
          ],
          "_supportedProfile" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ]
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ]
            }
          ],
          "documentation" : "Required resource type to when requesting data or attachments using Questionnaire",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "QuestionnaireResponse",
          "supportedProfile" : [
            "http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-sdc-questionnaireresponse|2.1.0-preview"
          ],
          "_supportedProfile" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ]
            }
          ],
          "documentation" : "Required resource type to fetch completed questionnaires from data source. **SHALL** support CDex SDC QuestionnaireResponse Profile for signed QuestionnaireResponse.",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "Subscription",
          "documentation" : "Required resource type to subscribe to data source for Task-based requests.",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "SHOULD"
            }
          ],
          "type" : "Task",
          "supportedProfile" : [
            "http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request|2.1.0-preview",
            "http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request|2.1.0-preview"
          ],
          "_supportedProfile" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ]
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ]
            }
          ],
          "documentation" : "Required resource type to request and fetch clinical information using Task-based query and for requesting attachments.\n\n1. If Da Vinci CDex Data Consumer Client supports Task-based query, they **SHALL** support the *CDex Task Data Request Profile*.\n2. If Da Vinci CDex Data Consumer Client supports requesting attachments, they **SHALL** support the following profiles: \n - *CDex Task Attachment Request Profile*\n - *CDex Patient Demographic Profile*\n - *CDex PractitionerRequest Profile*",
          "interaction" : [
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "create"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "search-type"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "read"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "vread"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "SHOULD"
                }
              ],
              "code" : "update"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "patch"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "delete"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-instance"
            },
            {
              "extension" : [
                {
                  "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                  "valueCode" : "MAY"
                }
              ],
              "code" : "history-type"
            }
          ]
        }
      ],
      "interaction" : [
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "MAY"
            }
          ],
          "code" : "transaction"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "MAY"
            }
          ],
          "code" : "batch"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "MAY"
            }
          ],
          "code" : "search-system"
        },
        {
          "extension" : [
            {
              "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode" : "MAY"
            }
          ],
          "code" : "history-system"
        }
      ]
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.