Blood pressure category calculator

This capability applies that ACC/AHA table deterministically: it validates the pair, rejects impossible orderings where diastolic exceeds systolic, picks the more severe band when the two numbers disagree, and returns structured JSON with a machine-readable category key, a human label, the echoed reading string, and the guideline name. The path is pure comparison logic with no network, no model, and no wall clock, so homework checkers, coaching apps, and prepaid API clients pin identical outputs in tests.

What ACC/AHA categories mean and which inputs you need

Send required fields systolic and diastolic as finite numbers; aliases sbp, sys, systolic_bp, and systolic_mmhg work for the top number, while dbp, dia, diastolic_bp, and diastolic_mmhg work for the bottom number. Identical inputs always yield identical JSON because the algorithm never touches the network, a model, a clock, or a random generator. Missing fields, non-finite values, out-of-range readings, and any case where diastolic exceeds systolic all fail with invalid_input and are not charged.

Reading the response fields and how conflicting bands resolve

When systolic and diastolic fall into different bands, the higher severity wins: for example systolic one hundred twenty-five with diastolic eighty-two is stage one because diastolic crossed eighty, not elevated. Isolated high systolic with low diastolic still climbs the table by the systolic rule, matching how clinicians teach the more severe component. On success the response echoes systolic and diastolic, sets unit to mmHg, and builds reading as a compact SBP slash DBP string for display. The category field is a stable machine key among normal, elevated, hypertension_stage_1, hypertension_stage_2, and hypertensive_crisis, while category_label is the matching human phrase for UI chips and reports. Guideline is always ACC/AHA two thousand seventeen and method is always acc_aha_bp_category so downstream code can branch without sniffing shapes. Use category for filters and analytics, category_label for user-facing copy, and reading when you only need a single display line. Diastolic greater than systolic is rejected with a clear invalid_input message that mentions diastolic exceeds systolic, because that ordering is not a valid clinic pair for this product. Do not confuse this endpoint with mean arterial pressure calculators, pulse-pressure tools, pediatric percentile charts, or ESC/ESH European tables—those are different intents and different thresholds.

API usage, pricing, product workflows, and practical limits

Call the free in-browser blood pressure category calculator for classroom demos, patient education pages, and quick personal checks without reimplementing the ACC/AHA table in every spreadsheet. Prefer consistent units; if your UI only collects whole millimetres of mercury, send integers and the engine still accepts numeric strings. Keep expectations educational: this is a classification and learning tool, not a diagnostic medical device, and people with symptoms, known cardiovascular disease, pregnancy, or medication changes should follow professional medical advice rather than any single automated label alone. Send a JSON body with required systolic and diastolic blood-pressure values in millimetres of mercury. Use the prepaid API when a health SaaS, telehealth intake form, wellness app, electronic worksheet, or school LMS needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with your own measurement workflow—seated rest, correct cuff size, and multiple readings—then store category alongside the raw numbers for dashboards and export CSV columns for systolic, diastolic, category, and guideline. Authors shipping SDKs can map category and category_label into chips, colour bands, and alert thresholds—the same ordered labels students and coaches learn from ACC/AHA teaching materials.