<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>Core Outcome Set–STAndards for Reporting: The COS-STAR Statement</title>
        <author>Jamie J. Kirkham</author>
        <author>Sarah Gorst</author>
        <author>Douglas G. Altman</author>
        <author>Jane M. Blazeby</author>
        <author>Mike Clarke</author>
        <author>Declan Devane</author>
        <author>Elizabeth Gargon</author>
        <author>David Moher</author>
        <author>Jochen Schmitt</author>
        <author>Peter Tugwell</author>
        <author>Sean Tunis</author>
        <author>Paula R. Williamson</author>
      </titleStmt>
      <publicationStmt>
        <p>Tag layer of the DHSS Meta-Tagging Project. The article text is reproduced from the
           staged copy named in sourceDesc and is not altered; the tags are held separately in
           standOff so that overlapping and nested spans are preserved.</p>
      </publicationStmt>
      <sourceDesc>
        <bibl>
          <title>Core Outcome Set–STAndards for Reporting: The COS-STAR Statement</title>
          <date>2016</date>
          <publisher>PLOS Medicine</publisher>
          <idno type="DOI">10.1371/journal.pmed.1002148</idno>
          
          <idno type="record">kirkham2016-core-outcome-set-standards-for-reporting-the</idno>
          <note type="staged-file">kirkham2016-core-outcome-set-standards-for-reporting-the.txt, the project's staged copy</note>
          <note type="text-sha1">4dcefcb3b9f7b9e0b6e11ee679db5d98ab4ec3b5</note>
          <note type="rights">open-access</note>
        </bibl>
      </sourceDesc>
    </fileDesc>
    <profileDesc>
      <textClass><keywords><term>social-sciences</term></keywords></textClass>
      <particDesc>
        <person xml:id="paper"><p>the paper's own words</p></person>
        <person xml:id="tagger"><p>the tag layer; a sentence written by the tagger about the
          paper, always anchored to a quotation but not itself a quotation</p></person>
      </particDesc>
    </profileDesc>
    <revisionDesc>
      <change when="2026-10-06"
              who="build_paper_edition.py">53 spans located by searching the stored text for the quote's exact words, allowing any whitespace between them</change>
    </revisionDesc>
  </teiHeader>
  <standOff>
    <spanGrp type="tags">
      <span xml:id="t0" from="#a27" to="#a28" type="research_question" ana="#research_question" resp="#paper">which reporting items are essential for studies developing core outcome sets</span>
      <span xml:id="t1" from="#a9" to="#a10" type="contribution" ana="#contribution" resp="#paper">the 18-item COS-STAR reporting checklist</span>
      <span xml:id="t2" from="#a9" to="#a10" type="claim_type" ana="#claim_type" resp="#paper">method</span>
      <span xml:id="t3" from="#a27" to="#a28" type="phenomenon" ana="#phenomenon" resp="#paper">transparent and complete reporting of core outcome set development studies</span>
      <span xml:id="t4" from="#a7" to="#a8" type="method" ana="#method" resp="#paper">expert-consensus<term>expert-consensus</term></span>
      <span xml:id="t5" from="#a19" to="#a20" type="mechanisms" ana="#mechanisms[0]" resp="#tagger" cert="0.95">mechanisms<term>The use of COS can help improve the consistency in outcome measurement and reduce outcome reporting bias, which has led to much unnecessary waste in the production and reporting of research [ 2 ].</term></span>
      <span xml:id="t6" from="#a3" to="#a4" type="mechanisms" ana="#mechanisms[1]" resp="#tagger" cert="0.95">mechanisms<term>COS studies will not achieve their goal if reports of COS are not complete and transparent.</term></span>
      <span xml:id="t7" from="#a23" to="#a24" type="mechanisms" ana="#mechanisms[2]" resp="#tagger" cert="0.95">mechanisms<term>Recent work shows that reporting quality is currently variable [ 4 ], restricting the ability of potential users of COS, for example clinical trialists, systematic reviewers, and guideline developers, to assess the relevance to their own work.</term></span>
      <span xml:id="t8" from="#a21" to="#a22" type="mechanisms" ana="#mechanisms[3]" resp="#tagger" cert="0.95">mechanisms<term>The credibility of the group that has developed the COS, in relation to their experience of outcome assessment and how they have engaged with key stakeholders during the development process, may influence subsequent uptake of the COS.</term></span>
      <span xml:id="t9" from="#a67" to="#a68" type="mechanisms" ana="#mechanisms[4]" resp="#tagger" cert="0.95">mechanisms<term>The intention of the COS-STAR checklist is to promote the transparency and completeness of reporting of COS studies such that COS users can judge whether the recommended set is relevant to their work.</term></span>
      <span xml:id="t10" from="#a57" to="#a58" type="mechanisms" ana="#mechanisms[5]" resp="#tagger" cert="0.95">mechanisms<term>Feedback from this exercise informed the final version of the COS-STAR checklist.</term></span>
      <span xml:id="t11" from="#a11" to="#a12" type="limitations" ana="#limitations[0]" resp="#tagger" cert="0.95">A limitation of the COS-STAR Statement is that it was developed without representative views of low- and middle-income countries.</span>
      <span xml:id="t12" from="#a49" to="#a50" type="limitations" ana="#limitations[1]" resp="#tagger" cert="0.95">Although the response rate to the survey was low, over 86% (183/214) of round one participants completed round two, with no evidence of attrition bias between rounds ( S1 Consensus Meeting Presentation ).</span>
      <span xml:id="t13" from="#a75" to="#a76" type="limitations" ana="#limitations[2]" resp="#tagger" cert="0.95">The consensus meeting participants acknowledged that there is limited empirical evidence and methodological development relating to some of the reporting items that were considered for inclusion and chose to exclude those items until these issues are better understood.</span>
      <span xml:id="t14" from="#a79" to="#a80" type="limitations" ana="#limitations[3]" resp="#tagger" cert="0.95">Patient representatives, rather than patients, were invited to participate.</span>
      <span xml:id="t15" from="#a77" to="#a78" type="limitations" ana="#limitations[4]" resp="#tagger" cert="0.95">The geographical spread of participants in the Delphi survey, and consequently the consensus meeting, is representative of COS study developers, being predominantly North American and European [ 4 ].</span>
      <span xml:id="t16" from="#a73" to="#a74" type="limitations" ana="#limitations[5]" resp="#tagger" cert="0.95">As with similar reporting guidelines [ 17 ] that have undergone several revisions, COS-STAR is an evolving guideline and may well require modification in the future.</span>
      <span xml:id="t17" from="#a39" to="#a40" type="controls" ana="#controls[0]" resp="#tagger" cert="0.95">In round two, each participant who participated in round one was shown the number of respondents and distribution of scores for each item for all stakeholder groups separately, together with their own score from round one.<note>eliminates: consensus driven by hidden group-level feedback</note></span>
      <span xml:id="t18" from="#a43" to="#a44" type="controls" ana="#controls[1]" resp="#tagger" cert="0.95">Consensus, defined a priori [ 8 ], was achieved if at least 70% of the voting participants from each stakeholder group scored between 7 and 9.<note>eliminates: overall agreement that masks disagreement in one stakeholder group</note></span>
      <span xml:id="t19" from="#a49" to="#a50" type="controls" ana="#controls[2]" resp="#tagger" cert="0.95">Although the response rate to the survey was low, over 86% (183/214) of round one participants completed round two, with no evidence of attrition bias between rounds ( S1 Consensus Meeting Presentation ).<note>eliminates: systematic dropout between Delphi rounds</note></span>
      <span xml:id="t20" from="#a55" to="#a56" type="controls" ana="#controls[3]" resp="#tagger" cert="0.95">Testers were independent of the COS-STAR development process.<note>eliminates: testing only by guideline developers</note></span>
      <span xml:id="t21" from="#a53" to="#a54" type="controls" ana="#controls[4]" resp="#tagger" cert="0.95">The process of obtaining feedback and refining the checklist was repeated until no further changes were needed.<note>eliminates: a single unrevised draft checklist</note></span>
      <span xml:id="t22" from="#a25" to="#a26" type="concepts" ana="#concepts[0]" resp="#paper" cert="0.95">core outcome set<term>core outcome set</term></span>
      <span xml:id="t23" from="#a17" to="#a18" type="concepts" ana="#concepts[1]" resp="#paper" cert="0.95">COS users<term>COS users</term></span>
      <span xml:id="t24" from="#a5" to="#a6" type="concepts" ana="#concepts[2]" resp="#paper" cert="0.95">COS-STAR<term>COS-STAR</term></span>
      <span xml:id="t25" from="#a15" to="#a16" type="concepts" ana="#concepts[3]" resp="#paper" cert="0.95">outcome reporting bias<term>outcome reporting bias</term></span>
      <span xml:id="t26" from="#a37" to="#a38" type="concepts" ana="#concepts[4]" resp="#paper" cert="0.95">Delphi survey<term>Delphi survey</term></span>
      <span xml:id="t27" from="#a43" to="#a44" type="concepts" ana="#concepts[5]" resp="#paper" cert="0.95">consensus definition<term>consensus definition</term></span>
      <span xml:id="t28" from="#a33" to="#a34" type="concepts" ana="#concepts[6]" resp="#paper" cert="0.95">Explanation and Elaboration document<term>Explanation and Elaboration document</term></span>
      <span xml:id="t29" from="#a5" to="#a8" type="unhoused_relations" ana="#unhoused_relations[0]" resp="#tagger" cert="0.98">Delphi survey → COS-STAR</span>
      <span xml:id="t30" from="#a33" to="#a34" type="unhoused_relations" ana="#unhoused_relations[1]" resp="#tagger" cert="0.98">Explanation and Elaboration document → COS-STAR</span>
      <span xml:id="t31" from="#a19" to="#a20" type="unhoused_relations" ana="#unhoused_relations[2]" resp="#tagger" cert="0.98">core outcome set → outcome reporting bias</span>
      <span xml:id="t32" from="#a67" to="#a68" type="unhoused_relations" ana="#unhoused_relations[3]" resp="#tagger" cert="0.98">COS-STAR → COS users</span>
      <span xml:id="t33" from="#a69" to="#a70" type="senses" ana="#senses[0]" resp="#tagger" cert="1.0">COS-STAR is a minimum reporting guideline, not a quality-ranking tool or a prescribed consensus method</span>
      <span xml:id="t34" from="#a35" to="#a36" type="claim_relations" ana="#claim_relations[0]" resp="#tagger" cert="0.98">extends → the previous systematic review of COS studies involving a Delphi survey [5]</span>
      <span xml:id="t35" from="#a39" to="#a44" type="concept_edges" ana="#concept_edges[0]" resp="#tagger" cert="0.98">consensus definition —part-of→ Delphi survey<note>strength of the relation: 1 · note: The a-priori threshold is categorically the decision rule used within the two-round Delphi survey.
