{{ summary.title }}
{{ summary.primary }}
{{ summary.secondary }}
{{ badge.text }}
Growth percentile trend inputs
Use the child's charting sex: Female or Male.
Enter rows in this unit: cm/in for height, kg/lb for weight, kg/m² for BMI.
kg/m²
Default hybrid: WHO under 24 months, CDC from 24 months onward.
Enable only when corrected-age review is part of the child's growth record.
{{ apply_corrected_age ? 'On' : 'Off' }}
Enter completed weeks at birth, 22-40; term births can stay at 40.
weeks
Use 6-36 months; 24 months is common for preterm follow-up workflows.
months
Use one row per visit: age_months,value. Example: {{ visitExampleLine }}.
{{ visitRowCountText }}
Default downward; choose Any for weight/BMI reviews where either direction matters.
Conservative tightens alerts; Tolerant allows more drift; Balanced keeps defaults.
Enter 0.5-12 months, for example 3 for quarterly growth review.
months
Use Routine, Priority, or Urgent to match the current care context.
Enter 1-4 major lane crossings; lower values are more sensitive.
bands
Enter 8-40 percentile points; 20 catches larger channel shifts.
points
Use 3-18 months; short horizons keep the projection as a screening cue.
months
Metric Value Copy
{{ row.label }} {{ row.value }}
No metrics yet.
{{ header }} Copy
{{ cell }}
No visit ledger rows yet.
{{ header }} Copy
{{ cell }}
No interval audit rows yet.
Priority Recommendation Rationale Timeline Copy
{{ row.priority }} {{ row.recommendation }} {{ row.rationale }} {{ row.timeline }}
No follow-up plan rows yet.

        
Customize
Advanced
:

Introduction

Growth percentile trend review asks whether a child's measurements are holding roughly the same position on an age- and sex-specific reference, or whether that position is drifting across time. That matters because a child can keep getting taller, heavier, or show a changing body mass index while still moving away from the expected channel for the same age and sex.

A latest percentile answers only one part of the question. Serial review adds direction, pace, and context. It helps show whether the pattern looks steady, whether it crosses into a new band, and whether a short follow-up interval makes more sense than routine remeasurement.

The interpretation can become harder near early-childhood chart transitions. In U.S. practice, WHO standards are recommended below 24 months and CDC growth charts from 24 months onward, so a series that spans that boundary can change reference family even when measurement technique stays consistent. Preterm follow-up can add another layer because some visits are interpreted with corrected age rather than chronological age.

That makes the result most useful as a screening aid for organizing serial measurements rather than as a diagnostic verdict. It helps turn a run of visits into a clearer trend story, but the result still depends on clean anthropometry, sensible visit spacing, and the wider clinical picture.

This result is informational. It can support pediatric growth review, but it does not replace standardized charting, diagnosis, or treatment decisions.

Technical Details:

Each visit is turned into a same-age, same-sex position on a reference distribution. The raw measurement still matters, but the main question is where that measurement sits relative to the expected spread at that age. A child who gains height or weight can still drift downward in percentile terms if the gain is slower than the reference pattern, and can drift upward if it is faster.

The per-visit calculation uses LMS parameters from embedded WHO and CDC reference tables. For a given visit, the observed measurement is compared with the age-specific median and spread for the active reference family, then converted into a z-score and percentile. In hybrid mode, the current logic uses WHO below 24 months and CDC from 24 months onward. In WHO-first mode, WHO stays active through 60 months before continuing with CDC. CDC exact uses CDC tables across the supported age span.

Corrected age changes the reference age rather than the raw measurement. When prematurity correction is enabled, the review age is reduced by the prematurity offset until the chosen stop point is reached. That matters because the same value can land at a different percentile when it is compared with a younger reference age.

z = ( xM ) L - 1 LS Percentile = Φ(z)×100

x is the observed measurement, M is the reference median, S is the spread term, and L handles skew. When L is effectively zero, the logarithmic form is used instead.

The trend layer sits on top of those visit-level positions. Net percentile shift is the latest percentile minus the first. Major band crossings count movement across the calculator's fixed landmarks at P3, P15, P50, P85, and P97. The projected percentile extends the fitted percentile slope forward by 3 to 18 months, then clamps the result inside the percentile scale. Alert status turns on when either the total crossing count reaches the configured threshold or the percentile shift in the chosen direction is large enough.

