Medication plan and schedule
Maintain current medications, dosage, purpose, timing, clinician-administered treatments, allergies, and a clear view of what is scheduled today.
Development
Building DrugsRS in the open
This site is a work in progress. The roadmap separates the foundation required for responsible multi-user use from possible next steps and longer-range ideas.
Current status
Useful today, but not yet a production health platform
The current experience is an educational prototype. Amazon Cognito identity and encrypted, account-owned medication records are implemented, and medication or patient data is not retained in browser storage. Formal compliance controls and production-grade legal, privacy, audit, security, and clinical-governance systems are still prerequisites before real-world health use.
Product direction
A simple medication core, with optional features around it
The Medication Manager should remain useful on its own. More specialized capabilities—such as closed-loop reminders, drug-mixing analysis, cognitive or motor tracking, and future integrations—should be separate features that a person can opt into only when they are useful.
Default experience
Keep medication management focused
The default experience should answer a small set of everyday questions without requiring people to configure unrelated features.
Essential safety context
Surface relevant patient, allergy, food, substance, and medication risks without forcing the user through every advanced analysis tool.
Account, privacy, and governance
Continue strengthening account-owned records, export and deletion controls, auditability, security operations, consent, and the legal and compliance foundation needed for real-world use.
Portable medication summary
Keep a concise printable/shareable medication plan available without requiring enrollment in reminders, tracking, or other modules.
Choose what helps
Separate specialized capabilities into opt-in features
Advanced workflows should behave like modules: discoverable when needed, quiet when not enabled, and removable without disrupting the medication plan.
Closed-loop reminders
An optional reminder feature for SMS or other channels, dose acknowledgement, caretaker participation, missed-dose follow-up, refill prompts, and actual-dose history.
Drug Mixing Risks
An optional deeper interaction workspace for comparing medications, recreational substances, foods, selected doses, and source-backed risk information beyond the concise warnings shown in the core plan.
Cognitive and motor tracking
An optional companion feature or app that records cognitive or motor performance over time and lets the user compare trends with medication and dosage history. It should clearly distinguish observations from validated clinical conclusions.
Medication journal and outcomes
An optional place for symptoms, perceived benefit, side effects, questions, and personal observations, kept out of the primary medication workflow unless the user enables it.
Optional connections
Add integrations without turning the core into a control panel
Connections should reduce data entry or add context, while remaining independently enabled and clearly separated from the everyday medication experience.
Prescription capture
Optionally scan a bottle or label to prefill medication details, with user verification before information enters the plan.
Health-record and pharmacy connections
Optionally import clinical medication data or support refill workflows while preserving patient-entered over-the-counter, supplement, and substance information.
Longitudinal analysis
For users who opt in, correlate medication changes, adherence, observations, and cognitive or motor trends over time without presenting correlation as proof of causation.
Feature-level onboarding and controls
Give each optional capability its own explanation, permissions, settings, and off switch. The user should never need to understand every feature in order to use one.