Ambulatory blood pressure patterns are unreliable without positional context. A reading of 148/92 taken standing after walking briskly from the car to the clinic waiting room is clinically different from the same reading taken after five minutes seated at rest in the morning before medication. Your cardiologist needs both values and both contexts to adjust your antihypertensive regimen correctly. Most patient-maintained blood pressure logs record the number without the circumstances.
Why Isolated Values Are the Wrong Unit of Measurement
A single blood pressure reading is almost useless for diagnostic purposes. The value that matters is the pattern — the variation across times of day, body positions, meal states, and activity levels. Systolic 135 in the morning before medication, 122 two hours post-dose, 141 standing after a 30-minute walk — those three readings together are clinical information. In isolation, each one is just a number that might prompt an intervention it doesn't actually warrant, or miss one it does.
The Position field is where most casual health loggers take the shortcut that undermines their data. Left arm sitting versus right arm sitting can produce readings that differ by 10 mmHg systolic in patients with subclavian stenosis. Supine versus standing measurements reveal orthostatic hypotension — the blood pressure drop on rising that produces light-headedness and fall risk in older patients on antihypertensives. The field captures left/right arm, hand, leg, sitting, laying, standing as multichoice combinations. Mark them. Every time.
Glucose in Context
The Food field — before/after meal, with Breakfast/Lunch/Dinner options — is the glycemic context layer that transforms glucose readings from isolated data points into a metabolic picture.
A fasting glucose of 110 mg/dL is borderline. A post-prandial glucose of 165 mg/dL two hours after breakfast is relevant. Both together, with the meal type noted, give a treating physician the pattern they need to assess insulin resistance, adjust sulfonylurea dosing, or decide whether a continuous glucose monitor is warranted. Glucose logged without meal context is consistently misinterpreted — by patients and sometimes by clinicians who don't probe for it.
Temperature in the same record as blood pressure and glucose creates the clinical snapshot for days when systemic status matters: a temperature of 38.4°C will elevate heart rate, which changes pulse interpretation, and fever-related vasoconstriction can affect blood pressure readings in ways that make antihypertensive adjustments look necessary when the real intervention is treating the infection.
The BMI Calculation and Its Limits
The BMI field is a calculated value: weight in kilograms divided by height in centimetres squared, times 10,000. It's computed from the kg and cm fields stored in the same record. Having the formula run automatically means you don't have to calculate it — you enter weight and height, the database does the arithmetic.
The limit of BMI as a metric is well established — it conflates muscle mass with adipose tissue, particularly in athletic and muscular individuals, and it poorly characterizes fat distribution. Waist-to-hip ratio is a more meaningful predictor of metabolic syndrome risk for many patient profiles. The template as designed doesn't include WHR, but the Notes field can carry waist and hip measurements if that data point matters to your treatment plan.
Activity and Medication Tracking
Distance and Duration fields log exercise. These aren't sports performance metrics — they're clinical activity documentation. A patient with heart failure who walked 2.1 km in 35 minutes on a given day produces different cardiovascular context for the blood pressure reading at the end of that walk than a patient who spent the day sedentary. Exercise duration also matters for glucose management: aerobic activity drives glucose uptake for hours after the session ends, which shows up in post-exercise glucose readings that look anomalously low without the activity context recorded alongside.
Medicine1 and Medicine2 as double fields track dosage taken. The generic design accommodates any medication — the user defines which medicine each field represents. For a patient on a PRN antihypertensive that they take as-needed based on morning readings, this field documents whether the dose was taken before the morning measurement, which directly affects interpretation of the blood pressure value logged three hours later.
The accumulated record — weeks of daily timestamps, positional readings, pre/post-meal glucose values, weight trends, and medication logs — is the document a physician needs to assess therapeutic response without relying exclusively on the four or five readings taken in clinical visits spread across a year.