Rule elements that change the trend read
Rule element Current logic Why it changes the read
Reference pathway Hybrid uses WHO below 24 months and CDC from 24 months onward. WHO-first keeps WHO through 60 months, then continues with CDC. CDC exact stays on CDC. Percentiles can shift around early-childhood handoff points because the source family changes.
Corrected age When enabled, reference age is reduced by the prematurity offset until the chosen stop point from 6 to 36 months. Early preterm visits may compare against a younger reference age than the chronological age suggests.
Major band crossings Crossings are counted across P3, P15, P50, P85, and P97. The alert threshold is adjustable from 1 to 4 crossings and defaults to 2. Band changes summarize whether the series is staying in the same lane or moving across clinically familiar landmarks.
Directional shift alert The shift rule can watch downward drift only, upward drift only, or any direction. The default threshold is 20 percentile points and can be set from 8 to 40. This separates ordinary fluctuation from larger moves that deserve faster review even when crossings are limited.
Trend confidence High confidence requires at least 4 visits over at least 12 months. Moderate requires at least 3 visits over at least 6 months. Shorter series are labeled low confidence. Projection and drift labels are more believable when the series is longer and better spaced.

Those rules are why the latest percentile cannot be read in isolation. A latest point near the middle of the chart can still carry a review alert if the path crossed several bands, while a point near a boundary may still read as low-risk when the series is long, steady, and internally consistent.

Everyday Use & Decision Guide:

Start with one metric stream and one measurement style. Choose height, weight, or BMI, keep the unit consistent, and enter one visit per line as age_months,value. The review is most believable when every point in the series was measured in a similar way.

The reference pathway matters most when the series spans infancy into later childhood or when the latest point sits near an alert boundary. Hybrid is the safest baseline because it matches the built-in WHO-to-CDC handoff. If you are comparing runs, keep the same pathway each time. Otherwise a change in reference family can look like biologic drift when it is really a modeling difference.

Prematurity correction should be deliberate rather than automatic. Turning it on changes the age used for interpretation while the correction window is active, so it can materially move the percentile at early visits. If your workflow uses corrected age, document it consistently and keep the same stop point for repeat reviews.

  • Read Trend Brief first for the overall verdict, net shift, projected percentile, and confidence label.
  • Use Visit Ledger when you need to see chronological age, reference age, percentile, z-score, band, and source family side by side.
  • Use Interval Audit when the question is "which interval changed the story?" because it isolates measurement deltas, percentile deltas, z-score deltas, and band crossings.
  • Use Follow-Up Plan when you want plain-language timing and priority rather than numbers alone.

Risk tolerance and intervention urgency do different jobs. Risk tolerance can tighten or loosen the alert thresholds and follow-up window. Intervention urgency sharpens the follow-up tone and timing without changing the underlying percentile math.

Step-by-Step Guide:

  1. Choose sex, then select the metric stream you want to track: height, weight, or BMI.
  2. Pick the matching unit. Height accepts centimeters or inches, weight accepts kilograms or pounds, and BMI stays in kg/m^2.
  3. Paste one visit per line into Visit data rows using age_months,value. Decimal ages are allowed.
  4. Run the first review with the default pathway and alert settings unless you already know you need a stricter or looser screening posture.
  5. Read Trend Brief first. Focus on Trend verdict, Latest percentile, Net percentile shift, Major band crossings, Projected percentile, and Trend confidence.
  6. Open Visit Ledger next if the series crosses 24 months or uses corrected age. That is the fastest place to verify which reference family and age basis each visit used.
  7. Open Interval Audit when you need to pinpoint whether the concerning change came from one interval or from a broader drift across several visits.
  8. Use Trend Charts for the visual view. Percentile Runway shows the percentile path and short projection. Reference Lane Map shows the observed measurement against the exact percentile lanes at each visit age.
  9. Export only after the series looks believable. Trend Brief and Visit Ledger support CSV and DOCX, Interval Audit and Follow-Up Plan support CSV, chart cards export PNG or CSV, and JSON exports the full structured payload.

Interpreting Results:

A stable result usually looks like a small net shift, no meaningful band crossings, and a projected percentile that stays close to the current lane. A review-worthy result usually combines a larger shift with repeated crossings, a stronger direction-specific alert, or a low-confidence series that still looks concerning enough to recheck sooner.

The reference-age fields matter whenever prematurity correction is on or the series crosses the early-childhood handoff. A visit can move even when the raw value looks ordinary if the comparison age changes or the series switches from WHO to CDC. That is why the ledger is often more useful than the headline badge when a case is close to a boundary.

