The growing 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.
Health systems considering or implementing mCODE are making it clear that oncology clinical pathways should be prioritized as a mCODE point-of-care application. The key reasons for this is the burden on the oncologist on pathway navigation/documentation and the challenges of prior authorization. The other important factor is the use of mCODE, a HL7 FHIR-based interoperable standard, for pathway data.
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 oncologist accepts the treatment recommendation
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.
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.
|First demo of Camino to UPenn||22 January 2020|
|First demo of Camino to UCSF||30 January 2020|