Software for oncology operations

OncoTime

Synchronizing care and efficiency for life.

Chemotherapy Scheduling and Cancer Patient Navigation (Brazilian Federal Law 14.758) in a single platform — protocols, capacity, patient journey, and audit in the same workflow.

Law 14.758/2023 Cancer Patient Navigation instrumented with the legal deadline, validated phases, and categorized care barriers.
LGPD art. 11 Append-only audit log, granular per-module roles, and anonymized export (k-anonymity ≥ 5).
ANVISA Resolution RDC 220/2004 UTAQ capacity by wing, chair/bed, shift, and protocol, with validated clinical rules.

Platform

Integrated modules, a single care workflow.

OncoTime connects chemotherapy scheduling, Cancer Patient Navigation (Law 14.758), and patient communication in a single platform. Each module has its own rules, roles, and reports; audit, permissions, and visual identity are shared.

Module · Scheduling

Chemotherapy with predictability.

For nursing teams to coordinate protocols, cycles, and daily capacity.

Illustrative example · synthetic data. Values and counts are fictitious; the Infusions today, Overdue, Due (7d), Active protocols, Scheduled patients (period × shift), Daily occupancy, and Chair occupancy today blocks (with identifiers C1..Cn and BED1..BEDn per wing — aligned with ANVISA Resolution RDC 220/2004) reflect the actual architecture of the dashboard.
01

Assisted scheduling

Dates, shifts, wings, chairs, and beds in a guided workflow driven by clinical rules, with capacity validation and inter-cycle interval checks.

02

Protocols and cycles

Support for multi-day regimens, batch creation, treatment classification, walk-in fitting, and formal protocol closure.

03

KPIs and reports

Dashboards for occupancy, no-shows, pending tests, lead time, and protocol output, with PDF and XLSX export.

Module · Cancer Patient Navigation

Law 14.758/2023 with real instrumentation.

For the patient navigator to follow the patient journey from triage to surveillance, with the legal deadline and categorized barriers.

04

Navigator worklist

Prioritized queue of active patients with deadline alerts under Brazilian Federal Law 12.732/2012 — 60 days from diagnosis to treatment start.

05

Phase-based journey

Triage, diagnosis, staging, treatment, surveillance (or palliative care), and closure — with validated transitions and an append-only history.

06

Barriers, tasks, and notes

Categorized records of barriers per Law 14.758, with operational tasks and append-only follow-up notes.

Module · Patient Communication

Patient communication on an official channel.

An auditable, LGPD-aware institutional WhatsApp channel. Reminders, confirmations, and alerts move off the nursing team's personal phones onto a channel with recorded opt-in, approved templates (HSM), and message custody under CFM Resolution 1,821/2007.

07

Unified inbox

Conversations in Open, In progress, Awaiting reply, Escalated, and Closed states, with Normal or Urgent priority. Operators reply inline; patients never access the app.

08

HSM templates and opt-in

Approved templates (Utility · Authentication) per registered number, opt-in recorded per patient, and Meta's 24-hour window respected. No silent outreach outside the official channel.

09

Cross-module escalation

Clinical conversations route to the Navigator; scheduling topics route to Reception; every handoff is audited. Communication with Scheduling and Navigation flows through events, with no direct coupling.

Operations

From prescription to surveillance, without changing tools.

Each module has its own workflow, but both share the same audit backbone, permissions, and visual identity. Delivered as a web application (PWA), installable on desktop and mobile.

Scheduling

  1. Step 01

    Plan

    Choice of protocol, cycle, wing, chair or bed, and treatment window.

  2. Step 02

    Synchronize

    Shift capacity, tests, concurrent radiotherapy, classification, and rules side by side.

  3. Step 03

    Track

    Status, patient history, audit log, and the day's KPIs.

Cancer Patient Navigation

  1. Step 01

    Onboard

    Patient registration, initial phase, and Law 12.732 (60-day) countdown.

  2. Step 02

    Coordinate

    Prioritized worklist, barrier records, tasks, and follow-up notes.

  3. Step 03

    Transition

    Phase changes with validation, append-only history, and documented closure.

Security and governance

Designed for sensitive health data.

