Pediatric EHR growth chart workflows should be compared on four named decision points: which reference charts the system can display, how measurements are captured and used for percentile calculation, how the resulting plots appear during a visit, and how the product handles population-specific charts such as Down syndrome or preterm standards. The AAP clinical report and ONC developer resource both treat growth charting as a required pediatric function, but they do not name a single correct product. A documented implementation at Vanderbilt University Medical Center offers a useful historical benchmark for how workflow integration was actually measured [1][3][6]. Vendors vary in how much detail they publish, limiting the comparison.

The Four Decision Points

A practical comparison begins with chart selection. The Indian Health Service Well Child Module user manual describes WHO and CDC charts displayed on appropriate charts, with a legend present on all charts, not just charts with multiple values [2]. The ONC resource explicitly recommends biometric-specific norms, age- and sex-specific weight, height, length, head circumference, and BMI measurements, plus condition-specific charts such as those for Down syndrome [3]. A product that offers only one chart set or one graphical resolution may be less usable when site policies shift between WHO standards for younger children and CDC references for older ones.

Precision is the second decision point. AAP notes that body weight to the nearest gram is commonly accepted in neonatal facilities, while a tenth of a kilogram may be appropriate for older children [1]. The AAP report also warns that if growth curves are available in only one graphical resolution, frequently obtained measurements may become impossible to analyze visually [1]. An evaluator should ask whether the system stores the units and precision needed at each age band, rather than assuming chart display alone proves pediatric readiness.

What Certification and Standards Do and Do Not Establish

Drummond Group operates voluntary pediatric certification that tests base workflows with realistic patient data on a pass/fail basis under the ONC 2015 Edition program [8]. The AAP page identifies Drummond as the only organization testing and certifying health IT for pediatric functionality aligned with federal recommendations [8]. Certification tracks include well child visits and sick child visits for ambulatory settings, but the public page does not publish growth chart scoring details or list which vendors achieved certification [8].

The HL7 EHR-System Functional Model Pediatric Profile, Release 1, replaces earlier pediatric-specific requirements and includes conformance criteria for growth charting [3]. The ONC resource presents it as operating like a checklist for EHR development [3]. This is useful for verifying that a vendor has addressed recognized pediatric functions, but conformance language should not be treated as proof that a specific configured site workflow will be efficient or error-free.

A Suggested Evaluation Script

As a suggested demonstration, build three test patients: an infant under 24 months requiring WHO charts, a school-age child requiring CDC charts with BMI, and a 13-year-old with a BMI above the 120% of the 95th percentile threshold. Enter measurements at the site's stated precision, then ask the vendor to show the default visit view and the mouse-over values. Verify that off-chart points are visibly indicated, as the IHS manual describes [2], and that the extended BMI chart can be selected without leaving the encounter. Then print or export each chart, since printed and faxed growth charts are among the Vanderbilt desiderata [6]. Record whether percentile values match CDC SAS program output for the same inputs [7]. This script tests the named decision points without requiring a formal procurement pilot. For Down syndrome clinics, separate verification of condition-specific chart availability should be added because ONC and AAP each mention those populations [1][3].

A Documented Academic Implementation as Benchmark

The Vanderbilt University Medical Center experience, published in JAMIA, integrated growth charts into an EHR in a multispecialty pediatric clinic [6]. The authors defined growth chart usage as a mouse-click on a link that caused the system to display a chart, independent of whether the user entered measurements [6]. During July 2001 through June 2004, the site recorded 755,802 outpatient visits for patients aged 0–21 years [6]. The study found that adoption occurred when charts were integrated into routine workflow, but the publication does not compare alternative vendors.

The same report lists desiderata for EHR-based growth charts, including calculation of percentiles based on population norms, capture of different measurement units, support for automated data capture from digital scales, standardized charts as a default view, and printing or faxing [6]. These items remain useful as a critique list because they distinguish chart rendering from measurement workflow. An evaluator can ask vendors to show each item live with test patient data rather than accept a feature checklist.

The Oracle Health EHR Example and Its Limits

Oracle Health EHR documentation states that growth charts allow clinicians to view a pediatric patient's growth in comparison with the average for their age range [5]. The same page says the functionality is available to a limited number of customers and may be generally available later, and that it is not intended to provide treatment or diagnostic recommendations [5]. Oracle does not publish the chart reference sets, percentile calculation method, or visit-level navigation details in this source.

This contrasts with the IHS manual, which describes mouse-over dialogs displaying age at measurement, measurement type, value, and calculated percentage, and off-chart indicators for values outside vital highs and lows [2]. The difference is documentation depth, not proven product capability. When a vendor publishes limited material, the appropriate comparison action is to request the missing decision-point details rather than infer that the product lacks them.

Where the Comparison Becomes Site-Specific

Site context changes the weight of each decision point. A neonatal unit will prioritize gram-level weight entry and frequent measurement plotting [1]. A nutrition clinic may want accurate and precise weight, length, height, and head circumference data available to caregivers through a patient portal [1]. A primary care practice may emphasize percentile calculations and value-entry error detection during routine visits [1]. These settings can lead different evaluators to different products without any universal ranking being justified.

CDC materials add a data-management dimension that vendor demos seldom cover. The CDC provides coefficients and SAS programs for EHR integration of percentiles and z scores [7]. The extended BMI-for-age charts are designed for children above the 95th percentile because those patients can be harder to track on standard charts [7]. An evaluation should confirm whether a product supports extended charts and whether percentile calculations match the CDC program output for test cases.