Summarise Your Home Blood Pressure Log
A single home reading is noisy; a log is useful. This takes your readings, averages them, shows the spread between your lowest and highest, counts how many sit above the threshold you were given, and compares your first week with your last so a trend is visible. It interprets nothing — it organises the numbers so a short appointment can be about the pattern rather than one figure. Everything runs locally; your readings never leave the tab.
- Summary
- Average, spread, and counts from your own readings
- local
- What it replaces
- Handing over a page of unsorted numbers
- $0.00
- Input
- Date, systolic, and diastolic per reading
- no card
- Output
- An average, a spread, and a first/last comparison
- recomputed
What you pay otherwise
| Route | What you get | Cost |
|---|---|---|
| App with a subscription | Your readings stored on someone else's server | $3–$8/mo |
| Bringing one reading | The least informative number you have | misleading |
| Bringing the raw log | The appointment spent doing arithmetic | the slot |
| This page | A summary you can read out in ten seconds | $0 |
The workflow
Use the threshold your clinician gave you, not a general one
Home thresholds are usually set lower than clinic thresholds because there is no white-coat effect. Enter the figure you were actually given; the count above threshold is only meaningful against the right number.
Log both arms' worth of context if you have it
Time of day, whether you'd taken medication, and whether you'd been active all change a reading. The tool doesn't use them, but writing them beside the log makes the summary far more useful in the room.
Read the spread as well as the average
Two logs can share an average and look nothing alike. A wide spread between your lowest and highest is itself information a clinician will want, and it is invisible in an average alone.
Bring the summary, not a verdict
The first-week versus last-week line is a description of your own numbers, not a conclusion about your health. Let the clinician draw the conclusion — your job is to arrive with the pattern already sorted.
Worked example
Sample: 12 readings over 12 days, threshold 135/85 Average 138.4 / 87.1 Range 126-152 systolic Above threshold 9 of 12 (75%) First 6 readings 141.0 systolic average Last 6 readings 135.8 — lower by 5.2 mmHg Uploaded nothing — summarised in the tab
Numbers above are sample data produced by the tool's own pre-loaded example, run in the browser — not averages or measured benchmarks.
What breaks this
Using a clinic threshold for home readings makes the count above threshold meaningless. Logging only the readings that felt normal biases the average downward. Reading the summary as a diagnosis — it describes your numbers; it cannot interpret them.
Try it now
Twelve readings across twelve days are loaded, averaging 138/87 against a 135/85 threshold. Raise the threshold to 140/90 and watch the count above it fall.
Open the summariser →Go deeper: the printable chart
The summary is free forever. The $4 one-time tier adds:
- Printable chart — the readings and summary on one sheet for the appointment — estimate: ~8 min saved reformatting before each visit.
- Saved logs shelf — keep up to 12 logs in this browser — estimate: ~10 min saved finding the previous one.
- Reading trend export — the log as a clean table you can attach — estimate: ~12 min saved retyping it.