ClinBridge logs your blood pressure, heart rate, weight, fluid intake, symptoms, medications, meals, and activities — then analyzes the patterns over time so you and your cardiologist have real evidence to work from, not just a single office reading.

Four Advanced Analytics detectors continuously watch for clinically meaningful changes: sustained heart rate shifts, decompensation warning signs, pulse pressure trends, and symptom convergence patterns. Sentinel goes further — it watches for the personal pre-event patterns that came before your own prior clinical events, not population averages. When any tool finds something significant, it tells you what was found and why it matters — in plain language.

ClinBridge is a pattern awareness tool, not a diagnostic device. It does not diagnose, prescribe, or replace your care team. All findings are described as directional — they point toward patterns worth discussing with your cardiologist, never toward a conclusion. The phrase you will see throughout the app: "Math is directional, not definitive."

• Getting Started — Your name, your conditions, and your doctor's BP targets. Then start logging — the app guides you from there.
• How to Use — Daily workflow, doctor appointment prep, and the five detector tools
• 📌 Pinned Events — Your most powerful clinical tool for doctor appointments
• 🌅 Morning Check-In — How fluid and lifestyle pattern tracking works
• 🌡️ Heat Advisory — What to do on hot or humid days as a cardiac patient
• 🛡️ Sentinel — Personal pattern precursor — watches for what came before your prior events
• 💬 Ask — Ask plain-English questions about your logged data, detector findings, or any ClinBridge feature — AI-powered, privacy-preserving
• FAQ — Common questions answered plainly
• 📖 Glossary — Definitions for every clinical term and app phrase used in ClinBridge
• Data Mgmt — How to back up, export, and protect your data
• Privacy — How your data is stored, who can see it, and the medical disclaimer
• Known Issues — Bug fix history. If something seems wrong, check here first.
• ☕ Support — ClinBridge is free. If it helps you, a small contribution means a lot.

Your doctor asked you to track your blood pressure — start there. Log it every time you take a reading using the Log Blood Pressure button on the main screen.

If your doctor also mentioned fluid intake, weight, or symptoms — turn those on in Settings → Tracking Features. Each one adds a button to the main screen.

Everything else can wait. The more you log, the more ClinBridge learns about your patterns — and it will let you know when a new feature is ready to be useful to you.

As your data builds, Sentinel — the status banner on your main screen — will periodically surface one suggestion at a time. Not a list of everything the app can do. Just the one thing that's most useful to you right now, based on what you've already logged. Tap the banner anytime to see it.

Use the full setup guide below to configure everything at once — medications, daily schedule, notifications, and advanced features.

1. Morning Check-In — Tap the yellow banner at the top each morning. 45 seconds. Records how you feel and yesterday's context for pattern tracking.
2. Log BP — Use the Log Blood Pressure button after taking your reading. Tag it to a medication or activity if relevant.
3. Log Fluid — Every time you drink something, tap Log Fluid or use the event buttons. The progress bar updates in real time.
4. Log Meds — Mark each scheduled medication as taken when you take it. ClinBridge tracks adherence automatically.
5. Events fire as reminders — Set up timed events in Settings (Morning Meds, Lunch, Evening Walk, etc.) and the app will prompt you at each one.

1. Open Advanced Analytics — set the date range to cover since your last visit.
2. Tap Generate Doctor's Report — reviews BP trends, medication adherence, symptoms, fluid behavior, and morning patterns in one printable document.
3. Bring the report or show it on your phone/tablet during the appointment.

Sentinel is separate from the four detectors and works differently. Instead of watching for population-based thresholds, it watches for your personal pre-event patterns. Every time you pin a clinical event, Sentinel extracts what your data looked like in the 72 hours before it — your Footprint. When your live data resembles a prior Footprint, Sentinel tells you which event it matches and how. Tap 🛡️ Sentinel on the main screen to open it. See the 🛡️ Sentinel tab in this guide for the full explanation.

1. Set up a weekly backup event in Settings — it will remind you every week and let you export with one tap from the notification.
2. Use Device Sync & Backup → Export ALL Data before updating the app or switching devices.
3. If you use ClinBridge as a Home Screen icon on iPhone — always export before deleting the icon, as removing it erases all local data.

• Turn features on/off in Settings based on what your doctor has asked you to track.
• Set your BP target ranges in Settings so the app can color-code readings correctly.
• The Fluid Budget Dashboard lets you allocate your daily fluid goal across events so you pace intake throughout the day.
• Log symptoms with a severity rating — the Doctor's Report uses this to flag high-severity episodes for your cardiologist.
• Activity Timer: Use the timer in Log Activity to time workouts in real time. Tap ⏸ Pause to freeze the clock if interrupted — a PAUSED label confirms it's stopped. Tap ▶ Resume to continue, then ⏹ Stop & Use to save the full elapsed time.
• HR Rate Detector — Quick Stats: Open HR Rate Detector and use the Today / 7 Days / 30 Days / All Time buttons to analyse your heart rate trends across any time window. The chart scrolls horizontally for multi-day views and shows date labels so you can pinpoint when patterns occurred.
• Viewing history for any card: Each main page card (Blood Pressure, Weight, Symptoms, Activities, Meals, Medicines) has a 📋 View History button in its header. Tap it to see up to 90 days of entries in that card only — no other cards are affected. Tap ← Back to Today inside the card to return. Only one card can show history at a time.
• Correcting past weight entries: Tap ✏️ Edit Past Entries on the Weight card header to open 90-day weight history. A 🗓️ Jump to date picker lets you navigate directly to any date. Entries that deviate significantly from your 7-day rolling average are automatically flagged — yellow ⚠️ for 10–19 lbs off, red 🚨 for 20+ lbs — so data entry errors are easy to spot without scrolling through every record.

Analyzes your full HR history to find level shifts — periods where your resting heart rate durably changed to a new baseline — and rapid changes — sudden single-session jumps. Requires 6+ days of HR readings. Use the Today / 7 Days / 30 Days / All Time buttons to narrow the window. A "🔍 Investigate" button on any finding opens Anchor Date Investigation for that exact date.

Monitors five clinical signals simultaneously: weight gain, cardiac output (HR + pulse pressure), symptom frequency, fluid intake patterns, and notes keyword scan. Each signal is scored individually. The composite result ranges from ✅ All Clear → 📋 Early Indicator (1 signal) → ⚠️ Monitor Closely (2+ signals) → 🚨 Contact Cardiologist (multiple red signals). One signal alone is not cause for alarm — the value is in seeing multiple signals converge.

Pulse pressure is systolic minus diastolic BP. Normal range is 40–60 mmHg. A narrowing trend can indicate the heart is working harder to maintain output; a widening trend may indicate arterial stiffness. Many cardiac patients have a chronically reduced PP that is their personal baseline — the detector recognizes this and labels it "Chronically Narrow — Your Stable Baseline" rather than an acute alert. What matters is change from your baseline, not comparison to a textbook number.

