Click here for more sample CPC practice exam questions with Full Rationale Answers

Practice Exam

Click here for more sample CPC practice exam questions and answers with full rationale

Practice Exam

CPC Practice Exam and Study Guide Package

Practice Exam

What makes a good CPC Practice Exam? Questions and Answers with Full Rationale

CPC Exam Review Video

Laureen shows you her proprietary “Bubbling and Highlighting Technique”

Download your Free copy of my "Medical Coding From Home Ebook" at the top right corner of this page

Practice Exam

2018 CPC Practice Exam Answer Key 150 Questions With Full Rationale (HCPCS, ICD-9-CM, ICD-10, CPT Codes) Click here for more sample CPC practice exam questions with Full Rationale Answers

Practice Exam

Click here for more sample CPC practice exam questions and answers with full rationale

New PSO guidance raises questions over patient safety work product privilege

New PSO guidance raises questions over patient safety work product privilege

In May, the U.S. Department of Health and Human Services (HHS) published Guidance Regarding Patient Safety Work Product and Providers’ External Obligations in the hopes of clarifying what documents are considered patient safety work product (PSWP) and thus protected from discovery during litigation. Because the guidance has far-reaching implications for the scope of the privilege and confidentiality protection, providers should consider reexamining their process for collecting information in the pursuit of improving patient safety.

Under the Patient Safety and Quality Improvement Act (PSQIA), providers collect and manage information through a patient safety evaluation system (PSES), which is then sent to a patient safety organization (PSO) for analysis and feedback. To motivate providers to participate in PSOs, PSQIA entitles the submitted information broad privilege and confidentiality protections.

According to Michael R. Callahan, Esq., partner at Katten Muchin Rosenman, LLP, in Chicago, the guidance may impact how discoverability disputes are handled in courts. To understand why, consider the three primary buckets of patient safety information:

  • Bucket one: All mandated reports. For example, some states like New York and Florida require mandated adverse reporting if a wrong site surgery is performed. For these incidents, hospitals are required to prepare and submit a report to the state. Reports that fall within this bucket shouldn’t be treated as PSWP.
  • Bucket two: All reports that hospitals are required to collect and maintain pursuant to state and federal law, such as the Medicare Conditions of Participation (CoP).
  • Bucket three: All other information collected and maintained in a hospital’s PSES to improve quality, safety, and patient outcomes. This information is PSWP.

Disputes will arise from reports that fall into bucket two, Callahan says. HHS’s guidance stated that this type of information isn’t PSWP, but not all state and federal laws have crystal clear language defining what information hospitals need to collect and maintain.

"You will seldom find in the state and federal laws a specific list of documents which identifies the kinds of records and reports a provider is required to maintain and collect and to make available for inspection by a governmental authority. It is not that clear cut and hospitals use different terminology," he says.

For example, Callahan points out that in the case Tibbs v. Bunnell, discussed later in this article, the dispute was over the question of whether an incident report collected and reported to a PSO by a defendant hospital was a bucket two document. "The language under Kentucky law obligated the hospital to maintain and collect ‘incident investigation reports’ but does this refer to the incident report, a resulting root cause analysis report or a peer review investigation report? Is it all or none of the above?"

 

The PSO guidance

The guidance, which was published in the Federal Register in May, clarifies what information can and cannot be called PSWP. Information can be PSWP if:

  • A provider prepares it for reporting to a PSO and follows through in the reporting
  • A PSO develops it for the conduct of patient safety activities
  • A provider places it in a PSES to be reported to a PSO

 

Information that can’t be PSWP includes:

  • Patient medical records, billing and discharge information, or any other original patient or provider information
  • Materials collected and maintained separately from a PSES
  • Records mandated by federal and state law
  • Information prepared to satisfy external obligations

 

One criticism of the guidance is its expansion of the concept of original patient and provider records, Callahan says. PSQIA states these records, such as medical records and billing information, can never be privileged. The guidance further clarified the scope of what these records include:

  • Original records required of a provider to meet any federal, state, or local public health or health oversight requirements regardless of whether they are maintained inside or outside of the PSES
  • Copies of records that reside within a provider’s PSES that were prepared to satisfy a federal, state, or local public health or health oversight record maintenance requirement if the records are maintained only within the PSES and any original records are either not maintained outside of the PSES or were lost or destroyed

Callahan takes issue with HHS’ expansion of the definition of an original patient and provider record to include bucket one and bucket two documents, especially since it was put forth in guidance and not a final rule.

Requirements under the Administrative Procedure Act require a notice and comment period before a final rule is adopted. However, HHS chose to issue the guidance without following this procedure and therefore it should only be viewed as an interpretative rule, Callahan says. The U.S. Supreme Court decision earlier this year in the case of Perez v. Mortgage Bankers Association found that interpretive rules "do not have the force and effect of law."

