03.08.2013 Views

Public Health Law Map - Beta 5 - Medical and Public Health Law Site

Public Health Law Map - Beta 5 - Medical and Public Health Law Site

Public Health Law Map - Beta 5 - Medical and Public Health Law Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

intentionally made, incorrect decisions. System failures (more informally called<br />

“slipping through the cracks”) occur when a patient receives, or fails to receive, needed<br />

care due to inadvertence. Patients are at the greatest risk for system failures when they<br />

have nonserious conditions that are routinely managed without ongoing evaluation.<br />

System failures usually involve overlooking unexpected data. This might be ignoring<br />

the third call back by the mother of a child with an infected throat, which should have<br />

triggered a reevaluation of the patient’s treatment. This is not usually a problem<br />

because most children with infected throats have no major problem. It is the child with<br />

meningitis injured when the physician inadvertently continues routine treatment whose<br />

injuries lead to litigation.<br />

In obstetrics, common system failures include failing to diagnose existing systemic<br />

diseases, failing to offer screening tests at the appropriate time, failing to act on<br />

positive test results, <strong>and</strong> failing to respond quickly to threats to fetal or maternal health.<br />

System failures pose the major risk in obstetric care because most pregnant women are<br />

healthy <strong>and</strong> most pregnancies end in the birth of a healthy baby.<br />

Since the medical component of prenatal care is a screening program, failures in the<br />

prenatal care system are irrelevant to most women because they do not have any of the<br />

conditions for which the screening is performed. As with the child with an infected<br />

throat, the system failure harms only the patient who does not have the usual condition.<br />

In obstetrics, the failure of the prenatal system does not matter for most women; it does<br />

matter for a woman who has a medical condition that requires nonroutine treatment to<br />

protect her health or the health of the baby.<br />

To use the MSAFP example assume the physician has all abnormal laboratory reports<br />

put on the front of the chart for review. The file clerk loses 2% of all laboratory<br />

reports. Since the physician depends on abnormal results being flagged, no flag is<br />

taken to be a normal result.<br />

Assuming a rate of 1 neural tube defect per 500 births, the probability of a missed<br />

diagnosis is .02 ⋅ .002, or 1 per 25,000 births. The odds are that this practice could go<br />

on for years before resulting in an injury in any given physician’s practice. That injury<br />

can be very expensive. A $1 million award would not be unusual in such a case.<br />

Assume further that an average obstetrician delivers 50 babies a year. (This is a low<br />

number for a full- time obstetrician but is used to include family practitioners who<br />

deliver babies <strong>and</strong> physicians with substantial gynecology practices.) Then 25,000<br />

births represent 500 obstetrician-years, for a risk of $2,000 per obstetrician-year.<br />

From a management perspective, delivering routine obstetrical services is more like<br />

flying an airliner than like treating an acute illness: small things matter, <strong>and</strong> mistakes<br />

are infrequent but costly. As with flying the airliner, most of the things that matter are<br />

not done by the person in charge. The pilot does not service the engines, <strong>and</strong> most<br />

prenatal care is done by persons other than the supervising physician.<br />

1. Zero-Defects Management<br />

Zero-defects management is based on the premise that it is better to detect<br />

577

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!