Replication Data for "Hypophosphatemia as a biomarker of metabolic intolerance to enhanced nutrition in the PICU: a secondary analysis of the PEPaNIC RCT"

Open data API in a single place

Provided by Catholic University of Leuven

Get early access to Replication Data for "Hypophosphatemia as a biomarker of metabolic intolerance to enhanced nutrition in the PICU: a secondary analysis of the PEPaNIC RCT" API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.02.26 08:31
Created
2026.02.26
Available languages
English
Keywords
Parenteral nutrition, Children, Hypophosphatemia, Critical illness, Infection, Mechanical ventilation, Mortality, Clinical outcome, PICU
Quality scoring

Dataset description

Data integrated in the manuscript: Hypophosphatemia as a biomarker of metabolic intolerance to enhanced nutrition in the PICU: a secondary analysis of the PEPaNIC RCT. Background: The PEPaNIC RCT showed that early supplementation of insufficient enteral nutrition by parenteral nutrition (early-PN) worsened outcome of critically ill children as compared with withholding PN for 1 week (late-PN). The best timing to initiate nutritional support in the pediatric intensive care unit (PICU) remains unclear. In adults, declining phosphate levels may identify patients who are particularly harmed by early-PN. We therefore assessed whether early hypophosphatemia in critically ill children may indicate metabolic intolerance to nutrition. Methods: In this secondary analysis of the PEPaNIC RCT (n=1440), we investigated whether development of hypophosphatemia statistically interacts with the randomized intervention for its impact on clinical outcome, adjusting for baseline risk factors. Outcomes of interest included the incidence of new infections and the duration of PICU dependency as primary endpoints, 90-day mortality as safety endpoint, and duration of mechanical ventilation and of hospital stay as secondary endpoints. Subsequently, the impact of early-PN vs late-PN in patients with and without early hypophosphatemia was assessed. Analyses were performed for phosphate abnormalities on PICU day 1 and 2, with and without imputing 20.3% (day 1) or 22.0% (day 2) missing phosphate data. Results: Of patients with available phosphate measurements, 19.9% (211/1060) and 27.5% (243/883) developed hypophosphatemia on day 1 and day 2, respectively. Day 1 hypophosphatemia did not interact with the randomized intervention for any studied outcome. On day 2, hypophosphatemia interacted with randomization for risk of new infection (P=0.031), likelihood of earlier live PICU discharge (P=0.030), and time to live weaning from mechanical ventilation (P=0.025). Harm by early-PN was more pronounced in patients with hypophosphatemia than in those without. Results after imputing missing phosphate data were similar, with an additional interaction for 90-day mortality (P=0.038) revealing higher mortality with early-PN in patients with hypophosphatemia. Conclusions: Development of hypophosphatemia may identify critically ill children who are particularly harmed by early-PN. This opens perspectives for its use as a biomarker of metabolic intolerance to enhanced nutrition, which requires further investigation.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks