Methods and processes for development of a CONSORT extension for reporting pilot randomized controlled trials
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
Feasibility and pilot studies are essential components of planning or preparing for a larger randomized controlled trial (RCT). They are intended to provide useful information about the feasibility of the main RCT—with the goal of reducing uncertainty and thereby increasing the chance of successfully conducting the main RCT. However, research has shown that there are serious inadequacies in the reporting of pilot and feasibility studies. Reasons for this include a lack of explicit publication policies for pilot and feasibility studies in many journals, unclear definitions of what constitutes a pilot or feasibility RCT/study, and a lack of clarity in the objectives and methodological focus. All these suggest that there is an urgent need for new guidelines for reporting pilot and feasibility studies. The aim of this paper is to describe the methods and processes in our development of an extension to the Consolidated Standards of Reporting Trials (CONSORT) Statement for reporting pilot and feasibility RCTs, that are executed in preparation for a future, more definitive RCT. There were five overlapping parts to the project: (i) the project launch—which involved establishing a working group and conducting a review of the literature; (ii) stakeholder engagement—which entailed consultation with the CONSORT group, journal editors and publishers, the clinical trials community, and funders; (iii) a Delphi process—used to assess the agreement of experts on initial definitions and to generate a reporting checklist for pilot RCTs, based on the 2010 CONSORT statement extension applicable to reporting pilot studies; (iv) a consensus meeting—to discuss, add, remove, or modify checklist items, with input from experts in the field; and (v) write-up and implementation—which included a guideline document which gives an explanation and elaboration (E&E) and which will provide advice for each item, together with examples of good reporting practice. This final part also included a plan for dissemination and publication of the guideline. We anticipate that implementation of our guideline will improve the reporting completeness, transparency, and quality of pilot RCTs, and hence benefit several constituencies, including authors of journal manuscripts, funding agencies, educators, researchers, and end-users.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,604 | 0,901 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,019 | 0,001 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle