Dataset Information

A Core Outcome Set for Pediatric Critical Care.

ABSTRACT:

Objectives

More children are surviving critical illness but are at risk of residual or new health conditions. An evidence-informed and stakeholder-recommended core outcome set is lacking for pediatric critical care outcomes. Our objective was to create a multinational, multistakeholder-recommended pediatric critical care core outcome set for inclusion in clinical and research programs.

Design

A two-round modified Delphi electronic survey was conducted with 333 invited research, clinical, and family/advocate stakeholders. Stakeholders completing the first round were invited to participate in the second. Outcomes scoring greater than 69% "critical" and less than 15% "not important" advanced to round 2 with write-in outcomes considered. The Steering Committee held a virtual consensus conference to determine the final components.

Setting

Multinational survey.

Patients

Stakeholder participants from six continents representing clinicians, researchers, and family/advocates.

Measurements and main results

Overall response rates were 75% and 82% for each round. Participants voted on seven Global Domains and 45 Specific Outcomes in round 1, and six Global Domains and 30 Specific Outcomes in round 2. Using overall (three stakeholder groups combined) results, consensus was defined as outcomes scoring greater than 90% "critical" and less than 15% "not important" and were included in the final PICU core outcome set: four Global Domains (Cognitive, Emotional, Physical, and Overall Health) and four Specific Outcomes (Child Health-Related Quality of Life, Pain, Survival, and Communication). Families (n = 21) suggested additional critically important outcomes that did not meet consensus, which were included in the PICU core outcome set-extended.

Conclusions

The PICU core outcome set and PICU core outcome set-extended are multistakeholder-recommended resources for clinical and research programs that seek to improve outcomes for children with critical illness and their families.

SUBMITTER: Fink EL

PROVIDER: S-EPMC7785252 | biostudies-literature |

REPOSITORIES: biostudies-literature

ACCESS DATA

Similar Datasets

Project description:The use of core outcome sets (COS) ensures that researchers measure and report those outcomes that are most likely to be relevant to users of their research. Several hundred COS projects have been systematically identified to date, but there has been no formal quality assessment of these studies. The Core Outcome Set-STAndards for Development (COS-STAD) project aimed to identify minimum standards for the design of a COS study agreed upon by an international group, while other specific guidance exists for the final reporting of COS development studies (Core Outcome Set-STAndards for Reporting [COS-STAR]).An international group of experienced COS developers, methodologists, journal editors, potential users of COS (clinical trialists, systematic reviewers, and clinical guideline developers), and patient representatives produced the COS-STAD recommendations to help improve the quality of COS development and support the assessment of whether a COS had been developed using a reasonable approach. An open survey of experts generated an initial list of items, which was refined by a 2-round Delphi survey involving nearly 250 participants representing key stakeholder groups. Participants assigned importance ratings for each item using a 1-9 scale. Consensus that an item should be included in the set of minimum standards was defined as at least 70% of the voting participants from each stakeholder group providing a score between 7 and 9. The Delphi survey was followed by a consensus discussion with the study management group representing multiple stakeholder groups. COS-STAD contains 11 minimum standards that are the minimum design recommendations for all COS development projects. The recommendations focus on 3 key domains: the scope, the stakeholders, and the consensus process.The COS-STAD project has established 11 minimum standards to be followed by COS developers when planning their projects and by users when deciding whether a COS has been developed using reasonable methods.