Implementation of prehospital point-of-care ultrasound using a novel continuous feedback approach in a UK helicopter emergency medical service
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
BACKGROUND: There has been increased use of prehospital point-of-care ultrasound (PoCUS) by helicopter emergency medical services (HEMS) in recent years. Lack of governance structure and evidence of benefit have been described as major barriers to its implementation. This paper describes a novel approach to implementation of prehospital PoCUS and clinical governance framework in a UK HEMS. METHODS: A retrospective database review was undertaken at London's Air Ambulance (LAA) from 1st September 2021 to 31st March 2023. All patients who had PoCUS examination were included. Scans were archived in a cloud-based server and reviewed weekly by expert clinicians. They were graded in adequacy, agreement between reviewer and clinician was recorded and fed back to the clinicians allowing continuous feedback learning. In-hospital diagnosis was sought for patients having the full Pump, Pleura and Pouring blood (PPPB) protocol. Cohen's Kappa (ƙ) was calculated for inter-rater reliability. Sensitivity and specificity analysis was performed using 2 × 2 tables. RESULTS: LAA attended 3,068 missions. Our reviewers identified 701 PoCUS scanning encounters and 628 were included in the final analysis. Clinicians performed 420 scans for pneumothorax, 308 for free fluid and 305 pericardial effusions respectively. Majority of the population were male (85%) who sustained traumatic (93.5%) thoracic injuries (65%). Paramedics performed 29% of the scans. Reviewers deemed 83% of the scans of adequate quality. Inter-rater reliability between clinicians and reviewers was 0.6 for pericardial effusion, 0.67 for pneumothorax and 0.71 for free fluid respectively. A full PPPB protocol was performed in 52 patients out of which 46 were included. The sensitivity and specificity of PPPB protocol for diagnosis life-threatening injuries was 0.5 and 0.9 respectively. CONCLUSION: Introduction of prehospital PoCUS in a HEM service utilizing high quality training, user-friendly workflow and image archiving system, robust governance framework and continuous feedback may be feasible allowing high quality ultrasound examinations. The bespoke PPPB protocol in prehospital may improve diagnosis of life-threatening injuries.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,001 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,001 | 0,000 |
| Bibliométrie | 0,001 | 0,001 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,001 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle