Patient-reported outcomes (PROs)
PRO-CTCAE, EORTC QLQ-C30, and custom PRO instruments with adaptive scheduling and threshold-based escalation.
What We Do: Healthcare Expertise
Oncology & Chronic Disease Platform Engineering
A cancer diagnosis is one of the hardest journeys a patient can face - the software should not add to it. We build oncology and chronic disease platforms that handle multi-phase treatment plans, symptom tracking, and multi-provider coordination as first-class workflows.
What is oncology software?
Oncology software manages the parts of cancer care that span many visits and teams: multi-cycle treatment plans, dose changes, symptom reports between visits, lab trends and survivorship follow-up. Agnotic Technologies builds oncology and chronic disease platforms for digital health companies and cancer centers, connected to the EHR through FHIR R4 and HL7 v2.
| Capability | Implementation focus | Care outcome |
|---|---|---|
| Treatment plan management | Phased protocols, cycle scheduling, dose modifications, and audit-tracked plan changes across the care team. | Aligned treatment execution across oncologists, infusion teams, and primary care providers. |
| Symptom and side-effect tracking | PRO-CTCAE-aligned questionnaires, escalation rules, and longitudinal symptom dashboards for the care team. | Earlier intervention on toxicities and improved between-visit quality of life. |
| Chemotherapy adherence | Oral chemotherapy dose tracking, missed-dose escalation, and pharmacist-led adherence outreach workflows. | Higher completion of prescribed regimens and earlier outreach for at-risk patients. |
| Lab and biomarker visualization | Tumor marker trends, CBC and metabolic panel charts, and threshold alerting tied to treatment decisions. | Clinicians see meaningful trends instead of scrolling through raw result lists. |
| Multi-provider care coordination | Shared care plans, role-aware task lists, secure messaging, and event-driven status updates across teams. | Reduced coordination burden and fewer dropped handoffs between specialties. |
| Survivorship planning | Post-treatment surveillance schedules, late-effect screening, and long-term wellness check-ins. | Continuity of care beyond active treatment with documented survivorship plans. |
What we build for oncology teams
Production-grade capabilities we deliver across oncology, chronic disease, and complex care management products.
Care team collaboration
Shared care plans, structured handoffs, and role-aware inboxes for oncology, infusion, pharmacy, and primary care teams.
EHR-connected dashboards
Bidirectional sync with Epic, Oracle Health (Cerner) and athenahealth covering problems, medications, labs, and care plan updates.
Clinical trial matching
Eligibility screening pipelines that surface relevant trials to patients and care teams using structured clinical data.
How do we model treatment plans?
How we model oncology and chronic disease protocols so they remain maintainable as evidence evolves.
- Protocol templates with versioning, cycle definitions, and dose modification rules
- Lab-driven dosing logic with explicit hold and resume criteria
- Plan change audit trails capturing clinician, rationale, and effective dates
- Patient-facing views that translate clinical plans into plain language
How do symptom reports reach the right clinician?
Patterns we apply to make symptom data actionable for the care team.
- Severity-graded PRO responses with structured triage rules
- Care team routing aligned to coverage schedules and on-call rotations
- Closed-loop documentation back into the EHR for visit context
- Trend analysis across symptoms, vitals, and treatment cycles
Oncology platform failures we help prevent
Patterns we repeatedly see in oncology and chronic disease platforms that lead to coordination breakdowns.
Treatment plans modeled as free text
Impact: Dose changes are invisible to other providers and reporting becomes unreliable.
Mitigation: Structured protocol templates with versioning, dose modifiers, and machine-readable change logs.
Symptom data captured but not acted on
Impact: Patients submit PROs that never reach the right clinician in time.
Mitigation: Severity-graded triage rules, care team routing, and closed-loop EHR documentation.
Disconnected pharmacy and lab data
Impact: Oral chemotherapy adherence and dose adjustments lack the clinical context to be safe.
Mitigation: Bidirectional pharmacy and lab integration with explicit hold and resume criteria.
Facts and sources
Which standards and rules shape oncology software?
Short facts we design oncology data models and safeguards around, each linked to its primary source.
mCODE (minimal Common Oncology Data Elements) is an HL7 FHIR implementation guide that assembles a core set of structured data elements for oncology electronic health records.
Source: HL7 FHIR mCODE Implementation GuideHHS adopts the United States Core Data for Interoperability (USCDI) as the standard set of health data classes and data elements for certified health IT.
Source: 45 CFR 170.213 (eCFR)The HIPAA Security Rule requires administrative, physical and technical safeguards for electronic protected health information.
Source: 45 CFR Part 164 Subpart C (eCFR)
Frequently Asked Questions
Yes. The protocol, symptom-tracking, and care-team models we use generalize across oncology, transplant, autoimmune, and chronic disease workflows with role and content variation by program.
Yes. We use FHIR R4, HL7 v2, and SMART on FHIR for embedded contexts. We have implementation patterns for medications, observations, conditions, care plans, and document workflows.
Protocol templates are versioned, with safe migration paths for in-flight patients. Evidence updates can be applied at the program level without breaking active treatment plans or audit history.
It depends on how many treatment protocols the first release models, which patient-reported outcome instruments it uses, which EHR and lab systems it connects to and whether patients, clinicians or both use it. A single program on one EHR moves fastest. We give you a scoped plan after the scoping call.
Yes. Treatment plans, symptom reports and lab results are protected health information, so Agnotic signs a business associate agreement before any PHI is shared with our team. HIPAA-ready oncology software then needs role-based access, an audit log on every plan change and encryption of symptom and lab data.
Yes. A first release covers one workflow, such as weekly symptom reporting for patients on one treatment protocol, with triage rules and EHR documentation working end to end. Treatment plan management and survivorship care follow in later releases.
AI tools help our engineers draft code and tests, but a person reviews every change, and it passes the same automated tests and security checks as any other code. Which tools may see your code or data is agreed with you at the start.
Need an oncology platform that actually coordinates care?
Get a practical review of treatment plans, PROs, and EHR integration with a roadmap your engineering team can execute.
contact@agnotic.com
Partnerships
contact@agnotic.com