ArticleThe journal of extra-corporeal technology2011
Perfusion Downunder Collaboration Database--data quality assurance: towards a high quality clinical database.
Article in The journal of extra-corporeal technology, 2011. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 4 papers.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
4 citing papers in PubMed.
- Timing errors and temporal uncertainty in clinical databases-A narrative review.Frontiers in digital health · 2022Review
- An Evaluation Trial of The National Perfusion Registry.The journal of extra-corporeal technology · 2014Article
- Validation of a perfusion registry: methodological approach and initial findings.The journal of extra-corporeal technology · 2012Article
- Developing a benchmarking process in perfusion: a report of the Perfusion Downunder Collaboration.The journal of extra-corporeal technology · 2012Article
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
1 author.
Funding
No grant is acknowledged in the PubMed record.
Abstract
Maintaining a high quality clinical database is critical to obtain reliable information upon which to base clinical and institutional decisions, and to preserve the public and the user's confidence in the quality of the data. The success of the Perfusion Downunder Collaboration (PDUC) Database, a dataset for cardiopulmonary bypass procedures, can only be guaranteed through the assurance of the quality of its data. This paper presents the evaluation of the data quality in the PDUC Database. Three participating centers located in Adelaide, Australia were audited: Flinders Private Hospital (FPH), Flinders Medical Center (FMC), and Ashford Hospital (AH). Ten perCent of the cases submitted from the first year of data harvest were audited (2008: FPH and FMC, 2009: AH). A total of 57 variables were reviewed and rates of discrepancies (inaccurate, missing, not entered, cannot be validated) categorized as 0-25%, 25-50%, 51-75%, and 75-100% of cases (% = cases with discrepancy/total cases audited) evaluated. Sixty randomly selected cases were audited, comprising of 13 cases from FPH, 31 cases from FMC, and 16 cases from AH. Of a total of 3420 data points evaluated, 6.9% were found to be inaccurate and 3.2% were missing. For each participating center, the great majority of variables have discrepancies in few (0-25%) of the cases audited. The discrepancies found can be attributed to systematic errors (e.g., error in date difference calculation for length of stays, data transformation error for postoperative dialysis) and random errors (e.g., use of incorrect unit for creatinine, transcription error for discharge date). The PDUC Database is currently reasonably accurate and complete. This evaluation is part of a complex system of data quality assurance, and when conducted routinely, could provide a continuous feedback loop towards a high quality PDUC Database.
Indexed as
Identifiers
21449240PMC4680097What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.