Patient Safety / Quality

Saved by…um…Facebook?

A woman presented to a medical center in labor with her first child. Her pregnancy was at term and her water had broken that morning.* She was admitted and her labor monitored throughout the day. She was making slow, but normal progress. Fetal heart tones remained within normal range except for a few isolated decelerations. However, that evening the fetal heart rate crashed precipitously. The labor and delivery nurse called the on-call obstetrician/gynecologist, who arrived within 10 minutes and ordered an immediate Cesarean section delivery.

The delivery occurred 22 minutes after the doctor’s arrival. Nonetheless, the child suffered a catastrophic and irreversible brain injury because the umbilical cord was wrapped around his neck. The child lived for 39 days before life support was removed and he died.

Court case

The plaintiff claimed that nurses at the hospital failed to note and respond to signs of fetal distress hours before the fetal heart rate crash. She further argued that the nurses failed to follow hospital policy regarding reporting of decelerations on the fetal monitor. Moreover, she claimed that the nurse who was monitoring her had failed her boards twice and had a history of poor performance. The woman also claimed that the nurse waited 15 minutes before calling the doctor because she “was busy with other women in labor” and that the doctor did not arrive for another 15 minutes – and then it was almost a half hour before her C-section.

The hospital claimed that the cord accident could not be predicted or avoided and that it was a sudden event that occurred when the crash was noted and that a C-section delivery was promptly performed. The hospital also claimed that a few isolated decelerations were not troubling and that the hospital’s written policy did not reflect the proper modern practice. The hospital also claimed that a call was made promptly to the doctor and that the doctor responded quickly. The hospital maintained that the exact timing was not crucial, as the injury most likely had already occurred when the crash was seen.

According to a Trial Court Review, a $1,183,638 verdict was returned. The hospital sought a new trial and/or mistrial based on a Facebook posting by a juror: “I’m on jury duty. God help me,” to which a friend replied, “They’re guilty…whatever it is, they’re guilty.” The juror then replied, “Starting to feel that way.” That, the hospital claimed showed this juror had discussed and prejudged the case.

The plaintiff also moved for a new trial due to a failure to award damages in certain damages categories. The court’s decision found in favor of the hospital on its post-trial motion and then held that the plaintiff’s post-trial motion was moot.


Analysis

Labor is an inherently dangerous life event for a fetus and its mother. In the majority of cases, everything goes smoothly enough and ends happily. In a minority of cases, there are some problems. Electronic fetal monitoring is used to provide minute-by-minute information on the status of the fetus, accurate historical information on fetal status and the frequency/duration of contractions from earlier in labor, and insight into the stresses on the fetus and its ability to tolerate those stresses.

The normal fetal heart rate baseline is from 120 to 160 BPM and has both short and long-term “variability.” Early decelerations are periodic slowing of the fetal heartbeat, synchronized exactly with the contractions. These dips are rarely more than 20 or 30 BPM below the baseline.

Late decelerations are repetitive, gradual slowings of the fetal heartbeat toward the end of the contraction cycle. Clinically, the development of late decelerations is a worrisome sign that the fetus has very little reserve. Variable decelerations are variable in onset, duration, and depth. They are thought to represent a vagal response to some degree of umbilical cord compression. If the umbilical cord is only slightly compressed, this will obstruct the umbilical vein (low pressure system), which returns re-oxygenated blood to the fetal heart. So, a great deal, in this case, rests on whether the decelerations were early or late decelerations.

It is, of course, most unfortunate that the hospital had not updated its own policy regarding expected nursing responses to decelerations in fetal heart tones. Claiming that the nurse was right in not following the hospital’s own policy is a weak argument at best. All policies should be current and reflect what is expected of hospital personnel under any circumstance; it is administration’s ethical duty to the staff – and to the patients. To fail to do this is to endanger both staff and patient – and the institution. This is undoubtedly the major reason the jury found for the plaintiff and against the hospital.

However, the juror’s imprudent comments on Facebook gave the hospital an undeserved second chance…

*Russell v. Three Rivers Medical Center

Leah Curtin, RN, ScD(h), FAAN, is executive editor, professional outreach for American Nurse Today.

Related Articles:

4 thoughts on “Saved by…um…Facebook?”

  1. Leah Curtin says:

    I agree with each of the commentators — and would add one more thing. Not only are facebook postings able to be seen by others. So are emails. Consider these PUBLIC communications, and do not say (or post) anything you do not want the whole world to see/know!

  2. Anonymous says:

    This reiterates what I have been telling my teenage son for several years – Facebook isn’t seen solely by the individual to whom the communication is addressed.

  3. Anonymous says:

    Clearly the hospital should have up to date policies, but it is also important as this situation is discussed that FHR monitoring definitions are current and accurate. The recent assignment of Categories to describe FHR patterns has given hospital staff the ability to look at FHR baseline, variability and types of decelerations present, and assign a category. Each category has a plan of action associated with it.

  4. Anonymous says:

    A good example of how social media could be harmful…

Leave a Reply

You have to agree to the comment policy.

 

Shares