Your protocols, not ours
Upload care pathways as YAML. Piu follows your plan, not a generic one.
Piu Health runs your protocols, your medication regimen, and your rehab plan with your patient. You see the data when they come back.
FHIR R4 · SMART-on-FHIR · Epic + Cerner + Athena · HL7 v2
Upload care pathways as YAML. Piu follows your plan, not a generic one.
Per-patient MPR, vitals trends, PHQ-9 / GAD-7 deltas — directly in the EHR.
Post-procedure check-ins, day-1, day-3, day-7, day-14. Real-time escalation when something looks off.
Piu is your protocol on every day you don’t see the patient. It is not a clinician.
Piu detects a value outside your protocol bands. Example: home SBP 168 mmHg, three readings in 48h.
Piu pings your care-team inbox — not yours directly. Triaged by your MA or RN first.
When you open the patient chart, the escalation, the trend, and the patient’s own words are already there. FHIR Observation + Flag resources.
// Default thresholds ship with each pathway. Edit per panel or per patient.
You upload care pathways as YAML — your CHF discharge protocol, your post-op knee bundle, your T2D titration ladder. Piu executes step-by-step on the schedule you set. Version-controlled. Diffable. You own the source of truth.
pathway: chf_post_discharge_v2
author: dr_patel
day_1:
- weight_check: { time: "08:00", flag_if: ">2lb from baseline" }
- sbp: { time: "08:15", flag_if: ">140 or <90" }
- symptom_check: ["dyspnea", "edema", "fatigue"]
day_7:
- lab_reminder: bnp
- escalate_if: weight_trend_up OR sbp_uncontrolled// Sample. Real pathways are co-authored with your clinical team during onboarding.
Prefer not to write YAML? Build your pathway by describing it — no-code agent builder, early access →
App Orchard listed. SMART-on-FHIR launch from any patient chart. Writes back as Observation + Communication resources.
CDS Hooks subscription. Surfaces Piu summaries inline at patient open.
MDP partner. Reads problem list + medication list. Writes structured notes.
Anything FHIR R4 + HL7 v2. Six-week integration. We do the heavy lifting.
“Piu doesn’t try to be a doctor. It does the boring 364-day stuff so I can do the visit.”
“The handoff lands in our MA queue, not my inbox. That’s the whole game.”
“I write the protocol once. Piu runs it on every patient who fits the cohort.”
Early signal from our design-partner cohort. A controlled study is underway (n=400, A1c primary endpoint, readout 2026).
BAA signed. Clinical lead workshop to translate your existing protocols into YAML pathways.
SMART-on-FHIR app registered. Test patients flowing both ways. Your IT keeps the keys.
Piu runs on a pilot cohort. Escalations go to a parallel queue. You compare to standard of care.
Cutover to your full panel or service line. Weekly office hours with our clinical lead for 90 days.
Whitelist Piu inside your patient portal and we’ll co-brand the app for your system if you want it.
HIPAA-aligned · BAA-ready · SOC 2 in progress · Multi-tenant isolation · Model choice per tenant — your protocols and patient data never touch another system’s. Read the security brief →
Starting at $10 PMPM · EHR integration included · go-live in 6 weeks
Talk to clinical lead →