Care plans

A Care plan is a grouping of prescribed and planned treatments, procedures or medication orders for a particular patient in the context of a particular diagnosis. This category is therefore about the planned care: in practice, it is possible to deviate from the original Care plan and provide care in a different way than planned. For example, the start date of the next cycle of chemotherapy may be cancelled or postponed by a week because a patient's condition is too poor on the planned start date. A user uses the other search term categories in CTcue to determine when the care (a care activity, medication administration, surgery...) was actually provided.

Example of care plans: chemotherapy planning of cancer patients.

Overview

Filter name in app	Priority	FHIR field	Brief description	Example data
ID	Must have	CarePlan.identifier.value	Unique identifier for care plan.
Description	Must have	CarePlan.description	Brief characterisation or the name of the care plan.	IMATINIB 1DD 400MG CML; bevacizumab + capecitabine 1000 mg/m2; Medical oncology docetaxel monotherapy breast cancer
Template	Should have	Not yet mapped	A hospital can use standard templates for care plans. This field indicates which template has been chosen.	ChipSoft: VCMO code.
Indication	Should have	Not yet mapped	Indication for the care plan. Indicates which disease or diagnosis is being treated with the care plan.	Colon cancer, COPD, Herpes simplex
Category	Could have	CarePlan.category.coding.display	Type or subcategory of care plan	Medication course; Treatment plan; Therapy plan
Type	Could have	CarePlan.activity.detail.kind	Further specification of the type of care plan.	Cytostatics
Cycle number	Must have	Not yet mapped	The cycle number of the care plan.	Integer: 1, 2, 6.
Age at time of event	Must have	Derived from Patient (CarePlan.subject)	Age of the patient, in years, when the execution of the care plan is to start.
Status	Must have	CarePlan.status	Status of the care plan	Cancelled, Active, Inactive, Future, Completed, Expired.
Performing care provider name	Could have	Derived from Practitioner (CarePlan.contributor)	Name of the care provider performing / executing the care plan.	Dr. Jane Doe, nurse John Doe.
Requesting care provider name	Could have	Derived from Practitioner (CarePlan.author)	Name of the healthcare provider who drew up and registered the care plan in the EHR.	Dr. Jane Doe, nurse John Doe.
Start date	Must have	CarePlan.period.start	Planned start date for the care plan.	DD-MM-YYYY hh:mm
End date	Should have	CarePlan.period.end	Planned end date for the care plan.	DD-MM-YYYY hh:mm
Request date	Should have	CarePlan.created	Date on which the treatment plan was requested.	DD-MM-YYYY hh:mm