HL7 Europe Common Cancer Model, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/cancer-common/ and changes regularly. See the Directory of published versions
Table 1 provides for each Concept: a description of what it represents, some notes (e.g., exclusions), other terms usually adopted to indicate it, and the relationship with other Concepts.
On dates and temporality. To rebuild the cancer journey, dates are fundamental. It is important to define which concepts or attributes can evolve during the journey to understand when to update the same instance versus when to create another one.
| Concept | Description | Note | Also known as | Connection / Dependency |
|---|---|---|---|---|
| CancerConditionAtDiagnosis |
Represents the Cancer Condition at the First Diagnosis, which is the start of the cancer journey. All attributes never change. It must have:
It must include at least one of these dates, as they represent the key dates in the diagnostic process:
|
Each time a patient has a new cancer (so not related and independent from the first one), they have a new Cancer Condition. In case in time, there is an updated of the Cancer Condition (related to the same cell type, so depending on the first cancer), it will be reflected in a new ClinicalCancerProgression instance. If a cancer is metastatic at the First diagnosis, the information on the metastasis is collected within the CancerStage not in the ClinicalCancerProgression instance. The couple Histology Behaviour and Body Site identifies the Cancer Condition. |
Cancer Condition: Primary Cancer, Secondary Primary Condition |
Connected with:
Basing on the availability in EHR, it can be directly or indirectly connected with some other concepts as:
|
| CancerPatient |
Represents the subject that is affected by one or more Cancer Conditions. It has:
It can have:
|
Subject |
Directly connected with:
Indirectly connected with other concepts through CancerConditionAtDiagnosis. If available in EHR, connected to all possible Procedures and Reports as Subject (not reported in the model). |
|
| CancerStage |
Represents the stage of the Cancer Condition at the First Diagnosis (CancerConditionAtDiagnosis) and describes the tumour extent. The stage can be Clinical (is based on Imaging) or Pathological (is based on the main Surgery). A CancerConditionAtDiagnosis must always have one CancerStage of type Clinical, which is defined based on Imaging. It may also be associated with a CancerStage of type Pathological, which is defined based on Surgery. It must have:
|
In case in time, there is an extension of the Cancer Condition (related to the same cell type, so depending on the first cancer), it will be reflected in a new ClinicalCancerProgression instance with Disease Status (as Progression or Recurrence), while the CancerStage will not change. If a cancer is metastatic at the First diagnosis, the information on the metastasis is collected within the CancerStage not in the ClinicalCancerProgression instance. If a cancer is metastatic at the diagnosis, the information on the metastasis is collected within the CancerStage not in the ClinicalCancerProgression. |
Connected with:
|
|
| Imaging |
Represents the Imaging information used to define the Clinical CancerStage. It must have:
|
Connected with a CancerStage (of type Clinical). Basing on the availability in EHR it can be directly or indirectly connected with an Imaging Report. |
||
| CancerTreatment (Surgery, ActiveSurveillance, Radiotherapy, SystemicTreatment) |
Represents either a single treatment or a multimodal set of procedures and therapies performed to treat the CancerCondition (i.e., the CancerCondition (AtDiagnosis) and, where applicable, the ClinicalCancerProgression). It can be divided in 4 main types:
|
Typically it is very difficult to define if the target is the CancerCondition (AtDiagnosis) or to a specific ClinicalCancerProgression because the target is the overall CancerCondition. Also Diet or Exercise can be prescribed Treatments but are not considered for the first period. SystemicTreatment excludes drugs administered for other pathologies, such as diabetes or hypertension. Should it be necessary to manage administrations unrelated to the CancerCondition, a separate entity would need to be introduced. In the logical model:
|
Treatment: Anti-cancer treatment Definitive: curative |
Connected to:
Basing on the availability in EHR it can be connected with some other concepts as:
|
| Last Follow Up |
Represents the patient’s health status information collected during the most recent follow-up visit. It has:
In case of a living CancerPatient, it must have:
In case of a dead CancerPatient, it must have:
|
Directly connected with:
Indirectly with other concepts through CancerPatient. Basing on the availability in EHR it can be connected with some other concepts as:
|
||
| OverallCancerTreatmentResponse |
Represents the standard way to measure how well a CancerPatient responds to a all performed Treatments on the Cancer Condition. It is based on whether tumours shrink, stay the same, or get bigger. It is evaluated by clinician during a follow-up Visit based on an Evidence. It can be one of the following:
It must have:
|
It could seem like a repetition of the Disease Status, but it doesn’t. It is important to have OverallCancerTreatmentResponse and Disease Status separated because they have different purposes. The OverallCancerTreatmentResponse is used to evaluate the effects of the Treatments while Disease Status is to represent the evolution of the Cancer Condition over time. It is the Disease Status that evolves over the time not the OverallCancerTreatmentResponse. It is difficult to associate a response with a specific individual treatment. Instead, the response represents the cumulative effect of all interventions performed up to that point to treat the Cancer Condition. |
Connected to:
Basing on the availability in EHR it can be connected with some other concepts as:
|
|
| ClinicalCancerProgression |
Represents the evolution over the time and over the space of the Cancer Condition. Every time that there is a new evaluation, there will be a new instance of ClinicalCancerProgression that must have:
and it can have attributes to represent the location where the cancer is extended at the time of the assertion (typically evaluated with an Imaging) that can be:
|
After the First Diagnosis, every time that there is an evaluation of the Cancer Condition during a Visit, a new instance of ClinicalCancerProgression is created. If a cancer is metastatic at the First diagnosis, the information on the metastasis is collected within the CancerStage not in the ClinicalCancerProgression. Please note that, although the term ClinicalCancerProgression includes the word progression, it is intended to describe the evolution of the disease over time, which does not necessarily imply a worsening or progression of the disease. |
Connected with:
Basing on the availability in EHR it can be directly or indirectly connected with some other concepts as:
|
| Concept | Notes |
|---|---|
| Treatment Plan |
It could be useful to record not only the actual treatment, but also what was planned. In fact, the Treatment can change based on the Treatment Response. It could be also useful to consider guidelines and if a patient has agreed or not. |
| Clinical Trials |
It could be useful to consider that a patient can participate in trials and represent its purposes and objectives. |
| Quality of Life (QoL)/ Patient-Reported Outcome Measures (PROMs) ect.. |
It could be useful to consider questionnaires to evaluate the quality of life and outcomes, but not with priority. They could be recorded during a Visit. |
| Adverse Events / Late Effects / Toxicities |
It could be useful, but is difficult to have and can be biased, it requires hospitalization. |
| Risk Factors / Environmental Factors / Genomic Predisposition / Familiarity |
It could be useful to have to cover specific research, but not with priority. |
| Genomics / Biomarker |
They could be important, but their scope and usage needs specific discussions, so they are not included in the version 1, but are the next candidate future model extensions. |