Designing and expanding electronic symptom monitoring across oncology populations while balancing patient needs, clinical workflows, technology, staffing, and operational capacity.
Scaling ePROs in Oncology
Expanding electronic symptom monitoring across oncology populations is less a technology rollout than a series of trade-offs. Each new population brings different symptom profiles, different treatment rhythms, and different expectations about how often a patient can reasonably be asked to report. Each new site brings its own staffing, its own workflows, and its own history with the tools already in use.
My work in this area focuses on making those trade-offs deliberately. That means defining which patients are monitored and why, choosing instruments that are clinically useful without being burdensome, deciding how reports are routed and who owns the response, and setting expectations for response times that the team can actually meet.
It also means building the operational scaffolding that a pilot does not need but a program cannot live without: coverage plans, escalation paths, documentation standards, training for new staff, and a way to see how the program is performing across sites.