Graves v. Cas Medical Systems, Inc.

735 S.E.2d 650, 401 S.C. 63, 2012 S.C. LEXIS 335
CourtSupreme Court of South Carolina
DecidedDecember 12, 2012
DocketNo. 27168
StatusPublished
Cited by20 cases

This text of 735 S.E.2d 650 (Graves v. Cas Medical Systems, Inc.) is published on Counsel Stack Legal Research, covering Supreme Court of South Carolina primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Graves v. Cas Medical Systems, Inc., 735 S.E.2d 650, 401 S.C. 63, 2012 S.C. LEXIS 335 (S.C. 2012).

Opinion

Justice HEARN.

India Graves, a six-month-old girl, died while being monitored by one of CAS Medical Systems’ products. India’s parents, Kareem and Tara Graves, subsequently filed a products liability lawsuit against CAS, contending the monitor was defectively designed and failed to alert them when India’s heart rate and breathing slowed. The circuit court granted CAS’s motion to exclude all of the Graves’ expert witnesses and accordingly granted CAS summary judgment. We affirm as modified.

FACTUAL/PROCEDURAL BACKGROUND

India and her sisters, Asia and Paris, were triplets born prematurely to Kareem and Tara. All three girls spent the first six weeks of their lives in the hospital so they could be monitored, a standard practice for premature babies. When they were finally sent home, their doctor ordered that the Graves use a monitor manufactured by CAS to track their breathing and heart rates as a precaution. The monitor was designed to sound an alarm, which, by all accounts, is quite loud, if the subject were to experience an apneic, bradycardia, or tachycardia event.1 Once the breathing or heart rate returns to normal, the alarm stops. Each machine also keeps a log of any events, which is the term for when the alarm sounds, and records the pertinent data and vital signs.

As an additional safety measure, CAS installed not only a back-up alarm, but also a feature that records whether the alarm sounded. This system operates primarily through an independent and separate microphone specifically designed to listen for the alarm. If it hears the alarm, it then makes a notation in the monitor’s internal log. If it does not hear the alarm, then it records “Front alarm not heard,” and the monitor will sound the backup alarm. A microphone listens [69]*69for this back-up alarm as well and records whether it was heard. If the back-up alarm fails, all the lights on the front of the monitor flash.

On the night of April 10, 2004, India was hooked up to the monitor and fell asleep next to her father on his bed. At the time, Tara was awake doing chores.2 Tara eventually moved India to her bassinet, and Tara herself went to sleep around 2:00 in the morning on April 11th. According to Tara, she woke up shortly before 4:00 a.m. from a bad dream and decided to go check on the babies. Paris and Asia responded to her touch, but India did not. When she realized India was not breathing, she immediately began CPR. Kareem woke up during the commotion and called 911. By the time EMS arrived, India was already dead. An autopsy revealed that she died from Sudden Infant Death Syndrome (SIDS), which essentially means that no attributable cause of death exists.

Tara and Kareem claim the monitor’s alarm never sounded that night. Additionally, they testified that all the lights on the front of the monitor were on, although they were solid and not flashing. Another family member who was asleep downstairs from India also could not recall hearing the alarm go off. Tara further testified the machine was not turned off until the next day, when the monitor was removed for testing.

India’s monitor recorded the following events beginning the morning of April 11th. At 2:39 a.m., the monitor first detected a slow heart beat from India. Over the next thirteen minutes, the monitor recorded twenty-three separate apnea or bradycardia events. By 2:52 a.m., India had passed the point of resuscitation. The monitor recorded six more events before showing it was powered down at 3:50 a.m. The log shows it was then powered back up the next morning. For every event, the monitor recorded hearing the alarm properly sound and accurately traced India’s slowing breathing and heart rate. As India’s treating physician put it, the machine’s performance was tragically perfect: “[A]s sad as it is, the tracing is beautiful. It is a — you watch the baby die on the leads.”

