Enter the tests from your health checkup or clinic report. Review numbered explanations, supplied laboratory ranges and a summary of supported result combinations.
Interactive form loads when the script is enabled. General guidance is available below.
What can you enter?
The form covers 72 tests. This is an input catalog, not a recommendation to order every test. Availability differs by country, clinic and screening package.
Do I need to fill every field?
Leave them blank. Blank values are omitted from interpretation and are never assumed to be zero or normal. Use only results from the same blood draw.
Why are units and reference intervals important?
Select the exact units printed on your report. Reference intervals vary by method and population. All 72 tests receive result-specific explanations. Without a laboratory interval, sourced adult intervals or separate clinical criteria are used. Unknown fasting, sex or age details receive conditional explanations. Personal treatment targets differ from reference intervals. Select a sign only when one is printed on the report. Standard glucose screening categories are a separate concept and apply only under the stated conditions.
Can this diagnose an illness?
No. A high or low result is not a diagnosis, and in-range results do not exclude disease. Tumor markers cannot independently confirm or exclude cancer. Pregnancy, childhood and specialist treatment need individualized interpretation.
Related tools
Why do glucose and HbA1c explanations differ?
This record maps a limited set of adult glucose and HbA1c screening branches to the deployed rules and official evidence. Laboratory reference intervals and screening thresholds are different concepts.
- 1. Fasting glucose: 100 and 126 mg/dL
- The code separates 100 to below 126 from 126 or above when fasting is selected and diabetes is not established. Fasting means at least eight hours. See NIDDK, “Diabetes Tests & Diagnosis”: “Fasting plasma glucose test” and the diagnostic-results table. Nonfasting values do not receive fasting categories; unknown fasting status produces conditional wording. Ordinary post-meal testing is not an OGTT. Pregnancy needs different criteria; one result alone does not confirm diabetes.
- 2. HbA1c: 5.7% and 6.5%
- Branches are below 5.7%, 5.7% to below 6.5%, and at least 6.5%. See NIDDK, “The A1C Test & Diabetes”: “A1C results and what the numbers mean” and “A1C tests can be affected by changes in red blood cells or hemoglobin”. Fasting is unnecessary. Blood loss, transfusion, iron deficiency and hemoglobin variants can affect results. Reported interference triggers a reliability warning rather than a dependable glucose classification. Established diabetes uses individual treatment goals instead of new screening labels.
- 3. When the program withholds exact-value interpretation
- The implementation does not treat “<126” as exactly 126. Conflicting entered intervals and H/L flags trigger a request to check the original report. These are software input-handling rules, not evidence that NIDDK validated this tool.
What was actually checked?
Check date: 1 November 2026, Korea Standard Time. An AI-assisted document-to-code comparison was followed by local execution of the retrieved, unmodified calculation and interpretation functions. All 15 selected cases followed the expected branches: fasting glucose 99, 100, 125 and 126 mg/dL; HbA1c 5.6%, 5.7%, 6.4% and 6.5%; nonfasting and unknown fasting status; established diabetes; A1c interference; a bounded value; conflicting interval/flag entries; and exclusion of a special population from adult glucose explanations. For example, 126 mg/dL produced confirmation-needed diagnostic-range wording when fasting, but no fasting category when nonfasting.
This is a source comparison and a limited software check. It does not validate low-glucose or emergency alerts, every unit conversion, all combined explanations, the other 70 tests, or accuracy in real patients. This remains a development version without independent clinician validation.
Kidney and electrolyte results: what the rules do—and do not establish
Evidence and software check: 1 November 2026 (Korea Standard Time). This separate check covers selected branches involving creatinine, reported eGFR, BUN, urea, uric acid, sodium, potassium, chloride, total CO₂, total calcium, phosphorus and magnesium. It does not extend the glucose check to every test or validate diagnosis in real patients.
eGFR is a numeric category, not a confirmed chronic diagnosis
For an exact reported eGFR in mL/min/1.73 m², the code uses G1 ≥90, G2 60–<90, G3a 45–<60, G3b 30–<45, G4 15–<30 and G5 <15. KDIGO 2024, Tables 1–2 and Practice Point 1.1.3.2 distinguishes these ranges from CKD diagnosis: chronicity requires evidence over at least three months, and cause and urine albumin also matter. G1/G2 alone do not establish CKD. This is not an instruction to wait three months before seeking care.
Keep a reported inequality. For example, “≤30” is not exactly 30. The current tool withholds an exact G category for bounded results, including “≥90”; its bounded-result text asks for clinician review. When eGFR is entered on its own, “<30” also triggers its additional prompt-review wording, whereas “≤30” and “<60” do not trigger that extra paragraph. Absence of that paragraph does not mean the result is normal or needs no follow-up. The form does not assess duration or calculate an ACR-based CKD risk category.
Different tests and units must stay different
BUN measures the nitrogen component of urea; do not copy a urea mg/dL number into BUN. The form accepts BUN in mg/dL, and urea in mmol/L or mg/dL. Its urea conversion is 1 mmol/L = 6.006 mg/dL, consistent with the Luzerner Kantonsspital urea method information. Total calcium is not ionized calcium, and chemistry total CO₂ is not blood-gas pCO₂. Use the analyte, unit and laboratory interval printed on the report.
Critical alerts are institutional examples, not a complete triage system
In the adult branch, potassium ≤2.5 or ≥6.0 mmol/L triggers an alert; sodium ≤120 or ≥160 mmol/L does too. The potassium upper boundary reflects Mayo’s critical/semi-urgent results list, updated October 2026, chemistry table (page 2). North Bristol’s out-of-hours protocol, appendix instead lists ≥6.5 for potassium. These notification policies are not universal emergency diagnoses or normal ranges. Follow your testing service’s urgent instructions regardless of this tool’s output; severe symptoms need immediate medical help.
Unit rounding can affect borderline results. For total calcium the tool uses Mayo’s rounded factor: mg/dL ×0.25 = mmol/L. KDIGO’s conversion table uses 0.2495. Thus 13 mg/dL corresponds to 3.25 or 3.2435 mmol/L under the respective conventions; the tool must not replace the original report or a laboratory critical alert.
What was actually tested?
- Exact eGFR values just below, at and above 15, 30, 45, 60 and 90; selected bounded and conflicting entries.
- Potassium boundaries 2.5, 6.0 and 6.5; sodium 120 and 160; selected total-calcium, magnesium and phosphorus alert boundaries, in their stated base units.
- Selected laboratory-interval classifications, conversions, creatinine/BUN combinations, population exclusions and combined electrolyte messages. Low magnesium with low potassium or calcium prompts joint assessment, not a supplementation prescription; see NIH ODS, Magnesium: deficiency and assessment.
The saved, unchanged engine passed 146 predefined executable assertions; six additional checks located saved bilingual renal caveat text, and one checked that the tested source matched the saved script. These are limited software checks, not 153 clinical validation cases. Some checks record implementation behavior rather than independently establish clinical accuracy. The saved renal text builder was also run locally for five inequality/exact-value examples; this is not a live browser test. Every explanatory cause, every combined pattern, all conversions and the remaining catalog are not validated by this batch. Independent clinician validation has not been established.
Sources and methodology
Explanations use explicit rules and supplied laboratory intervals, not a live AI diagnosis. Content review date: 1 October 2026. This development version has not received independent clinician validation.