MOPA — Medical Oncology Prior Authorization
0.1.1-snapshot-080926 - snapshot-080926 United States of America flag

MOPA — Medical Oncology Prior Authorization - Local Development build (v0.1.1-snapshot-080926) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CapabilityStatement: Oncology CRD Client Capability Statement (Experimental)

Official URL: http://hl7.org/fhir/us/codex-mopa/CapabilityStatement/ocpa-crd-client Version: 0.1.1-snapshot-080926
Standards status: Informative Computable Name: OcpaCrdClientCapabilityStatement

Capability Statement for systems acting as an Oncology CRD Client (e.g., an EHR or oncology ordering system). A conformant client claims support for the Da Vinci CRD oncology profile defined in this IG by meeting the requirements below.

Raw OpenAPI-Swagger Definition file | Download

Language: en

Oncology CRD Client 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: client

A conformant Oncology CRD Client SHALL:

  1. Include the selected anti-cancer regimen as a RequestGroup conforming to AntiCancerRegimenRequestGroup in context.draftOrders and context.selections.
  2. Fire order-select when the provider selects a regimen from the order-set, before signing. At this stage the RequestGroup is present but component MedicationRequests may not yet be finalised.
  3. Fire order-sign when the provider signs the order, with finalised component MedicationRequest resources included in context.draftOrders.
  4. Populate RequestGroup.instantiatesCanonical with the canonical URL of the AntiCancerRegimenPlanDefinition when the definition is known.
  5. Populate RequestGroup.extension:category/treatmentIntent and RequestGroup.extension:category/lineOfTherapy when known at ordering time. Both reslices use the Da Vinci CRD ext-request-category URL and their required oncology value sets. This use requires the proposed CRD 2.2.1 RequestGroup extension-context expansion.
  6. Provide fhirAuthorization in the CDS Hooks request when available, to allow the CRD service to query patient context directly 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		yy
PlanDefinitionSupported Profiles
  Anti-Cancer Regimen PlanDefinition		y
Condition yy
Observation yy
MedicationRequest yy
Core FHIR Resource
RequestGroup
Reference Policy
Interaction summary
  • Supports read, create.

Supported Profiles

Anti-Cancer Regimen RequestGroup

Documentation

SHALL include a conformant RequestGroup in context.draftOrders at order-select and order-sign, including the profile-sliced Da Vinci CRD ext-request-category values for available treatment intent and line-of-therapy context.

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

Supported Profiles

Anti-Cancer Regimen PlanDefinition

Documentation

SHOULD support read of the PlanDefinition referenced by RequestGroup.instantiatesCanonical.

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

Documentation

SHALL expose Condition resources (mCODE primary cancer) for CRD service queries.

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

Documentation

SHOULD expose Observation resources for staging, biomarkers, and performance status when a CRD service requires them. Treatment intent and line of therapy are carried only as RequestGroup ext-request-category values.

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

Documentation

SHOULD expose MedicationRequest resources (prior therapy) for CRD service queries.