Analyzes 30 days of symptom logs across three layers: (1) Intraday clusters — 3+ symptoms within a 4-hour window on the same day; (2) Multi-day escalation — the same symptom worsening in severity across multiple days; (3) Clinical triads — recognized symptom combinations with known cardiac significance (e.g., shortness of breath + fatigue + edema). The 60-day Timeline tab shows where clusters occurred visually.

When any detector finds a significant event (yellow or red), it suggests pinning it. Pinned events are saved permanently — they never roll off with the 90-day data window. Each pin captures the detector's full finding plus all raw log data for that date.

Pinned events appear in three places: the 📌 Pinned Events button in Analytics, the 60-day Timeline as amber markers, and your Doctor's Report as a dedicated section.

After your cardiologist appointment: use "Archive & Clear" to permanently save the current pins and start fresh for the next period. An appointment nudge reminds you automatically.

All four detectors use statistical pattern detection on self-reported data. The math is directional, not definitive. A finding means: "this pattern is present in your data and worth discussing." It does not mean: "something is wrong." Findings can reflect real clinical changes, data entry errors, device variability, or normal day-to-day fluctuation. Your cardiologist provides the clinical interpretation — ClinBridge provides the data and the pattern recognition to make that conversation more productive.

A Pinned Event is a flagged finding from one of ClinBridge's four detectors — captured permanently, along with the full raw data behind it, so it never disappears when your 90-day rolling window advances. It is the difference between "I thought I noticed something" and "here is the exact date, the exact reading, and every data point around it."

Any single detector firing on any single day is background noise. What ClinBridge watches for is convergence — two or more independent detectors flagging the same time window from different directions. When your HR level-shifts and your pulse pressure narrows and your symptom frequency rises in the same week, that combination is clinically meaningful in a way that no individual reading can be.

A single yellow flag: worth watching. Three yellow flags on the same week: worth showing your cardiologist.

Open Pinned Events before your appointment. Each detector-backed pin card now shows a “What to Say at Your Appointment” box with a pre-written sentence generated directly from your detector data. You do not have to figure out how to explain it — just read it aloud exactly as written.

After reading, ask: “Does this line up with anything you’re seeing in my chart? Is it worth investigating further, or is it within normal variation for my condition?”

The sentences in the “What to Say” box are generated entirely from detector data — not from your written notes or your memory. You cannot edit them, and that is by design.

This means the app stands behind every word it generates. If you choose to say something different at your appointment, that is your right — but the documented, data-backed language is always there as your record. A cardiologist reading a timestamped, algorithm-generated sentence weighted by your personal baseline carries more clinical credibility than a patient’s self-description.

A patient using ClinBridge chose to share their experience and gave permission for it to be discussed here. They have a pacemaker and had been logging their heart rate daily for several weeks. The HR Rate Detector identified a durable level shift — a point where the resting heart rate had measurably settled into a new, stable baseline distinctly different from the weeks before it. The change wasn't a single bad reading. It was a sustained pattern across multiple days that the algorithm confirmed as statistically significant.

The pacemaker's remote monitoring system reviewed the same time period during its scheduled download. It did not flag the shift. The clinical team saw nothing requiring follow-up.

The patient brought the Pinned Event to their next cardiology appointment and read it aloud. The cardiologist reviewed the supporting data, confirmed the shift was real, and ordered follow-up testing. The window between device downloads — where most of daily life happens — is exactly the gap that self-logged, multi-stream data is built to fill.

• Archive after your appointment — once your cardiologist has reviewed the pins and either acted on them or noted them, use "Archive & Clear" to permanently save that period and start fresh for the next visit cycle.
• Keep active during a workup — if tests are pending or a diagnosis is not yet finalized, leave pins in place. They are part of the active clinical record and should remain readable until you have an answer.
• Mark addressed, don't delete — if you've discussed a pin and your doctor said it was benign, mark it Addressed rather than deleting it. The historical context is still valuable if a similar pattern returns later.

Your heart already works harder than most. In hot weather, it must also pump extra blood to your skin to cool your body — on top of whatever activity you're doing. This dual demand can trigger dangerous drops in blood pressure, arrhythmias, or acute decompensation, especially with conditions like heart failure, hypertension, or a pacemaker/ICD.

ClinBridge automatically matches conditions in your profile against a list of cardiac and metabolic conditions known to increase heat risk: Heart Failure, Hypertension, Atrial Fibrillation, Coronary Artery Disease, Pacemaker/ICD, Cardiomyopathy, PAD, Diabetes, CKD, COPD, Obesity. Any custom conditions you've entered are also included.

• Pre-hydrate: drink 8–16 oz of water before going outdoors
• Avoid peak heat hours: 10 AM – 4 PM
• Cool down for at least 10 minutes after exercise before re-entering an air-conditioned space
• Watch for warning signs: dizziness, excessive sweating, flushing, rapid or irregular heartbeat, chest discomfort
• Inform your cardiologist of any new symptoms that appeared during or after heat exposure

When your doctor says "50 oz of fluid per day," they're giving you a safe baseline number — typically set for your average conditions. They're usually not accounting for your activity level that day, how many hours you'll be awake, whether it's hot outside, or how well you slept the night before. Your body's actual fluid needs vary with all of these things.

ClinBridge can't tell you whether to exceed your limit. But it can track what happens when you do — and over time, build a pattern that you and your doctor can review together to get you a more personalized recommendation.

ClinBridge records your self-reported data and identifies patterns. It does not recommend specific fluid amounts, tell you whether to exceed your prescribed limit, or replace your care team's guidance. Use the patterns you collect to have a better-informed conversation with your cardiologist — not to make independent medical decisions.

Morning Check-In is on by default. To turn it off: Settings → Features → uncheck "🌅 Morning Check-In & Pattern Tracking." When off, no prompt appears and no data is collected. If you turn it back on, previously collected check-ins are still available and will appear in future reports.

Yes — always export your data before updating. Go to Device Sync & Backup → Export ALL Data and save the file. Then update, then import your data back. This takes about 60 seconds and protects everything you've recorded. The app will show you an update banner and walk you through the steps.

At minimum, before any app update and once a week as a habit. Also back up before clearing your browser cache or before deleting the ClinBridge icon from your Home Screen — both of those actions erase your local data. Go to Device Sync & Backup → Export ALL Data.

After importing, the app reloads automatically. If your data still doesn't appear: close the app completely and reopen it. On any phone or tablet, close the app fully and reopen it. On any desktop or laptop browser, close the tab and open a fresh one at clinbridge.clinic. On iPhone/iPad specifically, swipe up from the bottom and swipe away ClinBridge before reopening. Your .json backup file is safe — you can import it again as many times as needed on any device.

Not automatically — you need to export before updating and import after. This is intentional: ClinBridge never moves your data without you taking a deliberate action. Your health data stays under your control at all times.

ClinBridge has four pattern detectors that analyze your historical data — not just today's readings. The HR Rate Detector finds sustained heart rate shifts and sudden changes. The Decompensation Warning monitors five clinical signs of CHF fluid overload building simultaneously. The Pulse Pressure Detector tracks the gap between your systolic and diastolic readings as a cardiac output indicator. The Symptom Convergence Detector finds clusters, escalations, and clinical patterns across your symptom history. All four are in the Analytics section of the main page.

