Pub Date : 2020-07-29DOI: 10.21203/rs.3.rs-48402/v1
R. Cote, S. Perle, D. Martin
Introduction Previous analysis of registered clinical trials has found a number of protocols result in changes in the registered primary outcome measures. This investigation determined if reported primary outcomes in chiropractic-related clinical trials registered in clinicaltrials.gov match their published results. Additionally, we assessed secondary outcomes, publication status and whether raw data were posted to the registry. Methods Clinicaltrials.gov was searched for chiropractic-related trials and having a completed status. If the study was published, outcome measures were compared between the clinicaltrials.gov entry and the published paper to assess for consistency. Results Within clinicaltrials.gov 171 chiropracticrelated protocols were identified with 102 of those published (59.6% publication rate). Ninety-two of the published papers (90.2%) had agreement between their primary outcome and the entry on clinicaltrials.gov and 82 (80.4%) agreed with the secondary outcomes. Conclusion A modest rate of agreement between clinicaltrials.gov entries and the published papers was found. While chiropractic-related clinical trials are fewer compared to medical trials, chiropractic-related research has a substantially better rate of primary and secondary outcome concordance with registered protocols.
{"title":"Agreement of primary outcomes in chiropractic-related clinical trials registered in clinicaltrials.gov with corresponding publication.","authors":"R. Cote, S. Perle, D. Martin","doi":"10.21203/rs.3.rs-48402/v1","DOIUrl":"https://doi.org/10.21203/rs.3.rs-48402/v1","url":null,"abstract":"Introduction\u0000Previous analysis of registered clinical trials has found a number of protocols result in changes in the registered primary outcome measures. This investigation determined if reported primary outcomes in chiropractic-related clinical trials registered in clinicaltrials.gov match their published results. Additionally, we assessed secondary outcomes, publication status and whether raw data were posted to the registry.\u0000\u0000\u0000Methods\u0000Clinicaltrials.gov was searched for chiropractic-related trials and having a completed status. If the study was published, outcome measures were compared between the clinicaltrials.gov entry and the published paper to assess for consistency.\u0000\u0000\u0000Results\u0000Within clinicaltrials.gov 171 chiropracticrelated protocols were identified with 102 of those published (59.6% publication rate). Ninety-two of the published papers (90.2%) had agreement between their primary outcome and the entry on clinicaltrials.gov and 82 (80.4%) agreed with the secondary outcomes.\u0000\u0000\u0000Conclusion\u0000A modest rate of agreement between clinicaltrials.gov entries and the published papers was found. While chiropractic-related clinical trials are fewer compared to medical trials, chiropractic-related research has a substantially better rate of primary and secondary outcome concordance with registered protocols.","PeriodicalId":343541,"journal":{"name":"The Journal of the Canadian Chiropractic Association","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2020-07-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114779415","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2010-03-01DOI: 10.1016/0009-8981(91)90165-9
A. Bussières
{"title":"CCA Young Investigator Award.","authors":"A. Bussières","doi":"10.1016/0009-8981(91)90165-9","DOIUrl":"https://doi.org/10.1016/0009-8981(91)90165-9","url":null,"abstract":"","PeriodicalId":343541,"journal":{"name":"The Journal of the Canadian Chiropractic Association","volume":"70 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2010-03-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115340655","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Discusses the value of profiles and how they differ from standards. Profiles address the problem of computer standards not being precisely designed to meet end-user needs. A standard's scope is generally much narrower than an entire computer system. To support user needs, a particular computer system may have to comply with many individual standards. Several factors may limit the scope of each standard. Moreover, no formal standards body requires that standards completely address end-user needs. Finally, a standard's scope is often reduced because an area originally covered by the standard does not have sufficient consensus to be retained in that standard. A consensus-based standard can be produced only in those areas that have sufficient consensus. Profiles are specifications that formally capture an organization's information technology needs. They are becoming a way to map the middle ground between overall user needs and the standards related to those needs. Profiles can be used to inventory an existing computing strategy, support a computing procurement or drive the evolution of an organization's computing strategy. Actually, organizations have been developing profiles for many years. However, they've gone by such names as procurement specifications, bid documents, strategic plans or recommended practices. At a minimum, a profile identifies user requirements and the standards or specifications that meet those requirements. A profile may also include more details on an organization's computing strategy. >
{"title":"What is a Profile?","authors":"C. Severance","doi":"10.1109/2.410156","DOIUrl":"https://doi.org/10.1109/2.410156","url":null,"abstract":"Discusses the value of profiles and how they differ from standards. Profiles address the problem of computer standards not being precisely designed to meet end-user needs. A standard's scope is generally much narrower than an entire computer system. To support user needs, a particular computer system may have to comply with many individual standards. Several factors may limit the scope of each standard. Moreover, no formal standards body requires that standards completely address end-user needs. Finally, a standard's scope is often reduced because an area originally covered by the standard does not have sufficient consensus to be retained in that standard. A consensus-based standard can be produced only in those areas that have sufficient consensus. Profiles are specifications that formally capture an organization's information technology needs. They are becoming a way to map the middle ground between overall user needs and the standards related to those needs. Profiles can be used to inventory an existing computing strategy, support a computing procurement or drive the evolution of an organization's computing strategy. Actually, organizations have been developing profiles for many years. However, they've gone by such names as procurement specifications, bid documents, strategic plans or recommended practices. At a minimum, a profile identifies user requirements and the standards or specifications that meet those requirements. A profile may also include more details on an organization's computing strategy. >","PeriodicalId":343541,"journal":{"name":"The Journal of the Canadian Chiropractic Association","volume":"136 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128568601","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}