BEUDAMED
    FDA Adverse Event Other Summary report: N

    FIRST DATABANK

    MDR report key: 4895191 · Received July 1, 2015

    Report

    Report Number
    MW5043595
    Event Type
    Other
    Date Received
    July 1, 2015
    Report Date
    May 4, 2015
    Product Code
    OUG
    Report Source
    Voluntary report
    Reporter Occupation
    OTHER

    Narratives

    Description of Event or Problem · 1

    HELLO THERE, I JUST GOT OFF THE PHONE WITH FIRST DATABANK (FDB) AND WAS A LITTLE CONCERNED WITH THEIR RESPONSE. LONG STORY SHORT, I INQUIRED IF THEY HAD UPDATED/REVIEWED THEIR DRUG FILE AS (B)(6) RELEASED AN UPDATED VERSION OF THE CONFUSED DRUG NAME LIST EARLIER THIS YEAR. AFTER A FEW E-MAILS GOING AROUND, I RECEIVED A CALL FROM A REPRESENTATIVE TODAY NOTING THAT THEY'D JUST RELEASED AN UPDATED FILE (SINCE A NEW MONTH BEGAN) BUT WHETHER THE UPDATED (B)(6) LIST WAS IN THAT FILE IS QUESTIONABLE. THE REPRESENTATIVE SAID TO WAIT 48 HOURS FOR THE CLINICAL TEAM TO REVIEW THE INFORMATION AND THEN THEY'LL LET ME KNOW. I'LL GET A DATA SET CONTAINING THE FDA/(B)(6) TALL MAN LETTERING LIST, THE (B)(6) CONFUSED DRUG NAME LIST, AND FDB'S "TALL MAN PLUS" LIST. THE CONCERN I HAVE IS WHETHER ANY OF THE OTHER DRUG KNOWLEDGE DATABASES HAVE UPDATED THEIR DRUG FILES AS WELL. I'VE HAD BAD EXPERIENCES WITH (B)(6) AND I'M NOT SURE IF (B)(6) USES THE TWO LISTS BUT I FIGURED I'D LET THE GROUP KNOW THAT THE UPDATED CONFUSED DRUG NAME LIST MAY NOT HAVE BEEN UPDATED IN (B)(6) SYSTEMS. MEDICATION ADMINISTERED TO OR USED BY THE PATIENT: NO. (B)(6).

    Devices

    Seq Brand Generic Product Code Manufacturer Model Lot UDI-DI
    429562 FIRST DATABANK NONE OUG

    Patients

    Seq Age Sex Outcome Treatment
    1