When a detector finds a significant pattern, it suggests pinning it. A pinned event is permanently saved — it never disappears when your 90-day data window rolls forward. It captures the detector's finding, the event date, and all the raw data (BP readings, symptoms, weight, notes) from that day. Pinned events appear in your Doctor's Report as a dedicated section, in the 60-day Timeline as amber markers, and in the Pinned Events viewer under Analytics. Think of pins as your pre-prepared clinical evidence for your next cardiologist appointment.

After your appointment, open the Pinned Events viewer and tap "Archive & Clear." This permanently saves all current pins to an archive (you can always view them), then clears your active list so the next period starts fresh. ClinBridge will remind you automatically — if you have an upcoming appointment within 14 days, or if you just had one this week, a banner appears on the main page and inside the Pinned Events modal. If no appointment is logged but your oldest pin is 60+ days old, you'll see a gentle nudge to archive and refresh.

It means ClinBridge's detectors can tell you that a pattern exists in your data — but they cannot tell you why it exists or what it means for your specific medical situation. A detected HR level shift is real math — but it could reflect a clinical change, a medication adjustment taking effect, seasonal variation, or something entirely benign. Your cardiologist provides the interpretation. ClinBridge provides the evidence and the pattern recognition to make that conversation richer and more productive than walking in with just a blood pressure number.

ClinBridge keeps 90 days of rolling data on your device. For long-term preservation, export your data as a backup at the end of each quarter — the last day of March, June, September, and December. Save these files somewhere safe (iCloud, Google Drive, email to yourself). A new cardiologist years from now could import your Q3 2026 backup and see your complete cardiac picture from that period. Pinned events in each backup capture the most significant findings for that quarter, pre-annotated for clinical review.

No — ClinBridge findings are not emergency indicators. A red finding means the pattern in your data is statistically significant and worth discussing with your cardiologist promptly — not that you are in immediate danger. If you are experiencing chest pain, severe shortness of breath, sudden dizziness, or other acute symptoms, call 911 or go to an emergency room regardless of what ClinBridge shows. ClinBridge is for pattern tracking over time, not acute symptom assessment.

ClinBridge stores everything — your blood pressure readings, symptoms, medications, weight, fluid logs, notes, and pinned events — exclusively in your browser's local storage on the device you are using right now. There is no server. There is no account. There is no cloud sync. Nothing you enter is ever transmitted anywhere.

• Health data you enter manually: BP readings, symptoms, weight, fluid intake, medications, activities, meals, notes
• Settings and preferences you configure: conditions, BP targets, fluid limits, event schedules, medication list
• Pinned events and their communication logs — stored locally and included in your exported backup file
• Anonymous usage analytics (Google Analytics 4) — page views, feature usage, general app performance. No personally identifiable information, no health data values.

• Never sends your health data to any server, database, or third party
• Never creates an account, requires login, or tracks your identity
• Never sells, shares, or monetizes your information in any form
• Never displays advertisements
• Never requires an internet connection to function — works fully offline after first load

Only you — on the device where ClinBridge is installed. If you export your data and share the .json file with someone (a family member, caregiver, or doctor), that person can import and view it. That sharing is entirely under your control and only happens when you initiate it.

If you add ClinBridge to your Home Screen on iPhone or iPad, be aware that the local storage is tied to that browser and device. Removing the icon erases the stored data. Always export a backup before removing the icon or clearing browser data.

ClinBridge was built by a cardiac patient after a hospitalization, motivated by a simple question: why isn't there a tool that tracks all the things my cardiologist actually needs to see — BP trends, symptoms, fluid balance, medication adherence, and pattern detection — in one place, for free, without giving up my health data?

The answer was to build it. The privacy model — all data on-device, no accounts, no servers — is not a limitation. It is a deliberate choice rooted in the belief that your cardiac health data is yours, belongs to no one else, and should never become a product.

ClinBridge is a personal health tracking tool, not a medical device. It is not FDA-cleared, CE-marked, or certified as a clinical diagnostic system. It does not provide medical advice, diagnosis, or treatment recommendations.

Accuracy statement: All pattern detection is statistical and based on self-reported data. Findings are directional, not definitive — they identify patterns worth discussing with your cardiologist, not conclusions about your medical condition. Results may be affected by data entry errors, device measurement variability, and individual clinical factors the app cannot account for.

Always consult your cardiologist or other qualified healthcare provider before making any changes to your care plan based on information from ClinBridge.

🔄 Reset Today's Data

Removes only today's BP readings, symptoms, meals, activity, dismissed events, and daily plan. Your settings, medications, procedures, appointments, and all previous days are kept.

⚠️ Delete ALL Data on This Device

Permanently erases everything: all daily readings (every day), settings, medications, procedures, appointments, custom symptoms/activities, analytics notes, and reminders. The app will return to a fresh-install state.

💾 When to Back Up Your Data

Your data lives only on this device. Back up regularly so you never lose it.

• Before every app update — always export your data before installing a new version
• Before clearing browser cache — clearing Safari or Chrome data wipes ClinBridge data too
• Before deleting the Home Screen icon — removing the icon erases all data on iOS
• Weekly — as a general habit, export once a week for peace of mind

How to back up: Go to Device Sync & Backup → Export ALL Data. Save the .json file to your Files app, iCloud, or email it to yourself.

🔄 How to Update to a New Version

When a new version is available, the app will show a banner at the top. Follow these steps in order — skipping step 1 risks losing your data.

1. Export your data first — Device Sync & Backup → Export ALL Data → save the file
2. Tap the update banner and follow the instructions to open the new version
3. Once the new version loads, go to Device Sync & Backup → Import All Data
4. Select your saved .json file — your data will be restored
5. Verify your readings and settings appear correctly before using the app

📥 If Your Imported Data Doesn't Appear

After importing, the app reloads automatically. If your data still doesn't appear:

• Wait for the page to fully finish reloading before checking
• If data is still missing, close the app completely and reopen it
• On iPhone: swipe up from the bottom, swipe away ClinBridge, then reopen
• On Chromebook: close the tab and open a fresh one at clinbridge.clinic
• If data still doesn't appear, try the import again — your .json file is safe to re-use

• 💬 Ask ClinBridge — Usage analytics added. Three GA4 events now fire through the existing cbTrack() system: ask_panel_opened (each time the Ask panel is opened — measures session frequency), ask_question_submitted with session_q_count parameter (each question sent — counts total volume and questions-per-session depth), and ask_answer_received with session_q_count (each successful answer — measures completion rate vs abandoned questions). A per-session counter _askSessionQuestionCount resets each time the panel opens, enabling average questions per session to be tracked in GA4. This data supports future rate-limit decisions without guessing at real usage patterns.