Audit 2026-09-28: DOUBTFUL - read against its full span and kept, but the span writes &#x27;Consensus, defined a priori&#x27; and &#x27;the Delphi exercise&#x27;, not &#x27;consensus definition&#x27; / &#x27;Delphi survey&#x27;.</note><term>consensus definition</term><term>Delphi survey</term></span>
      <span xml:id="t36" from="#a9" to="#a10" type="content_tags" ana="#content_tags.findings[0]" resp="#tagger" cert="0.95">The COS-STAR Statement consists of a checklist of 18 items considered essential for transparent and complete reporting in all COS studies.</span>
      <span xml:id="t37" from="#a51" to="#a52" type="content_tags" ana="#content_tags.findings[1]" resp="#tagger" cert="0.95">It was confirmed that the required items would be relevant to the reporting of a COS regardless of whether it had been developed for effectiveness trials, systematic reviews, or routine care.</span>
      <span xml:id="t38" from="#a61" to="#a62" type="content_tags" ana="#content_tags.findings[2]" resp="#tagger" cert="0.95">The checklist aims to cover the minimum reporting requirements related to the background, scope, methods, results, conclusion, and limitations of such studies.</span>
      <span xml:id="t39" from="#a63" to="#a64" type="content_tags" ana="#content_tags.findings[3]" resp="#tagger" cert="0.95">The checklist is designed to be applicable regardless of consensus methodology used to develop the COS (inclusive of mixed methods) and the various participant groups who may have been involved in selecting outcomes (inclusive of patient representatives), as identified in a previous systematic review [ 4 ].</span>
      <span xml:id="t40" from="#a65" to="#a66" type="content_tags" ana="#content_tags.findings[4]" resp="#tagger" cert="0.95">The COS-STAR checklist provides guidance for minimal COS study reporting, but, in certain circumstances, additional reporting items may be warranted at the discretion of the study authors.</span>
      <span xml:id="t41" from="#a13" to="#a14" type="content_tags" ana="#content_tags.findings[5]" resp="#tagger" cert="0.95">Conclusions With many ongoing COS studies underway, the COS-STAR Statement should be a helpful resource to improve the reporting of COS studies for the benefit of all COS users.</span>
      <span xml:id="t42" from="#a71" to="#a72" type="content_tags" ana="#content_tags.findings[6]" resp="#tagger" cert="0.95">The COS-STAR Statement would not distinguish which of these COS should be used, although it may be useful for critical appraisal of published COS.</span>
      <span xml:id="t43" from="#a25" to="#a26" type="content_tags" ana="#content_tags.definitions[0]" resp="#tagger" cert="0.95">core outcome set<term>core outcome set</term></span>
      <span xml:id="t44" from="#a29" to="#a30" type="content_tags" ana="#content_tags.definitions[1]" resp="#tagger" cert="0.95">COS<term>COS</term></span>
      <span xml:id="t45" from="#a1" to="#a2" type="content_tags" ana="#content_tags.quantities[0]" resp="#tagger" cert="0.95">Over 200 COS to date have been developed, but the clarity of these reports is suboptimal.</span>
      <span xml:id="t46" from="#a31" to="#a32" type="content_tags" ana="#content_tags.quantities[1]" resp="#tagger" cert="0.95">A previous review found that only 38% of published studies contained recommendations about how to measure the outcomes in the COS [ 4 ].</span>
      <span xml:id="t47" from="#a35" to="#a36" type="content_tags" ana="#content_tags.quantities[2]" resp="#tagger" cert="0.95">A preliminary list of 48 reporting items was developed from a previous systematic review of COS studies involving a Delphi survey [ 5 ], the personal experiences of COS development, and reporting by the project management group (The COS-STAR Group).</span>
      <span xml:id="t48" from="#a41" to="#a42" type="content_tags" ana="#content_tags.quantities[3]" resp="#tagger" cert="0.95">An additional nine reporting items were suggested in round one of the Delphi exercise and were scored in round two.</span>
      <span xml:id="t49" from="#a45" to="#a46" type="content_tags" ana="#content_tags.quantities[4]" resp="#tagger" cert="0.95">COS developers ( n = 25), COS users ( n = 107), medical journal editors ( n = 40), and patient representatives ( n = 11) participated in both rounds, with 13 individuals also having been involved in clinical guideline development.</span>
      <span xml:id="t50" from="#a49" to="#a50" type="content_tags" ana="#content_tags.quantities[5]" resp="#tagger" cert="0.95">Although the response rate to the survey was low, over 86% (183/214) of round one participants completed round two, with no evidence of attrition bias between rounds ( S1 Consensus Meeting Presentation ).</span>
      <span xml:id="t51" from="#a47" to="#a48" type="content_tags" ana="#content_tags.quantities[6]" resp="#tagger" cert="0.95">The consensus meeting was a one-day event held in London, United Kingdom, in January 2016, with 17 international participants, including COS developers ( n = 6), medical journal editors ( n = 4), COS users ( n = 5) [trialists ( n = 1), Cochrane systematic review co-editors ( n = 2), and clinical guideline developers ( n = 2)], and patient representatives ( n = 2).</span>
      <span xml:id="t52" from="#a59" to="#a60" type="content_tags" ana="#content_tags.quantities[7]" resp="#tagger" cert="0.95">The COS-STAR Statement The 18-item COS-STAR checklist presented in Table 1 applies to COS development studies for which the aim is to decide which outcomes should be included in the COS and does not extend to cover the reporting of work to determine how those outcomes should be defined or measured.</span>
    </spanGrp>
  </standOff>
  <text>
    <body>
        <p><anchor xml:id="a0"/> Abstract. Background Core outcome sets (COS) can enhance the relevance of research by ensuring that outcomes of importance to health service users and other people making choices about health care in a particular topic area are measured routinely. <anchor xml:id="a1"/>Over 200 COS to date have been developed, but the clarity of these reports is suboptimal.<anchor xml:id="a2"/> <anchor xml:id="a3"/>COS studies will not achieve their goal if reports of COS are not complete and transparent.<anchor xml:id="a4"/> <anchor xml:id="a5"/>Methods and Findings In recognition of these issues, an international group that included experienced COS developers, methodologists, journal editors, potential users of COS (clinical trialists, systematic reviewers, and clinical guideline developers), and patient representatives developed the Core Outcome Set–STAndards for Reporting (COS-STAR) Statement as a reporting guideline for COS studies.<anchor xml:id="a6"/> <anchor xml:id="a7"/>The developmental process consisted of an initial reporting item generation stage and a two-round Delphi survey involving nearly 200 participants representing key stakeholder groups, followed by a consensus meeting.<anchor xml:id="a8"/> <anchor xml:id="a9"/>The COS-STAR Statement consists of a checklist of 18 items considered essential for transparent and complete reporting in all COS studies.<anchor xml:id="a10"/> The checklist items focus on the introduction, methods, results, and discussion section of a manuscript describing the development of a particular COS. <anchor xml:id="a11"/>A limitation of the COS-STAR Statement is that it was developed without representative views of low- and middle-income countries.<anchor xml:id="a12"/> COS have equal relevance to studies conducted in these areas, and, subsequently, this guideline may need to evolve over time to encompass any additional challenges from developing COS in these areas. Conclusions <anchor xml:id="a13"/>With many ongoing COS studies underway, the COS-STAR Statement should be a helpful resource to improve the reporting of COS studies for the benefit of all COS users.<anchor xml:id="a14"/> Paula Williamson and colleagues present reporting standards for studies that report core outcome sets for health research. Introduction There is growing recognition that insufficient attention has been paid to the outcomes measured in clinical trials, which need to be relevant to health service users and other people making choices about health care if the findings of research are to influence practice and future research. <anchor xml:id="a15"/>In addition, outcome reporting bias, whereby results are selected for inclusion in a trial report on the basis of those results, has been identified as a problem for the interpretation of published data.<anchor xml:id="a16"/> The development and implementation of core outcome sets (COS) is drawing increasing attention across all areas of research in health [ 1 ] and has relevance for research practice on a global scale. <anchor xml:id="a17"/>A recent survey reveals that some trialists, systematic reviewers, and guideline developers (COS users) do now refer to COS studies as a starting point for outcome selection in their work [ 1 ].<anchor xml:id="a18"/> <anchor xml:id="a19"/>The use of COS can help improve the consistency in outcome measurement and reduce outcome reporting bias, which has led to much unnecessary waste in the production and reporting of research [ 2 ].<anchor xml:id="a20"/> A recently updated systematic review identified over 200 published COS studies [ 1 ], and many more are known to be under development [ 3 ]. The first step in COS development is typically “what to measure,” whereas the “how” and “when” usually come later. The value of a COS depends largely on why and how it was developed. <anchor xml:id="a21"/>The credibility of the group that has developed the COS, in relation to their experience of outcome assessment and how they have engaged with key stakeholders during the development process, may influence subsequent uptake of the COS.<anchor xml:id="a22"/> Furthermore, the reporting quality of COS development studies is also relevant to implementation. <anchor xml:id="a23"/>Recent work shows that reporting quality is currently variable [ 4 ], restricting the ability of potential users of COS, for example clinical trialists, systematic reviewers, and guideline developers, to assess the relevance to their own work.<anchor xml:id="a24"/> <anchor xml:id="a25"/>A COS has previously been defined as an agreed standardised set of outcomes that should be measured and reported, as a minimum, in all clinical trials in specific areas of health or health care [ 2 ].<anchor xml:id="a26"/> COS are being developed for settings other than clinical trials. Although previous recommendations have been made regarding the reporting of a Delphi survey component of a COS study [ 5 ], it is timely to gain wider consensus given the increasing activity in this area, particularly because various other methods and components are incorporated in the COS development process [ 1 ]. <anchor xml:id="a27"/>In this article, we present the results of a research project, in which the objective was to develop a guideline (Core Outcome Set–STAndards for Reporting [COS-STAR]) for the reporting of studies developing COS using an approach proposed by the Enhancing the QUAlity and Transparency Of health Research (EQUATOR) Network [ 6 ].<anchor xml:id="a28"/> The reporting checklist is relevant regardless of the consensus methodology used in the development of the COS and can be applied to COS developed for effectiveness trials, systematic reviews, or routine care [ 7 ]. <anchor xml:id="a29"/>Terminology A COS describes what should be measured in a particular research or practice setting, with subsequent work needed to determine how each outcome should be defined or measured.<anchor xml:id="a30"/> <anchor xml:id="a31"/>A previous review found that only 38% of published studies contained recommendations about how to measure the outcomes in the COS [ 4 ].<anchor xml:id="a32"/> This reporting guideline was developed to address this first stage of development, namely, what should be measured. Ethical Approval The University of Liverpool Ethics Committee was consulted and granted ethical approval for this study (Reference RETH000841). Informed consent was assumed if a participant responded to the Delphi survey or agreed to attend the consensus meeting. <anchor xml:id="a33"/>Development of the COS-STAR Statement A full protocol outlining the Delphi procedures for the COS-STAR study was published elsewhere [ 8 ], including the intention to produce an associated Explanation and Elaboration (E+E) document in which the meaning and rationale for each checklist item is given.<anchor xml:id="a34"/> <anchor xml:id="a35"/>A preliminary list of 48 reporting items was developed from a previous systematic review of COS studies involving a Delphi survey [ 5 ], the personal experiences of COS development, and reporting by the project management group (The COS-STAR Group).<anchor xml:id="a36"/> <anchor xml:id="a37"/>This preliminary list of potential reporting items was included in an international two-round Delphi survey in order to ascertain the importance of these reporting items.<anchor xml:id="a38"/> The Delphi survey involved four key stakeholder groups, chosen to encompass aspects of COS development, reporting, and uptake. Invitations by email were sent to the following: (i) lead authors of 196 published COS studies in the Core Outcome Measures in Effectiveness Trials (COMET) database, with a request to also forward on the invitation to any methodologist involved; (ii) editors of 250 journals in which COS studies have been published and 70 journals involved with CoRe Outcomes in WomeN’s health ([CROWN], http://www.crown-initiative.org/ ), an initiative endorsing the uptake of COS; (iii) potential users of COS who were (a) principal investigators of open phase III/IV trials, commercial or non-commercial, registered on clinicaltrials.gov (20% random sample from 8,449 registered trials) or (b) 76 Coordinating Editors from 53 Cochrane Review Groups; and (iv) 33 patient representatives from previous COMET workshops and the COMET Public and Patient Participation, Involvement and Engagement (PoPPIE) Working Group. It did not prove possible to invite clinical guideline developers listed on the Guidelines International Network website ( http://www.gin2015.net/about/ ) due to this being a member organisation, so a question about involvement in clinical guideline development was added to the survey instead. The aim was to recruit as many individuals from each stakeholder group as possible for the Delphi exercise. Participants were sent a personalised email outlining the project as described in the study protocol together with a copy of the first systematic review of COS studies [ 4 ]. Delphi participants rated the importance of each reporting item on a scale from 1 (not important) to 9 (critically important) as defined in the protocol [ 8 ]. In round one of the Delphi study, participants could suggest new reporting items to be included in the second round. <anchor xml:id="a39"/>In round two, each participant who participated in round one was shown the number of respondents and distribution of scores for each item for all stakeholder groups separately, together with their own score from round one.<anchor xml:id="a40"/> <anchor xml:id="a41"/>An additional nine reporting items were suggested in round one of the Delphi exercise and were scored in round two.<anchor xml:id="a42"/> <anchor xml:id="a43"/>Consensus, defined a priori [ 8 ], was achieved if at least 70% of the voting participants from each stakeholder group scored between 7 and 9.<anchor xml:id="a44"/> <anchor xml:id="a45"/>COS developers ( n = 25), COS users ( n = 107), medical journal editors ( n = 40), and patient representatives ( n = 11) participated in both rounds, with 13 individuals also having been involved in clinical guideline development.<anchor xml:id="a46"/> The variable number of respondents per stakeholder group did not affect the results, because feedback in round two was presented by group. The Delphi process was conducted and managed using DelphiManager software developed by the COMET Initiative ( http://www.comet-initiative.org/delphimanager/ ). The anonymised data from both rounds of the Delphi process, itemised by stakeholder group, are available in S1 Delphi Data . <anchor xml:id="a47"/>The consensus meeting was a one-day event held in London, United Kingdom, in January 2016, with 17 international participants, including COS developers ( n = 6), medical journal editors ( n = 4), COS users ( n = 5) [trialists ( n = 1), Cochrane systematic review co-editors ( n = 2), and clinical guideline developers ( n = 2)], and patient representatives ( n = 2).<anchor xml:id="a48"/> Individuals were selected to be invited to the meeting using the following broad principles: (i) Delphi participants who completed both rounds; (ii) a balance across the four stakeholder groups; (iii) a balance amongst COS developers of those using Delphi surveys and those using other methods; (iv) a balance across COS users of trialists, systematic reviewers, and guideline developers; and (v) a reasonable geographic spread. Initial invitations were determined by the authors based on their knowledge of individuals’ expertise. If an individual could not attend, they were replaced by someone else from the same stakeholder group wherever possible. The roles of each participant were not mutually exclusive, and there was a mix of clinical and methodological experience. The objective of the meeting was to discuss and vote on the series of 57 reporting items thought to be potentially important for inclusion in the COS-STAR checklist. Three additional participants (one facilitator and two note takers) attended the meeting but did not participate in the discussion or voting. The Delphi results for all 57 reporting items were presented to the consensus meeting participants prior to and during the meeting ( S1 Consensus Matrix Delphi ). A copy of the consensus meeting slides showing the response rates, geographical distribution, and Delphi round two results for each stakeholder group can be found in S1 Consensus Meeting Presentation . <anchor xml:id="a49"/>Although the response rate to the survey was low, over 86% (183/214) of round one participants completed round two, with no evidence of attrition bias between rounds ( S1 Consensus Meeting Presentation ).<anchor xml:id="a50"/> Members of the COS-STAR group (study authors) who could not attend the meeting were contacted in advance to discuss the results; their comments were documented and fed into the meeting discussion. Following presentation of the Delphi result for each potential reporting item, the item was discussed and then voted on by the meeting participants, and retained if more than 70% of the voting participants (at least 12 of the 17 voting participants) scored between 7 and 9. Voting was undertaken using OMBEA response ( http://www.ombea.com/ ). During discussion of the second Consensus Process item, “Description of what information was presented to participants about the consensus process at its start,” one participant commented on the absence of an item related to ethical approval. The group agreed to vote on this, and consensus was achieved that this item should be included in the reporting guideline ( S1 Consensus Meeting Critical Scores ). This issue has become more relevant as the inclusion of patients as participants in COS development has increased. Discussion of the format of the reporting checklist was given consideration by the management group. <anchor xml:id="a51"/>It was confirmed that the required items would be relevant to the reporting of a COS regardless of whether it had been developed for effectiveness trials, systematic reviews, or routine care.<anchor xml:id="a52"/> A word of warning was given by those participants at the meeting with previous experience of reporting guideline development: avoid making the first guideline too stringent and risk developers not using it. The need to merge some reporting items and create some sub-items was noted, together with suggestions for an explanatory document to enhance the usefulness of the final COS-STAR checklist. Specifically, the following amendments were made by the COS-STAR group after the meeting: (1) Participants (methods): The four items under this topic were considered to overlap. The suggestion was made, and accepted by the group, that one item covering the sub-items of who, how, and why would be more meaningful. (2) Consensus process: There was general agreement that although all five items under this topic could provide useful information, some were too specific to be included, acknowledging that there is no gold standard approach. The suggestion was made, and accepted by the group, that one item covering the description of the consensus process would more likely be followed. (3) Outcome scoring: a suggestion was made to include both aspects in a single item. (4) Participants (results): a suggestion was made to combine these issues into a single item. (5) Outcome results: there was general agreement that these multiple items were too detailed and should be merged together, elaborating on the issues in the E+E document ( S1 Explanation and Elaboration ). (6) Limitations: it was agreed that it was good practice to include an item related to limitations and include the examples provided in the E+E document. Following the meeting, a draft of the COS-STAR checklist was circulated to the COS-STAR group and the remainder of the consensus meeting attendees. All comments and revisions were taken into consideration and the checklist revised accordingly. <anchor xml:id="a53"/>The process of obtaining feedback and refining the checklist was repeated until no further changes were needed.<anchor xml:id="a54"/> The comprehension of the final checklist items was reviewed by two expert guideline developers (DGA, DM). Testing was undertaken by two COS developers who were writing up their COS studies. Two researchers currently developing COS also reviewed the statement. <anchor xml:id="a55"/>Testers were independent of the COS-STAR development process.<anchor xml:id="a56"/> <anchor xml:id="a57"/>Feedback from this exercise informed the final version of the COS-STAR checklist.<anchor xml:id="a58"/> <anchor xml:id="a59"/>The COS-STAR Statement The 18-item COS-STAR checklist presented in Table 1 applies to COS development studies for which the aim is to decide which outcomes should be included in the COS and does not extend to cover the reporting of work to determine how those outcomes should be defined or measured.<anchor xml:id="a60"/> <anchor xml:id="a61"/>The checklist aims to cover the minimum reporting requirements related to the background, scope, methods, results, conclusion, and limitations of such studies.<anchor xml:id="a62"/> In the accompanying E+E document ( S1 Explanation and Elaboration ), explanations are provided for the meaning and rationale for each checklist item. <anchor xml:id="a63"/>The checklist is designed to be applicable regardless of consensus methodology used to develop the COS (inclusive of mixed methods) and the various participant groups who may have been involved in selecting outcomes (inclusive of patient representatives), as identified in a previous systematic review [ 4 ].<anchor xml:id="a64"/> <anchor xml:id="a65"/>The COS-STAR checklist provides guidance for minimal COS study reporting, but, in certain circumstances, additional reporting items may be warranted at the discretion of the study authors.<anchor xml:id="a66"/> For example, study authors may wish to describe the steps in deciding how to measure the core outcomes if this was considered [ 9 ]. 10.1371/journal.pmed.1002148.t001 Table 1 Core Outcome Set-STandards for Reporting: The COS-STAR Statement. SECTION/TOPIC ITEM No. CHECKLIST ITEM TITLE/ABSTRACT Title 1a Identify in the title that the paper reports the development of a COS Abstract 1b Provide a structured summary INTRODUCTION Background and Objectives 2a Describe the background and explain the rationale for developing the COS. 2b Describe the specific objectives with reference to developing a COS. Scope 3a Describe the health condition(s) and population(s) covered by the COS. 3b Describe the intervention(s) covered by the COS. 3c Describe the setting(s) in which the COS is to be applied. METHODS Protocol/Registry Entry 4 Indicate where the COS development protocol can be accessed, if available, and/or the study registration details. Participants 5 Describe the rationale for stakeholder groups involved in the COS development process, eligibility criteria for participants from each group, and a description of how the individuals involved were identified. Information Sources 6a Describe the information sources used to identify an initial list of outcomes. 6b Describe how outcomes were dropped/combined, with reasons (if applicable). Consensus Process 7 Describe how the consensus process was undertaken. Outcome Scoring 8 Describe how outcomes were scored and how scores were summarised. Consensus Definition 9a Describe the consensus definition. 9b Describe the procedure for determining how outcomes were included or excluded from consideration during the consensus process. Ethics and Consent 10 Provide a statement regarding the ethics and consent issues for the study. RESULTS Protocol Deviations 11 Describe any changes from the protocol (if applicable), with reasons, and describe what impact these changes have on the results. Participants 12 Present data on the number and relevant characteristics of the people involved at all stages of COS development. Outcomes 13a List all outcomes considered at the start of the consensus process. 13b Describe any new outcomes introduced and any outcomes dropped, with reasons, during the consensus process. COS 14 List the outcomes in the final COS. DISCUSSION Limitations 15 Discuss any limitations in the COS development process. Conclusions 16 Provide an interpretation of the final COS in the context of other evidence, and implications for future research. OTHER INFORMATION Funding 17 Describe sources of funding/role of funders. Conflicts of Interest 18 Describe any conflicts of interest within the study team and how these were managed. Discussion The COS-STAR checklist was developed using an approach that has been recommended for developing medical reporting guidelines [ 6 ]. <anchor xml:id="a67"/>The intention of the COS-STAR checklist is to promote the transparency and completeness of reporting of COS studies such that COS users can judge whether the recommended set is relevant to their work.<anchor xml:id="a68"/> For example, although the adequacy of the description of the scope of a COS is increasing [ 1 ], further improvement is needed in order for uptake to be maximised and, in turn, assessed. The COS-STAR E+E document ( S1 Explanation and Elaboration ) was developed to provide an explanation of each of the COS-STAR checklist items and to provide a framework for good reporting practices, with examples, for those interested in conducting and reporting COS development work. It follows a similar format to that used in other explanatory documents [ 10 , 11 ]. The E+E document also describes the endorsement and implementation strategies planned for the COS-STAR Statement. COS-STAR is not a quality assessment tool and should not be used in this way, for example, to compare the validity of similar related COS. <anchor xml:id="a69"/>Similarly, the checklist does not make recommendations about which methodology should be used or which stakeholder groups to include to reach consensus in COS development projects; guidance on such issues can be found elsewhere [ 2 , 12 ].<anchor xml:id="a70"/> As an example, several studies have looked at developing COS in childhood asthma, each using different methodology and proposing slight variations in the core outcomes [ 13 – 16 ]. <anchor xml:id="a71"/>The COS-STAR Statement would not distinguish which of these COS should be used, although it may be useful for critical appraisal of published COS.<anchor xml:id="a72"/> <anchor xml:id="a73"/>As with similar reporting guidelines [ 17 ] that have undergone several revisions, COS-STAR is an evolving guideline and may well require modification in the future.<anchor xml:id="a74"/> <anchor xml:id="a75"/>The consensus meeting participants acknowledged that there is limited empirical evidence and methodological development relating to some of the reporting items that were considered for inclusion and chose to exclude those items until these issues are better understood.<anchor xml:id="a76"/> As an example, there is some evidence that the method of feedback does influence how people score outcomes [ 18 ], which perhaps suggests that this is important information to report. However, until there is better guidance on how COS developers should present feedback, the item was excluded from the current reporting checklist. The guideline may also require modification as new stakeholder groups with relevant interests and experience emerge. For example, regulators have recently recommended the use of COS in trials of medicinal products in patients with asthma [ 19 ] and will be encouraged to provide feedback on the statement. <anchor xml:id="a77"/>The geographical spread of participants in the Delphi survey, and consequently the consensus meeting, is representative of COS study developers, being predominantly North American and European [ 4 ].<anchor xml:id="a78"/> This is recognised as a limitation, however, of both COS study development and this reporting guideline, given the equal relevance to low- and middle-income countries. <anchor xml:id="a79"/>Patient representatives, rather than patients, were invited to participate.<anchor xml:id="a80"/> Due to this being a relatively complex area of methodology, individuals known to have had some level of involvement with COS development were selected, thereby increasing their understanding. As patient involvement and participation in COS development increases, their contribution to a future revision of this reporting guideline will be sought. An important objective of the COMET Initiative is to promote wider involvement. Although the acceptance rate to the Delphi invitation may appear low, participation in round two was above 85% in each stakeholder group, with no evidence of attrition bias ( S1 Consensus Meeting Presentation ). Readers are invited to submit comments, criticisms, experiences, and recommendations via the COMET website ( http://www.comet-initiative.org/contactus ), which will be considered for future refinement of the COS-STAR Statement. Supporting Information S1 Consensus Matrix Delphi Consensus matrix for round one and round two of the COS-STAR Delphi survey. (DOCX) Click here for additional data file. S1 Consensus Meeting Critical Scores Percentages of participants scoring each item as critical for inclusion (7–9) at the COS-STAR meeting. (DOCX) Click here for additional data file. S1 Consensus Meeting Presentation Consensus meeting slides presented at the COS-STAR consensus meeting. (PPT) Click here for additional data file. S1 Delphi Data Delphi Data for round one and round two of the COS-STAR Delphi survey. (XLSX) Click here for additional data file. S1 Explanation and Elaboration Explanation and Elaboration document for COS-STAR. (DOCX) Click here for additional data file.<anchor xml:id="a81"/></p>
    </body>
  </text>
</TEI>