The projection should be read as a short warning signal rather than as a forecast. It assumes the recent percentile slope continues in a straight line. Real growth does not always behave that way, especially when visits are sparse or measurement technique changes.

How to read common output patterns
Pattern What it usually means What to check next
Stable channel The series stays in roughly the same percentile neighborhood and does not accumulate enough crossings or directional shift to trigger a review alert. Confirm routine follow-up timing and keep measurement technique consistent.
Downward drift The later visits are landing lower in percentile terms than the early visits, often with one or more band crossings. Review the interval where the shift began, then recheck measurement quality and visit spacing.
Upward drift The series is moving upward across the reference lanes. That can reflect catch-up growth, excess gain, or a reference-family transition that needs context. Check whether the change is persistent across several intervals and whether the handoff at 24 months affected the comparison.
Low confidence The series is too short or too compressed in time for the trend label to carry the same weight as a longer run. Interpret the result cautiously and prioritize another well-measured visit before overreading the projection.

Worked Examples:

Example 1: A stable height series across the WHO-to-CDC handoff

Enter the default height rows 12,74.9, 24,86.1, 36,95.0, and 48,102.2 in centimeters. The review processes 4 visits across 36 months, places the first visit at the 63.4th percentile and the last at the 63.0th percentile, and returns a net shift of only -0.5 points with 0 band crossings. The projected percentile at 6 months is 62.8, so the series stays in a stable channel even though the reference family changes from WHO at 12 months to CDC from 24 months onward.

Example 2: A corrected-age BMI series in early infancy

Use BMI rows 3,13.8, 6,14.6, 9,15.4, and 12,16.1, then turn on corrected age with gestational age set to 32 weeks and a 24-month stop point. The review shifts the reference ages to 1.2, 4.2, 7.2, and 10.2 months, all within the WHO segment. In this run the latest percentile is 36.5, the net shift is +13.8 points, and the series logs 2 band crossings, so the follow-up tone moves to a priority posture even though the latest point is still inside the middle percentiles.

Example 3: A downward height drift that triggers review

Enter height rows 12,76.5, 24,84.0, 36,90.0, and 48,95.0 with the crossing alert tightened to 1 and the shift alert set to 12 points. The first visit lands at the 83.3rd percentile and the last at the 8.8th percentile. The summary shows a -74.4 point net shift, 2 major band crossings, and a projected percentile of 0.1 at the 6-month horizon. That is the kind of output where Interval Audit matters because it shows that the largest single drop occurred from 12 to 24 months.

Example 4: Troubleshooting a red error banner

If a row contains text instead of numbers, such as 24,abc, the parser returns a row-specific numeric error and the trend should not be interpreted. If only one valid row remains after cleanup, the review stops and asks for at least two visit rows. The corrective path is to fix the non-numeric line, keep one visit per row, and rerun the baseline before comparing summaries or charts.

FAQ:

Why did the percentile change even though the child grew?

Because the review compares each measurement with the expected distribution at that age. A child can gain centimeters, kilograms, or BMI points and still move downward in percentile terms if the gain is slower than the reference pattern.

What does Ref age (mo) mean in the ledger?

It is the age actually used for percentile lookup. When prematurity correction is off, it matches chronological age. When correction is on and still inside the stop window, it can be younger than the chronological age.

Why can one series use WHO at one visit and CDC at another?

Hybrid mode changes source family at 24 months. That mirrors the common U.S. practice of using WHO standards below age 2 and CDC growth charts from age 2 onward.

Why can the follow-up priority rise even when the latest percentile is not extreme?

Because the review is driven by trend as well as position. A middle-percentile latest point can still trigger a stronger plan when the series crossed several bands, shifted quickly, or carries a short, low-confidence history that still looks unstable.

Why am I seeing a red error banner?

The most common reasons are a non-numeric row, a zero or negative measurement, or too few valid visit lines after parsing. Fix the bad row and make sure at least two valid visits remain.

Does my visit data stay in the browser?

Yes. This calculator does not ship a server helper for the main workflow, so the calculations, tables, charts, and exports are generated in the current browser session.

Glossary:

Percentile
The relative position of a measurement within the same-age, same-sex reference distribution.
Z-score
The distance from the reference median expressed in standard-deviation units.
Reference age
The age used for percentile lookup after any corrected-age adjustment has been applied.
Major band crossing
Movement across one or more of the calculator's fixed percentile landmarks: P3, P15, P50, P85, and P97.
Net percentile shift
The latest percentile minus the first percentile in the series.
Trend confidence
A label based on visit count and age span that indicates how much weight the calculator gives the trend summary.