minimal Common Oncology Data Elements (mCODE) Implementation Guide
1.18.1 - STU 2 (Post-Ballot, Pre-Publication Draft)

minimal Common Oncology Data Elements (mCODE) Implementation Guide, published by HL7 International Clinical Interoperability Council. This is not an authorized publication; it is the continuous build for version 1.18.1). This version is based on the current content of https://github.com/HL7/fhir-mCODE-ig/ and changes regularly. See the Directory of published versions

Home

Background

Cancer is among the leading causes of death worldwide. According to the National Cancer Institute, in the United States, 39.5 percent of men and women will be diagnosed with cancer at some point during their lifetimes. In 2020, an estimated 1,806,590 new cases of cancer will be diagnosed in the United States and 606,520 people will die from the disease. While these numbers are staggering, the silver lining in the wide prevalence of cancer is the potential to learn from treatment of millions of patients. If we had research-quality data from all cancer patients, it would enable higher quality health outcomes. Today, we lack the data models, technologies, and methods to capture that data.

mCODE™ (short for Minimal Common Oncology Data Elements) is an initiative intended to assemble a core set of structured data elements for oncology electronic health records (EHRs). mCODE is a step towards capturing research-quality data from the treatment of all cancer patients. This would enable the treatment of every cancer patient to contribute to comparative effectiveness analysis (CEA) of cancer treatments by allowing for easier methods of data exchange between health systems. mCODE has been created and is being supported by the American Society of Clinical Oncology (ASCO®)in collaboration with the MITRE Corporation.

In late 2018, ASCO convened committee of twenty leading clinical experts in oncology, radiology, surgery, and public health developed two use cases that drove the initial clinical data requirements for mCODE:

While mCODE ultimately is meant to be applicable across all types of cancer, the initial focus (and both use cases) has been on solid tumors.

In addition to information obtained from subject matter experts, several pre-existing standards, nomenclatures, and guidelines were consulted in the development of this specification, including:

After initial development, in early 2019, an open survey was conducted to validate and prioritize the data elements from these use cases. Further down-scoping was done based on whether the data would be stored or capture in an electronic health record (EHR), and if it would place undue documentation burden on clinicians.

Scope and Conceptual Model

This implementation guide is a Domain of Knowledge IG. The purpose of this IG is to show how to represent clinical concepts generally, not to have a complete set of agreements for interoperable exchanges.

mCODE consists of data elements divided into six loosely-arranged groups. Refer to the links below for details on the content and artifacts in each group:

The groups are illustrated in the following diagram:

mCODE Logical Model

Data Dictionary

In addition to the FHIR artifacts, readers should also take note of the Data Dictionary , a simplified, flattened list of mCODE elements in MS-Excel format.

There is also a Data Dictionary Differential that compares STU 1 with STU 2 on an element-by-element basis.

Understanding this Guide

The mCODE Implementation Guide was developed using the standard HL7 FHIR publishing tools. The page layouts and symbols are explained in the FHIR documentation. In viewing a profile page, note that there are multiple views. The “Differential Table” view represents the difference between the current profile and its base resource or profile. When interpreting this view, bear in mind that the immediate parent may not be a base FHIR resource, but it could be a US Core profile or another profile in this guide. The “Snapshot Table” represents the entire profile, with all elements.

In the event there are differences between the page renderings in this IG and the associated FHIR artifacts, the FHIR artifacts should be taken as the source of truth. In the unlikely event that an artifact’s snapshot is inconsistent with its differential, the differential should be taken as the source of truth.

Contributions

mCODE is an open source project and welcomes all contributors. The source code for this IG is maintained in the HL7 Github. Instead of just suggesting a change, consider creating a branch, making the change, and submitting a pull request. All of our profiling work is done in FHIR Shorthand and all narrative content in markdown (specifically, Kramdown). We suggest using the Visual Studio Code editor with the FHIR Shorthand plug-in. For more information on how to get started with IG development, visit the FSH School.

If you have questions or comments about this guide, please reach out on chat.fhir.org or create an issue in the HL7 Jira.

Credits

The authors recognize the leadership and sponsorship of Dr. Monica Bertagnolli, former ASCO President and Dr. Jay Schnitzer, MITRE Chief Technology and Chief Medical Officer. The ASCO/CancerLinQ team was led by Dr. Robert Miller. Dr. Travis Osterman of Vanderbilt University leads the mCODE Technical Review Group. Andre Quina guides the overall mCODE effort at MITRE. Dr. Charles Mayo of University of Michigan, Randi Kudner of ASTRO, and Martin von Siebenthal of Varian made significant contributions to the much improved radiotherapy portion of this IG. MITRE contributors include Mark Kramer, May Terry, Max Masnick, Saul Kravitz, Rute Martins, Chris Moesel, Caroline Potteiger, Steve Bratt, and Sharon Sebastian. HL7 sponsorship and input from Clinical Interoperability Council and Clinical Information Modeling Initiative is gratefully acknowledged, with special thanks to Richard Esmond, Laura Heermann Langford, and Lindsey Hoggle. The capability statements were rendered with tools developed by Eric Haas and modified by Corey Spears.

This IG was authored by the MITRE Corporation using FHIR Shorthand (FSH) and SUSHI, a free, open source toolchain from MITRE Corporation.

Contact Information

Topic Who Role Email
Implementation and use cases Steve Bratt CodeX Accelerator Program Manager sbratt@mitre.org
Domain content Dr. Travis Osterman Chair, mCODE Technical Review Group travis.osterman@vumc.org
Modeling and FHIR IG issues Mark Kramer Modeling Lead mkramer@mitre.org

MITRE: Approved for Public Release. Distribution Unlimited. Case Number 16-1988