Severity: Warning
Message: Undefined array key "choices"
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 249
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: 8192
Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated
Filename: models/Detail_model.php
Line Number: 71
Backtrace:
File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos
File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: 8192
Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated
Filename: helpers/my_audit_helper.php
Line Number: 8919
Backtrace:
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace
File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "choices"
Filename: controllers/Detail.php
Line Number: 256
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 256
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 256
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 257
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 257
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 258
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 258
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 259
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 259
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Undefined array key "usage"
Filename: controllers/Detail.php
Line Number: 260
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 260
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Trying to access array offset on value of type null
Filename: controllers/Detail.php
Line Number: 260
Backtrace:
File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: file_get_contents(https://...@gmail.com&api_key=61f08fa0b96a73de8c900d749fcb997acc09): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests
Filename: helpers/my_audit_helper.php
Line Number: 143
Backtrace:
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 143
Function: file_get_contents
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 209
Function: simplexml_load_file_from_url
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3098
Function: getPubMedXML
File: /var/www/html/application/controllers/Detail.php
Line: 574
Function: pubMedSearch_Global
File: /var/www/html/application/controllers/Detail.php
Line: 488
Function: pubMedGetRelatedKeyword
File: /var/www/html/index.php
Line: 316
Function: require_once
Severity: Warning
Message: Attempt to read property "Count" on bool
Filename: helpers/my_audit_helper.php
Line Number: 3100
Backtrace:
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3100
Function: _error_handler
File: /var/www/html/application/controllers/Detail.php
Line: 574
Function: pubMedSearch_Global
File: /var/www/html/application/controllers/Detail.php
Line: 488
Function: pubMedGetRelatedKeyword
File: /var/www/html/index.php
Line: 316
Function: require_once
Background: Fracture-related infection (FRI) is a challenging complication in musculoskeletal trauma surgery and often complicates the management of open fractures. The CDC currently advocates a surveillance period of 90 days after fracture fixation, but it is unclear what duration of follow-up constitutes adequate surveillance for FRI. Inadequate follow-up will underestimate infections and, in clinical research, will make any interventions studied appear better than they really are, thereby resulting in misleading conclusions.
Questions/purposes: (1) What is the timing of FRI onset in patients with open fractures? (2) What is the proportion of FRIs captured when follow-up is limited to 90 days postoperatively versus when follow-up is extended to 1 year?
Methods: This is a secondary analysis of patient data from a previous retrospective cohort study that investigated whether the duration of perioperative antibiotic prophylaxis was independently associated with FRI in patients with open fractures. Of the 530 eligible patients in the source study, 3% (14) died. Of the remaining 516 patients, 97% (502) patients with 559 long-bone open fractures had 2 years of follow-up constituted the base cohort. Forty-seven fractures in 46 patients were complicated by FRI and were the focus of this secondary analysis. Medical records were reviewed in detail specifically for the current study. Seventy-eight percent (36 of 46) of patients were male, and the mean ± SD age was 42 ± 16 years. The most common mechanism of injury was a motor vehicle accident (63% [29 of 46] of patients), and the tibia was the most involved site (53% [25 of 47] of fractures). The median (interquartile range) time to debridement was 3.0 hours (IQR 2.0 to 4.0). FRIs developed in 3% (7 of 247) of Type I open fractures, 7% (11 of 164) of Type II, 17% (18 of 107) of Type IIIA, 29% (9 of 31) of Type IIIB, and 20% (2 of 10) of Type IIIC open fractures. Each clinic visit of each patient was reviewed, and data about the time of onset of any symptoms and signs suggesting or confirming an FRI, as reported by patients and/or determined by treating surgeons, were recorded. The proportions of FRIs with onset by specific time periods were determined. A Kaplan-Meier survival analysis was performed, and the FRI event rates with 95% confidence intervals were calculated.
Results: The median (IQR) time to the onset of FRI was 52 days (IQR 15 to 153). Follow-up of 90 days captured only 64% (30 of 47) of FRIs, whereas follow-up of 1 year captured 89% (42 of 47) of FRIs. The proportion of FRIs with onset within 1 year increased to 95% (42 of 44) in the presence of an already healed fracture.
Conclusion: Follow-up of 90 days after the management of an open long-bone fracture is inadequate for postoperative surveillance, especially for research purposes. Clinical research on interventions would report results appearing to be much better than they really are, potentially resulting in misleading conclusions. Follow-up of 1 year is preferable because most FRIs will develop before that time, especially when fracture union has occurred. A small percentage of patients may still develop infections beyond the first year after the management of an open fracture. The risk of missing these infections by not extending follow-up beyond 1 year must be balanced against the additional logistical burden. Future prospective multicenter studies and registries with long-term patient follow-up would help clarify this issue.Level of Evidence Level III, diagnostic study.
Download full-text PDF |
Source |
---|---|
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC8673965 | PMC |
http://dx.doi.org/10.1097/CORR.0000000000001911 | DOI Listing |
Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!