"The guidance is simply an interpretation provided by HHS. While it certainly expresses the position of HHS, the Office of Civil Rights and the Agency for Healthcare Research and Quality (AHRQ) from a regulatory enforcement standpoint, it is not binding on state or federal courts," he says.

As a result, different interpretations of PSQIA will likely lead to continued challenges to court orders to turn over documents hospitals believe to be PSWP. Some of these discoverability disputes have made their way to state supreme courts.

 

Southern Baptist Hospital of Florida v. Charles

In a case that will go before the Florida Supreme Court later this year, Southern Baptist Hospital of Florida v. Charles, the PSO guidance may play a role in determining whether occurrence reports?reports that hospital collects and maintains for events that are inconsistent with its routine operations or care of patients, or that could result in an injury?are PSWP.

The plaintiff sued Southern Baptist Hospital of Florida, claiming his sister suffered a catastrophic neurological injury due to negligence. During discovery, the plaintiff requested documents related to adverse medical incidents and the conduct of physicians who worked at the hospital. This request was made pursuant to Amendment 7 of the Florida Constitution, which provides patients with the right to access "any records made or received in the course of business by a healthcare facility or provider relating to any adverse medical incident."

Although the hospital produced some of the requested documents, it declined to turn over occurrence reports that were collected within its PSES and reported to its PSO, claiming they were PSWP and therefore privileged and confidential under PSQIA.

The plaintiff argued that PSQIA only protects documents generated exclusively for submission to a PSO, so anything collected to also satisfy a state law is not PSWP. The circuit court agreed, finding that information collected for dual purposes was not PSWP and ordered the hospital to produce the documents.

This order was later reversed by an appellate court, which said the documents were PSWP because they were collected in the hospital’s PSES and reported to a PSO. Further, documents can simultaneously be PSWP and meet a state reporting requirement. The plaintiff appealed to the state supreme court, which will hear the case in October.

Since the documents in question fall into bucket two, the plaintiff will likely cite the guidance to support a position that the reports can’t be treated as PSWP and therefore are discoverable, says Callahan. However, the argument can be made that the guidance is not legally binding on the courts.

 

Tibbs v. Bunnell

The release of the PSO guidance likely contributed to the U.S. Supreme Court’s denial to hear Tibbs v. Bunnell. The case would have provided a nationwide interpretation of the scope of privilege and confidentiality protections under PSQIA for reports submitted to PSO, as well as whether PSQIA preempted state laws.

In Tibbs, a patient’s estate brought a wrongful death and medical malpractice suit against three surgeons employed by University of Kentucky Hospital. The plaintiffs sought to discover a post-incident event report generated by a surgical nurse through the hospital’s PSES and subsequently sent to its PSO.

At trial, the hospital argued that the report was protected under PSQIA and therefore not subject to discovery. However, the trial court ruled that the report was not protected under PSQIA. The hospital appealed.

Although the appellate court found that the privilege provided by the PSQIA did preempt the Kentucky state law, it stipulated that protections afforded by PSQIA only apply to documents that contain "self-examining analysis," meaning those in which the provider analyzes his or her own actions. The court then sent the matter back to the trial court for evaluation of whether the report contained self-examining analysis.

The hospital appealed to the Kentucky Supreme Court, arguing that the appellate court erroneously limited the scope of privilege protections under PSQIA. The Supreme Court reversed the Court of Appeals’ interpretation of PSQIA, finding it too narrow. However, it also ruled that the incident report was not protected under PSQIA because its creation, maintenance, and utilization was required in the regular course of the hospital’s business, as well as under Kentucky state law. Therefore it cannot be collected within the hospital’s PSES and treated as PSWP.

In response, the hospital filed a petition for the U.S. Supreme Court to review the Kentucky Supreme Court’s decision. The petition had the support of more than 50 PSOs, hospitals, and health systems from across the country, as well as the American Hospital Association, AMA, and The Joint Commission. Last October, the court asked the U.S. solicitor general to file a brief on his views of the case and whether the petition should be granted or denied.

Just as the guidance was published, the solicitor general filed his brief to the court. The brief recommended that the court deny the petition in light of the guidance issued by HHS and because hearing the case would be premature until it is seen how the lower courts interpret and apply the guidance.

In June, the U.S. Supreme Court denied the petition without comment and without remanding the case back to the Kentucky Supreme Court to take the guidance into consideration. This leaves the Kentucky Supreme Court’s ruling in place, although the decision is only binding on Kentucky courts.

 

Carron v. Rosenthal

