FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2905462783> ?p ?o ?g. }

• W2905462783 endingPage "192" @default.
• W2905462783 startingPage "191" @default.
• W2905462783 abstract "Where Are We Now? The current study by Wong and colleagues [11] has broad implications for health policy as we continue to look for more-effective and efficient models of care. Evaluating how case volume and facility complexity impacts postoperative hip-fracture surgery has drawn considerable attention, with studies finding that increased surgical volume at the surgeon level (as opposed to the facility level) reduces morbidity and mortality following orthopaedic surgery [6, 8-10]. However, studies focusing on the impact of hospital/surgeon volume and facility complexity on hip fractures often disagree with one another, with some indicating that higher volume/higher complexity facilities produce better results, and others finding the opposite [2, 3, 7]. This is important because hip-fracture surgery is among the most-common nonelective orthopaedic operations, with 300,000 performed each year in the United States [1, 4]. In networked care, complex surgery can be echeloned. If increased surgical volume and facility complexity indeed influence the safety of these operations, patients then could be transferred to higher-volume centers. However, if surgical volume is not an important factor, then healthcare systems might reasonably decide not to deploy resources in the transfer of care for what would be a large number of patients. That gap in knowledge left the door open for the current study [11], which reviewed 11 years of data from the Veterans Affairs Surgical Quality Improvement Program (VASQIP) database from VA facilities on the West coast of the United States. The authors found no correlation between surgical volume or facility complexity level and early complications following hip-fracture surgery. This was used to support their conclusion that patients who are treated with hip fracture surgery at high- and low-volume/complexity facilities in the VA should expect similar risk of 30-day adverse outcomes. Adding some external validation to this work, Okike and colleagues [7] came to the same conclusion after reviewing results within the Kaiser-Permanente system from 14,294 patients treated for hip fracture. Where Do We Need To Go? The primary limitation of large-database research is that it lacks the ability to answer why an association (if any) exists. Merely finding an association (or lack thereof, as was the case in the current study) does not, and more importantly should not, define best practice. Good health policy requires more than associations; it depends on thoughtful and convincing explanations. For example, in this study, the incidence of tracked complications was not different between higher- and lower-volume or lower-complexity facilities [11]. This finding alone can be interpreted in multiple ways. It could mean that experience does not matter, and all facilities perform hip fracture surgery with a comparable level of safety, or it could mean that higher-volume or higher-complexity facilities care for patients who have more medical comorbidities and by virtue of the fact that there is no increase in the frequency of complications, these sites actually may be providing considerably better care. One way to adjudicate this would be to review the charts of all cases with complications. However, this is almost never possible with administrative databases, which typically deidentify records. Using retrospectively applied comorbidity scores to overcome this limitation relies on the adequacy of comorbidity recording, which can be unreliable [5]. As such, we are left without an answer to the “why?” Turning to the full medical record and imaging could enable an explanation for this finding. The “why” has and will always be locked in the full dataset. Administrative database studies are complimentary to, but cannot replace, hypothesis-driven research. In addition, many large-database studies are limited in terms of the endpoints they can evaluate; by definition, they can only explore those endpoints that are available, which typically are limited to basic demographics, a limited number of coded diagnoses and procedures (which themselves can be subject to coding error), and adverse outcomes incurred over a prespecified time period [5]. These elements alone can identify research questions, but rarely can they answer them. By contrast, prospective, hypothesis-driven research is limited in its ability to deal with infrequent events, such as rare complications; it would take an extraordinarily large randomized study, for example, to determine whether mixing antibiotics into bone cement during hip hemiarthroplasty surgery causes more help than harm. Our best evidence is likely to come from a combination of large-database, registry, and high-quality prospective research. How Do We Get There? Given the prevalence of hip fracture surgery in the VA and general population, prospective, validation of these findings is needed. For events that occur with sufficient frequency, such as 1-year mortality, researchers should try to use prospective methods and formal hypothesis testing, rather than large-database research. To keep sample size manageable, rare events—those in the range of 1% to 2% in terms of frequency—could be aggregated as “any major adverse event” to help generate greater expected occurrences. A cost of this aggregation is that it may pool complications or mask correlations that exist between a specific treatment approach and complication. For these reasons, while there is a clear hierarchy between prospective hypothesis-driven clinical research and large-database studies, the two can be complimentary. Independently assessing rare events could be too onerous for hypothesis-driven methods. As such, registries or prospectively maintained healthcare data, akin to the VASQIP, may be the only pragmatic option. However, in these circumstances, it is essential to assess the impact of confounders, such as comorbidities, demographics, and facility-specific/surgery-specific factors. Ideally, the database would have a means for identifying patients who sustain a rare occurrence, which would then allow direct full chart and imaging review of these unique patients. This enhanced method overcomes the limitations of studies that rely solely on data prerecorded in the database. Administrative database studies have a place in our evidence base, but their findings must be understood in the context of their limitations." @default.
• W2905462783 created "2018-12-22" @default.
• W2905462783 creator A5067385070 @default.
• W2905462783 date "2018-12-07" @default.
• W2905462783 modified "2023-09-26" @default.
• W2905462783 title "CORR Insights®: Are Case Volume and Facility Complexity Level Associated With Postoperative Complications After Hip Fracture Surgery in the Veterans Affairs Healthcare System?" @default.
• W2905462783 cites W2012596468 @default.
• W2905462783 cites W2013758898 @default.
• W2905462783 cites W2017364283 @default.
• W2905462783 cites W2056057966 @default.
• W2905462783 cites W2109744908 @default.
• W2905462783 cites W2608068999 @default.
• W2905462783 cites W2750674126 @default.
• W2905462783 cites W2760606502 @default.
• W2905462783 cites W2802719114 @default.
• W2905462783 cites W2884577264 @default.
• W2905462783 cites W2889416085 @default.
• W2905462783 doi "https://doi.org/10.1097/corr.0000000000000515" @default.
• W2905462783 hasPubMedCentralId "https://www.ncbi.nlm.nih.gov/pmc/articles/6345299" @default.
• W2905462783 hasPubMedId "https://pubmed.ncbi.nlm.nih.gov/30531424" @default.
• W2905462783 hasPublicationYear "2018" @default.
• W2905462783 type Work @default.
• W2905462783 sameAs 2905462783 @default.
• W2905462783 citedByCount "0" @default.
• W2905462783 crossrefType "journal-article" @default.
• W2905462783 hasAuthorship W2905462783A5067385070 @default.
• W2905462783 hasBestOaLocation W29054627831 @default.
• W2905462783 hasConcept C121332964 @default.
• W2905462783 hasConcept C126322002 @default.
• W2905462783 hasConcept C141071460 @default.
• W2905462783 hasConcept C160735492 @default.
• W2905462783 hasConcept C162324750 @default.
• W2905462783 hasConcept C1862650 @default.
• W2905462783 hasConcept C194828623 @default.
• W2905462783 hasConcept C20556612 @default.
• W2905462783 hasConcept C2775969662 @default.
• W2905462783 hasConcept C2776541429 @default.
• W2905462783 hasConcept C2778885795 @default.
• W2905462783 hasConcept C2781385661 @default.
• W2905462783 hasConcept C2988170871 @default.
• W2905462783 hasConcept C43893838 @default.
• W2905462783 hasConcept C50522688 @default.
• W2905462783 hasConcept C545542383 @default.
• W2905462783 hasConcept C62520636 @default.
• W2905462783 hasConcept C68312169 @default.
• W2905462783 hasConcept C71924100 @default.
• W2905462783 hasConceptScore W2905462783C121332964 @default.
• W2905462783 hasConceptScore W2905462783C126322002 @default.
• W2905462783 hasConceptScore W2905462783C141071460 @default.
• W2905462783 hasConceptScore W2905462783C160735492 @default.
• W2905462783 hasConceptScore W2905462783C162324750 @default.
• W2905462783 hasConceptScore W2905462783C1862650 @default.
• W2905462783 hasConceptScore W2905462783C194828623 @default.
• W2905462783 hasConceptScore W2905462783C20556612 @default.
• W2905462783 hasConceptScore W2905462783C2775969662 @default.
• W2905462783 hasConceptScore W2905462783C2776541429 @default.
• W2905462783 hasConceptScore W2905462783C2778885795 @default.
• W2905462783 hasConceptScore W2905462783C2781385661 @default.
• W2905462783 hasConceptScore W2905462783C2988170871 @default.
• W2905462783 hasConceptScore W2905462783C43893838 @default.
• W2905462783 hasConceptScore W2905462783C50522688 @default.
• W2905462783 hasConceptScore W2905462783C545542383 @default.
• W2905462783 hasConceptScore W2905462783C62520636 @default.
• W2905462783 hasConceptScore W2905462783C68312169 @default.
• W2905462783 hasConceptScore W2905462783C71924100 @default.
• W2905462783 hasIssue "1" @default.
• W2905462783 hasLocation W29054627831 @default.
• W2905462783 hasLocation W29054627832 @default.
• W2905462783 hasLocation W29054627833 @default.
• W2905462783 hasLocation W29054627834 @default.
• W2905462783 hasLocation W29054627835 @default.
• W2905462783 hasOpenAccess W2905462783 @default.
• W2905462783 hasPrimaryLocation W29054627831 @default.
• W2905462783 hasRelatedWork W2088696087 @default.
• W2905462783 hasRelatedWork W2133127616 @default.
• W2905462783 hasRelatedWork W2161830070 @default.
• W2905462783 hasRelatedWork W2324942821 @default.
• W2905462783 hasRelatedWork W2512376941 @default.
• W2905462783 hasRelatedWork W2587127841 @default.
• W2905462783 hasRelatedWork W3018119167 @default.
• W2905462783 hasRelatedWork W3042320319 @default.
• W2905462783 hasRelatedWork W3177070821 @default.
• W2905462783 hasRelatedWork W3206924778 @default.
• W2905462783 hasVolume "477" @default.
• W2905462783 isParatext "false" @default.
• W2905462783 isRetracted "false" @default.
• W2905462783 magId "2905462783" @default.
• W2905462783 workType "article" @default.