The polypharmacy problem.

It starts simply. A statin for cholesterol. An SSRI for the anxiety that follows a cardiac event. A PPI because the SSRI upsets the stomach. Melatonin because the PPI fragments sleep. Magnesium because the PPI is depleting it. A muscle relaxant because the magnesium isn't enough and the cramps are affecting the workout the cardiologist asked for.

Six medications. Three specialists. Each prescription is individually reasonable. Together, they form a cascade where the treatment for one side effect introduces the next condition. This is polypharmacy, and it is extraordinarily common in anyone managing more than one chronic issue.

Why it persists

Each clinician sees their own lane. The cardiologist adjusts the statin. The psychiatrist adjusts the SSRI. Nobody holds the full graph because no single appointment is long enough to audit it, and the patient's memory of 'when this started' degrades faster than the drug stack grows.

The problem isn't that clinicians don't care. The problem is that the information architecture around the patient doesn't support the question: 'What introduced what?'

What the engine does differently

Pivotical maintains a timestamped dependency graph of every medication, symptom, and lab result. When you add a new medication, the engine traces the chain backward: why was this prescribed? Was a symptom logged before it that correlates with an existing drug? Is this treating a root cause or a downstream effect?

The 32 clinical protocols inside the engine each carry an integrations block — nutrition contraindications, gym intensity caps, environment thresholds, timing anchors. When two protocols conflict, the engine surfaces the conflict as a structured event, not a buried footnote. Your ER brief, your caregiver's dashboard, and your next appointment all carry the same graph.

• 01Every medication carries a provenance: when it was added, what symptom preceded it, which protocol activated it.
• 02The trigger engine runs a reverse dependency check every 30 minutes — if a downstream drug can be reduced because the upstream cause resolved, it flags it.
• 03Sub-agents for nutrition, gym, and environment adjust their own recommendations in real time based on the current drug graph.

We didn't build this to replace a clinical audit. We built it to make the audit possible by giving the clinician — and the patient — a graph they can actually read.