• 💬 Ask ClinBridge — BP data context bug fixed. BP readings were serializing as undefined/undefined in the data context sent to Ask, making all BP-related questions unanswerable. Root cause: buildAskContext() was reading r.sys, r.dia, r.hr, and r.time but the BP reading object stores these as r.s, r.d, r.h, and r.t respectively. The same mismatch affected the historical average BP calculation. Also fixed: weight time field (lw.time → lw.t). All BP data, heart rate, and weight timestamps now serialize correctly into Ask context.
• 💬 Ask ClinBridge — Meal data added to context. Meals were entirely absent from Ask context. Ask could confirm meals tracking was enabled but could not see any logged entries, making questions like “has skipping snacks affected my BP?” impossible to answer. Fixed: today’s meal log (from in-memory M array, field m for name, t for time) and up to 20 meals from the last 14 days (from getAllHistoricalData().meals) are now included in context.
• 💬 Ask ClinBridge — Full context audit: symptoms, medications, and pinned events fixed. A complete audit of buildAskContext() revealed that every data type except fluid total and notes had wrong field names. Symptoms used s.name (should be s.symptom) — both today’s and 14-day history. Medications used m.name (should be m.medicine) and a nonexistent m.dose field (replaced with m.time). Pinned Events used p.date, p.doctor, and p.status which do not exist as top-level fields — corrected to p.eventDate, p.commLog.to, and p.commLog.status respectively. Pinned Event p.summary (the detector’s clinical summary text) and question responses (q.response) are now also included in context. All Ask questions involving symptoms (“what symptoms have I had?”), medications (“what did I take today?”), and pinned events (“what do I need to discuss with my doctor?”) now receive accurate data.

• 💬 Ask ClinBridge — Conversational data & feature assistant. A floating 💬 Ask button now lives on the main screen at all times. Tap it to open a conversation panel where you can ask plain-English questions about your logged data (BP, fluid, weight, HR, symptoms, notes, medications, meals), how any ClinBridge feature works, patterns you see, and more. Ask has full awareness of everything you have logged today and in recent history, including your notes. If your question is unclear, Ask offers 2–3 tappable rephrased options. Answers stay in a threaded conversation so you can ask follow-ups without starting over. Ask never diagnoses or interprets readings medically — it redirects those questions warmly to your cardiologist. A new 💬 Ask tab in Help & About (next to Sentinel) explains the feature in full with real examples. Powered by Claude AI via a privacy-preserving Cloudflare Worker proxy — your data is never stored.
• 🔧 Ask panel — Today’s Status button collision fixed. The floating Today’s Status button was visible behind the Ask panel and overlapping the Ask send button. Today’s Status is now hidden automatically when the Ask panel opens and restored to its correct state when the panel closes.
• 📱 Today’s Status button reappearing behind Ask panel on iPhone PWA — fixed. The standalone scroll listener managing the Today’s Status FAB checked only .modal elements for open-state, not the Ask panel. On iPhone PWA, scrolling within the fixed Ask sheet still fires window.scroll, which re-showed the FAB when scrollY > 300px because the Ask panel is not a .modal. Fix: scroll listener now also checks askPanel.style.display, matching the existing _syncFab() logic. Belt-and-suspenders: FAB z-index reduced from 999999 to 999985 (below the Ask backdrop at 999989) so it can never float above the Ask panel regardless of timing.

Clinical Event & Appointment Intelligence — 4 New Nudge Rules — Closes the gap between clinical events that happen in the real world and the data ClinBridge needs to stay accurate. New helper function _openSentinelToEventLog() deep-links directly into Sentinel and opens the Clinical Event Log form, scrolling it into view (400ms deferred after render). Four new NUDGE_RULES: (1) pre_appointment_snapshot — fires when a saved appointment is 0–3 days away, no Snapshot saved in 7 days, and 14+ BP readings exist. suppressDays: 3. Action button opens Symptom Convergence → Timeline tab. (2) post_visit_clinical_event — fires when a saved appointment date was 1–4 days ago and no sentinel clinical event has been logged on or after that date. suppressDays: 5. Action button opens Sentinel Clinical Event Log form. (3) hr_shift_no_clinical_event — fires when a pinned HR level shift event (source: hr_detector) exists but no clinical event has been logged within 30 days of the pin date. suppressDays: 14. Action button opens Sentinel Clinical Event Log form. (4) clinical_event_log_unknown — fires when app age ≥30 days, 20+ BP readings, hasConditions, and clinbridge_sentinel_events is empty — the user has never logged any clinical event. suppressDays: 30. Educational nudge, action button opens form. All 4 rules read cardiacAppointments and clinbridge_sentinel_events directly from localStorage via try/catch, matching the existing pattern used by other rules. Gap 4 (reset-baseline reminder after deliberate non-reset) intentionally held — fires too close to a user choice and risks feeling intrusive. Test suite additions required (v12 → Section 52).

Getting Started — “Open Settings Now” button opened Settings hidden behind Help & About — The button called openSettings() directly. openSettings() writes to #modal and makes it visible — but #aboutModal (Help & About) was still displayed on top of it, hiding Settings completely. Fix: button now calls closeHelpModal(); setTimeout(function(){ openSettings(); }, 100); — the identical pattern used by every Settings-opening button inside the wizard (_wzGoSettings()). All other tappable elements in the Getting Started section were audited: wizard navigation stays within #aboutModal and is unaffected. No other buttons had this issue.

Getting Started Tab Rewrite — Progressive Onboarding — The Getting Started tab has been rewritten from a 1,200-word feature manual into a four-section progressive onboarding experience. Section 1: a warm three-step handshake (name, conditions, BP targets) with a direct “Open Settings Now” button. Section 2: plain-language guidance on what to log first — doctor-prescription framing, no feature inventory. Section 3: a short explanation of how Sentinel surfaces one suggestion at a time as data builds, so users understand they don’t need to configure everything upfront. Section 4: the full Setup Wizard repositioned at the bottom under “Already familiar with ClinBridge?” — preserved completely, just no longer the first thing a new user sees. Zero new JavaScript. Zero new logic. Zero conditional paths. The tab is static HTML — testable by eye on any device. Rationale: the behavioral nudge system is now the progressive onboarding engine; the Getting Started tab’s job is to earn trust and get the three critical data points in, then step back.

Behavioral Profile Layer — Accumulated Data Integration — Goal 3 of the v9.10.x behavioral intelligence sprint. Five changes shipped: (1) Streak rules corrected — streak_7_days and streak_30_days now use currentStreak directly instead of the old count/age approximation, which could fire for non-streak loggers. (2) fluid_never_logged nudge — fires when age ≥14 days, 20+ BP readings, hasConditions, and fluid.count = 0. Fluid tracking is a direct decompensation signal; this gap is clinically meaningful for cardiac patients. suppressDays: 21. Action button opens fluid log. (3) pulse_pressure_never_viewed nudge — fires when age ≥14 days, 20+ BP readings, hasConditions, and the Pulse Pressure detector has never been opened. suppressDays: 30. (4) appointment_never_saved nudge — fires when age ≥30 days, hasConditions, and engagement.appointmentsSaved = 0. First rule to use the engagement.* block. Without a saved appointment the Appointment Snapshot workflow is inert. suppressDays: 21. Action button opens appointment modal. (5) Instant-dismiss backoff in evalCard() — if cardsShown ≥ 8 and cardsInstantDismissed / cardsShown ≥ 0.75, nudge evaluation is skipped for that Sentinel session. Unlocks and encouragements still fire. First use of signals.* data in rule logic. Ratio self-corrects naturally as cardsReadAndDismissed grows. Test suite additions required (v12): fluid_never_logged fires/suppresses correctly; pulse_pressure_never_viewed fires/suppresses; appointment_never_saved fires/suppresses; backoff activates at threshold and lifts as ratio improves; streak_7_days uses currentStreak not count; streak_30_days uses currentStreak ≥30.

