• Decrease font size
  • Return font size to normal
  • Increase font size
U.S. Department of Health and Human Services

MAUDE Adverse Event Report: ECLIPSYSSUNRISE CLINICAL MANAGER

  • Print
  • Share
  • E-mail
-
Super Search Devices@FDA
510(k) | DeNovo | Registration & Listing | Adverse Events | Recalls | PMA | Classification | Standards
CFR Title 21 | Radiation-Emitting Products | X-Ray Assembler | Medsun Reports | CLIA | TPLC | Inspections
 

ECLIPSYS SUNRISE CLINICAL MANAGER   Back to Search Results
Event Date 06/12/2010
Event Type  Injury   Patient Outcome  Hospitalization,Other,Life Threatening,Required Intervention
Event Description

The eclipsys sunrise clinical manager emr/cpoe is in use at (b) (6) hospital. This system appears to have a serious deficiency: an apparent lack of date constraint validity checking when users are seeking information on prior medication orders and administration. (b) (6), (b) (6) was admitted (b) (6) 2010, for cerebrovascular problems. Famotidine iv was started prophylactically to prevent gastric problems, but was discontinued and changed to protonix a few days later due to suspicion of causing severe agitation and confusion, causing her to pull her lines. Around (b) (6) 2010, patient was transferred to physical therapy floor in the hospital. Hospital considers such a transfer to be a "discharge" and "readmission. " however, patient did poorly, had to be sent back to med-surg floor several days later. Due to having pulled a percutaneous endoscopic gastrostomy tube -peg tube-, she was started on tpn on (b) (6) 2010. In the first bag of tpn solution was 40 mg. Famotidine. Patient's mental status began deteriorating and she began to get very, very agitated and confused once again. Eclipsys sunrise problem/bug was noted when son, a physician informaticist -and author of this report- noted the 40 mg famotidine in the tpn bag, and reported to the floor rn that this was contraindicated. The rn pulled up the medication order and administration records on the eclipsys sunrise clinical manager system to confirm famotidine had been administered previously. Famotidine was shown only as being ordered for tpn on (b) (6), but not prior. The rn selected a date constraint entry box, at which time a calendar widget popped up. The rn set the date constraint back to (b) (6), then (b) (6), then (b) (6) 2010, but the use of the famotidine at that time did not appear. Son of patient demanded the famotidine be stopped anyway, which it was, and that an allergy entry be entered. However, it was fortunate son was a physician and remembered the name of the medicine. In tracing this error today, it was found that the data from admission on (b) (6) to "discharge" to physical therapy floor (b) (6) 2010, was unavailable since it was considered a "prior admission" although the patient had never left the hospital physically. The sunrise system, however, failed to flag the (b) (6) 2010 date constraint entries as 'out of bounds' for the current admission. The validity of the date constraints was not checked, preventing the rn user from realizing he should have called up the prior admissions records. If son of patient had not been a physician, gamotidine might have been continued and patient might have suffered more severe consequences than she did after the 40 mg was given in the first tpn bag. As it was, she spent the next three days in a severe delirium and is only slowly recovering. That the eclipsys sunrise ehr did not alert its user that the date constraints they set for seeking medication ordering and administration data were out of bounds -beyond the range of the current "admission" -is a significant and severe oversight and/or bg, and a danger to patients not fortunate enough to have a physician informaticist son closely monitoring their care.

 
Search Alerts/Recalls

  New Search  |  Submit an Adverse Event Report

Brand NameECLIPSYS
Type of DeviceSUNRISE CLINICAL MANAGER
Device Event Key1772483
MDR Report Key1729552
Event Key1641601
Report NumberMW5016413
Device Sequence Number1
Product CodeLNX
Report Source Voluntary
Reporter Occupation Physician
Type of Report Initial
Report Date 06/15/2010
1 Device Was Involved in the Event
1 Patient Was Involved in the Event
Date FDA Received06/15/2010
Is This An Adverse Event Report? No
Is This A Product Problem Report? Yes
Device Operator Health Professional
Was Device Available For Evaluation? No
Is The Reporter A Health Professional? Yes
Was The Report Sent To Manufacturer? No
Is this a Reprocessed and Reused Single-Use Device? No
Is the Device an Implant? No
Is this an Explanted Device?

Patient TREATMENT DATA
Date Received: 06/15/2010 Patient Sequence Number: 1
#TreatmentTreatment Date
NA
-
-