Medical Tracker

The description states that Medical Tracker is a mobile-responsive web application designed for informal caregivers managing complex medical regimens. It enables:

• Recording when medication has been given
• Logging symptoms, behavior, emotions and care updates
• Reviewing a shared chronological timeline
• Editing or deleting entries after mistakes
• Viewing historical data over time

It connects via Google Apps Script to a Google Sheet, which serves as the backend without requiring a central database. The frontend is built in React.

The author notes it was built using AI tools including Codex and GPT-5.6 Sol, with assistance from an implementation partner (Codex) and product thinking partner (GPT).

Inferred: It is not a commercial SaaS offering but rather an open-source tool intended for personal or family deployment.

The author positions Medical Tracker as a lightweight coordination tool for families managing complex care, particularly those with patients like cancer patients. The core value proposition is:

• A simple shared record that reduces reliance on phone calls or verbal handovers
• Designed to be fast and understandable under pressure
• Built without diagnostic or prescribing capabilities

The product evolved from a personal solution into an open-source project, with the author stating they “transformed something built for one family into an open-source project that other people can inspect, adapt and deploy.”

Inferred: The positioning has shifted from a private family tool to a reusable public resource, though there is no evidence of commercial intent or broader market traction.

The description states the target audience includes:

• Families coordinating care for individuals with complex medical needs (e.g., cancer patients)
• Informal caregivers, including those in different locations or countries
• People who need to track medication, symptoms and emotional changes

There is no evidence of segmentation beyond this general group. No specific personas, use cases or customer types are detailed.

Inferred: The ICP appears to be caregivers managing chronic or serious illness in a non-clinical setting — not healthcare providers or institutions.

The description states that Medical Tracker is open source, and the author mentions they “removed family-specific configuration” and documented how others can deploy their own version using Google Sheets and Apps Script.

There is no mention of any pricing model, monetization strategy, or paid features. The product is described as a tool for self-hosting rather than a hosted service.

Inferred: No business model is evident beyond the open-source sharing of code and documentation.

The project was built using:

• Frontend: React
• Backend: Google Apps Script connected to Google Sheets
• AI tools used: Codex, GPT-5.6 Sol
• Development approach: AI-assisted development with feedback loops from family members

The author reports that the first working version was ready in about one day, and it was iterated over three days based on real-world usage.

Inferred: The technical stack is minimal and self-hosted, which suggests low infrastructure costs but also limited scalability or enterprise-grade features.

The author states that the application was tested with family members actively providing care, and that it went unchanged for two months after initial refinement. However:

• There is no evidence of external users beyond the founder’s family
• No data on adoption, retention or usage frequency is provided
• No revenue, customer base or user metrics are mentioned

Inferred: The product shows early-stage maturity with internal validation but lacks any measurable traction.

The description does not mention competitors or similar tools. It also does not state whether there are existing solutions for family-based care coordination or medication tracking.

Inferred: No competitive analysis is evident, and the author does not reference prior art or market positioning against other tools.

• No commercial traction: The only users mentioned are family members; no evidence of broader adoption.
• Open-source nature: While this may reduce costs, it implies no direct revenue model or customer lock-in.
• Limited functionality: The tool is described as a record-keeping system without analytics, reminders or clinical integration.
• Self-hosted architecture: Reliance on Google Sheets and Apps Script raises concerns about data privacy, scalability and long-term maintainability.
• No validation with healthcare professionals: The product explicitly avoids clinical decision-making but lacks input from clinicians.

1. What is the actual user base beyond your family? Have others deployed this tool?
2. Are there any plans to monetize or scale this beyond open-source sharing?
3. How do you plan to address concerns around data privacy and security in a self-hosted model?
4. Has anyone from the healthcare community reviewed or validated the product?
5. What are the long-term maintenance challenges of relying on Google Sheets and Apps Script?