Development
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
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.
Necessary
Required before treating DrugsRS as a durable, account-based health application.
Cognito provides verified email/password identity, while a JWT-protected DynamoDB service stores each account’s medication and optional patient record. Browser health-data persistence is disabled. Formal audit, retention, export, consent, compliance, and operational controls remain necessary.
Determine the project’s covered-entity and business-associate responsibilities, then implement the required administrative, physical, and technical safeguards with qualified legal and security guidance.
Define consent, data retention, deletion, auditability, incident response, threat modeling, terms, privacy disclosures, secure operations, and an ongoing vulnerability-management process.
Create a clear print view of every current medication, its dosage amount, and its schedule, followed by an appendix of the known mixing, patient, food/product, and substance risks identified for that plan.
Considered ideas
Features that could reduce manual work and help patients or caretakers follow a complete plan.
Send reminders through SMS and potentially other channels, such as phone calls, then record acknowledgement from the patient or caretaker that a dose was consumed or administered.
Estimate when a prescription may run low and provide timely prompts to review remaining supply and refill status.
Explore secure pharmacy connections that could submit refill requests after explicit patient approval and show request status without implying guaranteed fulfillment.
Bootstrap the Medication Manager from available clinical data and optionally keep it synchronized. Imported records would remain only one input: this is a patient-controlled tool that must also retain over-the-counter products, supplements, and disclosed recreational-drug use that may be absent from a clinical chart.
Stretch ideas
Longer-range concepts that need careful validation, moderation, safety boundaries, and privacy design.
Let people share successes, surprises, and warnings while actively limiting medical misinformation, self-diagnosis, unsafe advice, harassment, and claims that cannot be responsibly moderated.
Use image recognition and text extraction to prefill medication, prescription, and schedule details from a bottle photo, with mandatory user verification before anything enters the plan.
Record what was actually consumed or administered—not only what was scheduled—and make missed, late, skipped, or uncertain entries explicit.
Maintain an audit history and timeline or Gantt-style view of starts, stops, dosage changes, overlapping medications, and the source of each change.
Capture patient observations such as how a drug felt, whether it seemed helpful, unexpected effects, questions for the next appointment, and experiences worth discussing with a clinician.