Baseline Conditions Cross-Reference — Each BP reading card now shows a personal baseline context pill when the reading is within configured thresholds (no red alert) but meaningfully elevated above the user’s personal quiet baseline. The pill appears in amber with the specific deltas: e.g. “↑ Sys +14 · HR +16 vs your baseline”. Thresholds: systolic ≥10 mmHg above baseline, diastolic ≥8 mmHg, HR ≥12 bpm — any one triggers the pill. Requires 14+ qualifying baseline days; never fires alongside a threshold alert. _sentMetrics() extended to return avgSys and avgDia; _sentComputeBaseline() extended to include both in the baseline object. New _getPersonalBaseline() session-cached wrapper computes once per 5 minutes and reuses across all readings in a render — avoids re-scanning 150 days per card. No changes to alert logic or Sentinel engine.

Heat & Humidity Sentinel Integration — The Heat Advisory system is now wired into CB_BEHAVIOR. Three additions to the behavioral schema: heat_advisory screen tracker (records manual advisory checks), heatAdvisoryAutoFired signal counter (increments each time an advisory fires automatically after activity logging), and heatAdvisoryEnabled in the setup snapshot (captured on every Settings save). Two new nudge rules: heat_advisory_conditions_disabled fires when the user has heat-sensitive conditions and 5+ activity logs but Heat Advisory is off — direct action button opens Heat Settings (suppressDays: 14). heat_advisory_feature_unused fires when the advisory is enabled and conditions are present but neither auto nor manual advisories have ever fired — guides the user to start using temperature bands during activity logging (suppressDays: 30). Both rules pass the cry-wolf test: they fire because of a safety behavior gap, not to add trigger volume.

Behavioral Intelligence — Setup Gap Rules + Unified Guidance — Three new companion card nudge rules now fire based on the CB_BEHAVIOR setup snapshot: setup_no_conditions (fires at 3+ days if no conditions set, suppressed 7 days), setup_no_patient_name (fires at 5+ days if name missing, suppressed 14 days), and setup_bp_not_customized (fires when 20+ readings logged and 5+ days old with default BP targets, suppressed 14 days). Each card includes a direct action button that closes Sentinel, opens Settings, and scrolls to the relevant section. The settings_complete encouragement rule now reads d.setup directly instead of calling _checkSettingsGaps() live. The standalone Settings Gap Card in Sentinel (v9.10.35) has been retired — setup guidance is now unified under the companion card system. snapshotSetup() is now called on app init (500ms deferred) so the setup block is populated from day one, not only after the user visits Settings.

Behavioral Intelligence Layer — Schema v2 Redesign — The silent behavioral observer has been redesigned from the ground up. CB_BEHAVIOR now tracks five dimensions: presence (screens and log types used), frequency and recency (with streak tracking and time-of-day distribution per log type), quality (notes attached to logs, context saves), setup completeness (snapshotted on every Settings save — patient name, conditions, daily events, medications, BP target customization), and engagement depth (anchor investigations saved, Doctor’s Reports generated, analytics notes, context notes, appointments, data exports, wizard completion). Signal response tracking records whether companion cards are read before dismissal or instantly dismissed, giving the rule engine a measure of its own effectiveness. 9 new hooks added. Full forward migration from v1 installs with zero data loss. No visible UI changes.

• Help & About — tab bar displaying as rows instead of a single scrollable strip — Opening Help & About showed the section tabs stacked into a grid or multiple rows. This pushed the content area off-screen and made tapping a tab appear to do nothing. The tab bar now displays as a single horizontal row that scrolls left and right. All sections switch correctly when tapped.
• Help & About — wrong content visible when first opened — An internal HTML error caused Known Issues content to appear in the main area instead of the Welcome section on first open. Fully resolved — Welcome now shows correctly every time.

• Help & About tabs broken after tapping Sentinel — Adding a 14th tab caused the tab bar to wrap to additional rows, collapsing the content area height on mobile. Only the first section div was visible. Tab bar now scrolls horizontally in a single row — unlimited tabs, full content height preserved. Scroll reset in setHelpSection moved to after section toggle for correct mobile behavior. Sentinel added to search labels.

• Sentinel — modal footer and disclaimer cut off — Modal structure missing flexbox column layout caused the bottom border and disclaimer to be hidden when content filled the scroll area. Fixed: footer now always visible below scrollable content.
• Sentinel — grammar error "1 streams are" — Status banner used plural regardless of stream count. Fixed to "1 stream is" / "2 streams are" correctly.
• Sentinel — Help & About documentation added — Full dedicated tab explaining what Sentinel is, how Footprints work, the Clinical Event Log, and why this approach is clinically novel. Written for cardiac patients, not developers.

• Sentinel v2 — Two-tier stream scoring and Clinical Event Log — Sentinel now compares your streams against your recent pattern (last 14 days, or since a logged clinical event), not your all-time baseline. New Clinical Event Log lets you record pacemaker adjustments, new medications, procedures, and hospitalizations with a baseline reset option. Plain-language stream cards rewritten throughout.

• Sentinel — Personal Pattern Precursor Detector — ClinBridge's most advanced feature. Sentinel watches your live data streams against your personal baseline and your Footprints — the 72-hour pre-event patterns extracted from your Pinned Events. When streams converge the same way they did before a prior clinical event, Sentinel surfaces a pattern match before symptoms escalate. Not a diagnosis — a mirror of your own data history. Directional, not definitive.

• Pinned Events — Add Question gave no feedback after save — Question was saved correctly to localStorage but the pin card did not re-render, so the question appeared missing. Tapping Add multiple times created duplicate ghost entries. Fixed: card now re-renders immediately after save.
• Pinned Events — checkbox (Mark Asked) did nothing visually — Toggle function looked for a DOM element ID that was never set on the rendered button. In-place update always failed silently. Fixed: card re-renders after toggle so asked/unanswered state is always accurate.
• Pinned Events — ✕ delete question did nothing — Function attempted to remove a DOM row by ID that was never assigned. Fixed: confirm dialog added to prevent accidental deletes, card always re-renders after deletion.

• Button spacing too tight in logging modals (senior usability fix) — Morning Check-In symptom grid, Yes/No pairs, and waking-hours selectors had 6–8 px gaps between tappable buttons. Log Symptom recent-symptom chips, Log Fluid quick-add row, and the Log Activity BP-before button had sub-12 px spacing. All raised to minimum 12 px. No font sizes or button sizes changed.

