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
OR
The oncologist denies the treatment recommendation, gives the rationale, and suggests alternative(s).

Pathways contain both oncology and 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.  Clinical data exchange and preauthorization are out of scope for this use case.