Sodium correction rate calculator
Divide the planned change in sodium by the hours you have: going from 118 to 126 mEq/L over 24 hours is a third of a mEq/L per hour, or 8 per day. It works for raising and for lowering sodium. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Current sodium
- 118
- Target sodium
- 126
- Duration
- 24
- Delta sodium
- 8 mEq/L/h
- Correction rate
- 0.3333333333
- Rate per 24h
- 8
- Direction
- increase
Serum sodium correction rate is how fast sodium concentration changes when it moves from a current value to a target value over a stated treatment window. Nursing calculations, electrolyte lectures, and hyponatremia worksheets all ask for that hourly figure so a planned rise or fall can be compared with teaching limits. This sodium correction rate calculator accepts current sodium, target sodium, and a strictly positive duration in hours, returns the correction rate per hour together with the sodium delta and a twenty-four-hour equivalent, and rejects a non-positive duration so a divide-by-zero never becomes a silent Infinity.
How the hourly sodium correction rate is computed from current Na, target Na, and duration
Serum sodium correction rate is the planned change in sodium concentration divided by the hours over which that change is intended to occur. In symbols, correction rate equals target sodium minus current sodium, all divided by duration. Sodium is reported in milliequivalents per litre or millimoles per litre, which are numerically equal for monovalent sodium, and duration is reported in hours so the quotient has units of milliequivalents per litre per hour.
A positive rate means sodium is being raised, the usual direction when teaching correction of hyponatremia; a negative rate means sodium is being lowered, the usual direction when teaching correction of hypernatremia; a zero rate means the target equals the current value. Duration must be a finite number strictly greater than zero: a zero interval would divide by zero, and a negative interval would reverse the arrow of time rather than describe a treatment window. This capability implements that closed form exactly.
It does not choose intravenous fluids, does not apply the Adrogue-Madias predicted change per litre of infusate, does not estimate total body water, and does not enforce a clinical safety cap such as eight or twelve milliequivalents per litre per day. Those limits belong to guidelines and to qualified clinicians. Always frame outputs as educational estimates of a planned rate, not as a diagnosis, a prescription, or a substitute for professional judgment, laboratory reference ranges, or bedside osmotic-demyelination risk assessment.
Where sodium correction rate calculators show up in real work
Secondary-school and college physiology and nursing courses constantly assign sodium correction drills from textbook hyponatremia and hypernatremia panels, so a single trusted oracle that returns the hourly rate, the twenty-four-hour equivalent, and the signed delta speeds grading and demo setup. Clinical training programs use the planned rate as a bedside arithmetic check before discussing osmotic demyelination risk or overly rapid falls in chronic hypernatremia, and instructors need deterministic answer keys that match hand arithmetic on milliequivalents per litre and hours.
Product teams building educational lab or simulation widgets want a documented current-target-duration path that clients can audit by hand rather than a black-box fluid engine that mixes several formulas without disclosure. Research assistants preparing synthetic electrolyte datasets need stable correction-rate labels from known triples without network calls or model drift. If you later need albumin-corrected calcium, anion gap, mean arterial pressure, or an infusate-change predictor, treat those as separate search intents and landings rather than overloading this sodium correction rate calculator page.
Always present results as educational estimates of a planned rate; clinical decisions require qualified professionals, local protocols, and assays this tool does not collect.
What you can do with it
Nursing and physiology demos
Show planned rise or fall of serum sodium in training labs without mixing Adrogue-Madias fluid models or diagnostic cutoffs on the same landing.
FAQ
What is sodium correction rate?
It is the planned change in serum sodium divided by the hours over which that change is intended.
What happens if duration is zero or negative?
A non-positive duration cannot define a rate per hour, so the engine rejects it rather than returning Infinity or inventing an absolute value.
What does it cost?
The browser tool is free and runs locally.
What does a negative correction rate mean?
That sodium is being lowered, the usual direction when hypernatremia is corrected. A positive rate means sodium is being raised, as when correcting hyponatremia, and zero means the target equals the current value.
Does the calculator warn me if the correction is too fast?
No. It reports the planned rate but does not apply a safety cap such as 8 or 12 mEq/L per day. Those limits come from guidelines and qualified clinicians, so check the result against them yourself.
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/sodium-correction-rate \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"current_sodium":118,"target_sodium":126,"duration":24}'const res = await fetch("https://api.kit.forhosting.com/health/sodium-correction-rate", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"current_sodium": 118,
"target_sodium": 126,
"duration": 24
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/health/sodium-correction-rate",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"current_sodium": 118,
"target_sodium": 126,
"duration": 24
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/health/sodium-correction-rate", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"current_sodium":118,"target_sodium":126,"duration":24}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"current_sodium":118,"target_sodium":126,"duration":24}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/health/sodium-correction-rate", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"current_sodium": 118,
"target_sodium": 126,
"duration": 24
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "health.sodium_correction_rate",
"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
How the hourly sodium correction rate is computed from current Na, target Na, and duration
The computation is pure floating-point arithmetic with no network calls, no random seeds, no wall-clock timestamps, and no machine-learning drift, so identical triples of current sodium, target sodium, and duration always yield identical JSON.
What you send and what you get back
Send three required fields. Classic smoke checks include one hundred eighteen to one hundred twenty-six over twenty-four hours, which yields a correction rate of one third of a milliequivalent per litre per hour and eight milliequivalents per litre per day, and one hundred sixty to one hundred fifty over twenty hours, which yields a negative half milliequivalent per litre per hour. If your upstream form collects minutes, convert to hours first so the denominator stays in the unit this contract documents. The field current_sodium is the starting serum sodium in milliequivalents per litre and must be a finite number; aliases current_na, na_current, serum_sodium, and sodium_current are accepted. The field target_sodium is the destination serum sodium in the same units and must be finite; aliases target_na, na_target, goal_sodium, and sodium_target are accepted. The field duration is the treatment window in hours and must be finite and strictly greater than zero; aliases hours, duration_hours, time_hours, and treatment_hours are accepted. Missing fields, non-numeric strings, NaN, Infinity, and zero or negative duration fail with invalid_input and are not charged. On success the response echoes the cleaned current_sodium, target_sodium, and duration values, reports delta_sodium as target minus current, reports correction_rate as that delta divided by duration, reports rate_per_24h as the same planned change scaled to twenty-four hours, sets direction to increase, decrease, or none, labels unit as mEq/L/h with unit_sodium mEq/L and unit_duration h, and restates formula as rate equals target_sodium minus current_sodium over duration with method sodium_correction_rate. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where sodium correction rate calculators show up in real work
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
Classroom electrolyte answer keys
Generate hourly sodium correction rate, twenty-four-hour equivalent, and signed delta from textbook current/target/duration triples so instructors and auto-graders share one transparent ground truth.
Deterministic electrolyte fixtures
Bulk-produce stable correction-rate labels for synthetic panels and regression tests with hard invalid_input on non-positive duration.
Technical questions
What formula and units do you use?
correction_rate = (target_sodium − current_sodium) / duration, with sodium in mEq/L (equal to mmol/L for Na+) and duration in hours. The primary result is reported in mEq/L/h; rate_per_24h scales the same plan to a day.
How do I format the input?
Send current_sodium, target_sodium, and duration as finite numbers (e.g. 118, 126, and 24). Duration must be strictly greater than zero. Documented aliases such as current_na, target_na, and hours are also accepted.