The Cost of HIT-Safe Anticoagulant Use at a Tertiary Care, Adult, Academic Hospital.
Notice bibliographique
Résumé
Abstract Objective: Heparin-induced thrombocytopenia (HIT) is a potential adverse outcome of heparin therapy. At Sunnybrook Health Sciences Centre (SHSC), a patient suspected of HIT has heparin discontinued, a HIT enzyme-linked immunosorbent assay (ELISA) ordered, and is then treated with a HIT-safe anticoagulant. Few studies have assessed the cost of treating suspected (negative and confirmed) HIT. The objective of our study was to quantify the direct costs associated with treating HIT from a Canadian hospital perspective. Methods: A cost analysis was conducted at SHSC, a 701-bed academic hospital with cardiac surgery. Suspected HIT included all patients who had a HIT ELISA ordered. A confirmed HIT case had one of the following: positive serotonin release assay (SRA), positive HIT ELISA (optical density: 0.4 to 1.0) plus high clinical probability for HIT, or strongly positive HIT ELISA (optical density > 1.0). A negative HIT case had a negative HIT ELISA or SRA. Costs associated with using HIT-safe anticoagulants included: drug acquisition, preparation time, monitoring tests, and the management of bleeding (e.g., blood transfusions). The average treatment cost (2007 Canadian dollars) per case of confirmed HIT, confirmed HIT with thrombosis (HITT), and negative HIT was calculated. Cost data was obtained from the hospital human resources, pharmacy database, and laboratory. Results: There were 108 suspected HIT cases in 2005. Thirty-one of the suspected HIT cases were treated: 12 out of 88 negative HIT cases, 7 out of 8 confirmed HIT cases, and all 12 confirmed HITT cases (Table). Six cases were treated with more than one HIT-safe anticoagulant (one negative HIT case and five confirmed HITT cases). Lepirudin accounted for 64% of the total HIT-safe medication costs in 2005. Overall, the direct thrombin inhibitors (DTIs) accounted for 96% of the treatment costs. Seventeen patients were treated with fondaparinux, eight of whom were negative HIT cases. Cases with confirmed HITT had greater treatment costs per patient than those with confirmed HIT. The average treatment cost of a negative HIT case was $64 ($0–$3,987). Conclusions: The treatment costs presented appear to be lower than costs presented in other studies. This may, in part, be the result of a hospital HIT management policy and a comprehensive TE Service that manages all cases of HIT. The total costs and the cost per patient were greatest for the DTIs. Table: HIT-safe anticoagulant use. Negative HIT Confirmed HIT Confirmed HITT Total cost of use NA - not applicable, SD - standard deviation, 1One patient received both lepirudin and fondaparinux, 2 One patient died before receiving any treatment, 3 Five patients received more than one HIT-safe anticoagulant Average argatroban cost ± SD (range) $3,987 n = 1 $0 n = 0 $4,023 ± $4,211 ($693 – $8,757) n = 3 $16,056 Average bivalirudin cost ± SD (range) $0 n = 0 $9,302 n = 1 $0 n = 0 $9,302 Average lepirudin cost ± SD (range) $221 n = 1 $3,562 ± $23 ($3,545 – $3,578) n = 2 $4,793 ± $4,842 ($1,099 – $16,744) n = 9 $50,482 Average danaparoid cost ± SD (range) $228 ± $135 ($90 – $359) n = 3 $0 n = 0 $54 n = 1 $738 Average fondaparinux cost ± SD (range) $91 ± $58 ($28 – $196) n = 8 $81 ± $67 ($42 – $182) n = 4 $263 ± $100 ($140 – $365) n = 5 $2,367 Total number treated 131 72 183 NA Average HIT-safe anticoagulant cost ± SD (range) $64 ± $428 ($0 – $3,987) Median = $0 n = 88 $2,094 ± $3,314 ($0 – $9,302) Median = $119 n = 8 $4,715 ± $4,776 ($252 – $16,744) Median = $3,156 n = 12 $78,945
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.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,000 | 0,004 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,001 |
| Bibliométrie | 0,001 | 0,002 |
| Études des sciences et des technologies | 0,001 | 0,000 |
| Communication savante | 0,001 | 0,000 |
| Science ouverte | 0,001 | 0,001 |
| Intégrité de la recherche | 0,000 | 0,001 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,004 | 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écouleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».