Corrected reticulocyte count
With 4.5 % reticulocytes and a hematocrit of 30, the corrected reticulocyte count is 3 %. The observed share is scaled by the patient's hematocrit over a normal 45, so anemia no longer inflates it. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Reticulocyte percentage
- 4.5
- Hematocrit
- 30
- Normal hematocrit
- 45 %
- Hematocrit ratio
- 0.6666666667
- Corrected percentage
- 3
When a complete blood count shows anemia, the raw reticulocyte percentage can look reassuringly high even though marrow production is not keeping up, because the same number of young red cells is counted against a smaller circulating pool. The corrected reticulocyte count, also called the reticulocyte index, rescales that observed percentage by the ratio of the patient's hematocrit to a normal adult hematocrit, conventionally forty-five percent. This calculator accepts the reticulocyte percentage and the patient hematocrit, computes CRC equals reticulocyte percentage times hematocrit divided by the normal hematocrit, and returns the corrected percentage.
What the corrected reticulocyte count measures and how the formula works
The corrected reticulocyte count answers a teaching question that the raw reticulocyte percentage cannot: given this patient's anemia, is the marrow releasing young red cells in proportion to the drop in hematocrit? Automated counters and stained smears report reticulocytes as a percentage of all red cells. When the circulating red-cell mass is low, that percentage inflates even if the absolute number of reticulocytes has not risen.
Textbook correction multiplies the observed percentage by the ratio of the patient's hematocrit to a normal adult hematocrit, conventionally forty-five percent, yielding CRC equals reticulocyte percentage times hematocrit over normal hematocrit. The engine does not compute the reticulocyte production index, which further divides by a maturation-time factor that depends on how severe the anemia is; that is a different search intent and a different formula.
It also does not convert a fraction hematocrit such as zero point thirty liters per liter unless you first express it as thirty percent, because the published contract is percent on the zero-to-one-hundred scale. The observed reticulocyte percentage must likewise be a finite non-negative percent in the same scale.
Classroom use, product pipelines, limits, and related searches
Hematology and nursing courses constantly assign corrected reticulocyte count drills from textbook complete-blood-count pairs, so a single trusted oracle that returns CRC beside the hematocrit ratio speeds grading and demo setup. Keep expectations educational: this is a calculation and learning tool, not a diagnostic medical device, and people with symptoms, known anemia, bleeding, hemolysis, or medication changes should follow professional medical advice rather than any single automated number. Prefer this landing when the search is corrected reticulocyte count, reticulocyte index, or CRC from reticulocyte percent and hematocrit.
It is not an absolute reticulocyte count in cells per microliter, not a reticulocyte production index with a maturation correction, not a plasma-volume or Nadler blood-volume tool, and not a hematocrit unit converter. If your laboratory ticket reports hematocrit as a fraction between zero and one, multiply by one hundred before you call. If you later need mean arterial pressure, anion-gap teaching ratios, or protein-to-creatinine screening, treat those as separate search intents rather than overloading this corrected reticulocyte count page.
What you can do with it
Hematology teaching apps
Education apps show the hematocrit ratio next to the corrected reticulocyte count without re-coding the forty-five percent adult reference on every client.
FAQ
What hematocrit values are rejected?
Hematocrit must be a finite percent between 0 and 100 inclusive.
Is this the reticulocyte production index (RPI)?
RPI further divides CRC by a maturation-time factor based on how low the hematocrit is, which is a different formula and a different search intent.
Is the corrected reticulocyte count calculator free?
The browser tool runs free on your device.
Can I change the normal hematocrit from 45 percent?
Curricula that use 40 or 42 percent as the adult reference can pass that value without changing the rest of the contract.
Why does the raw reticulocyte percentage need correcting?
In anemia there are fewer red cells, so the same number of young cells is counted against a smaller pool and the percentage looks higher than marrow output really is. Scaling by hematocrit removes that distortion.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/health/reticulocyte-count \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"reticulocyte_percentage":4.5,"hematocrit":30}'const res = await fetch("https://api.kit.forhosting.com/health/reticulocyte-count", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"reticulocyte_percentage": 4.5,
"hematocrit": 30
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/reticulocyte-count",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"reticulocyte_percentage": 4.5,
"hematocrit": 30
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/reticulocyte-count", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"reticulocyte_percentage":4.5,"hematocrit":30}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"reticulocyte_percentage":4.5,"hematocrit":30}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/reticulocyte-count", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"reticulocyte_percentage": 4.5,
"hematocrit": 30
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.reticulocyte_count",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Hematocrit values outside zero through one hundred fail with invalid_input and are never charged.
What the corrected reticulocyte count measures and how the formula works
The result is still a percentage, often called the reticulocyte index, and it is the quantity this capability returns as corrected_percentage. Hematocrit must be a finite number between zero and one hundred inclusive; values outside that closed interval fail with invalid_input. Optional normal_hematocrit defaults to forty-five and must be strictly greater than zero so the ratio is defined. Identical inputs always produce identical JSON because the path is pure arithmetic with stable rounding, no random seed, and no wall clock.
Inputs, response shape, and what invalid hematocrit looks like
The specified hematocrit error is the out-of-range case: a hematocrit of one hundred ten or of negative five is not between zero and one hundred, so the engine rejects it rather than inventing a wrap or a fraction conversion. Classic smoke checks include four point five percent reticulocytes with hematocrit thirty, which yields a ratio of two thirds and a corrected percentage of three, and eight percent reticulocytes with hematocrit twenty-two point five, which yields a corrected percentage of four. Send a JSON body with two required fields. reticulocyte_percentage is the observed reticulocyte percent from the complete blood count or smear, aliases retic, reticulocyte, retic_percent, and retic_pct, and must be a finite number between zero and one hundred. hematocrit is the patient hematocrit as a percent, aliases hct, hct_percent, and patient_hematocrit, and must also be a finite number between zero and one hundred inclusive. Optional normal_hematocrit, aliases normal_hct, hct_normal, and reference_hematocrit, is the adult reference used in the denominator; it defaults to forty-five and must be strictly greater than zero and at most one hundred. Missing fields, empty strings, non-numeric values, NaN, and Infinity fail with invalid_input naming the field and are not charged. On success the response echoes the cleaned reticulocyte_percentage, hematocrit, and normal_hematocrit, reports hematocrit_ratio as hematocrit divided by the normal reference, and sets corrected_percentage to the CRC. unit is the percent sign, formula restates corrected_percentage equals reticulocyte_percentage times hematocrit over normal_hematocrit, and method is always corrected_reticulocyte_count so clients can branch without sniffing shapes. Successful API calls cost $0.002 per item; validation failures never consume prepaid balance.
Classroom use, product pipelines, limits, and related searches
Education apps can show the intermediate hematocrit_ratio next to corrected_percentage without re-coding the forty-five percent default on every client. Simulation labs and health-education backends that already store reticulocyte percent and hematocrit can call a prepaid endpoint instead of duplicating the quotient in every language. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Integration use cases
Medical and nursing school homework
Students submit observed reticulocyte percent and patient hematocrit, then pin expected corrected_percentage JSON in automated checkers with deterministic outputs.
Simulation labs and SaaS backends
Server pipelines that already store CBC reticulocyte percent and hematocrit call a prepaid endpoint for CRC fields instead of duplicating the formula in every language.
Technical questions
How is the corrected reticulocyte count calculated?
corrected_percentage = reticulocyte_percentage × (hematocrit / normal_hematocrit). The default normal_hematocrit is 45 percent. The response also includes hematocrit_ratio and a formula string.