Editorial, Evidence, and Release Review

No named clinician has completed a site-wide clinical review.Internal review is performed under the responsibility of Child Growth Lab's individual developer. AI assistance is not clinical review.

The individual developer is responsible for source selection, implementation review, public wording, test acceptance, release decisions, and corrections. The site has no external medical board, formal independent medical peer-review process, regulatory approval or certification, or prospective clinical trial validation. This page does not present the site as doctor reviewed, physician approved, or clinically certified.

See About Child Growth Lab for ownership and purpose, and Methodology for calculator-specific formulas and sources.

Passing software or editorial checks is not clinical validation, certification, or a substitute for an appropriate healthcare professional.

The public date shown on this page is 2026-09-02. It records that a substantive internal review or update was completed for the stated public content and process.

It does not mean a clinician signed off that day, that sources are monitored in real time, that every external source was rechecked that day, that every page received clinical review, or that the content is guaranteed current forever. Formatting-only changes do not create a new review date.

1. 1. Identify the claim or method

   Define what is being asserted or calculated and which user-facing scope it has.

2. 2. Check the best-fit source

   Use the official dataset, government guidance, professional guideline, or primary technical source that fits the claim.

3. 3. Compare source to implementation or wording

   Compare the source-derived algorithm contract or public medical statement with the repository.

4. 4. Test the affected behavior

   Use regression, boundary, browser, accessibility, or content-contract checks as appropriate.

5. 5. Release and verify

   Pass pre-release and release gates, verify the Production result, and update the affected date truthfully when the change is substantive.

Repository release records document 6 public calculators covering the reviewed WHO Baby, CDC height/weight, Kids BMI, Growth Velocity, Corrected Age, and Mid-Parental Height implementation responsibilities. The Baby Growth Percentile Calculator contains the reviewed WHO weight-for-age, length-for-age, weight-for-length, and head-circumference-for-age indicators; these indicators are combined within one calculator workflow rather than separate public products. For each responsibility, the review can cover source and version, intended population, age and unit rules, date handling, formulas, thresholds, interpolation, rounding, boundary cases, displayed outputs, and expressly excluded uses.

Repository records also document the evidence and content re-review of the 6 retained education guides. That is a different review type from calculator algorithm review; neither count means 12 pages received clinician review.

Source choice depends on the claim; one rigid universal ranking is not sufficient.

Provenance checks record the source identity, version, retrieval information, permission where required, checksums where practical, and the scope in which a source may be used. Commercial calculators, blogs, AI answers, and search snippets do not override an original or otherwise authoritative source.

Citing CDC, WHO, AAP, PES, RCPCH, or another organization does not imply its endorsement of this independent site. Sources can change after publication; the maintenance date records completed review work rather than continuous monitoring. A new authoritative source may trigger review when identified. Calculator-specific evidence is listed in Methodology.

The review translates each accepted source into an explicit implementation contract: population, age or date mapping, required inputs, units, formula, source data tables, interpolation, thresholds, boundary equality, supported outputs, excluded uses, error states, rounding, and visible results. Changes are inspected as diffs so the page explanation, tests, and production implementation remain aligned.

Current formula versions are read dynamically from the central site configuration:

• cdc-lms-v2
• who-igrowup-v2
• corrected-age-v3
• tanner-mid-parental-v3
• cdc-kids-bmi-v3
• growth-velocity-v3

These version labels identify internal implementation contracts for reproducibility and change review; they are not certifications, medical approvals, or external version numbers. Detailed formula and data tables belong in Methodology.

Numerical validation uses official examples or vectors when available, independently reproduced expected values where appropriate, separate validation scripts when the repository contract supports them, and boundary, unit, date, browser, and result-state tests. Passing tests confirms reviewed software contracts; it does not prove clinical validity for every child or situation.

Public wording is checked to distinguish reference from diagnosis, screening from diagnosis, percentile from a health score, one point from a trend, arithmetic estimate from prediction, and a technical input guard from a biological cutoff.

Review removes unsupported treatment, referral, feeding, or calorie advice; guarantees; universal normal-or-abnormal claims; and stigmatizing language. Disclaimers and limitations remain visible, and explanations should remain understandable to caregivers and professional users. Wording review cannot replace clinical judgment or make incomplete measurements clinically sufficient.

The guide re-reviews included authoritative-source rechecks where relevant, factual medical boundaries, parent comprehension, unsupported-diagnosis prevention, source/reference preservation, direct calculator handoffs, and browser/accessibility release checks. They are evidence and content work, not doctor review, clinician approval, peer review, or clinical validation.

Code/content gates: unit, regression, content-contract, and independent validator checks. Browser gates: Playwright flows, responsive layouts, keyboard operation, axe checks, and console/page-error diagnostics. Publishing gates: metadata, canonical, sitemap, robots, privacy, and internal-link checks.Deployment gates: pre-release validation, Production deployment, and direct Production acceptance. Release PASS is not medical certification.

Privacy review checks whether child health inputs are incorrectly collected or sent, where measurements are processed, the difference between browser-local calculation and ordinary infrastructure logs, and whether the public statement remains accurate. See Privacy Policy. Passing release gates cannot cover every device, assistive-technology combination, or future browser change.

How AI assistance is used

AI tools may help retrieve and organize research, compare source passages, draft wording or code, propose tests, and inspect diffs. AI is not a medical source, clinician, independent expert review, or final publisher. Its output is checked against primary sources, repository contracts, and executable tests before the individual developer decides whether to keep and publish it.

AI does not publish automatically, accept clinical responsibility, or supply an independent medical opinion. Using multiple tools or automated checks does not mean that multiple clinicians reviewed the work.

Advertising and editorial independence

Advertising may help support the free site, but it does not determine evidence sources, formulas, thresholds, result categories, safety wording, limitations, or whether a correction is made. Advertising must remain distinct from editorial content and must not imply advertiser endorsement. Ownership, funding context, audience, and site purpose are described on the About page.

Reports may concern a source, algorithm, displayed explanation, privacy statement, accessibility barrier, broken link, or other technical behavior. Contact support@childgrowthlab.com or use the Contact page.

1. Compare the report with the original source and current implementation.
2. Determine the affected algorithm, data, page, explanation, privacy statement, or user flow.
3. Add or update a regression check when practical.
4. Make the scoped code, content, provenance, or accessibility correction.
5. Run the full release acceptance process for the proposed correction.
6. Update the affected public review date after substantive re-review.
7. Verify the released fix on the Production domain.

Support is not a medical or emergency service. Do not email medical records, names, dates of birth, or other identifying child information. Not every report requires a change, no fixed response time is promised, and an unresolved report may remain under investigation until reliable evidence is available.