minimal Common Oncology Data Elements (mCODE) Implementation Guide
4.0.0-ballot - STU4 Ballot United States of America flag

minimal Common Oncology Data Elements (mCODE) Implementation Guide, published by HL7 International / Clinical Interoperability Council. This guide is not an authorized publication; it is the continuous build for version 4.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of and changes regularly. See the Directory of published versions

CapabilityStatement: mCODE Data Sender CapabilityStatement: Get in-scope patients using reverse chaining (Experimental)

Official URL: Version: 4.0.0-ballot
Draft as of 2020-10-30 Computable Name: CapabilityStatementSenderPatientsWithCancerCondition
Other Identifiers: OID:2.16.840.1.113883.4.642.

Uses reverse chaining to retrieve a Bundle of Patient resources with a condition code in mCODE’s cancer condition value set.

Raw OpenAPI-Swagger Definition file | Download

mCODE Data Sender CapabilityStatement: Get in-scope patients using reverse chaining

  • Implementation Guide Version: 4.0.0-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats:
  • Published on: 2020-10-30 07:15:00-0400
  • 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

An mCODE Server SHALL:

  1. Support all profiles defined in this Implementation Guide..
  2. Implement the RESTful behavior according to the FHIR specification.
  3. Return the following response classes:
    • (Status 400): invalid parameter
    • (Status 401/4xx): unauthorized request
    • (Status 403): insufficient scope
    • (Status 404): unknown resource
    • (Status 410): deleted resource.
  4. Support json source formats for all mCODE interactions.
  5. Identify the mCODE profiles supported as part of the FHIR meta.profile attribute for each instance.
  6. Support the searchParameters on each profile individually and in combination.

The mCODE Server SHOULD:

  1. Support xml source formats for all mCODE interactions.
  1. See the General Security Considerations section for requirements and recommendations.
  2. A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.
Summary of System-wide Interactions

Capabilities by Resource/Profile


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
PatientSupported profiles:
  Cancer Patient Profile
Group ycode

Resource Conformance: SHALLPatient

Core FHIR Resource
Reference Policy
Interaction summary
  • SHALL support read, search-type.

Search Parameters

Resource Conformance: SHALLGroup

Core FHIR Resource
Reference Policy
Interaction summary
  • SHALL support search-type.

Search Parameters