Model Number MERGE CARDIO V10.1.1.1 |
Device Problem
Data Problem (3196)
|
Patient Problem
No Known Impact Or Consequence To Patient (2692)
|
Event Date 09/28/2016 |
Event Type
malfunction
|
Manufacturer Narrative
|
On 10/26/2016, the dchu contacted the customer to evaluate patient safety issues.The wrong patient reports were readily apparent to the user and no indication was made of patient safety issues.Upon investigation the reports were importing with a file extension but without a file name.The reports were importing to the customer's shared directory as ".Pdf" instead of "filename.Pdf".The lack of the filename is causing the report to be pulled by the customer's hospital information system (his) and matched to random patients within the customer's his.Merge healthcare is working with the customer to resolve this issue.When more information becomes available, a supplemental report will be submitted.
|
|
Event Description
|
Merge cardio is a system intended to be used to acquire, store, print, transfer, and archive clinical information including images, hemodynamic studies and reports, measurements (via import from dicom structured reporting, text files or optical character recognition of measurements captured on images) and cardiology signal (waveform) data.On (b)(6) 2016, a customer contacted merge healthcare and stated that merge cardio's pdf reports were posting under the wrong patient in their hospital information system (his).Clinical reports posting under the wrong patient has a potential for incorrect treatment of the patient which may lead to harm.The customer reported that no patient harm was caused as a result of this issue and that the issue is readily apparent to the user.(b)(4).
|
|
Manufacturer Narrative
|
This supplemental report is submitted to the fda in accord with applicable regulations and as indicated by merge healthcare in the initial report submitted 10/27/2016.An internal investigation was completed by merge healthcare (vrcs-13294) and it was found that, after a doctor confirms a report, it gets saved as a pdf and is given a numerical name in sequence.Periodically the report is being stored without that numerical name, just as ".Pdf".This causes issues with saving in the emr.Updating permissions on the getformattedfilename sp in condor database will resolve this issue.The issue, which is readily apparent, does not pose patient safety concerns.The potential impact to a patient has been reviewed and the risk level has been assessed as low (non-serious injury).Additionally, a low number of customers have reported this issue therefore reducing the frequency of occurrence.No further actions are anticipated at this time due to the issue being readily apparent, the low number of complaints, the ability for merge support to correct this issue by updating the database and low impact on patients.
|
|
Search Alerts/Recalls
|
|