Assisted scheduling
Dates, shifts, wings, chairs, and beds in a guided workflow driven by clinical rules, with capacity validation and inter-cycle interval checks.
Software for oncology operations
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.
Platform
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
For nursing teams to coordinate protocols, cycles, and daily capacity.
| Period | Day | Morning | Afternoon |
|---|---|---|---|
| Today | 42 | 24 | 18 |
| Week | 218 | 132 | 86 |
| Month | 812 | 512 | 300 |
| Tomorrow | 38 | 22 | 16 |
C1..Cn and BED1..BEDn per wing —
aligned with ANVISA Resolution RDC 220/2004) reflect the actual
architecture of the dashboard.
Dates, shifts, wings, chairs, and beds in a guided workflow driven by clinical rules, with capacity validation and inter-cycle interval checks.
Support for multi-day regimens, batch creation, treatment classification, walk-in fitting, and formal protocol closure.
Dashboards for occupancy, no-shows, pending tests, lead time, and protocol output, with PDF and XLSX export.
Module · Patient Communication
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.
Conversations in Open, In progress, Awaiting reply, Escalated, and Closed states, with Normal or Urgent priority. Operators reply inline; patients never access the app.
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.
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
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
Choice of protocol, cycle, wing, chair or bed, and treatment window.
Shift capacity, tests, concurrent radiotherapy, classification, and rules side by side.
Status, patient history, audit log, and the day's KPIs.
Security and governance
Audit log, granular permissions, and explicit regulatory framing. Clinical and operational decisions remain traceable for later review.
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
Short answers for those evaluating feasibility before bringing in the team. For technical and regulatory depth, talk to us.
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.
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).
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.
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.
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.
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.
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.
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
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.