| Metric | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
| No metrics yet. | ||
| {{ header }} | Copy |
|---|---|
| {{ cell }} | |
| No detail rows yet. |
| Priority | Recommendation | Rationale | Timeline |
|---|---|---|---|
| {{ row.priority }} | {{ row.recommendation }} | {{ row.rationale }} | {{ row.timeline }} |
| No guidance recommendations available yet. | |||
| Handoff item | Value | Operational cue |
|---|---|---|
| {{ row.label }} | {{ row.value }} | {{ row.note }} |
| No handoff brief rows available yet. | ||
Pediatric growth review is mainly about trajectories. A child’s height, weight, and body mass index change with age, sex, and developmental stage, so the practical question is rarely whether one number looks big or small in isolation. The more useful question is how the child is tracking over time and whether that direction still looks plausible.
That is why serial visits matter. A child who holds roughly the same percentile across several measurements tells a different story from one whose height drifts downward, whose weight shifts sharply, or whose body mass index begins crossing alert thresholds after age two. The meaning comes from the sequence, not just the latest point.
Growth Chart Report Generator turns that sequence into one compact report. You enter sex and visit rows in the format age in months, height in centimeters, and weight in kilograms, and the page builds percentile and z-score estimates for each visit, a screening-flag count, a triage lane, a suggested follow-up interval, a guidance table, a handoff brief, a trend chart, and a full JSON export.
That makes it useful for educational review, pre-visit organization, and team handoffs where you want the numbers, the alert logic, and the operational cue in one place. A stable series can stay in a routine lane, while a falling height percentile plus low recent height velocity can push the handoff toward urgent review.
The important boundary is accuracy. This page does not implement official CDC or WHO LMS chart software. It uses internal interpolated reference curves with WHO-style, CDC-style, or hybrid adjustments to produce approximate screening estimates, so it should be read as structured decision support rather than as a replacement for formal clinical growth-charting systems.
The simplest workflow is to paste one visit per line as age_months,height_cm,weight_kg, using the same measurement technique you would trust in a chart review. The page accepts flexible separators, sorts visits by age, and uses the latest entry when duplicate ages appear. That keeps the input format forgiving while still producing a clean chronological report.
After the rows are entered, the top summary answers the fastest operational questions first: how many critical flags and watch flags were found, where the latest visit sits for height, weight, and BMI percentiles, what triage lane the case currently belongs to, and how soon the next follow-up should happen under the chosen rules.
The rest of the output is split into purpose-driven tabs. The metrics tab gathers headline values such as flag counts, latest percentiles, triage lane, and follow-up timing. The visit table lists each visit with height, weight, BMI, percentile estimates, and recent height velocity. The guidance tab turns the current result into prioritized recommendations with rationales and timelines. The handoff tab condenses the report into queue-lane language for operational transfer. The chart tab plots height, weight, and BMI percentiles together across time, and the JSON tab exposes both inputs and derived outputs in one structured payload.
The advanced settings are there because not every team wants the same alert posture. Some controls change the screening logic directly, such as the growth reference set, band-crossing threshold, percentile-shift threshold, height-velocity floor, BMI alert percentile, baseline follow-up interval, WHO-CDC transition marker, report focus mode, and the number of critical flags required for urgent triage. Other controls mainly change the guidance tone and follow-up posture, such as risk tolerance, intervention urgency, catch-up priority, and projection confidence.
The export options follow the same practical pattern. Metrics and visit tables can be copied as CSV, downloaded as CSV, or exported as DOCX. Guidance can be copied or downloaded as CSV. The chart can be downloaded as PNG, WebP, JPEG, or CSV. The entire report can also be copied or downloaded as JSON. Routine calculations happen in the browser, so the point at which data leaves the page is the point where you choose to copy, download, or share it.
For each visit, the page converts the raw height and weight into a BMI value using the standard relationship of kilograms divided by meters squared. It then estimates height, weight, and BMI percentiles by comparing each measurement with sex-specific internal reference medians and standard deviations. Those estimates are also expressed as z-scores, which are useful when you want to understand how far a value sits from the tool’s internal midpoint rather than only which percentile it lands near.
The reference-set control adjusts those internal curves in three different ways. WHO-style settings place more emphasis on birth-to-60-month behavior, CDC-style settings lean more toward the age 24 months and older framing, and the hybrid mode blends those adjustments for continuity across the series. Because the underlying curves are internal approximations rather than official CDC or WHO chart tables, the output is best treated as a screening estimate and handoff summary, not as a definitive charting result.
The report builder focuses on the latest visit and the most recent interval, because those are the areas where handoff urgency usually lives. It looks for low linear growth percentile, low or high weight percentile, elevated BMI percentile at age 24 months or older, large recent percentile shifts, downward crossings of major percentile bands, and height velocity below the configured floor. Each signal is labeled either critical or watch, and those counts feed the triage lane and recommended follow-up timing.
| Signal | Default trigger in the package | Severity |
|---|---|---|
| Low height percentile | Latest height below the 3rd percentile | Critical |
| Low weight percentile | Latest weight below the 3rd percentile | Watch |
| High weight percentile | Latest weight above the 97th percentile | Watch |
| Elevated BMI percentile | Age 24 months or older and BMI at or above the chosen threshold, 95th by default | Watch |
| Downward height band crossing | Recent drop across the configured number of major bands, 2 by default | Critical |
| Large weight percentile shift | Recent change meets the configured shift threshold, 25 points by default | Watch |
| Low recent height velocity | Recent annualized height velocity below the chosen floor, 4 cm/year by default | Critical |
The triage lane is then derived from those flag counts. If critical flags meet or exceed the urgent critical threshold, the report moves into the urgent lane. If there are no urgent-critical conditions but at least one watch condition, it moves into the priority lane. Otherwise it remains in the routine lane. The suggested follow-up interval begins with the baseline follow-up setting and can be shortened automatically when flags appear or when the chosen focus mode makes the latest pattern more concerning.
The focus mode is deliberately narrow. Balanced mode treats linear growth, weight trajectory, and BMI together. Linear-growth mode shortens follow-up more aggressively when height percentile is low. Adiposity-risk mode does the same when BMI reaches the 95th percentile or higher. None of those modes changes the raw percentile calculations; they change the emphasis of the operational summary and timing.
The guidance tab adds one more layer. Risk tolerance changes how early borderline values are treated as actionable. Intervention urgency compresses timelines and raises recommendation priority. Catch-up priority changes the recommendation emphasis toward linear growth, weight gain, or a balanced plan. Projection confidence changes how cautious the wording should be when the report is handed off. Again, those controls mainly affect the recommendation language and timing rather than the core visit calculations.
The JSON export mirrors the report in a structured way. It contains a timestamp, the raw inputs, the summary object, the metrics table, the detail rows, the handoff brief rows, the guidance rows, and the chart payload. That makes the output useful not only for reading in the page, but also for archiving, audit trails, or passing the current state into another workflow you control.
age_months,height_cm,weight_kg.A percentile is a comparison with peers of the same sex and age inside the chosen reference model. A child does not need to sit near the 50th percentile to be doing well. In many real growth reviews, the more important question is whether the child is staying near a familiar path or drifting away from it unexpectedly.
The report’s flag counts are meant to make that drift visible. A critical flag points to a stronger signal that should move a case up the review queue. A watch flag suggests closer monitoring or contextual review without necessarily implying urgent pathology. The categories are operational cues, not diagnoses.
The age 24-month mark is especially important. In U.S. practice, WHO growth standards are generally used before age two and CDC growth charts after age two, and BMI-for-age becomes a standard framing tool once children are 2 years or older. This page makes that transition explicit with both the reference-set control and the WHO-CDC transition marker in the handoff brief.
The follow-up interval should also be read as a workflow recommendation rather than a hard clinical order. It is derived from your baseline follow-up setting, the number and type of flags, and the selected focus mode. A shorter follow-up suggestion means the current pattern deserves quicker reassessment under the rules you chose, not that the child automatically has a confirmed disorder.
Measurement quality remains one of the biggest hidden error sources. Inaccurate length or height technique, different scales, clothing changes, unit mistakes, or inconsistent visit spacing can create apparent percentile shifts and false velocity signals. When a result looks surprising, the first question should usually be whether the underlying measurements are trustworthy.
With the default sample series, the page produces a five-visit report ending at 36 months with height at 56.7th percentile, weight at 54th percentile, BMI at 22.5th percentile, no active flags, a routine lane, and a three-month follow-up suggestion. That is the kind of output you would expect when the series stays coherent across time.
If the latest visit drops below the 3rd percentile for height and the most recent annualized height velocity also falls below the configured floor, the page can produce multiple critical flags at once. In practice that moves the report into the urgent lane, shortens the follow-up interval, and shifts the handoff language toward prompt review of measurement quality and possible causes of faltering growth.
For a child older than 24 months whose BMI percentile rises above the chosen alert threshold, the report can show a watch-level adiposity signal even if height trajectory remains steady. In that situation, the guidance tab usually stays less acute than an urgent linear-growth case, but it still shortens review timing and changes the operational emphasis if adiposity-risk focus is selected.
No. It uses internal interpolated reference curves with WHO-style, CDC-style, or hybrid adjustments. That makes it useful for approximate screening and handoff support, but not a substitute for formal charting systems.
Use one visit per line as age in months, height in centimeters, and weight in kilograms. The parser accepts common separators such as commas, spaces, semicolons, or tabs.
That age is a common U.S. transition point between WHO and CDC growth-chart framing, and this report also starts BMI percentile alerting only at age 24 months or older.
Metrics and visit tables can be copied as CSV, downloaded as CSV, or exported as DOCX. Guidance can be copied or downloaded as CSV. The chart can be downloaded as PNG, WebP, JPEG, or CSV, and the whole report can be copied or downloaded as JSON.
Routine calculations happen in the browser. Data leaves the page when you choose to copy, download, or share the results.
No. It summarizes growth-pattern signals and workflow cues. Formal diagnosis depends on validated charting, clinical context, examination, and follow-up judgment.