A PHP Error was encountered

Severity: Warning

Message: file_get_contents(https://...@pubfacts.com&api_key=b8daa3ad693db53b1410957c26c9a51b4908&a=1): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests

Filename: helpers/my_audit_helper.php

Line Number: 176

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 176
Function: file_get_contents

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 250
Function: simplexml_load_file_from_url

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3122
Function: getPubMedXML

File: /var/www/html/application/controllers/Detail.php
Line: 575
Function: pubMedSearch_Global

File: /var/www/html/application/controllers/Detail.php
Line: 489
Function: pubMedGetRelatedKeyword

File: /var/www/html/index.php
Line: 316
Function: require_once

Identification of potential drug name confusion errors in the Sentinel System. | LitMetric

Purpose: In July 2015, the US Food and Drug Administration (FDA) published a drug safety communication regarding errors in prescribing and dispensing of the antidepressant Brintellix (vortioxetine) and the antiplatelet Brilinta (ticagrelor) that arose due to proprietary drug name confusion. Brintellix is indicated for major depressive disorder; Brilinta is indicated to reduce cardiovascular death, myocardial infarction, and stroke in patients with acute coronary syndrome or history of myocardial infarction. Brintellix was renamed to Trintellix in May 2016. Using Brilinta and Brintellix as a proof-of-concept feasibility use case, we assessed whether drug name confusion errors between the pair could be identified in electronic health care data via the combination of a claims-based algorithm and limited manual claims data review.

Methods: Using data from the Sentinel System, we defined potential errors as Brintellix users without an on- or off-label indication for Brintellix, without a dispensing for a drug with the same indications as Brintellix, and with an on- or off-label indication for Brilinta between -365 and +30 days after index Brintellix dispensing; the reverse was done for Brilinta. We manually reviewed claims profiles of potential cases.

Results: We identified 27 (0.1%) potential errors among 21 208 Brintellix users; 16 appeared to be likely errors based on claims profile review. Fifty-one (0.3%) of the 16 779 Brilinta users were identified as potential errors, and four appeared to be likely errors.

Conclusions: A claims-based algorithm combined with manual review of claims profiles could identify potential drug name confusion errors, and narrow down likely errors that warrant further investigation.

Download full-text PDF

Source
http://dx.doi.org/10.1002/pds.4891DOI Listing

Publication Analysis

Top Keywords

drug confusion
16
confusion errors
12
potential errors
12
errors
9
brintellix
9
potential drug
8
sentinel system
8
myocardial infarction
8
claims-based algorithm
8
brintellix users
8

Similar Publications

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!