• Help & About tab bar scrolling out of reach — Scrolling through a long tab pushed the tab row off-screen. Closing and reopening was the only escape. Tab bar is now sticky.
• Glossary tab never highlighted as active — The Glossary key was missing from the internal active-state list. Content showed but the button stayed unlit. Fixed.
• Heat Advisory section unreachable from UI — Full section content existed but had no tab button. Completely inaccessible. Tab button added.
• Privacy "Got It!" button not syncing floating button correctly — Called an orphaned closeAbout() instead of closeHelpModal(). The floating Today's Status button did not restore correctly after closing. Fixed.

• Pinned Events comm layer — UI freeze on save — All 6 comm layer operations now update only the affected element in-place. Toast confirmations added. No modal rebuild on save.

• Numeric fields accepting letter "e" (browser scientific notation) — All number inputs accepted e, E, +, and - as valid browser scientific notation. One global listener now blocks them across all 30+ numeric fields.

• All Notes search box — single-character typing bug — Every keystroke rebuilt the entire modal, destroying the focused input mid-typing. Search now updates only the notes list without ever replacing the input element.

• Already-linked BP card — no dismiss button — The gray "already linked" card in Log Activity had no way to be dismissed. A ✕ button now closes it.

• BP Before Activity button invisible in Manual duration mode — Moved out of the timer container so it appears in both Timer and Manual Entry modes.
• Recent BP contextual card not appearing on Log Activity open — Now shows consistently. "Use This Reading" stamps in-place without creating a duplicate entry.

• Custom Symptom Delete button silently failing — Duplicate function overriding the correct one. Resolved by renaming the duplicate.
• Decompensation badge showing 0 on page load — Badge now updated by a silent startup analysis at 1200ms after load.
• Pulse Pressure Detector not generating pin suggestions — Pin injection was matching outdated status title strings. Updated to match all current titles.
• Condition dropdown in Log Symptom not alphabetical — Now sorted alphabetically on every render.

• Critical — All main page panels blank after v9.9.25 — A duplicate function silently overrode the main-page data renderer, causing all panels to show blank on launch. Resolved by renaming the analytics version.
• "Edit Past Entries" button doing nothing on Chromebook — Silently blocked by an incorrect empty-history check, and when it ran it changed all panels to 90-day history mode simultaneously. Both issues resolved.
• Opening weight history changing all other panel view modes — Weight history now has its own isolated state variable and never affects other panels.
• Delete/edit weight entry not updating display in history mode — Now patches in-memory array immediately without a page reload.

• Event Repeat Schedule filtering inconsistent — Day-of-week events were correctly hidden from Today's Events but still appeared in the Next Event banner and Next Fluid Event callout. All three now apply the same filter.
• Activity Duration Trends showing stale "Coming Soon" label — Chart was fully functional; the placeholder label was never removed.

• Medication Effectiveness — Co-Administered Med Analysis — BP readings for a multi-med session now appear in the analysis for every medication taken, not just the primary one.

• Doctor's Report showing "Coming Soon" instead of generating — Restored to full live generation with audited calculations.
• Avg Daily Fluid dividing by full period instead of tracked days — Now uses days with meaningful data only.
• Doctor's Report totalDays inflated by 1 — Erroneous +1 removed from Math.ceil calculation.
• Doctor's Report Diagnosis field showing "Not specified" — Now pulls from Settings cardiac and custom conditions correctly.
• Alert chime replaying on every reminder reshow — Chime now fires once per event at initial notification only.
• Missing sticky close buttons in three modals — Added to Advanced Analytics, Doctor Appointment, and View All Appointments.

• Budget Dashboard +/− buttons doing nothing — A re-render was wiping edits on every tap. Fixed with edit cache.
• Budget "Scale to Fit" only touching events with existing goals — Now applies weighted distribution across all events.
• Budget Dashboard increment locked to 8 oz — Now steps 1 oz at a time for precise targets.
• Fluid Mode Assistant "Apply" button doing nothing — Called a non-existent function. Fixed throughout.
• All main page buttons broken after previous build — Unescaped apostrophes in onclick handler strings. Resolved by rewriting with named functions.
• Budget ring text partially hidden behind ring stroke — Replaced negative margin hack with proper absolute-centered overlay.

Once enough check-in data exists, a "Your Fluid Response Profile" view in Settings shows your personal pattern in plain language. This becomes the foundation for a productive conversation with your cardiologist about a personalized daily limit.

Barometric pressure drops correlate with PPH episode severity. ClinBridge will detect significant pressure changes and issue a proactive heads-up so you can adjust hydration and activity before symptoms occur.

Optional read-only access for a spouse, adult child, or caregiver to view your dashboard and receive alerts — without being able to edit your data.

Correlate meal logs with post-meal BP readings to identify which foods or meal sizes consistently trigger PPH episodes. Over time, builds a personal map of your dietary BP triggers.

Log sleep quality and duration. Poor sleep is a major driver of next-day BP irregularities and OSA complications. Correlating sleep quality with BP trends gives your doctor a fuller clinical picture.

Full native apps with reliable background notifications, HealthKit / Google Fit integration, Apple Watch complications, and wrist-tap logging. No browser required.

Auto-import heart rate and activity data from Apple Watch, Fitbit, and Garmin — so you are not re-entering data that your devices already captured.

ClinBridge is built by a patient, for patients. If there is something your care plan requires that ClinBridge does not yet do, we want to know. Use the Contact & Feedback section in Settings to send a suggestion directly to the development team.

Sentinel — “What to Tell Your Doctor” box — When any stream is drifting or alarming, Sentinel now displays a highlighted box at the top of the modal with pre-written plain-language sentences the user can read aloud at their appointment. One sentence per flagged stream, automatically generated from live data. Box is hidden on All Clear. Orange border for drifting, red for alarming. Built for seniors and new users who need a clear, unambiguous read-aloud prompt.

Help & About tab bar — horizontal scroll layout — Tab bar now scrolls horizontally in a single row. Full content height is always preserved regardless of tab count. Standard mobile UX pattern — swipe the tab bar to reach any section. Scales to any future tab additions without layout impact.

Sentinel documented in Help & About — Dedicated tab covers what Sentinel watches, what a Footprint is, how the Clinical Event Log works, and why personalized pre-event pattern recognition is clinically novel. Modal footer and disclaimer now always visible. Grammar corrected.

Sentinel v2 — Two-tier scoring drives alarms from 14-day recent pattern. Clinical Event Log with baseline reset. Stream cards in plain language with specific action guidance and date ranges.

Sentinel — Personal Pattern Precursor Detector — Watches 3 live data streams (HR daily spread, symptom frequency, pulse pressure) against your personal baseline. Learns from your Footprints — 72-hour pre-event windows extracted from all Pinned Events. Badge turns yellow at 2 drifting streams, red at 3. Pin any match for your Doctor's Report. Built from your real data: 9 Footprints across 45 days.