Regardless of the U.S. Supreme Court’s denial to hear Tibbs, discovery disputes are still playing out in other courts. The Rhode Island Supreme Court will be hearing an appeal of an order for a hospital to produce incident reports in Carron v. Rosenthal. In this case, the plaintiff is suing her obstetrician and Newport Hospital for medical malpractice after her newborn baby suffered irreversible brain damage following a failed labor induction and died days later.

Two nurses prepared incident reports known as Medical Event Reporting System (MERS) reports, which were submitted to the hospital’s PSO. The hospital also produced separate state-mandated adverse event reports.

Later during discovery, the nurses were deposed but had difficulty remembering what had happened, so the plaintiffs asked that the hospital produce the MERS reports. The hospital objected, citing PSQIA and the Rhode Island Patient Safety Act.

According to Callahan, much of the plaintiff’s argument was based on the Kentucky Supreme Court’s decision in Tibbs that reports required by state statutes can’t be treated as PSWP. However, Newport Hospital argued that in Tibbs, the University of Kentucky Hospital collected state mandated reports in its PSES. At Newport Hospital, state mandated reports are collected separately. The MERS reports were separate reports distinguishable from the mandated reports and therefore were PSWP, according to the hospital.

Despite this argument, the trial court ruled in favor of the plaintiff and order the hospital to show the MERS reports to the nurses?but not the plaintiff?to refresh their memories before they were to be deposed again. The hospital appealed and, because Rhode Island does not have an appellate court, the state supreme court exercised its discretion to hear the hospital’s appeal. A decision is expected later this year.

 

What can providers do?

With the U.S. Supreme Court declining to hear Tibbs, and ongoing confusion in regards to the guidance, providers that participate in a PSO have a few options for how to proceed.

Providers can choose not to do anything and simply maintain the status quo as they wait for further regulatory or judicial developments, says Callahan. "We have these other cases before state supreme courts and it’s conceivable one of those will be appealed. It doesn’t mean the U.S. Supreme Court is going to accept one of these other ones, but that’s a development that providers may want to wait on."

PSOs will also likely have questions about the guidance and will reach out to AHRQ for additional guidance, so providers will want to wait to see if there is any further clarification, he says.

Providers that choose to comply with the guidance will need to determine if any information they were previously collecting in their PSES for reporting to their PSO is no longer considered PSWP. These providers will need to review state and federal laws, including the Quality Assurance and Performance Improvement standards set forth in the Medicare CoP, to ensure the information doesn’t fall into buckets one or two, Callahan says. Anything that’s determined to fall into those two buckets will require modifications to the provider’s PSES policy.

Since the guidance is an interpretive rule, some providers may choose to fight requests to turn over disputed documents, Callahan says. Providers would choose this path if they believed a court would be more likely to side with their interpretation of PSQIA.

More drastically, providers could simply decide to abandon their PSOs altogether. However, there are several factors to consider before making that move, says Callahan.

The Affordable Care Act requires hospitals with more than 50 beds that want to provide healthcare services to patients enrolled in a state insurance exchange to be enrolled in a PSO. This was modified to allow hospitals to meet the requirement by contracting with a hospital engagement network (HEN) or quality improvement organization (QIO).

However, contracting with a HEN or QIO doesn’t offer providers the same privilege protection received from participating in a PSO. Those providers would still have their state law protections, but those vary and some states may not have any protections at all or limited protections, Callahan says.

Providers considering leaving their PSO will need to evaluate their state protections, including the scope of protected activities and entities.

"Using Illinois as an example, [state law protections] only generally apply to hospitals, surgery centers, and managed-care entities. The statutes do not apply to physicians, physician groups, labs, pharmacies, home health, or other licensed providers. So if you have formed a clinically integrated network with all these different provider boxes, only the hospital?for all practical purposes?will be protected," Callahan says.

Providers should also check to see if it’s possible under state law to inadvertently waive the privilege if protected information is not handled correctly (e.g., information is disclosed improperly). Under PSQIA, the protections afforded to PSWP can never be waived.

Callahan also notes it’s important for providers to know that state privilege protections only apply in state courts or state claims. So, for example, if a physician is terminated but falls under a protected class (race, age, sex, religion, etc.), he or she can file a federal claim. The physician can then request access to protected peer review documents. Although the hospital may try to argue that they are privileged and confidential under the state peer review statute, state privilege statutes cannot be asserted to preempt federal claims. However, if the documents were collected in a PSES and reported to a PSO, they would not be undiscoverable.

"The PSQIA has many advantages to offer. Part of the problem, however, is that there are not many appellate court interpretations of the law and most of those decision have only involved medical malpractice cases" Callahan says. "Unfortunately, because the U.S. Supreme Court denied the petition in Tibbs, these disputes will have to be decided on a state-by-state basis. This is great for the attorneys but not helpful for PSOs and participating providers."

HCPro.com – Credentialing and Peer Review Legal Insider