Audit log, granular permissions, and explicit regulatory framing. Clinical and operational decisions remain traceable for later review.

Append-only audit log Status transitions, released test results, journey changes, and protocol closures recorded immutably. Corrections are logged as new entries — never overwrites (LGPD art. 11; CFM Resolution 1,821/2007).
Granular permissions Role matrix with per-module actions (Scheduling and Navigation), per role (nursing, navigation, management, quality), and per report. Each transition records the responsible user.
Data architecture On-premise deployment in the hospital data center, or dedicated cloud operated by Kalatha. Per-institution segregation (tenant), encryption in transit and at rest.
Legal compliance Brazilian Federal Law 14.758/2023 (Cancer Patient Navigation) and Law 12.732/2012 (60 days from diagnosis to treatment) instrumented per feature. ANVISA Resolution RDC 220/2004 reflected in UTAQ capacity.
Epidemiological privacy RAS-DATASUS export (Brazil's public health datalake reporting) with k-anonymity ≥ 5 — automatically suppresses cells with few patients to prevent re-identification through cross-referencing (LGPD art. 13).
Incident response Data Protection Officer (DPO) designated by contract with the controller institution. Notification to ANPD and to the data subject under LGPD art. 48 (within 72 hours of becoming aware of the incident, where applicable).

Continuous adequacy. We are in an active project to qualify for SBIS-CFM (NGS1/NGS2 Security Seal) and for the domains of ISO/IEC 27001 and 27701. We do not claim a seal that has not been issued — we describe status, scope, and timeline.

See full methodology →

Frequently asked questions

The questions that come up before "let's see a demo."

Short answers for those evaluating feasibility before bringing in the team. For technical and regulatory depth, talk to us.

What does deployment look like?

Phased, guided deployment: assessment of current operations, modeling of protocols and capacity, configuration of roles and audit, training by role (nursing, navigation, management), and assisted go-live. IT effort is light — the product is a web application (PWA), installable on desktop and mobile.

Where does the data live?

Two options: (a) dedicated cloud operated by Kalatha through an infrastructure partnership, or (b) on-premise in the hospital data center, with a dedicated deployment package. In both modes, sensitive health data is segregated per institution (LGPD art. 11).

Does it integrate with our current system?

We support PDF, XLSX, CSV, and JSON exports, and we are evolving integrations through HL7 FHIR R4 (Patient, Encounter, MedicationRequest, ServiceRequest, Observation, Task). For TISS scenarios and specific webhooks, we align scope during deployment. We do not promise "integrates with anything" — in the technical conversation, we say exactly what is native and what becomes a project.

How does support work?

Service in Portuguese, during business hours, with an urgent channel for incidents that affect clinical operations. SLA by severity is agreed in the contract. Versions and relevant changes are communicated in advance to the institution's team.

What is the investment?

Pricing on request — it varies with oncology volume, deployment mode (dedicated cloud vs. on-premise), and integration scope. We do not publish a price list because the operational design of each hospital is different; what we deliver is a tailored proposal after a discovery session.

Does it work offline?

As a web application (PWA), access depends on a connection. For hospitals with unstable links, we recommend on-premise mode: the application runs on the institution's network and downtime is limited to short windows of local maintenance.

Do you comply with Law 12.732/2012 (60 days)?

The Navigation module instruments the Law 12.732/2012 deadline with a per-patient countdown, alerts in critical windows, and categorized barrier records (Law 14.758/2023). Compliance depends on correct use of the product by the institution — the software provides visibility and instrumentation; operations belong to the clinical team.

How is sensitive data handled (LGPD)?

Append-only audit log of transitions and journey changes, granular per-module roles, corporate authentication, and epidemiological export with k-anonymity ≥ 5 (suppressing cells with few patients). For details, see the Security section — a dedicated privacy policy is available on request.

OncoTime

Bring clarity to your oncology routine.

A product that brings Chemotherapy Scheduling and Cancer Patient Navigation together in a single platform, with audit, granular permissions, and support for the deadlines of Law 12.732/2012. Tell us about your operation and we will walk through the modules in a guided session.

By submitting, you agree to be contacted by sales about OncoTime. We do not send automated newsletters and do not share your data with third parties.