An oncology configuration where the protocol, the meeting decision and inter-cycle monitoring are one thread.

Oncology day units, cancer coordination teams and shared hospital–community pathways.

Which problem does it solve?

Decision, execution and patient-reported reality live in three separate systems.

The protocol instance carries the cycles, and every actor reads its current state.

Inter-cycle symptoms are part of the protocol timeline, not an unstructured phone log.

The oncology path of the tour follows one protocol instance across three settings.

Oncology teams and cancer care coordinators

On-Kare for oncology

Cancer care is a protocol with named cycles, a multidisciplinary meeting that decides, and a patient who lives between the two.

01
The multidisciplinary decision lives in minutes of a meeting, not in the record that executes it.
02
Toxicity between cycles is reported by phone and recorded inconsistently.
03
Coordination across hospital, city and home care depends on documents being re-sent.

the meeting outcome sets the protocol, its cycles and its checkpoints.

graded reports reach the team before the next cycle, not during it.

hospital, community and home teams read the same plan and its current step.

Referenced, never restated: each capability is described on its own page.

Which surface carries each business domain in this context: Pro for the team, Me for the patient, One for the shared layer underneath.

Read what it covers and how it is delivered.

Read what it covers and how it is delivered.

Read what it covers and how it is delivered.

01
Protocols are versioned and their deviations must be justified and recorded, not silently applied.
02
Symptom grading follows recognised scales, and automation may prepare but never grade on its own.
03
Data flows to registries and trials with their own consent and export requirements.

No oncology customer story is publishable yet; the tour shows the protocol thread on real screens.

The surface this workflow runs on.

What is it?: An oncology configuration where the protocol, the meeting decision and inter-cycle monitoring are one thread.
Who is it for?: Oncology day units, cancer coordination teams and shared hospital–community pathways.
Which problem does it solve?: Decision, execution and patient-reported reality live in three separate systems.
How does it work?: The protocol instance carries the cycles, and every actor reads its current state.
How is it different?: Inter-cycle symptoms are part of the protocol timeline, not an unstructured phone log.
What is the proof?: The oncology path of the tour follows one protocol instance across three settings.

This page is part of a platform of 2,156 clinical and operational capabilities across 8 business domains.

ISO 27001SOC 2 Type IIGDPR · DPOHIPAA-ready, BAA available30+ jurisdictionsSee the dated detail

Cancer care is a protocol with named cycles, a multidisciplinary meeting that decides, and a patient who lives between the two.

Medical review: 2026-08-24 · Legal review: 2026-08-24