Sentinel — Personal Pattern Precursor Detector — Watches 3 live data streams (HR daily spread, symptom frequency, pulse pressure) against your personal baseline. Learns from your Footprints — 72-hour pre-event windows extracted from all Pinned Events. Badge turns yellow at 2 drifting streams, red at 3. Pin any match for your Doctor's Report. Built from your real data: 9 Footprints across 45 days.

Pinned Events question UI — three interaction bugs fixed — Add Question now shows the saved question immediately. Mark Asked checkbox now reflects state instantly. Delete (✕) now confirms before removing and always takes effect. All three operations re-render the pin card in place.

Button spacing audit — all main logging modals — Systematic pass through Log BP, Log Fluid, Log Activity, Log Symptom, Log Weight, Log Meal, and Morning Check-In. Minimum 12 px gap enforced between every pair of tappable buttons. Reduces misfire taps for senior users on touchscreens. TestSuite v4 Section 15 (Help & About, 18 new automated tests) released alongside.

Help & About — complete tab overhaul — Sticky tab bar. Larger tap targets. Pinned Events and Heat Advisory tabs added. Pinned Events tab includes full clinical context, doctor workflow, and anonymized case study.

Pinned Events comm layer UI freeze fixed — All 6 operations now in-place with toast. No modal rebuild. Smooth on mobile.

Pinned Events Communication Layer — Log Communication (who, date, response, status) and Add Question per-pin. All data archives with the pin.

All Notes search box fix — Multi-character keywords now work. _filterNotesInPlace() handles live search without destroying the input element.

Help & About documentation catch-up and Already-linked BP card dismiss button.

Recent BP contextual card at Log Activity open. BP Before Activity button in Manual mode. Manual mode info card.

Symptom System Full Overhaul — 70+ synonym mappings, Bulk Rename, clinical context prompt, Manage Symptoms rebuilt in 3 sections.

Tier C Pattern Ripening Nudge and Tier D Urgent Convergence Alert. Glossary Tab. Help & About full rewrite with QR code.

Four detectors live: HR Rate Detector, Decompensation Warning, Pulse Pressure Detector, Symptom Convergence. Pinned Events, 60-day Timeline, Appointment Snapshot, Archive & Clear.

Per-card history isolation. Weight outlier flagging (AHA/ACC thresholds). Weight jump-to-date picker. Critical launch-day regression fix.

Activity Timer Pause/Resume. HR Rate Detector Quick Stats Period Selector. All Notes emoji header fix.

Advanced Analytics analyzes BP readings before and after logged meals. Flags events with ≥15 mmHg systolic drops. For informational tracking only.

The force your heart uses to push blood through your arteries, measured in millimeters of mercury (mmHg). Expressed as two numbers: systolic (the top number — pressure when your heart beats) over diastolic (the bottom number — pressure when your heart rests between beats). Example: 120/80 mmHg. Normal range for most adults is below 130/80, but your cardiologist will give you a personal target that may differ.

The difference between your systolic and diastolic readings. Example: if your BP is 118/85, your pulse pressure is 33 mmHg. Normal range is 40–60 mmHg. A narrow pulse pressure (below 40) can indicate the heart is working harder to push blood forward — a pattern seen in reduced cardiac output and certain valve conditions. A wide pulse pressure (above 60) may indicate arterial stiffness. Many cardiac patients have a chronically narrow PP that is their personal baseline — what matters is change from that baseline, not comparison to textbook normals.

How many times your heart beats per minute (bpm). Normal resting range is 60–100 bpm. Below 60 is bradycardia (slow heart rate); above 100 is tachycardia (fast heart rate). Patients with pacemakers may have a lower set rate limit — your pacemaker clinic can tell you what range is expected for your device settings.

A heart rate below 60 bpm. In ClinBridge, the HR Rate Detector flags readings below 50 bpm specifically, as this is below the range most pacemakers are programmed to allow. Bradycardia is normal for well-trained athletes and some medication effects (beta-blockers, for example, intentionally slow the heart rate). Context matters — discuss any persistent low readings with your cardiologist or device clinic.

A sustained change in your heart rate baseline — where your resting HR was consistently at one level, then durably shifted to a new level and stayed there. This is different from a single high or low reading. ClinBridge's HR Rate Detector identifies these shifts statistically by comparing before-and-after windows for stability. A level shift is clinically significant because it suggests something changed in your cardiac state — compensation, medication effect, disease progression, or recovery. Your cardiologist will want to know.

A chronic condition where the heart doesn't pump blood as efficiently as it should. "Congestive" refers to fluid backing up into the lungs and body (edema). Heart failure doesn't mean the heart has stopped — it means it's working harder than it should to maintain output. Management focuses on monitoring fluid balance, weight, symptoms, and medication adherence. ClinBridge's Decompensation Warning system is specifically designed to detect early signs of fluid buildup before symptoms become severe.

When a cardiac patient's condition worsens — typically due to fluid overload in CHF — to the point where symptoms become severe and hospitalization may be required. Early decompensation signs include rapid weight gain (fluid retention), worsening shortness of breath, swelling in legs and ankles, fatigue, and reduced activity tolerance. The goal of ClinBridge's Decompensation Warning detector is to surface multiple early signals before they progress to a crisis.

In the Decompensation Warning detector, each of the five clinical signals (weight, cardiac output, symptoms, fluid, notes) can score 0, 1, or 2 points based on severity. Maximum total is 8 points. The detector shows how many points are active and which signals contributed. One point alone is labeled "Early Indicator" — not alarming. Two or more points prompt closer monitoring. Two or more red-level signals prompt contacting your cardiologist.

When multiple symptoms occur together or escalate simultaneously in a pattern that suggests an underlying common cause. In ClinBridge, convergence is detected across three layers: symptoms clustering within a 4-hour window on the same day, the same symptom worsening in severity over multiple days, and recognized clinical symptom triads. The significance is that individual symptoms are often dismissed — but a convergent pattern of multiple symptoms is harder to attribute to chance and more likely to represent a real clinical event.

A recognized combination of three symptoms that together suggest a specific condition or event. ClinBridge recognizes: the CHF Decompensation Triad (shortness of breath + fatigue + swelling/edema — a classic early decompensation pattern); the Arrhythmia Triad (palpitations + dizziness + chest pressure/tightness — may indicate an arrhythmia episode, note timing and duration); and the Systemic Symptom Pattern (nausea + fatigue + reduced appetite — nonspecific, worth noting but not alarming on its own). Triads are worth mentioning to your cardiologist, not reasons to panic.

A drop in blood pressure that occurs after eating. "Postprandial" means after a meal; "hypotension" means low blood pressure. Common in older adults and those with autonomic nervous system conditions. Typically defined as a drop of ≥20 mmHg systolic within 1–2 hours of eating. Symptoms include dizziness, lightheadedness, and fainting. ClinBridge's Post-Meal BP Patterns analysis in Advanced Analytics can help identify whether your BP drops consistently after meals.