[70]*70The Graves subsequently filed a strict liability design defect claim against CAS, contending the monitor’s software design caused the alarm to fail.3 Their claim revolves around what is known as “spaghetti code,” which is when computer code is unstructured and becomes “a rather tangled mess.” Spaghetti code can result from the overuse of “goto” or “unconditional branch” statements, which causes a signal working its way through the code to jump around instead of following a linear path. Boiled down, the Graves’ theory is that certain unknown external inputs occurring during India’s apneic and bradycardia events triggered some of these goto statements as the signal was being sent to sound the alarm. This in turn caused the signal to be pushed off course and never reach its destination.

To support this theory, the Graves designated three software experts to testify regarding the alarm’s failure: Dr. Walter Daugherity, Dr. William Lively, and Frank Painter. In arriving at their conclusions that a software defect caused the alarm to fail, none of the experts did much actual testing of the software. Instead, they used a “reasoning to the best inference” analysis, which is similar to a differential diagnosis in the medical field where potential causes of the harm are identified and then either excluded or included based on their relative probabilities. In this case, three potential causes were identified: hardware error, complaint error, and software error. Complaint error means that the monitor was misused or the alarm did sound and the Graves failed to hear it.4 All the experts were able to dismiss hardware error as a [71]*71cause because the machine was tested and shown to have functioned properly. Thus, the question became whether complaint error or a software error occurred.

Dr. Daugherity excluded complaint error because the machine was hooked up to India properly and he did not believe anyone could sleep through the alarm. In other words, because the Graves claim the alarm did not wake them, that means it did not go off. After being confronted with the fact that the monitor listens for the alarm and separately records whether it was heard, Dr. Daugherity accordingly concluded it “is certain” the internal logs showing the alarm sounded on the morning of April 11th are not reliable “in light of the undisputed testimony that the alarm did not function.”5 Having dismissed hardware and complaint error, Dr. Daugherity ultimately concluded that software error was the most likely cause of the alleged failure based on his independent review of the code and other reported incidents of alarm failure.6

As to Dr. Lively, the record does not show he engaged in any analysis regarding complaint error. He did agree with Dr. Daugherity that the most likely cause was software error. [72]*72In arriving at this conclusion, however, Dr. Lively relied only on Dr. Daugherity’s review of the code and did nothing to search for a defect himself. In fact, he testified it was not his job to look through the code for errors, and that responsibility fell on Dr. Daugherity. He also relied on the same reports of other failures as Dr. Daugherity, but he admitted that he did not know whether these other reports had been substantiated.

Painter as well concluded a software error most probably caused the alarm to fail. He, like Dr. Daugherity, excluded complaint error because of the Graves’ own statements that the alarm failed.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Karrie Gurwood v. GCA Services Group, Inc.
Court of Appeals of South Carolina, 2025
James Ware v. Beaufort County
Court of Appeals of South Carolina, 2025
Eichin v. Covidien LP
D. South Carolina, 2024
Tekayah Hamilton v. Regional Medical Center
Court of Appeals of South Carolina, 2023
State v. Jaron Gibbs
Supreme Court of South Carolina, 2023
State v. Young
Court of Appeals of South Carolina, 2021
Norton v. General Motors LLC
D. South Carolina, 2020
State v. Phillips
Supreme Court of South Carolina, 2020
Ray v. City of Rock Hill
Court of Appeals of South Carolina, 2019
State v. Simpson
823 S.E.2d 229 (Court of Appeals of South Carolina, 2019)
State v. Mealor
825 S.E.2d 53 (Court of Appeals of South Carolina, 2018)
State v. Greene
814 S.E.2d 496 (Supreme Court of South Carolina, 2018)
Lord v. D&J Enterprises, Inc.
Court of Appeals of South Carolina, 2018
Barry Zuckerman v. Wal-Mart Stores East, L.P.
611 F. App'x 138 (Fourth Circuit, 2015)
Holmes v. Haynsworth, Sinkler & Boyd
Supreme Court of South Carolina, 2014
Riley v. Ford Motor Co.
757 S.E.2d 422 (Court of Appeals of South Carolina, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
735 S.E.2d 650, 401 S.C. 63, 2012 S.C. LEXIS 335, Counsel Stack Legal Research, https://law.counselstack.com/opinion/graves-v-cas-medical-systems-inc-sc-2012.