Generated Narrative: CapabilityStatement ocpa-crd-service

Oncology CRD Service Capability Statement

  • Implementation Guide Version: 0.1.1-snapshot-080926
  • FHIR Version: 4.0.1
  • Supported Formats: json, xml
  • Published on: 2026-05-04
  • Published by: HL7 International / Clinical Interoperability Council

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

A conformant Oncology CRD Service SHALL:

  1. Be capable of evaluating the selected anti-cancer regimen RequestGroup and optionally resolving its instantiated PlanDefinition.
  2. Evaluate patient-specific treatment-intent and line-of-therapy slices carried with the Da Vinci CRD ext-request-category URL on the RequestGroup. Use fhirAuthorization — when provided in the CDS Hooks request — to query the EHR FHIR server for additional required oncology patient context (cancer condition, staging, biomarkers, performance status, and prior therapy).
  3. Return informational cards at order-select indicating the approvability status of the ordered regimen. These cards are advisory — the order has not been committed.
  4. Return a final determination at order-sign with the appropriate indicator: success for Authorization Satisfied, warning for PA-required or DTR-required.
  5. Surface biosimilar substitution requirements at order-select so the provider is informed of payer modifications before signing.
  6. Return a DTR launch card when required context is not available from the EHR FHIR server.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCSearches_include_revincludeOperations
RequestGroupSupported Profiles
  Anti-Cancer Regimen RequestGroup		y
PlanDefinitionSupported Profiles
  Anti-Cancer Regimen PlanDefinition		y
Condition y
Observation y
MedicationRequest y

Resource Conformance: unspecified RequestGroup

Core FHIR Resource
RequestGroup
Reference Policy
Interaction summary
  • Supports read.

Supported Profiles

Anti-Cancer Regimen RequestGroup

Documentation

SHALL resolve and evaluate RequestGroup resources received in CDS Hooks context.draftOrders, including the profile-sliced Da Vinci CRD ext-request-category values for treatment intent and line of therapy.

Resource Conformance: unspecified PlanDefinition

Core FHIR Resource
PlanDefinition
Reference Policy
Interaction summary
  • Supports read.

Supported Profiles

Anti-Cancer Regimen PlanDefinition

Documentation

SHOULD resolve PlanDefinition referenced by RequestGroup.instantiatesCanonical.

Resource Conformance: unspecified Condition

Core FHIR Resource
Condition
Reference Policy
Interaction summary
  • Supports search-type.

Documentation

SHALL query Condition (primary cancer condition) from EHR FHIR server when fhirAuthorization is provided.

Resource Conformance: unspecified Observation

Core FHIR Resource
Observation
Reference Policy
Interaction summary
  • Supports search-type.

Documentation

MAY query Observation for staging, biomarkers, and performance status when required by policy; treatment intent and line of therapy are carried only in RequestGroup ext-request-category values.

Resource Conformance: unspecified MedicationRequest

Core FHIR Resource
MedicationRequest
Reference Policy
Interaction summary
  • Supports search-type.

Documentation

SHOULD query MedicationRequest (prior therapy) from EHR FHIR server when relevant.

 <status value="draft"/> <experimental value="true"/> <date value="2026-05-04"/> <publisher value="HL7 International / Clinical Interoperability Council"/> <contact> <name value="HL7 International / Clinical Interoperability Council"/> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/cic"/> </telecom> <telecom> <system value="email"/> <value value="ciclist@lists.HL7.org"/> </telecom> </contact> <description value="Capability Statement for systems acting as an **Oncology CRD Service** (e.g., a payer or prior-authorization platform). A conformant service claims support for the Da Vinci CRD oncology profile defined in this IG by meeting the requirements below."/> <jurisdiction> <coding> <system value="urn:iso:std:iso:3166"/> <code value="US"/> <display value="United States of America"/> </coding> </jurisdiction> <kind value="requirements"/> <fhirVersion value="4.0.1"/> <format value="json"/> <format value="xml"/> <implementationGuide value="http://hl7.org/fhir/us/codex-mopa/ImplementationGuide/hl7.fhir.us.codex-mopa"/> <implementationGuide value="http://hl7.org/fhir/us/davinci-crd/ImplementationGuide/hl7.fhir.us.davinci-crd"/> <rest> <mode value="server"/> <documentation value="A conformant Oncology CRD Service SHALL: 1. Be capable of evaluating the selected anti-cancer regimen `RequestGroup` and optionally resolving its instantiated `PlanDefinition`. 2. Evaluate patient-specific treatment-intent and line-of-therapy slices carried with the Da Vinci CRD `ext-request-category` URL on the RequestGroup. Use `fhirAuthorization` — when provided in the CDS Hooks request — to query the EHR FHIR server for additional required oncology patient context (cancer condition, staging, biomarkers, performance status, and prior therapy). 3. Return informational cards at `order-select` indicating the approvability status of the ordered regimen. These cards are advisory — the order has not been committed. 4. Return a final determination at `order-sign` with the appropriate indicator: `success` for Authorization Satisfied, `warning` for PA-required or DTR-required. 5. Surface biosimilar substitution requirements at `order-select` so the provider is informed of payer modifications before signing. 6. Return a DTR launch card when required context is not available from the EHR FHIR server."/> <resource> <type value="RequestGroup"/> <supportedProfile value="http://hl7.org/fhir/us/codex-mopa/StructureDefinition/anticancer-regimen-requestgroup"/> <documentation value="SHALL resolve and evaluate RequestGroup resources received in CDS Hooks context.draftOrders, including the profile-sliced Da Vinci CRD ext-request-category values for treatment intent and line of therapy."/> <interaction> <code value="read"/> </interaction> </resource> <resource> <type value="PlanDefinition"/> <supportedProfile value="http://hl7.org/fhir/us/codex-mopa/StructureDefinition/anticancer-regimen-plandefinition"/> <documentation value="SHOULD resolve PlanDefinition referenced by RequestGroup.instantiatesCanonical."/> <interaction> <code value="read"/> </interaction> </resource> <resource> <type value="Condition"/> <documentation value="SHALL query Condition (primary cancer condition) from EHR FHIR server when fhirAuthorization is provided."/> <interaction> <code value="search-type"/> </interaction> </resource> <resource> <type value="Observation"/> <documentation value="MAY query Observation for staging, biomarkers, and performance status when required by policy; treatment intent and line of therapy are carried only in RequestGroup ext-request-category values."/> <interaction> <code value="search-type"/> </interaction> </resource> <resource> <type value="MedicationRequest"/> <documentation value="SHOULD query MedicationRequest (prior therapy) from EHR FHIR server when relevant."/> <interaction> <code value="search-type"/> </interaction> </resource> </rest> </CapabilityStatement>