Page tree
Skip to end of metadata
Go to start of metadata

Problem and Target Outcome


The complexity of cancer care increases with each year with new drug regimens and tumor genomics. To deal with this, oncologists need decision support to help standardize care. This combined with rising healthcare costs associated with expensive cancer therapies has led to the rapid growth of oncology clinical pathways. 

Target Outcome:

Health systems considering or implementing mCODE are making it clear that oncology clinical pathways should be prioritized as an mCODE point-of-care application.  The key reasons for this are the burden on the oncologist on pathway navigation/documentation and the challenges of prior authorization.  The other important factor is the use of mCODE, an HL7 FHIR-based interoperable standard, for oncology data.

OCP Details


An Oncology Clinical Pathway (OCP):  detailed decision tree protocol for selection of treatment options by oncologists, primarily focused on anticancer drug regimens for specific patient populations, including type, stage, and molecular subtype of disease.


Oncologist launches pathway Smart-on-FHIR application.

  • The EHR system supports FHIR RESTful API and the integration of SMART-on-FHIR applications.
  • The EHR system can consume and produce valid FHIR resources.
  • The pathways content must come from recognized sources, such as academic medical centers or pathway vendors.

The oncologist accepts the treatment recommendation
The oncologist declines the treatment recommendation, gives the rationale, and suggests alternatives.


Pathways contain oncology and other clinical data elements that are not in mCODE for branch navigation.  These need to be modeled into CodeX elements to be used in pathway navigation.

  • The oncologist can enter pathway data elements via EHR forms or other means of structured documentation.
  • The pathways application can access the pathway data elements for navigation.

This use case covers the use of the pathways application to reach a treatment option.  Preauthorization is out of scope. 


Conference Call Information

Important Dates

First demo of Camino to UPenn22 January 2020
First demo of Camino to UCSF30 January 2020

Use Case Team

Domain LeadJim O'ConnorThe MITRE Corporation

Technical LeadDylan HallThe MITRE Corporation

Chief EngineerRob DingwellThe MITRE Corporation

  • No labels