An irregular heart rhythm — the heart beats too fast, too slow, or with an irregular pattern. Common types include atrial fibrillation (AFib), where the upper chambers quiver instead of beating regularly, and various bradycardias and tachycardias. Symptoms can include palpitations (feeling your heart beat irregularly or rapidly), dizziness, shortness of breath, or fatigue. Some arrhythmias are asymptomatic. ClinBridge logs heart rate with each BP reading; rapid changes and low readings are flagged for review.

ClinBridge stores 90 days of daily readings on your device. After 90 days, the oldest day is removed as a new day is added — like a rolling 90-day window. This means data from more than 90 days ago is no longer in the app unless you exported a backup at that time. To preserve data long-term: export quarterly (last day of each quarter is a good practice). Pinned Events and Appointment Snapshots are exceptions — they are stored permanently and never roll off.

A clinically significant finding that you've chosen to permanently preserve. When a detector flags something worth showing your cardiologist, tapping "📌 Pin" saves the finding, the date, and all raw data from that day to a permanent list that never rolls off. Pinned events appear in your Doctor's Report and on the 60-day Timeline. After your cardiologist appointment, use "Archive & Clear" to save all current pins to a permanent archive and start fresh.

Your personal "normal" — the consistent pattern your readings follow when nothing unusual is happening. ClinBridge uses the word "baseline" in two contexts: (1) Your personal BP/HR baseline — the average range your readings cluster around, used as the reference point for detecting changes; and (2) Baseline symptoms in the Morning Check-In — symptoms you experience routinely (such as chronic ankle swelling after a procedure) that are part of your normal state, not new developments. Baseline symptoms are recorded for your doctor but excluded from pattern correlation calculations.

ClinBridge's core accuracy principle. The detectors use real statistical methods on real data — but statistics identify patterns, not causes. A detected HR level shift is mathematically real. Whether it represents disease progression, a medication effect, recovery, or random variation requires clinical judgment that only your cardiologist can provide. ClinBridge points in a direction and gives you the evidence to have a productive conversation — it does not tell you what that pattern means for your specific medical situation.

ClinBridge's design philosophy. Many health apps generate advice or recommendations — telling you what to do. ClinBridge instead verifies patterns across multiple data streams before surfacing a finding. It only escalates when signals converge — when two or more independent data streams agree that something changed. A single reading doesn't trigger an alert. A single signal point doesn't trigger a pin suggestion. This "verification first" approach is designed to prevent false alarms and preserve the credibility of findings that do get surfaced.

Every other cardiac monitoring tool watches for what is happening right now. Sentinel watches for what came before. It is built on a simple but powerful idea: the patterns in your own data in the days before a clinical event are more meaningful than any population-based threshold — because they are yours.

Sentinel watches three data streams around the clock — your HR daily spread, your symptom frequency, and your pulse pressure. It compares each one not to a textbook average, but to your own recent personal pattern. When two or more streams drift above your recent normal at the same time, Sentinel surfaces a pattern match — before symptoms escalate, not after.

Your recent pattern is calculated from your own logged data — the last 14 days, or from a clinical event date if you have logged one. This means Sentinel stays calibrated to where you are in your health journey, not where you were six months ago.

Every time you pin a clinical event from one of ClinBridge's detectors, Sentinel automatically extracts what your data looked like in the 3 days before that event and saves it as a Footprint. Over time, Sentinel builds a personal library of your pre-event signatures.

When your current data resembles a prior Footprint, Sentinel tells you specifically — which event it resembles, what your data looked like then, and what your data looks like now. It does not tell you what is going to happen. It tells you that a pattern you have lived through before is appearing again.

Pacemaker adjustments, new medications, procedures, hospitalizations — any clinical change that legitimately shifts your baseline belongs in the Clinical Event Log inside Sentinel. You will find it by opening Sentinel and tapping + Log Clinical Event.

When you mark an event as a baseline reset, Sentinel compares your streams to your data after that event — not before it. This is critical after a pacemaker adjustment, for example: your heart rate pattern may shift significantly as settings take effect, and Sentinel needs to know that the shift is intentional and clinical, not an emerging problem.

The Clinical Event Log is also a permanent record of your care timeline — visible in Sentinel, yours to keep, never transmitted anywhere.

No published cardiac monitoring tool has done this at the individual patient level outside a hospital setting. Academic research on pre-decompensation pattern recognition requires Holter monitors, IRB approvals, and study populations measured over months or years. The results are then averaged across those populations — which means the thresholds apply to the average patient, not to you.

Sentinel does it differently. It uses the data you are already logging every day. It compares you to yourself. Your quiet baseline, your pre-event Footprints, your recent pattern — everything Sentinel knows comes from your own history, not from a population study. That is what makes it personal in a way that published thresholds cannot be.

Sentinel is not a diagnosis. It is not a medical device. A pattern match does not mean something is wrong — it means your data looks similar to a prior period that preceded a clinical event in your own history. That is worth noting. It is not worth panicking about.

Sentinel provides the documented evidence and the pattern recognition. Your cardiologist provides the clinical interpretation. The goal is to walk into your next appointment with something real to show — not a vague feeling that something might be off, but a specific, timestamped pattern match from your own data that your doctor can evaluate.

Ask is a conversational helper built into ClinBridge. It knows every feature of the app and has full awareness of your logged data — so you can ask plain questions and get plain answers, based on what you’ve actually recorded.

Ask anything about how the app works, your logged data, or patterns you see. Here are real examples:

Tap the 💬 Ask button on the main screen. A conversation panel opens. Type your question in plain English — no special format required.

Ask reads your logged data — your BP readings, fluid intake, weight, symptoms, notes, medications, and more — and gives you a real answer based on what you have actually recorded. It also knows every feature of ClinBridge in depth, so it can explain how anything works.

If your question is unclear, Ask will offer you a few clearer versions to tap. You can ask follow-up questions in the same window without starting over — the conversation stays connected.

Ask is not a doctor and will never try to be one. It will not tell you what your readings mean for your health, suggest a diagnosis, or recommend any medical course of action.

If your question calls for clinical interpretation, Ask will say so warmly and point you to your cardiologist — which is always the right call. Use 📌 Pinned Events to capture anything you want to bring to your next appointment.

✅ You do not need to word it perfectly. Ask plain questions the same way you would ask a knowledgeable friend.

✅ Follow-ups work. After an answer, keep asking in the same window. The conversation stays connected until you close it.

✅ Ask about your notes. “Did I mention shortness of breath in my notes?” is a great question. Ask can search through what you have written.

✅ Ask about any feature. Detectors, reminders, Morning Check-In, Advanced Analytics, the Doctor’s Report — anything in the app is fair game.

✅ Start simple. If you are new to Ask, try one of the example questions first to get a feel for it.

Your support helps cover hosting, development time, and keeps ClinBridge free for every patient who needs it.

100% optional — your health data stays private regardless

• GitHub Pages hosting & domain costs for clinbridge.clinic
• Development time building new features requested by patients
• Keeping ClinBridge permanently free — no freemium, no ads