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

Case Management Monthly, October 2016

Case study

MOON requirement delayed in IPPS final rule

Learning objective

At the completion of this educational activity, the learner will be able to:

  • Identify details of the delay to the Medicare Outpatient Observation Notice (MOON) notification requirement

 

Hospitals got a last-minute reprieve from the MOON notification requirement, which was set to go into effect August 6. Citing the need for additional time to revise the standardized notification form that hospitals will need to use to notify patients about the financial implications of being assigned to observation services, CMS moved back the start date for the requirement in the 2017 Inpatient Prospective Payment System (IPPS) final rule to "no later than 90 days," after the final version of the form is approved.

CMS released the new draft of the form August 1 and planned to accept public comments for 30 days. Some experts said that this could mean a January 1, 2017, start date for the requirement, but that remains to be determined, says Stefani Daniels, RN, MSNA, ACM, CMAC, founder and managing partner of Phoenix Medical Management, Inc., in Pompano Beach, Florida.

 

A reprieve for struggling hospitals

The decision to push back the notification requirement start date was likely a relief for many hospitals who reported struggling this summer to comply with the notification requirement, formally known as the Notice of Observation Treatment and Implication for Care Eligibility (NOTICE) Act, which was signed by President Barack Obama August 6. (See related story on p. 3.) The act requires hospitals to provide a verbal and written notice of outpatient status to any patient in observation who has been in the hospital for more than 24 hours, stipulating that hospitals must inform patients within 36 hours from the start of the service, or at the time of discharge, about their status.

The goal of the legislation is to ensure patients are aware of their status and what it might mean for them financially?in particular, how it might affect their postacute care options.

Patients often (wrongly) assume that if they’re in a hospital bed, they are an inpatient.

They also don’t understand the implications of outpatient billing status.

One of the biggest issues that can crop up when a patient’s care orders place him or her on observation status is that he or she will not be eligible for Medicare coverage for a postacute stay in a skilled nursing facility (SNF), and instead may need to pay more out of pocket. Medicare currently only covers SNF extended care rehabilitation services for patients who have three consecutive inpatient days in a hospital. For example, one day in observation and two days as inpatient equals three days in the hospital, but does not meet the three-day inpatient day stay requirement because it only includes two inpatient days.

"An Office of Inspector General report found that the average out-of-pocket cost for SNF services not covered by Medicare was more than $ 10,000 per beneficiary," stated a press release issued by the congressional leaders who promoted the bill (http://ow.ly/S6JSB).

To comply with the rule, hospitals will now need to designate someone?in some cases it may be the case manager?to provide this notification.

 

A changing requirement

The 2017 IPPS final rule shed a few additional details about the notification requirement, including that "hospitals and CAHs may deliver the MOON to individuals receiving observation services as an outpatient before such individuals have received more than 24 hours if "the individual is transferred, discharged, or admitted as an inpatient," says Daniels. The final rule also states that insurers must notify patients of any changes in status initiated by the insurer before he or she has left the hospital.

"Too often, hospital business office reps are informed that a level of care change to observation services is being made by the insurer long after the patient has left the hospital. This could result in the risk of noncompliance with the NOTICE Act," says Daniels.

CMS issued a revised version of the MOON document from the first draft of the document, which was published on the PRA website (http://ow.ly/7TPE302eSiM). (See the new version of the form on pp. 7?8.)

"CMS has made substantive changes to the MOON from the first iteration. The old MOON cannot be used," says Ronald Hirsch, MD, FACP, CHCQM, vice president of the Regulations and Education Group at Accretive Health in Chicago.

The new version of the MOON document requires a narrative outlining why the patient is being placed in outpatient status with observation services. "CMS says that in the future it will consider model language for use in this section. The MOON ‘additional information’ section may be used to add information to meet any state law observation notification requirements that differ from the MOON federal requirements but the MOON may not be used for non-Medicare/Medicare Advantage (MA) patients," says Hirsch.

The final rule also says that the MOON is required for any Medicare/MA patient who receives 24 hours of observation and must be given to the patient within 36 hours. But CMS allows the MOON to be given to any Medicare/MA patient who receives observation services.

"On the other hand, CMS ‘encourages hospitals not to deliver the MOON at the initiation of observation services,’ at which point patients may be overwhelmed and confused," says Hirsch.

When organizations are determining which patient should get the MOON, observation hour counting should begin with the order for observation. The 24-hour period is consecutive and "carved out hours" should not be considered, says Hirsch.

CMS doesn’t dictate which staff members can deliver the MOON, rather leaving that up to the hospital or CAH to decide.

In addition, it states that patients don’t have the right to appeal their placement in outpatient status with observation services, says Hirsch. "CMS removed the QIO quality complaint reference on the MOON to avoid confusion about this," he says.

Organizations should note that the MOON is required for patients in whom Medicare is a second payer and for all patients with MA plans even though the copayments and SNF requirements for those patients may differ from those described on the MOON.

Stay tuned for future updates on this topic as CMS works on the MOON and other details of the requirement.

 

Getting ready for MOON

Learning objective

At the completion of this educational activity, the learner will be able to:

  • Identify challenges related to implementing the Medicare Outpatient Observation Notice (MOON) and the Notice of Observation Treatment and Implication for Care Eligibility (NOTICE) Act.

 

When CMS decided to postpone the MOON notification requirement a few days before the scheduled implementation date of August 6, it provided a welcome reprieve for many hospital staff members who were scrambling to get ready (see related story on p. 1).

"We were almost ready to go, however, plans are actually now on hold until the final draft is approved, in probably January," says Frantzie Firmin, MS, RN, director, utilization management and care coordination of Brigham & Women’s Hospital in Boston.

The hospital’s preparations included development of a process to deliver the notification to patients who needed it.

"Our organization, Partners Healthcare System, has decided to address the MOON implementation systemwide. As a result, we set up a case management expert panel, which is a collaborative practice committee that meets regularly to address and develop a plan that will ensure regulatory compliance across the system," she says.

The group worked with the electronic medical system team to develop an automated workflow directly within the system. "Each hospital has its own work queue set up," says Firmin. "The Medicare patients in the work queue are only those in observation status that have been there 12 hours or more."

Care coordinators and insurance support nurses have access to the work queue, which allows them to identify their observation patients. "Furthermore, we have also added functionality in [our electronic system] to document that the notice has been given," she says. Staff members are able to check off the status and date of receipt for each patient, and then the patient’s name moves out of the work queue.

The system also allows the insurance support nurse or care coordinator to print the form and provide a copy to the patient before discharge.

Other organizations had taken similar steps.

RWJ Barnabas Health in Toms River, New Jersey, also formed a small task force to ensure compliance with MOON, says Shawna Grossman Kates, MSW, MBA, LSW, CMA, the organization’s case and bed management director. But while MOON is new to them, this type of observation notification requirement is not. New Jersey hospitals have already been subject to an even more restrictive patient notification requirement for several years, she says.

Hospitals in New Jersey must issue a letter to patients detailing their status at the time of placement.

Sometimes that’s difficult to do. It requires different portals because notifications may affect everyone, from the elderly adult coming in through the ER to pediatrics observation patients or labor and delivery observation patients.

"To some degree, the emphasis on MOON has instigated a renewed attention to make sure we’re in compliance with the state of New Jersey’s regulations and that we have continuity and standard practices on a systemwide basis," she says.

Massachusetts General Hospital in Boston has come up with a workflow for how the form will be delivered and a communication plan to deliver it, says Nancy Sullivan, MBA, CMAC, executive director of case management at the organization.

But like other organizations, plans at Massachusetts General Hospital are on hold as CMS prepares the final version of the new MOON form.

Part of the hospital’s initial plan to comply with MOON prior to the postponement was to print a daily report that listed the patients who would need the notice and to use case management resource specialist staff members, who provide support to case managers, to deliver the notification. The hospital worked with staff members to develop a training script.

 

A challenging requirement

While case management experts agree that notifying patients and giving them information about their status is the right thing to do, there are significant challenges they are trying to work past to make the notification a reality.

For example, CMS’ new proposed form, says Kates, is not written in simple language that is easy for most patients to understand. "The Medicare MOON document is not third-grade reading level language," she says. This means that unless CMS makes changes to the form before finalizing it, there will be an additional burden on staff members delivering the notification to clearly explain it to patients. Many organizations will likely need to come up with simpler materials to augment the form to help patients understand the complex subject matter.

Organizations are not permitted to modify the finalized version of the MOON form. "But many are coming up with a one-page handout or an FAQ, or adapting their state hospital association FAQ on observation documents," says Kates.

While CMS estimates the notification process would take about 15 minutes per patient, says Sullivan, it’s likely to take much more staff time due to the complexity of the material.

"The kinds of topics that they plan to include in the letter are complicated," she says.

The challenging nature of these discussions was reinforced by a recent conversation Sullivan had with an elderly family member whose husband was admitted to the hospital.

The woman had called Sullivan in hopes of having her explain all the hospital jargon and insurance-speak. Trying to explain the billing nuances involved in skilled nursing facilities and Medicare Advantage is no easy task, says Sullivan?particularly if the family is in the midst of a medical crisis.

"I feel like the patient should know what their financial responsibilities will be, I support the concept," she says. But at the same time she says she also understands the real challenges hospital staff members involved in delivering that information will face.

Another factor complicating the notification is that it’s unclear how many languages the document will be available in. At Massachusetts General Hospital, patients speak a multitude of languages so the hospital will likely need translation services when delivering the written and verbal notices.

A third challenge is having a system in place to ensure all the patients who need notifications, get them.

"The biggest implementation challenge will be to ensure we have a mechanism in place to capture all the patients that have been in observation across the hospital," says Firmin. "Although we have a dedicated observation unit, we often have observation patients overflowing across the hospital."

In order for the notification process to be successful, staff members?including nursing staff?should be engaged in the process, says Sullivan. Ideally, nursing staff should have a working knowledge of these issues, particularly in the event a case manager isn’t available and a patient starts asking questions.

It remains to be seen what the final MOON form will look like. CMS opened a 30-day comment period on the MOON August 1 and has said that the rule will go into effect no more than 90 days from the finalization of the form.

Based on this timeline, Kates says she anticipates a January 1 start date, but that remains to be seen.

In the meantime, organizations will be waiting to see the final result of this process, and from there determining how to comply.

 

Ask the Expert

Questions about MOON and CMS notification regulations

Learning objective

At the completion of this educational activity, the learner will be able to:

  • Identify strategies to comply with the Medicare Outpatient Observation Notice (MOON) notification and understand rules related to navigating the skilled benefit for Medicare

 

One of the topics raising the most questions in case management today is related to the MOON notification requirement. Hospitals were struggling this summer to comply with the Notice of Observation Treatment and Implication for Care Eligibility (NOTICE) Act, which was signed by President Barack Obama August 6, requiring hospitals to provide a verbal and written notice of outpatient status to any patient in observation who has been in the hospital for more than 24 hours. Just prior to the August 6 implementation date, hospitals received word that the notification requirement would be delayed pending approval of modifications made to the government’s notification form. (See related story on p. 1.)

But despite the delay, case managers still have questions about MOON, which were answered this month by Ronald Hirsch, MD, FACP, CHCQM, vice president of the Regulations and Education Group at Accretive Health in Chicago. Janet L. Blondo, MSW, LCSW-C, LICSW, CMAC, ACM, CCM, C-ASWCM, ACSW, manager of case management at Washington Adventist Hospital in Takoma Park, Maryland, and Peggy Rossi, BSN, MPA, CCM, a consulting associate for the Center for Case Management in Wellesley, Massachusetts, also tackled a Medicare notification question this month.

 

Q: What is the consequence if we miss giving a patient who meets the MOON criteria the notice? Has there been an update if the observation hours will need a modifier or the claim a value or condition code to show that the notice was given?

 

Hirsch: CMS has not stated the consequence of not issuing a MOON. CMS will be updating its survey tools in the future and may address it there. CMS stated in the IPPS final rule that, "all monitoring and enforcement of the MOON will be consistent with our oversight procedures for other hospital delivered notices."

 

Q: Now that CMS has released a new version of the MOON form, how should my organization proceed?

 

Hirsch: CMS released a new version of the MOON August 1, but it must go through the public comment period. After that time, it will be issued an Office of Management and Budget number and then there will be a 90-day implementation period. Until that time, hospitals should follow any state regulations for notices to outpatients and patients receiving observation services.

 

Q: I read your article on navigating the skilled benefit for Medicare and I have a few related questions. My understanding is that you can only use a Hospital-Issued Notice of Noncoverage (HINN) for inpatient, so you could use it if less than a three-day stay. We have been giving Advance Beneficiary Notices (ABN) for our traditional Medicare patients that are observation when families are not timely on getting a skilled nursing facility secured to those patients that require it. Is this correct?

 

Rossi: The HINNs have varied uses, and if a HINN is used it should be the HINN1, as this is a letter used to deny any admission?it is a preadmission denial and is issued when it is known the stay will not be covered. Another letter to use will be an ABN, as the ABN is a letter designed by CMS to deny outpatient services, when it is known they will not be covered.

 

Blondo: HINN1 is known as a preadmission/admission HINN and can be given prior to a hospital stay when it is expected that the entire stay will be denied for coverage. So if a patient was brought to the hospital ED for the purpose of SNF placement and the physician is writing an order to admit to inpatient, many hospitals have their ED case manager intervene by giving the patient and family the HINN1. The physician does not have to agree with the issuance of the denial notice. Seeing the denial notice often convinces the patient and family to choose another plan of care for the patient, and no admission takes place.

For patients placed in observation, ABNs are used for Medicare Part B outpatient services when it is believed Medicare will no longer pay for the services it normally would cover. Some common reasons one would issue an ABN include when services are not reasonable and necessary or when the care is custodial. So if the family hasn’t moved fast enough to take that available SNF bed and the patient’s care is considered custodial, it is correct to issue the ABN.

For more information, see Medicare Advance Beneficiary Notices, October 2015, Medicare Learning Network, Department of Health and Human Services, Centers for Medicare & Medicaid Services at: www.cms.gov/Outreach-and-Education/Medicare-Learning-Network-MLN/MLNProducts/downloads/abn_booklet_icn006266.pdf.

 

Got a question on any case management topic that you’d like to ask our experts? Email it to Kelly Bilodeau at [email protected].

 

HCPro.com – Case Management Monthly

2016 Taxes will be Held from the 3rd Q Reimbursements

If your chapter owed money for income made in 2016, you should have been contacted by one of your representatives on the AAPCCA Board of Directors, informing you of the amount due. Of the 508 chapters in 2016, 47% of them made a profit leaving a $ 14,000 tax liability. However, 90% of the chapters that […]
AAPC Knowledge Center

Briefings on APCs, October 2016

CMS finalizes self-identified overpayments rule for services including Part B

by Judith L. Kares, JD

The Medicare Reporting and Returning of Self-Identified Overpayments final rule (81 Fed. Reg. 7654?7684), which became effective March 14, is designed to implement Section 1128J(d) of the Social Security Act, which was established under Section 6402(a) of the Affordable Care Act, effective March 23, 2010.

The rule applies only to healthcare providers and suppliers furnishing services under Medicare parts A and B. A separate rule was published in May 2014 that addresses the applicability of similar requirements to overpayments under Medicare parts C and D.

 

Key definitions

Let us begin with the definition of "overpayment" included in the rule. An overpayment means any funds that a person has received or retained under Medicare to which the person, after applicable reconciliation, is not entitled. A "person" means a provider or supplier furnishing services under original Medicare (parts A and B)?not a beneficiary. For purposes of the rule and its underlying statute, a person has an obligation to identify, report, and return overpayments in a timely and effective manner. Failure to do so may subject that person to significant sanctions, including sanctions under relevant federal statutes (e.g., the False Claims Act, Civil Monetary Penalties Law, etc.).

 

Identification

To comply with the regulatory requirements, a person first must be able to identify whether an overpayment has been received:

  • A person has identified an overpayment when the person has, or should have through the exercise of reasonable diligence, determined an overpayment was received and quantified the amount of the overpayment.
  • A person’ should have determined the receipt of an overpayment and quantified the amount if the person, in fact, received an overpayment, but fails to exercise reasonable diligence.

 

Although the overpayments rule provides an incentive for providers and suppliers to exercise reasonable diligence, the rule does not provide much guidance on what reasonable diligence actually constitutes. CMS simply states that reasonable diligence is fact-specific and must be demonstrated by timely, good faith investigation of credible information, generally within no more than six months. Determining whether information is sufficiently credible is also fact-specific. Examples of circumstances that might justify more than six months to investigate include physician self-referral law violations referred to the CMS Voluntary Self-Referral Disclosure Protocol (CMS SRDP), natural disasters, and states of emergency.

 

Applicable deadlines

A person who has received an overpayment must report and return it by the later of the following:

  • The date 60 days after the day the overpayment was identified
  • The date any corresponding cost report is due, if applicable

 

The 60-day time period begins either:

  • On the day reasonable diligence is c­ompleted and the overpayment is identified (including quantification)
  • If the person fails to conduct reasonable diligence, on the day the person received credible information of a potential overpayment

 

Absent extraordinary circumstances, in cases where there is credible information of a potential overpayment, the provider or supplier has up to eight months to report and return the overpayment (six months for timely investigation and two months [60 days] for reporting and returning). An example of credible information would be a Medicare contracto’?s determination of an overpayment, based on medical review.

An otherwise applicable deadline, however, will be suspended in any of the following circumstances:

  • OIG acknowledges receipt of an OIG Self-Disclosure Protocol (OIG SDP) submission, until settlement or the perso’?s withdrawal or removal from the OIG SDP
  • CMS acknowledges receipt of a CMS SRDP submission, until settlement or the perso’?s withdrawal or removal from the CMS SRDP
  • The person requests an extended repayment schedule, until the contractor rejects the request or the person fails to comply

 

Applicable reconciliation generally enables a person to identify funds to which the person is not entitled.

In the context of cost reporting, applicable reconciliation is the provide’?s year-end reconciliation of payments and costs to create the cost report. The cost report is due within five months of the end of the provide’?s fiscal year. Overpayments identified prior to submission of the cost report should be reflected in and returned at the time of filing. For example, overpayments as a result of periodic interim payments should be reported and returned at the time the initial cost report is due. 

Certain cost report overpayments cannot be identified until the Medicare contractor provides relevant information (e.g., payments in excess of certain caps, overpayments as a result of cost report outlier reconciliation, etc.). If a provider self-identifies an overpayment after submission and reconciliation of the initial cost report, the provider must report and return the overpayment within 60 days of identification. The applicable reporting process is to submit an amended cost report, along with the overpayment refund.

If the contractor identifies the overpayment during the cost report audit, it will determine the overpayment amount at the time of final cost settlement.

 

Six-year lookback period

Under the overpayments rule, an overpayment must be reported and returned if a person identifies the overpayment within six years of the date of its receipt. The otherwise applicable lookback period may be subject to certain limitations based on whether, and to what extent, the requirements of the rule and the ­underlying statute are retroactive.

The underlying statute (section 1128J[d] of the Social Security Act) is not retroactive. Therefore, failure to comply with its specific requirements prior to its effective date (March 23, 2010) is not a violation of the statute. Providers and suppliers, however, must report and return any overpayments not returned prior to March 23, 2010, in compliance with the statut’?s specific requirements, even if those overpayments were received prior to that date.

Similarly, the overpayments rule is not retroactive. Overpayments reported and returned prior to its effective date (March 14, 2016) are not expected to comply with the rule. For the time period from March 23, 2010, through March 13, 2016, however, providers and suppliers must make a good faith effort to comply with the specific requirements of the underlying statute, even if those overpayments were received prior to March 23, 2010. All providers and suppliers reporting or returning overpayments on or after March 14, 2016?including those received prior to March 14, 2016?must comply with the rule.

For example, Provider A receives an overpayment on March 22, 2010, which is identified, reported, and returned on March 10, 2016. In that case, the provider must make a good faith effort to comply with the specific requirements of the underlying statute.

Another example: Provider B receives an overpayment on March 22, 2010, which is identified, reported, and returned on March 15, 2016. In this case, the provider must comply with the specific requirements of the rule. 

 

Reporting options

CMS has indicated that the obligations of the overpayments rule are satisfied when a person follows the appropriate process to report and return the overpayment in good faith, including quantification. If a person calculates the overpayment amount using a statistical sampling methodology, the person must describe it in the report. Under the overpayments rule, providers and suppliers have a broad array of reporting processes from which to choose. These choices include certain existing processes and other processes that may be established in the future, including the following:

  • Voluntary refund process
    • This is generally only used when a refund is made by check and the overpayment was calculated using a sampling methodology
    • A person may also meet the rul’?s refund obligation by requesting a voluntary offset by the contractor
  • Claims adjustment and reversal process for Part A and B claims
    • For Part A claims, electronically processed through access to the FISS and recorded on the PS&R"
    • For Part B claims, paper-based
  • Credit balance report process
    • Hospitals must submit the Medicare Credit Balance Report (CMS-838) within 30 days of the close of each calendar quarter to disclose any credits to Medicare as a result of patient billing or claims processing errors
    • Any amounts due to Medicare must be repaid or claims adjusted at the time the report is filed
  • Disclosure under the OIG SDP or CMS SRDP resulting in a settlement agreement, using the process described in the respective protocol
  • Other reporting processes set forth by the applicable contractor to report overpayments; Medicare wants to reserve the right to modify existing or create new processes in the future

In addition to the options identified above, overpayments associated with cost reports generally should be reported through the existing cost report reconciliation process:

  • If identified prior to submission of the initial cost report, the overpayment should be reported and submitted along with the transmittal of the cost report
  • If identified in connection with cost-based reimbursement paid to a provider during a previous cost reporting period, the overpayment should be reported by reopening or amending the cost report and returned by submitting payment along with the amended or reopened cost report

 

One additional caveat: CMS agrees that where the contractor identifies a payment error by the contractor and notifies the provider or supplier that the contractor will adjust the claim""" to correct the error, the provider or suppler does not need to report and return the overpayment separately.

 

Edito’?s note

Kares is an expert on Medicare rules and regulations and is an instructor for HCPr’?s Medicare Boot Camp?Hospital Version®. She spent a number of years in private law practice, representing hospitals and other healthcare clients, then served as in-house legal counsel prior to her current legal/consulting practice. She is also an adjunct faculty member at the University of Phoenix, teaching courses in business and healthcare law and ethics.

 

Linking diagnoses and procedures to documentation in outpatient settings

by Lori-Lynne A. Webb, CPC, CCS-P, CCP, CHDA, COBGC, CDIP

In the outpatient setting, we have a different set of rules to follow in regard to the ICD-10-CM Official Guidelines for Coding and Reporting compared to those that follow the guidelines for inpatient care. The ICD-10-CM guidelines for outpatient coding are used by hospitals and providers for coding and reporting hospital-based outpatient services and provider-based office visits.

 

Following the guidelines

In addition, the terms "encounter" and "visit" can be used interchangeably. As a reminder, the guidelines for outpatient coding are different from inpatient coding because the term "principal diagnosis" is only applicable to inpatient services, as is coding diagnoses as probable, suspected, ruled out, and inconclusive.

For those who report outpatient or office-based services, instead of reporting a principal diagnosis, you would code the first-listed diagnosis, as well as signs and symptoms that are documented by the provider of care. In some cases, it may take more than one visit or encounter to arrive at and/or confirm a specific diagnosis. ICD-10-CM guidelines allow us to continue to report signs and symptoms over the course of the outpatient workup. The majority of the sign and symptom codes are found in Chapter 18 of ICD-10-CM; however, other sign and symptom codes can be found in many of the other sections and chapters of ICD-10-CM.

When assigning an ICD-10-CM diagnosis code for an outpatient or same-day surgery, it is appropriate to code the reason for the surgery as the first-listed diagnosis (i.e., reason for the encounter). When coding for an outpatient hospital observation stay, it is appropriate to code the current medical condition as the first-listed diagnosis (e.g., pregnant patient with decreased fetal movement).

In addition, it is appropriate to code for all additionally documented conditions. If the patient has chronic diseases noted, the chronic disease or disease status may be coded in addition to the primary reason the patient is seeking treatment, but only if the physician documents the chronic condition as impacting the current care or medical decision-making of the presenting problem or illness.

 

Dealing with documentation

Diagnosis codes are to be used and reported at the highest possible number of characters and specificity. However, sometimes all we have to go by is provider documentation of signs and symptoms. If the provider has not referenced a clinical significance to complaints or has only documented ill-defined symptoms, we have to code the documentation as a sign or symptom from the ICD-10-CM code set. It is the provider’s responsibility to clearly document a patient’s diagnosis.

Coders are not allowed to infer or code directly from an impression on diagnostic reports such as an x-ray, ultrasound, or pathology report. In the outpatient setting, the provider of care must confirm the diagnosis in the body of the patient’s visit note, procedure/operative note, or progress note.

For example, in the provider notes, the documentation states the patient has an "elevated blood pressure" of 160/90. As a coder, this does not mean the provider has diagnosed the patient with hypertension; it simply means the patient’s blood pressure is elevated today. However, if the provider notes that the patient has an elevated blood pressure of 160/90 today and will begin treatment for hypertension, the coder can code the ­specific hypertension diagnosis rather than the sign and symptom code of elevated blood pressure. If the coder does not have more specific information than "hypertension" written in the record, he or she should query the provider to get the most clarity possible, ensuring good clinical documentation and overall quality of medical care.

When assigning codes for an outpatient or ambulatory surgery case, code the diagnosis for which the surgery was performed. However, if the postoperative diagnosis is different than the preoperative diagnosis listed by the surgeon, code what is reported as the postoperative diagnosis. In reviewing or auditing an operative record, the surgeon should give both diagnoses. The rule of thumb is that the coder will code the diagnosis based on the postoperative notation or most definitive clinical documentation recorded in the patient’s medical chart.

When coding a diagnosis for ambulatory or same-day surgery, the urge to rely on the absolute information from a pathology report can be hard to resist. As coders, we have been trained to hold or delay submitting the insurance claim pending more information from a pathology report. Pathology reports contain great information on sizes, weights, measurements, cell types, malignancies, infections; they can house even more extensive clinical information than is normally reported in an operative/procedure record.

However, within the guidelines of coding, coders should not assign codes based on the pathology report unless the physician has confirmed the diagnosis within the operative, procedure, or progress notes. For example, if the physician notes within the documentation the removal of a "breast lesion/mass" and the pathology record documentation states "breast carcinoma," the coder should not code a breast carcinoma until the surgeon clarifies or adds the information from the pathology report to the operative and/or progress note.

Pathology reports can help us paint the picture of a patient’s status, but they can also be a hindrance. When coding for a lesion removal with CPT® codes, understanding how lesions are measured is vital to good documentation of the procedure. According to the CPT Manual, the measurements of the lesion need to include the size of the lesion itself and the margins for medical necessity prior to excision.

As part of good clinical documentation, the provider should document and include an accurate measurement of the lesion itself, and of the margins to be included. If the coder relies on only the pathology report, the sizing may not be accurate. Unfortunately, when excising specimens, it is common for the procured tissue to shrink or the specimen to be fragmented upon arriving at the pathology department. Measurement of the defect size post-excision may also be incorrect, as the excision site may expand once the tissue has been incised or excised. Either way, the result is incorrect documentation and coding.

The documentation bottom line is this:

  • Measurement of the lesion, plus the margins, should be made prior to the excision
  • Pathology reports should not be used in lieu of physician documentation
  • Query the physician regarding the size of the lesion, as well as the margins, excised if not clearly noted in the operative/procedure note

 

Using queries

Below is a generic lesion excision query form you can use to communicate to your provider the information you need to accurately code the encounter.

Excision of lesion(s) clarification

  • Patient name:
  • DOB:
  • DOS:
  • MR #:
  • Query date:
  • Requested by:

 

Documentation clarification is required to meet medical record documentation compliance, medical necessity, and accuracy of diagnosis and procedure coding.

In the medical record/operative procedure note, the following information is needed to assign the correct ICD-10-CM and CPT code(s). Please provide the following:

  • SIZE of the greatest clinical diameter in centimeters plus margins for each lesion excised
  • DEPTH of the tissue involved for each lesion (e.g., skin, fascia, muscle, or bone)
  • Type of CLOSURE for each lesion (e.g., simple, intermediate, or complex)

Please document and/or addend the patient’s operative/procedure record to include the requested information above. This information can be noted in the electronic medical record, or noted on this form in the area below. If you are using this form, please sign and date the attestation/addendum.

 

Following a checklist

The relationship between documentation and coding is intricate and often confusing. Every chart note, or piece of clinical documentation in the record, must stand on its own merit. If the record is audited, the coding should accurately reflect what was noted by the provider.

The documentation should always clearly reflect the following criteria:

  • Clinical evaluation and workup, including any pertinent history
  • Diagnostic and/or therapeutic treatment(s) carried out or ordered (e.g., lab tests, x-rays)
  • Continued plan of care or follow-up plans
  • Clinical diagnosis of disease, signs, and/or symptoms
  • Documentation of patient education provided in regard to the above

 

Electronic medical records for outpatient care and office-based services have also been instrumental in giving coders a clearer picture of the overall care and services provided to patients. Many electronic medical records allow the physician to choose the ICD-10-CM diagnosis code and include the additional supplies or procedures performed during the visit. If the provider documents a diagnosis for any performed procedures via an electronic record, the coder now has the additional role of auditing the patient record and the actual diagnosis codes chosen by the provider prior to billing the third-party insurance payers.

If upon review the coder (or auditor) sees the physician or provider has not chosen the most specific codes, the coder can easily review, clarify, and/or correct any errors quickly and easily prior to a claim being sent out. In addition, some payers have the capability to accept electronic copies of patients’ clinical documentation for their review or pre-authorization to expedite payment of services rendered.

Outpatient and office-based services are not always about illness. Wellness services, preventive care, pre- and postoperative care, and specialty-specific diagnosis care are all part of outpatient and office-based services. ICD-10-CM has accounted for these encounter types. If these encounters are well documented, they also need to be coded, billed, and incorporated into the claim. Many third-party payers are now providing coverage for payment of screening services.

The ICD-10-CM coding guidelines give clear instruction for how these types of services are to be reported. Again, it is the physician’s role to clearly state within the clinical documentation that the patient has presented for a wellness exam or a screening for specific illnesses or diagnoses (e.g., a pap test for cervical cancer, a colonoscopy to screen for colon cancer, lab tests for elevated blood sugar/diabetes). In these cases, the coding should reflect a clear diagnosis of screening. The screening diagnosis may be the only diagnosis assigned, as it may be the only reason for the patient visit.

It is becoming more common for physicians to follow and provide care for an established chronic problem while also screening for other issues during the encounter for that problem. If this is the case, the coder needs to audit and review the notes carefully to ensure the record clearly denotes what has been performed as follow-up care and what has been performed as screening (for either wellness or a suspected illness). If the record does not clearly show these as separately identifiable services, a physician query and/or addendum is in order.

Last but not least, always code what the record shows. If in doubt, query. Many coders rely on the old adage of "if it wasn’t documented, it wasn’t done." This type of coding should no longer be the rule of thumb or status quo. If a service or procedure appears in the clinical documentation but is poorly documented, good coders will find it well worth their time to investigate, confirm, have the record amended, and then code with accuracy. 

 

Editor’s note

Webb is an E/M and procedure-based coding, compliance, data charge entry, and HIPAA privacy specialist with more than 20 years of experience. Her coding specialty is OB/GYN office/hospitalist services, maternal fetal medicine, OB/GYN oncology, urology, and general surgical coding. She can be reached via email at [email protected] or http://lori-lynnescodingcoachblog.blogspot.com. Opinions expressed are that of the author and do not represent HCPro or ACDIS.

 

Overcome billing and coding challenges for comprehensive observation services

by Janet L. Blondo, LCSW-C, MSW, CMAC, ACM, CCM, C-ASWCM, ACSW

Billing correctly for observation hours is a challenge for many organizations. Getting it right requires knowing how to calculate observation hours for each patient, which is far from straightforward.

According to CMS, observation hours start accruing not when the patient comes into the hospital, but when the physician writes the order for observation. Observation hours end when all medically necessary services related to observation are complete. In some cases, this means that you can still bill for time spent completing the patient’s care after the physician writes the ­discharge order.

For example, a physician comes in to see the patient at 7:30 a.m. and writes the discharge order, which states discharge will occur pending the completion of tasks X, Y, and Z. The nursing staff finishes up those three tasks and the patient is finally ready to leave the hospital at 11 a.m. The hours between 7:30 a.m. and 11 a.m. are potentially billable observation hours because they were used to complete the patient’s medical care. Observation hours therefore end not with the discharge order, but with the completion of medical services.

In addition, because observation services are considered a temporary period to aid in decision-making, CMS states in the Medicare Benefit Policy Manual that only in rare and exceptional cases should observation services last more than 48 hours.

If a case reaches the 48-hour mark and the physician still hasn’t made a decision to discharge or admit the patient for inpatient care due to instability or risk of an adverse event if discharged, nor has any documentation made a compelling case for the need to continue observation, the services no longer meet the definition of observation care and the hospital should not bill for future hours. Hospitals should also not report observation hours after the physician has decided to send the patient home or to a lower level of care if the patient is receiving no active treatment and is just in a holding pattern until he or she moves to the next level of care or goes home.

 

Coding for comprehensive observation services

The 2016 OPPS final rule implemented changes for coding and billing for observation services. Among the changes made by CMS was the creation of a new comprehensive APC (C-APC) for comprehensive observation services.

Specifically, hospitals will now bill all qualifying extended assessment and management encounters, including observation services, through the newly created comprehensive observation services C-APC code 8011. A new status indicator, J2, was also created to specify that more than one service was provided.

CMS now requires hospitals to bundle services provided and previously billed separately?services such as level 3 ED visits, IV infusions, echocardiograms, speech therapy, and similar services. CMS pays a flat rate for the comprehensive observation services, which includes the bundled services.

Hospital staff should bill all hours of observation for a single encounter on one line under revenue code 0762. If the hospital provided observation care to a patient over multiple days, the date of service should be the date that observation care began. Although one rate is now paid for comprehensive observation services, HCPCS code G0378 is still used to bill observation services by the hour. When using this code, the organization should round to the nearest hour. For example, eight hours and 20 minutes in observation would round to eight hours, whereas nine hours and 40 minutes would round to 10 hours. If the hospital ­provided observation care to a patient over multiple days, the date of service should be the date that observation care began.

The second HCPCS level II code for observation is G0379. This code is used for a direct admission or referral for observation care from a physician in the community. Note that this code is not used if an ER physician or a physician from a provider-based department or clinic makes the referral. This code previously allowed hospitals to bill for costs associated with the visit, including registration and collecting clinical information about the patient, but costs are now bundled with the payment for the comprehensive observation services.

Claims that meet the following criteria will be paid under C-APC code 8011:

  • Claims that do not contain a procedure with HCPCS code with status indicator T (indicates a surgical procedure)
  • Must show eight or more hours of service under HCPCS code G0378
  • No other services on the claim must have a status indicator of J1

 

Services must be provided the day of or one day prior to the date of service for the following visit codes:

  • All ED visit levels, CPT codes 99281?99285 or HCPCS codes G0381?G0384 and critical care services CPT code 99291
  • HCPCS code G0463 (hospital outpatient clinic visit)
  • Same date of service for HCPCS code G0379 (referred by physician outside of hospital)

 

Hospitals can no longer bill separately for observation if these services are required after an outpatient surgical procedure. If a patient meets criteria for observation monitoring after the standar

HCPro.com – Briefings on APCs

2016 study guide error

This may seem a little late, but I was reviewing for the 2018 CCVTC with the 2016 version of the study guide (I bought it years ago with intent on taking test sooner). I noticed a mistake with the case regarding mitral valve reconstruction. The answer given for the question regarding CPT code selection clearly is incorrect. I was wondering if this was corrected in later editions and/or is this something I should pay attention to on the exam (as the authors of the exam wrote the study guide).

Medical Billing and Coding Forum

Credentialing & Peer Review Legal Insider, September 2016

Avoid HIPAA breaches from ransomware attacks

Although ransomware is not a new phenomenon, a recent increase in reported attacks along with several well-publicized cases have raised the public’s awareness of the threat it poses. Ransomware, a variety of malware, can be incredibly damaging because it is designed to infect a system, find and encrypt the system’s data, and lock out users until they pay a ransom–typically in an anonymous electronic currency like bitcoin–to regain access through a decryption key.

According to a U.S. government interagency report, there have been approximately 4,000 ransomware attacks each day since the beginning of the year, up from the 1,000 daily attacks reported last year. Further, a recent analysis by managed security services provider Solutionary found that 88% of ransomware attacks during the second quarter of this year targeted healthcare entities.

"Hospitals rely on data systems not only for the survival of their business, but the survival of their patients. Because of this, the perceived value of the data becomes much greater, meaning the criminals can charge premium ransoms against their victims," says Travis Smith, senior security research engineer at Tripwire, a Portland, Oregon-based cybersecurity firm.

The variants of ransomware that exist can complicate a hospital or other healthcare provider’s response, says Doron S. Goldstein, partner and co-head of privacy, data, and cybersecurity practice at Katten Muchin Rosenman, LLP, in New York City. In addition to the typical form of ransomware that infiltrates systems and locks users out of their data unless they make some form of payment, some types can also exfiltrate a copy of the locked data to the hacker, or delete the data but make it seem as though it’s encrypted and still present-tricking the user into paying for data that is actually gone.

"In each scenario, you don’t know if there is intention to release the data if you pay or not. You may pay and still get nothing. Or you may get it back. There is no certainty to it. Some victims have gotten access back; others have not," says Goldstein, a former software developer and network administrator. "The general guidance from law enforcement, such as the FBI, is not to pay ransom. But if everything you have is locked out, you may not feel like you have a choice."

HHS guidance

In light of the increased prevalence of ransomware threats, the U.S. Department of Health and Human Services (HHS) recently released guidance to help covered entities understand the risks associated with these types of attacks and how complying with HIPAA can help identify, prevent, and recover from ransomware.

"The HHS is just reacting to what is happening in the marketplace. The sustained increase in the number of successful ransomware attacks is proof that the ransomware problem is going to get worse before it gets better. Issuing guidance is raising awareness of the issue at hand," Smith says.

The HHS guidance states that healthcare entities can better protect against ransomware by implementing security measures required by the HIPAA Security Rule. According to the guidance, these measures include limiting access to electronic protected health information (PHI) to personnel and software that require it; and conducting risk analyses to identify threats and vulnerabilities to PHI.

"You have to do the risk analysis. Ransomware is just another form of malware; it’s particularly insidious, but they all require doing the risk analysis," says Goldstein.

A big takeaway from the HHS guidance is the importance of taking appropriate actions beforehand to mitigate the potential of damage caused by ransomware, he adds. Unlike malware that simply transfers PHI without authorization, ransomware makes the PHI unavailable or destroys it altogether.

"For a healthcare provider in particular, having data exfiltrated means there’s damage to the patients, but likely not to their immediate health. Being locked out of your health data or your patients’ health data is a potential threat to the life and health of patients," he says.

 

HIPAA breaches

The guidance provides clarification on whether a ransomware infection constitutes a HIPAA breach. A breach under HIPAA is any acquisition, access, use, or disclosure of PHI in a manner that is not permitted under the HIPAA Privacy Rule and that compromises the PHI’s security or privacy.

Prior to the release of the HHS guidance, instances of data exposure that revealed individuals’ PHI would be considered a HIPAA breach, says Justin Jett, director of compliance and auditing at Plixer International, a Kennebunk, Maine-based security analytics company. ­However, at that point, one could have made the argument that ransomware wouldn’t technically be considered a breach since it encrypts data rather than exposing it.

Now, according to the new guidance, if a ransomware infection encrypts electronic PHI that was not encrypted prior to the incident, a breach has occurred. The guidance reasons that the PHI has been "acquired" because hackers have taken control or possession of it. In these cases, the hospital must then undertake a risk analysis and, when applicable, comply with the breach notification requirements and notify individuals affected, HHS, and the media.

However, if the hospital had previously (prior to the ransomware attack) encrypted the PHI in a manner that would render it unusable, unreadable, or undecipherable to an unauthorized individual, there is a possibility the ransomware attack wouldn’t be considered a breach.

"I interpret this guidance as removing the loophole of ransomware not actually looking at the data. Since malware changes over time, it’s within the realm of possibility that ransomware will target [PHI] and exfiltrate the data once found. The new guidance states that if the ransomware is unable to actually see the protected healthcare information in cleartext (not encrypted), then it is not a reportable breach," Smith says.

Even in these cases, the guidance says additional analysis would be required to determine if the PHI was sufficiently encrypted prior to the attack. Goldstein says this emphasizes the need for a risk analysis whenever there is a security incident. He further noted that HHS may have included this guidance so covered entities could not view the ransomware’s own encryption of the data as protection against that data being compromised.

"In those cases, the data is technically encrypted by virtue of the ransomware, but it’s not encrypted by the covered entity; it’s encrypted by someone else who controls that encryption. It shouldn’t be viewed as encryption for the purposes of your risk analysis," Goldstein says."

 

Prevention and recovery

To better prevent ransomware, Jett says all staff should be appropriately trained on email and web security as most malware and ransomware comes from those sources. Additionally, companies should invest in heightened email security solutions, like anti-spam firewalls, which will help prevent the most obvious attacks from getting to employees’ inboxes.

The HHS guidance suggests that since HIPAA requires the workforces of covered entities to receive security training on detecting and reporting malware, employees can assist with early detection of ransomware by spotting indicators of an attack. These warning signs could include unusually high activity in a computer’s CPU as the ransomware encrypts and removes files, or an inability to access files that have been encrypted, deleted, or relocated.

Even if hospitals are vigilant, ransomware attacks may still occur. Again, the guidance suggests that HIPAA compliance may help hospitals recover from ransomware attacks due to HIPAA’s mandate for frequent backups of data.

Goldstein warns, however, that some variants of ransomware can lie dormant for a period of time in order to migrate across systems, including into data backups. Many hospitals and companies keep hot backups as part of their disaster recovery plan. These backups can be automatically or manually switched on if a system goes down. If ransomware has infiltrated a backup, the backup’s data could also become compromised and encrypted by the ransomware as soon as it’s activated.

"The important thing about dealing with the impact of ransomware is that it may require additional or different protections compared to what other malware requires to avoid or mitigate its ill effects," he says.

 

Recent ransomware attacks

All types of malicious software attacks are on the rise,but ransomware has recently received more high-profile media coverage, says Doron S. Goldstein, partner and co-head of privacy, data, and cybersecurity practice at Katten Muchin Rosenman, LLP, in New York City. "Ransomware has certainly gotten more coverage lately because of the potential damage, and the sophistication of some of these attacks has increased," he says.

The following are a few of the recent ransomware attacks that made headlines:

Hollywood Presbyterian Medical Center: In February, this Los Angeles hospital paid hackers the equivalent of $ 17,000 in bitcoins to regain access to its computer system, according to the Los Angeles Times. The malware prevented hospital staff from accessing their system for 10 days by encrypting its files; once the hospital paid the ransom, it was given a decryption key to unlock the files. In a statement, CEO Allen Stefanek said paying the ransom was the quickest way to restore the hospital’s systems.

Chino Valley Medical Center and Desert Valley Hospital: In March, hackers targeted these southern California hospitals by infiltrating their computer systems with ransomware. A spokesman for the two hospitals, which are part of Prime Healthcare Services, Inc., said technology specialists were able to limit the attacks so both hospitals remained operational, no data was compromised, and no ransom was paid.

MedStar Health: Also in March, this Columbia, Maryland-based system was targeted with ransomware that encrypted the system’s data. According to the Baltimore Sun, the hackers demanded that MedStar pay three bitcoins, worth approximately $ 1,250, to unlock a single computer, or 45 bitcoins, the equivalent of about $ 18,500, to unlock all of its computers. MedStar refused to pay the ransom, and staff at its 10 hospitals and more than 250 outpatient centers resorted to using paper records while system access was restored.

Kansas Heart Hospital: In May, hackers infected the network system of this Wichita hospital with ransomware. According to local CBS affiliate KWCH12, the hospital paid an undisclosed portion of the ransom demanded but the hackers refused to return full access and demanded a second payment. The hospital announced that it had refused to make the second payment and would work with its IT team and external security experts to restore access to the rest of the system.

 

Exciting updates: More content, tools, and news at your fingertips!

The challenges healthcare professionals tackle each day don’t wait for solutions, and neither should you. That’s why Credentialing & Peer Review Legal Insider (CPRLI) is transitioning to a more frequent and robust publishing model this fall by combining with the Credentialing Resource Center (CRC)’s flagship publication, Credentialing Resource Center Journal (CRCJ), to create a single source for all your credentialing, privileging, peer review, and legal news, tools, and best practice strategies.

Your updated member benefits gain you access to expanded content and tools on CRC–with new resources added weekly to the website (www.credentialingresourcecenter.com). Plus, as a CRC member you gain instant access to over 300 clinical privilege white papers, core privileging forms, Medical Staff Talk, and Credentialing Resource Center Daily (CRCD), CRC’s daily e-newsletter for medical staff leaders and MSPs. If you are already a CRC member, you will continue to receive the news and analysis you’ve come to rely on, plus expanded member benefits this fall.

To help readers keep tabs on available content, we will announce new articles in CRCD. At the end of each month, we’ll roll the corresponding weekly articles into a digital issue of the newly expanded 16-page CRCJ that mirrors the current digital format. As a member of CRC, you can continue to download and print high-quality PDFs of the current issue, as well as several years of back issues of CRCJ and CPRLI, directly from CRC’s website. We’re looking forward to delivering your peer review and credentialing guidance in a timelier, efficient, and more convenient manner.

Stay tuned for additional details as we near implementation. In the meantime, feel free to contact Editor Son Hoang at [email protected] with any questions.

 

Case summary

Maine supreme court upholds immunity for CVO questionnaire

The Supreme Judicial Court of Maine (the "Court") upheld a superior court’s ruling granting immunity to two physicians who provided negative comments regarding a third physician when they responded to a questionnaire from a credentials verification organization (CVO).

The decision stems from a dispute where Kevin F. Strong, MD, sought damages from Rebecca M. ­Brakeley, MD, and Jonathan M. Bausman, MD, alleging defamation and tortious interference with his business relationship with St. Mary’s Regional Medical Center in Lewiston, Maine.

In 2013, Strong applied for staff privileges at St. Mary’s, which reached out to its contracted CVO, Synernet, to collect, verify, and dispense Strong’s credentialing information. Synernet sent professional reference questionnaires to Brakeley and Bausman, who completed and returned them. Synernet forwarded the responses to St. Mary’s, which ultimately chose to deny staff privileges to Strong. Strong subsequently filed his complaint in the superior court against Brakeley and Bausman, claiming the denial was a result of negative comments in their questionnaires.

In court, Brakeley and Bausman argued that their statements were entitled to absolute immunity pursuant to Section 2511 of the Maine Health Security Act and filed a motion for summary judgment. The superior court granted the motion, and Strong appealed.

Strong made several arguments for why Brakeley and Bausman’s statements didn’t meet the criteria for immunity, but the Court rejected his interpretation of the statute.

In its decision to affirm the superior court’s summary judgment, the Court discussed the language of Section 2511 and its three subsections, which outline the circumstances when a physician is afforded immunity from civil liability, and why Strong’s interpretation was incorrect.

Central to Strong’s argument was Subsection 3 of the statute, which states that physicians "assisting the board, authority, or committee in carrying out any of its duties or functions provided by the law" are afforded immunity. Strong argued that Synernet was not a board, ­authority, or committee and therefore Brakeley and Bausman were not immune. However, the Court interpreted that subsection to include professional competence committees, which the Maine Health Security Act defines to include "[e]ntities and persons, including contractors, consultants, attorneys and staff, who assist in performing professional competence review activities."

Since St. Mary’s contracted with Synernet to collect, verify, and dispense credentialing information for its competence review process, the Court concluded Synernet qualified as a professional competence committee and therefore was a board, authority, or committee pursuant to the statute.

Strong also interpreted the language of Subsection 3 to mean that it only provided protection to a physician if he or she was a member of the board, authority, or committee. The Court found this interpretation illogical as it twisted the meaning of the subsection from protecting the acts of the physician providing assistance to instead protecting the committee receiving the assistance.

 

Source:

Strong v. Brakeley, Docket No. And-15-260 (Me. Apr. 21, 2016).

 

HCPro.com – Credentialing and Peer Review Legal Insider

PPO Offerings to Plummet on 2016 Exchanges




Health Leaders Media


Please add this newsletter to your Safe Sender list
View this email as a Web page | Manage Account

  November 11, 2015 Follow us on FacebookFollow us on TwitterJoin us on LinkedInRSS feed

PPO Offerings to Plummet on 2016 Exchanges

Rene Letourneau, Senior Editor for HealthLeaders Media

Because consumers are more sensitive to price than to provider choice, payers are dropping preferred provider option plans in big numbers. They find it is more financially advantageous to offer plans that are based on narrow networks. >>>

 

Editor’s Picks

Cost of Value-Based Plans? Less Transparency

Value-based health plans can cut costs, but not without some challenges for payers, such as getting employers to exercise "network discipline" and helping consumers fully understand their payment structure. >>>

Two-Midnight Rule Saga Lacks Happy Ending

Two of the country’s largest hospital associations are applauding recent changes to the two-midnight rule, but they say the Medicare payment regulation for short hospital stays remains a work in progress. >>>

Everybody’s Getting Smarter About Healthcare Value

A raft of new tools that rely on massive amounts of data are helping employers and their employees demystify the healthcare value equation. Even small employers and their employees are benefiting. >>>

‘Precision Delivery’ Goes Well Beyond Patient Experience

Don’t think of it as "talking a little differently or changing the layout of a space." Precision delivery is not that. "It’s about radically approaching the entire treatment pathway differently," says a healthcare innovation leader. >>>

HCAHPS: Making a Difference While There’s Still Time

Leaders must address organizational deficiencies before 2% of Medicare payments will be at risk in 2017. >>>

CA Providers Report Smooth Transition to ICD-10

The primary concern had been that providers would have multiple claims bounced back from insurers due to errors or unspecified codes. And while that’s happened to some degree, it hasn’t created widespread problems. >>>

Leveraging Resources Through Clinical Innovations

“What has emerged, more and more, are atypical relationships that aren’t focused on ownership; they’re focused on leveraging the strength of our partners,” says one senior executive. >>>

LIVE Webcast

Webcast: Integrating Behavioral Health—Decreasing Costs and Improving Care

Date: November 17, 2015, 1:00–2:00 p.m. ET
In this expert webcast, hear how Carolinas HealthCare System developed a strategy to optimize resources to create a truly integrated model.
Register Today >>>


News Headlines

Arbitrators side with UPMC; Highmark must pay $ 188 million for cancer care

TribLive, November 11, 2015

America’s pregnancy-care paradox: Paying ever more for the same bad results

The Atlantic, November 11, 2015

Unnecessary care at MA hospitals identified

MassLive, November 11, 2015

Health systems dipping into the business of selling insurance

Kaiser Health News, November 10, 2015

Scrutiny falls on failed Obamacare co-op

The Hill, November 10, 2015

Judge: Horizon must explain why it excluded NJ hospital from new plans

NJ.com, November 10, 2015

Universal healthcare amendment qualifies for 2016 CO ballot

Denver Business Journal, November 10, 2015

Person-centered healthcare focuses on patient as individual

PostBulletin.com / Associated Press, November 9, 2015

OHSU made risky $ 50 million loan to health insurer

The Register-Guard / Associated Press, November 9, 2015

White House challenges 20 cities on Obamacare

The Hill, November 9, 2015

Stay Connected to HealthLeaders

Don’t Miss the News You Want.

Spam filters exist for a reason, but not for the news you need. Make sure you aren’t missing your daily and/or weekly industry coverage. Add our address — [email protected] — to your address book or e-mail whitelist to keep the news you need in your inbox.

Is All of Your Leadership Team In The Know?

Our award-winning Daily News & Analysis e-newsletter can keep your leadership team abreast of relevant breaking news, and with in-depth industry coverage through 10 weekly e-newsletters that hit every pillar of healthcare, we’ve got your whole leadership team covered. Subscribe to any — or all — of our e-newsletters.

Multimedia/Events

HealthLeaders Media LIVE from Sharp Healthcare: The Pod ED

Date: December 16, 2015 | 11:00–2:00PM ET
In this live e-conference, discover how Sharp Healthcare has realigned its staffing structure to increase flexibility and teamwork, resulting in decreased patient wait times and a greatly enhanced patient experience.
Register Today >>>

From HealthLeaders Magazine

Rural Healthcare and the Challenge of Population Health

The issues facing rural providers are significant, but leaders are creating ways to survive in the changing healthcare environment. >>>

 

Leveraging Resources Through Clinical Affiliations

 

HCAHPS: Making a Difference While There’s Still Time

Sponsor this Newsletter

For advertising opportunities in this or other HealthLeaders Media email newsletters, please contact [email protected] or call 800.639.7477.

  MAGAZINE | NEWS | TERMS OF SERVICE | PRIVACY POLICY | ADVERTISE Follow us on FacebookFollow us on TwitterJoin us on LinkedInRSS feed

©2015 HealthLeaders Media

If you prefer not to receive this email newsletter, let us know.
HealthLeaders Media Health Plan Insider is a division of Fortis Business Media
HEALTHLEADERS MEDIA
100 Winners Circle, Brentwood, TN 37027
Serving the business information needs of healthcare executives and professionals.

 



HCPro.com – Health Plan Insider

2016 OPPS final rule introduces new modifiers and restructured APCs

Providers need to be aware of new modifiers added by CMS in the 2016 OPPS final rule, including a data collection and payment modifier that go into effect January 1, 2016.

Data collection modifier limited to one C-APC
Providers will only have to report a new data collection modifier when reporting related/adjunctive services associated with one comprehensive APC (C-APC), the stereotactic radiosurgery (SRS) C-APC, rather than all C-APCs, which is what CMS originally proposed. 
 
Because so many commenters expressed concerns and raised many operational and technical questions to CMS about using the new modifier to report related/adjunctive services for all C-APCs, CMS backed off its original proposal, says Jugna Shah, MPH, president and founder of Nimitt Consulting, based in Washington, D.C., and Spicer, Minnesota.
 
“This is really great news for two reasons,” says Shah. “First, it shows that CMS listens when providers speak, and particularly when they raise good operational points. Second, it will be easier for providers to operationalize the use of this modifier for the SRS C-APC, only rather than for all C-APCs.”
 
CMS will require modifier –CP (adjunctive service related to a procedure assigned to a C-APC procedure, but reported on a different claim) for adjunctive services related to SRS services described by the following codes but reported on a separate claim:
  • 77371, radiation treatment delivery, SRS, complete course of treatment cranial lesion(s) consisting of one session; multi-source Cobalt 60-based
  • 77372, radiation treatment delivery, SRS, complete course of treatment cranial lesion(s) consisting of one session; linear accelerator based
CMS expects the new modifier to be used with adjunctive services provided within 30 days prior to SRS treatment.
 
“It may be easier for providers to bill claims for these services for the entire month rather than trying to keep track of applying modifier –CP,” says Rinkle.
 
CMS explains what it means by related or adjunctive in the final rule by stating:
…services that are integral, ancillary, supportive, or dependent that are provided during the delivery of the comprehensive service. This includes the diagnostic procedures, laboratory tests and other diagnostic tests, and treatments that assist in the delivery of the primary procedure; visits and evaluations performed in association with the procedure; uncoded services and supplies used during the service; outpatient department services delivered by therapists as part of the comprehensive service; durable medical equipment as well as prosthetic and orthotic items and supplies when provided as part of the outpatient service; and any other components reported by HCPCS codes that are provided during the comprehensive service, except for mammography services and ambulance services…  
 
Examples of the types of questions commenters raised about reporting the new modifier, include:
  • Should facilities report adjunctive planning and preparation services when furnished in a setting outside of the hospital outpatient department?
  • Are adjunctive services limited to preoperative testing and planning services only?
  • Does the modifier apply to services performed by different physicians within a health system?
 
CMS did not answer these questions in the final rule, but instead indicated that it will address these and other issues in sub-regulatory guidance prior to January 1, 2016. 
 
The agency also noted in the final rule that it may consider its proposal to expand the use of this modifier to all C-APCs in the future.
 
CMS adds modifier –CT
As a result of the Protecting Access to Medicare Act of 2014, CMS is introducing modifier –CT (computed tomography services furnished using equipment that does not meet each of the attributes of the National Electrical Manufacturers Association [NEMA] XR-29-2013 standard) effective January 1, 2016.
 
Providers will need to append this modifier to a predetermined list of CPT®/HCPCS codes for CT scans when the services are furnished on equipment that does not adhere to NEMA standard XR-29-2013.
 
Those codes are:
  • 70450–70498
  • 71250–71275
  • 72125–72133
  • 72191–72194
  • 73200–73206
  • 73700–73706
  • 74150–74178
  • 74261–74263
  • 75571–75574
 
When these codes are reported with the modifier on a claim to be paid separately (i.e., not packaged into a composite APC or C-APC), CMS will impose a 5% payment reduction in 2016 and a 15% payment reduction beginning in 2017. This payment reduction applies under both the Medicare Physician Fee Schedule and the OPPS.
 
For more information on requirements for reporting modifier –CT, see CMS Transmittal 3402.
 
APC restructuring
CMS followed through with its proposal to restructure APCs for nine clinical families, with a few tweaks for specific services and procedures based on commenter suggestions.
 
“This may be the single largest restructuring of APC groups since the inception of OPPS,” says Shah. “And it’s likely just the beginning.”
 
CMS based the new groupings on the following:
  • Greater simplicity and improved understandability of the OPPS APC structure
  • Improved clinical homogeneity
  • Improved resource homogeneity
  • Reduced resource overlap in longstanding APCs
 
Following restructuring of ophthalmology and gynecology APCs in the 2015 OPPS final rule, CMS finalized restructuring in the following clinical families in the 2016 final rule:
  • Airway endoscopy procedures
  • Cardiovascular procedures and services
  • Diagnostic tests and related services
  • Eye surgery and other eye-related procedures
  • Gastrointestinal procedures
  • Gynecologic procedures and services
  • Incision and drainage and excision/biopsy procedures
  • Imaging-related procedures
  • Orthopedic procedures
 
For full details of changes to APCs relevant for your facility, see section III.D of the final rule.
 
Editor’s note: The 2016 OPPS final rule was published in the November 13 issue of the Federal Register. This article was originally published in Briefings on APCs. Email your questions to editor Steven Andrews at [email protected].
 
 

HCPro.com – JustCoding News: Outpatient

Accuracy is paramount for providers when reporting CMS’ new modifiers for 2016

Providers often struggle with modifiers–even those they’ve had available to report for many years–due to the unique scenarios they face at their facilities, staffing changes, and/or unclear or lacking authoritative guidance.

Starting January 1, 2016, CMS will require three new modifiers for providers to report. The good news is that it’s pretty clear when they must be reported, but the bad news is that it will take some time to determine the best way for each provider to operationalize them before the new year begins.
 
Modifier -CT
As a result of the Protecting Access to Medicare Act of 2014, CMS is introducing modifier -CT (computed tomography services furnished using equipment that does not meet each of the attributes of the National Electrical Manufacturers Association [NEMA] XR-29-2013 standard) effective January 1, 2016.
 
Providers will need to append this modifier to a predetermined list of CPT®/HCPCS codes for CT scans when the services are furnished on equipment that does not adhere to NEMA standard XR-29-2013. Those codes are:
  • 70450-70498
  • 71250-71275
  • 72125-72133
  • 72191-72194
  • 73200-73206
  • 73700-73706
  • 74150-74178
  • 74261-74263
  • 75571-75574
When these codes are reported with the modifier on a claim to be paid separately (i.e., not packaged into a composite APC or comprehensive APC [C-APC]), CMS will impose a 5% payment reduction in 2016 and a 15% payment reduction beginning in 2017. This payment reduction applies under both the Medicare Physician Fee Schedule (MPFS) and the OPPS.
 
The first step providers need to take is to talk with staff in the radiology department to determine whether the equipment in their facility is compliant with the NEMA standard. If the equipment is compliant, that’s great news, and those providers will not need to worry about using modifier -CT in 2016 and beyond, nor will they face any payment reductions for their CT services. If providers learn that some or all of their equipment is not compliant, then they should contact their vendors immediately to see if they can get compliant as soon as possible. If that’s not possible, then they will need to immediately determine how to operationalize reporting modifier -CT.
 
Providers need to know how many noncompliant machines they have and where they’re located. If a facility only has one noncompliant machine, then hardcoding modifier -CT with the related CPT codes may be the simplest solution until the machine is made compliant. If providers have multiple machines in the same or different locations and only some are compliant, then hardcoding may not be a good option.
Providers do not want to over-report modifier -CT and take a payment hit if it’s not necessary; similarly, they do not want to risk under-reporting modifier -CT since they could get overpaid.
 
Getting the reporting 100% correct is critical, since this modifier impacts both revenue and compliance. The key to getting the reporting correct is taking stock of equipment and internal processes. The best thing providers can do is get their machines or equipment NEMA compliant as soon as possible.
For more information on requirements for reporting modifier -CT, see CMS Transmittal 3402.
 
Modifier -CP
Modifier -CP (adjunctive service related to a procedure assigned to a C-APC procedure, but reported on a different claim), also effective January 1, 2016, is a data collection modifier.
 
The data collected by CMS in 2016 and 2017 is likely to inform future reimbursement for the stereotactic radiosurgery (SRS) C-APC, so accurate and consistent reporting across providers now will be important for future reimbursement. But it will not impact reimbursement in 2016, unlike modifier -CT, which will have payment implications starting January 1.
 
CMS will require modifier -CP when adjunctive services are reported on a separate claim for status indicator J1 stereotactic radiosurgery (SRS) services reported with the following codes:
  • 77371, radiation treatment delivery, SRS, complete course of treatment of cranial lesion(s) consisting of one session; multi-source Cobalt 60-based
  • 77372, radiation treatment delivery, SRS, complete course of treatment of cranial lesion(s) consisting of one session; linear accelerator-based
In the 2016 OPPS final rule, CMS says the modifier will be required when related or adjunctive services are provided up to 30 days before the SRS service and when provided on a different claim from the SRS.
While this is going to be operationally challenging and has already raised many questions, one thing providers can be grateful for and to consider a win is that CMS only finalized this modifier for use with related/adjunctive services for SRS and not for reporting related/adjunctive services for all C-APCs as originally proposed. Establishing the modifier only for SRS clearly shows that CMS heard commenter concerns about the operational difficulties with implementing it for all C-APCs.
 
Therefore, starting with requiring modifier -CP for only SRS allows CMS and providers to essentially pilot test this on a limited set of services, where the industry at least has an idea of many of the related/adjunctive services that could be billed on a separate claim.
 
Providers will again need to determine how best to operationalize the application of this modifier, which is likely going to involve individuals in many departments coming together to discuss the coding and billing processes in place today and the new ones that may be required in the future.
 
In the final rule, CMS unbundled the services shown by the list of codes below from the SRS C-APC payment rate, which means separate payment will be provided for these services when billed either on the same or separate claim from the SRS service in 2016 and 2017. Providers should ensure their chargemasters are updated for these codes:
  • CT localization (HCPCS codes 77011 and 77014)
  • MRI imaging (HCPCS codes 70551, 70552, and 70553)
  • Clinical treatment planning (HCPCS codes 77280, 77285, 77290, and 77295)
  • Physics consultation (HCPCS code 77336)
These codes are a good place for providers to start when trying to think about all of the different services patients would receive as a related or adjunctive service to SRS. Just keep in mind that there may be other services considered related or adjunctive to SRS provided 30 days prior on a different claim that would need to be reported with the modifier as well.
 
Operationalizing this modifier poses a unique challenge since it needs to be appended to services that are related to a service that hasn’t occurred yet (i.e., the SRS service). If providers don’t know that SRS has been ordered, scheduled, or is in the patient’s near future (within 30 days), then how will they know to append modifier -CP to services that occur days or weeks before SRS?
 
Providers should work with their radiation oncology department to determine how best to identify SRS patients and to monitor the services they are receiving over a period of time. One of the easiest ways, though not the most popular may be to hold claims until all services have been rendered so that one can definitively work through appending modifier -CP to all related services reported on separate claims.
There is no one-size-fits-all method to applying modifier -CP, so each provider will need to find the simplest, most accurate method to use this new modifier.
 
One thing providers can do right now is run reports to see what services have typically been reported 30 days prior to 77371 and 77372 for their SRS patients, and when they’ve been billed, in order to determine what services, in addition to the ones CMS has unbundled, might require the new modifier.
 
The danger with not reporting modifier -CP is that CMS will not have a sense of what costs from other services need to be built into the future SRS C-APC rate. CMS may simply use the data it has, while also eliminating separate payment for all of the services it has unbundled. The bottom line is that providers may see significant payment decreases in the future for SRS when only a single C-APC is assigned and separate payments for "related/adjunctive" services are eliminated if the C-APC is not reflective of all of the different types of related/adjunctive services provided to patients.
 
In the final rule, CMS says that it will issue further sub-regulatory guidance on using the modifier prior to January 1, 2016, to address commenters’ technical questions. Providers should be on the lookout for this information to ensure they begin reporting the new modifier properly when 2016 begins.
 
Modifier -PO
Providers are likely familiar with modifier -PO (services, procedures, and/or surgeries furnished at off-campus, provider-based outpatient departments) by now since its reporting has been voluntary throughout 2015 and becomes mandatory beginning January 1, 2016.
 
We’ve known about this modifier for some time, but many hoped it would remain voluntary for a longer period of time or go away altogether. No such luck.
 
Hopefully by now, providers have evaluated and catalogued all of their provider-based departments/settings to determine which are off-campus versus on-campus, as modifier -PO will be required to be reported on all OPPS-payable services provided in off-campus provider-based locations.
 
This includes packaged services, such as packaged labs, when provided in off-campus provider-based locations. Knowing whether to even worry about using this modifier and how many locations/sites to use it for is step one.
 
Step two is determining how to operationalize the use of this modifier. This modifier, like modifier -CP, does not have immediate payment implications, but it could in the future. Nevertheless, accurate and complete reporting is something the industry can expect CMS to monitor, especially in light of the budget bill Congress passed in November 2015. That bill restricts OPPS payments to off-campus provider-based locations starting in 2017 based on whether they were already designated as off-campus provider-based locations by November 1, 2015.
 
The inclusion of this provision in the budget bill came as a surprise to many given that it seemed CMS’ original plan was to collect data on what services are provided in on- versus off-campus provider-based departments and to examine payment difference among services in order to propose site-neutral payment policies in the future.
 
The budget bill seems to have sped up the process of clamping down on the overall issue of what CMS believes is overpaying certain types of services when rendered in provider-based departments versus free-standing sites. The issue of site neutrality and what was finalized in the budget bill are separate but clearly related items, as both are meant to address payment system differentials based on site/location.
 
By not allowing new off-campus provider-based locations to be paid under OPPS rates starting in 2017, Congress has drawn a hard line in the sand. But providers can likely expect to see the issue of site-neutral payments surface again once CMS has collected data on modifier ?PO and place of service codes 19 and 22 it introduced for physician reporting.
 
Based on what we know now, providers will still be required to report modifier -PO starting January 1, 2016, which means they need to determine the best way to operationalize this modifier. Hardcoding is again an option, and perhaps one that is easy to implement by using location codes and setting up the charge description master with duplicate lines for services provided in on- and off-campus locations. Another option is to use billing system edits or claims processing/editing logic to identify locations and have the modifier appended.
 
Providers should talk with their billing system vendors now to see if they can find a way to automate the use of modifier -PO, such as using location codes, since 100% of the services on the claims from off-campus provider-based locations will require the modifier.
 
A third option is to append the modifier manually, though this seems the least efficient method. However, it may be an option depending on the number of locations a provider has, system capabilities, and other considerations.
 
Like the other modifiers discussed, appending modifier -PO doesn’t have a one-size-fits-all solution. The best method will be determined by the number of off-campus locations, billing systems, volume, staffing, etc.
 
The most important factor to consider with any of these modifiers is the ease of application and accuracy. Providers want to streamline the process and automate as much as possible, but this must be balanced with accurate modifier use. Testing and internal auditing of these modifiers will be important to include in 2016 internal auditing plans.
 
Editor’s note: Shah is president and founder of Nimitt Consulting. This article was originally published in Briefings on APCs. Email your questions to editor Steven Andrews at [email protected].
 

HCPro.com – JustCoding News: Outpatient

Briefings on Coding Compliance Strategies, November 2016

Navigating the 2017 pressure ulcer coding changes in newly released guidelines

By Adrienne Commeree, CPC, CPMA, CCS, CEMC, CPIP

As if coders and clinical documentation improvement specialists aren’t under enough pressure as it is, the advent of the 2017 Official Guidelines for Coding and Reporting brings to the table new documentation requirements for pressure ulcer coding. The guidelines can be viewed here: www.cdc.gov/nchs/data/icd/10cmguidelines_2017_final.pdf.

Considering that these conditions impact length of stay, require additional monitoring and nursing care, and ultimately affect reimbursement for facilities, it’s no wonder coding for these conditions is under increased scrutiny. However, with a solid understanding of these types of ulcers, taking the time to read and understand the coding requirements can alleviate the "pressure" of ulcer codes.

 

New terminology

In April, the National Pressure Ulcer Advisory Panel (NPUAP) revised the pressure injury staging system, which can be found here: www.npuap.org/national-pressure-ulcer-advisory-panel-npuap-announces-a-change-in-terminology-from-pressure-ulcer-to-pressure-injury-and-updates-the-stages-of-pressure-injury. Since then, the NPUAP has received positive feedback regarding the system, and in August, The Joint Commission adopted the new terminology.

 

The definitions for each type of pressure injury are now:

  • Stage 1 pressure injury: Non-blanchable erythema of intact skin
  • Stage 2 pressure injury: Partial-thickness skin loss with exposed dermis

 

  • Stage 3 pressure injury: Full-thickness skin loss

 

  • Stage 4 pressure injury: Full-thickness skin and tissue loss

 

  • Unstageable pressure injury: Obscured full-thickness skin and tissue loss

 

  • Deep tissue pressure injury (DTPI): Persistent non-blanchable deep red, maroon, or purple discoloration

 

The new staging system identifies the stages of pressure ulcers as 1 through 4 as well as an unstageable ulcer. These are similar to the codes from the L89 category in ICD-10-CM, however, the system introduces new terms in an attempt to more accurately describe the stages and descriptions of such injuries.

The NPUAP no longer uses the term "pressure ulcer," and has replaced it with "pressure injury," since stage 1 and deep tissue injuries describe intact skin, not open ulcers. The system also introduced the new term DTPI with this update.

 

Incorporating these changes in ICD-10

CMS has been in discussion with the NPUAP to in-corporate the new terminology, however, these terms are not used in the 2017 ICD-10-CM/PCS code update. The incorporation of the pressure ulcer terminology will be directed by both CMS and The Joint Commission, and NPUAP is currently working to introduce the changes to the code definitions.

 

According to the NPUAP:

 

Some documentation requirements for pressure ulcer coding, such as using non-physician documentation for identifying pressure ulcer stages, hasn’t changed from 2016 to 2017. What has changed for 2017 is the requirements for coding the progression of stages.

For ulcers that were present on admission (POA) but healed at the time of discharge, assign the code for the site and stage of the pressure ulcer at the time of admission. Furthermore, if a patient is admitted with a pressure ulcer at one stage and it progresses to a higher stage, two separate codes should be assigned: one code for the site and stage of the ulcer on admission and a second code for the same ulcer site and the highest stage reported during the stay.

These new coding requirements differ greatly from 2016 guidance which required only the highest stage of the pressure ulcer to be reported for pressure ulcers that evolve into a higher stage during the admission.

These new requirements could have an impact on hospital-acquired condition (HAC) reporting, considering stage 3 and stage 4 pressure ulcers with POA indicators of either a N- No or U-Documentation is insufficient are considered to be HACs, and also are classified as major complications or comorbidities.

American Hospital Association Coding Clinic guidance from First Quarter 2009 stated that the National Quality Forum excludes progression of pressure ulcers that were present on admission as a serious reportable event (SRE), also called a "never event." The intent was not to penalize facilities for progression of a pressure ulcer that was POA, as these are difficult conditions and even with the best preventive measures in effect, ulcers may evolve to a higher degree. The revised guidance for 2017, which is necessitating that two codes be used to identify the different stages of a site, feels as if it’s changing the standpoint of whether the pressure ulcer evolution is now an SRE.

The latest Coding Clinic, Third Quarter 2016, has updated guidance for pressure injury terminology. They acknowledge the changes in definition by the NPUAP from pressure ulcer to injury and advise:

For a DTPI, there is an entry in the Alphabetic Index under "injury, deep tissue," with further guidance which states: "meaning pressure ulcer ? see ulcer, pressure, unstageable, by site." Therefore, per Coding Clinic, code a DTPI as an unstageable pressure ulcer by site.

 

What is in the future for coders?

Can coders expect to see changes in pressure ulcer terminology soon? The most recent Coding Clinic did not give a time frame for updates, thus the potential impact on hospital reimbursement is something we can only speculate on at this point. If a pressure ulcer evolves from a stage 1, 2, 3, or 4 during an inpatient admission, these ulcers could be identified as an HAC and therefore impact the diagnosis-related group.

 

Editor’s Note: 

Commeree is a coding regulatory specialist at HCPro, a division of BLR, in Middleton, Massachusetts. She has many years of experience in the healthcare industry involving coding, auditing, training, and compliance expertise. This article originally appeared on JustCoding, and opinions expressed are that of the author and do not represent HCPro or ACDIS. For questions, contact editor Amanda Tyler at [email protected].

 

A new sepsis definition: Finding coding compliance at a crossroads

This article is part two of a two-part series on the definition changes for sepsis. Reread part one in the October issue of BCCS.

 

In my October Clinically Speaking column, we discussed the evolution of the definition of sepsis and its implications in clinical care (Sepsis-1, Sepsis-2, and Sepsis-3), quality measurement (CMS’ SEP-1 core measure), and ICD-10-CM coding compliance.

We emphasized that the February 2016 definition of sepsis (Sepsis-3) as a "life-threatening organ dysfunction caused by a dysregulated host response to infection," differed from the terminology of sepsis and severe sepsis that has been embraced by many clinicians, CMS, and ICD-10-CM. We also discussed how provider documentation using the Sepsis-3 terminology eliminates the term "severe sepsis," and discussed that the definition change impacted ICD-10-CM code assignment and compliance.

Definitions and clinical indicators in Sepsis-2 are available at http://tinyurl.com/SepsisTwo, and definitions for Sepsis-3 are available at www.jamasepsis.com. CMS’ definition of sepsis and severe sepsis for the SEP-1 core measure is available at http://tinyurl.com/2017SEP1.

 

Coding Clinic update

Effective September 23, the American Hospital Association (AHA) Coding Clinic for ICD-10-CM/PCS published advice concerning the documentation and coding of sepsis in light of Sepsis-3. In Coding Clinic, Third Quarter 2016, p. 8, they stated "coders should never assign a code for sepsis based on clinical definition or criteria or clinical signs alone. Code assignment should be based strictly on physician documentation (regardless of the clinical criteria the physician used to arrive at that diagnosis)."

Coding Clinic went on to write (emphasis mine):

 

In my opinion, this means that Coding Clinic is saying ICD-10-CM still embraces the coding of infections without sepsis, with sepsis but without organ dysfunction, and with sepsis resulting in organ dysfunctions (otherwise known as severe sepsis), if the diagnosis is incorporated by the documenting physician. The AHA further stated that if a physician arrives at a diagnosis of sepsis or severe sepsis using whatever criteria he or she wishes, and then documents these terms in the medical record, the coder is to code it, period, end of story.

Alternatively, while Sepsis-3 states that the word "sepsis" requires the presence of acute organ dysfunction, Coding Clinic states that ICD-10-CM does not recognize this clinical concept. Unless the provider documents "severe sepsis" or associates an acute organ dysfunction to sepsis, a code reflecting this concept, R65.20 (severe sepsis), cannot be assigned. Furthermore, if a provider wishes to diagnose and document the term "sepsis" (without organ dysfunction) using Sepsis-2 or other reasonable criteria, the coder is obligated to code it as such in ICD-10-CM.

 

Coding Clinic, Fourth Quarter 2016

As we discussed last month, the fiscal year 2017 ICD-10-CM Official Guidelines were amended to state (emphasis mine):

 

In explaining this new guideline, Coding Clinic, Fourth Quarter 2016, pp. 147?149 stated (emphasis mine):

 

Coding Clinic went on to highlight that this concept applies only to coding, not the clinical validation that occurs prior to coding. Coding Clinic emphasized that clinical validation is a separate function from the coding process and the clinical skill embraced by CMS and cited in the AHIMA practice brief Clinical Validation: The Next Level of CDI. Access these at http://tinyurl.com/2016AHIMAclinicalvalidation and www.hcpro.com/content/327466.pdf.

 

Coding Clinic then went on to say that (emphasis mine) "a facility or a payer may require that a physician use a particular clinical definition or set of criteria when establishing a diagnosis, but that is a clinical issue outside the coding system."

While I agree that facilities should standardize clinical definitions for clinical and coding validation purposes, note how Coding Clinic gave tremendous power to a payer to define any clinical term any way they want to. This may differ from that of a duly-licensed physician charged with direct face-to-face patient care responsibilities using the definitions of clinical terms he or she learned in medical school or read in the literature.

As such, while our facilities may implement clinical validation prior to ICD-10-CM code assignment, a payer that is not licensed to practice medicine and has no responsibilities for direct patient care can require a provider or facility to use a completely different clinical definition that serves only one purpose in my mind, and that is to reduce or eliminate payment for care that was properly rendered, diagnosed, documented, and coded. I’m sure that legal battles will ensue, given this caveat written by Coding Clinic.

Solving the problem

In developing a sepsis strategy in light of these Coding Clinics, allow me to remind all of you that there are three environments by which we must consider disease terminology and supporting criteria. One cannot talk about sepsis, severe sepsis, or septic shock unless he or she states what environment they are in. These are:

  • Clinical language ? Physicians have a language that we use in direct patient care that communicates well with other physicians; we learned this language in medical school, in residency training, and in reading our literature. Every physician knows what "urosepsis," "unresponsiveness," and "neurotoxicity" is; however, ICD-10-CM does not recognize these terms for coding purposes, thus we ask physicians to use different words so that we can report them using the ICD-10-CM conventions. Systematized Nomenclature of Medicine — Clinical Terms (SNOMED-CT) is a clinical language we use in our problem lists and so is Sepsis-3. ICD-10-CM is not. Not all physicians embrace Sepsis-3, thus some may wish to label a patient as having sepsis even if they don’t have organ dysfunction, which makes clinical sense to them. See the articles listed above.
  • Coding language ? As discussed, Sepsis-3 amends clinical language only; however, for coding purposes we must still document using ICD-10-CM’s language, which still recognizes sepsis without and with organ dysfunction, bases coding on the individual physician’s criteria and documentation, and requires clinical validation using reasonable criteria prior to code assignment.
  • Core measure language ? Defining cohorts with core measures, such as SEP-1, is a clinical abstraction based on clinical criteria and not necessarily based on what a physician writes. For example, the definition of severe sepsis and septic shock is completely different in SEP-1 than that of Sepsis-3. Remember, however, that in 2017, if a physician documents severe sepsis and R65.20, and severe sepsis is coded, that record will be held accountable for the SEP-1 even if it doesn’t meet the SEP-1 criteria. View this regulation at http://tinyurl.com/jlau9ms.

Therefore, allow me to suggest the following strategy to ensure a balance of compliance with all three of these environments:

1.Standardize the definition and documentation of severe sepsis first. I believe that the Recovery Auditors (RA) are looking for records with sepsis codes that do not have R65.20 or R65.21 (septic shock) as a secondary diagnosis as to deny these codes and their resultant DRGs. In so doing, I believe that the definition of severe sepsis should be negotiated with and standardized by the medical staff, which could incorporate any or all of the following three criteria:

 

No matter what criteria is used, be sure to coordinate its development and deployment with your quality, clinical documentation integrity, and coding staff so that if a physician documents severe sepsis or septic shock, the SEP-1 algorithm can be implemented.

Also, be sure that physicians explicitly link organ dysfunctions to sepsis, or preferably, use the term "severe sepsis" so that R65.20 is not inadvertently missed by the coders. If a clinical documentation specialist or coder obtains a record supporting R65.20, be sure to notify the SEP-1 manager to determine if it qualifies for the SEP-1 core measure.

 

2.Develop a facilitywide definition for sepsis without organ dysfunction. As noted last month, many physicians do not believe that organ dysfunction is required to diagnose sepsis. Given that RAs are likely to use Sepsis-3 as a foundation for denying claims, we must have the statements of your internal medicine, critical care, and other physician committees as to what the definition of sepsis is for clinical and coding validation purposes. When it is documented by a provider without evidence of acute organ dysfunction, this statement can be used to rebut the RA’s denials. These will be handy if we are appealing beyond the first level.

3.Remind the RA that the ICD-10-CM guidelines are part of HIPAA and that coding is based on provider documentation. I’m sure that all of our contracts with private payers state that we will comply with federal laws, such as HIPAA. Given that the 2017 ICD-10-CM Official Guidelines state that we are to assign codes based on provider documentation, and not so much on what the RA thinks, and that Coding Clinic, First Quarter 2014, pp. 16?17, states that "the official guidelines are part of the HIPAA code set standards," we don’t want the RAs to violate HIPAA or our contracts with payers. This may require that our hospital attorneys or compliance officers weigh in, given that RAs have been known to deny codes based on provider documentation and want us to do the same.

 

Summary

Please recognize that this topic is very controversial and that the opinions expressed here are solely my own. I encourage all of us to discuss Sepsis-2, Sepsis-3, SEP-1, the 2017 Official ICD-10-CM Guidelines, and these Coding Clinics with our compliance officers and/or attorneys so that we can best support policies and procedures ensuring complete, precise, and compliant coding of sepsis in light of Sepsis-3. If you have success stories, please share them with me and the editor here at BCCS.

 

Editor’s note:

This article was part two of a two-part series. You can read part one in BCCS’ October issue. Dr. Kennedy is a general internist and certified coder, specializing in clinical effectiveness, medical informatics, and clinical documentation and coding improvement strategies. Contact him at 615-479-7021 or at [email protected]. Advice given is general. Readers should consult professional counsel for specific legal, ethical, clinical, or coding questions. For any other questions, contact editor Amanda Tyler at [email protected]. Opinions expressed are that of the author and do not necessarily represent HCPro, ACDIS, or any of its subsidiaries.

 

Has your CDI program shifted its focus for optimal PSI 15 performance?

by Shannon Newell, RHIA, CCS, and AHIMA-approved ICD-10-CM/PCS trainer

The recent adoption of a refined version of the Patient Safety Indicator (PSI) 90 composite by the Agency forHealthcare Research and Quality (AHRQ) has a significant impact on what discharges are included in PSI 15 (Unrecognized Abdominopelvic Accidental Puncture Laceration Rate).

Your clinical documentation improvement (CDI) program has likely focused on this measure due to the well-established challenges associated with accurate reporting of procedure-related accidental puncture/lacerations. Given the changes to PSI 15, should your CDI team shift its focus to promote and support accurate data integrity for this measure? Let’s take a look.

A fundamental understanding of patient safety indicator measures

Optimal data integrity for PSIs requires that we have the appropriate clinical documentation and reported ICD-10 codes to accurately reflect the following:

  • The numerator: The numerator for PSI 15, also called the "outcome of interest," reports the actual number of cases which experienced the accidental puncture/laceration.
  • The denominator: The denominator for PSI 15, also called the "cohort," establishes the population which is screened to identify the outcome of interest.
  • Risk adjustment: Denominator comorbidities, which have a statistically demonstrated impact on the likelihood of a patient incurring the patient safety event. The risk adjustment methodology establishes the expected number of discharges with the outcomes of interest.

 

The inputs above?numerator, denominator, risk adjustment?are used to calculate our observed over expected performance. CMS compares our performance to that reported by other hospitals, and our reimbursement may be then impacted if we do not appear to manage patients well.

For example, in the Hospital Acquired Condition Reduction program, if our performance for PSI 90 does not meet established thresholds, then our Medicare fee-for-service reimbursement is reduced by 1% the next CMS fiscal year (October 1?September 30) for every claim we submit.

 

The new PSI 15?what counts?

The revised measure specifications for PSI 15 have altered the numerator (outcome of interest). The denominator, or cohort?which represents the population at risk?has also undergone a noteworthy change).

The revised numerator and denominator greatly narrow the pool of discharges screened for accidental punctures or lacerations as well as those flagged with outcomes of interest.

From a CDI perspective, the likelihood of incorrectly reporting accidental puncture or laceration for the discharges included in the newly defined measure is greatly diminished.

 

PSI 15: Are you focused on risk adjustment?

Given that our performance for PSI 15 is assessed using our observed over expected rate of procedure related accidental puncture or lacerations, the CDI team’s focus may be better spent on strengthening the capture of comorbidities relevant to risk adjustment.

The AHRQ risk adjustment methodology looks for multiple comorbidities to calculate the predicted likelihood of accidental punctures/lacerations for each discharge.

The revision to the discharges included in the narrowed cohort has also impacted which comorbidities affect risk adjustment. This makes sense given that these comorbidities must be clinically relevant to the numerator and denominator. The number of comorbid categories has been reduced from 13 to 11. Some of the categories remain the same, some have been deleted, and new ones have been added.

 

Summary

Keeping abreast of revisions to claims-based measures is an expanded responsibility for today’s CDI program. These measures impact both reimbursement and quality profiles. Positioned with this information, the CDI program can then shift efforts to promote and support clinical documentation capture and accurate reporting of codes associated with areas of the greatest vulnerability and impact.

 

 

Editor’s note:

Newell is the director of CDI quality initiatives for Enjoin. She has extensive operational and consulting expertise in coding and clinical documentation improvement, performance improvement, case management, and health information management. You can reach Newell at (704) 931-8537 or [email protected]. Opinions expressed are that of the author and do not represent HCPro or ACDIS.

 

New clinical criteria definitions in 2017 Official Guidelines up the ante for coders

by Laura Legg, RHIT, CCS, CDIP, and AHIMA-approved ICD-10-CM/PCS trainer

The new guideline for code assignment and clinical criteria in the 2017 ICD-10-CM Official Guidelines for Coding and Reporting does not mean clinical documentation improvement is going away; instead it just upped the ante for continued improvement.

Up the ante means to increase the costs, risks, or considerations involved in taking an action or reaching a conclusion. With the new coding guideline for clinical validation that went into effect October 1, the stakes remain high for the diagnoses documented by the physician to be clearly and consistently demonstrated in the clinical documentation.

It is not that the information was not there before, but now the issue is finally getting attention. When clinical documentation is absent, coders are instructed to query the provider for clarification that the condition was present. But what are we to do if the clinical indicators are not clearly documented? For HIM professionals who deal with payer denials, this has been a haunting issue for a very long time.

The ICD-10-CM Official Guidelines for Coding and Reporting are the foundation from which coders assign codes. Coders need to review the new guidelines in detail to understand the changes and implications for their facilities.

The Centers for Disease Control and Prevention published these new guidelines which can be read in their entirety here: www.cdc.gov/nchs/data/icd/10cmguidelines_2017_final.pdf.

 

Taking a closer look

The coding guideline for section A.19 (code assignment and clinical criteria) has been labeled as controversial and, at this point, we have more questions than answers. Denials issued by payers due to the absence, or perceived absence, of clinical indicators by which the payer lowers the DRG is now being called DRG downgrading and it’s getting attention.

The code assignment and clinical criteria states:

 

Physicians and other providers document a patient’s condition based on past experience and what the clinician learned in medical school, which often differs from clinician to clinician. When you put a patient in front of a group of clinicians you will most likely get differing documentation. So how do we fix that?

The diagnosis of sepsis is a good example. There does not appear to be a universally accepted and consistently applied definition for the condition of sepsis.

In a patient record with the principal diagnosis code of sepsis, followed by the code for the localized infection, pneumonia, a payer denial could occur.

Payer denials often deny the sepsis diagnosis code stating that "the diagnosis of sepsis was not supported by the clinical evidence. Therefore, as a result of this review, the diagnosis code A41.9 [sepsis, unspecified organism] has been removed and the principal diagnosis re-sequenced to code J18.9 [pneumonia, unspecified organism] for pneumonia and to the lower paying DRG 193." This is now being referred to as a DRG downgrade. DRG downgrades can occur for different reasons including both DRG coding changes and clinical validation downgrades.

 

What is a coder to do?

What is a coder to do when a physician documents a diagnosis that may not be supported by the clinical circumstances reflected in the patient’s chart? Facilities and coding teams should develop guidance and be sure they fully understand the content and the impact of this coding guideline to coding practices.

Remember the section that reads: "the assignment of a diagnosis code is based on the provider’s diagnostic statement that the condition exists. The provider’s statement that the patient has a particular condition is sufficient."

This represents a catch-22. If the diagnosis is not clinically validated, both recovery auditors (RA), as well as commercial insurance auditors, are going to deny the claim. On the other hand, if coders or the facility decide not to report the diagnosis, they are in violation of the coding guidelines, which is also a major problem.

AHIMA’s 2016 Clinical Documentation Toolkit offers this advice:

The toolkit is available here: http://bok.ahima.org/PdfView?oid=301829.

 

Increasing clinical documentation

As the healthcare industry experiences an increased number of external audits, both federal and private, the need to up the ante on clinical documentation has become essential. The answer is not to let this guidance prompt lazy documentation, which has far reaching consequences, but to use it as a catalyst for improvement.

The goal of any clinical documentation improvement (CDI) program is to ensure a complete and accurate patient record, and this cannot be done without the presence of documentation supporting the clinical indicators and clear and consistent documentation regarding the condition. The provider’s documentation of their full thought process will accomplish this. If medical staff can come together and agree upon a definition for a certain condition, they can begin the process of being consistent with how the description is presented in the patient record.

CDI specialists and coders should not use the new guideline as an excuse not to query. Coders are not clinicians and, therefore, should not be expected to evaluate clinical criteria. Coding and CDI were separate functions, but, as audits from outside organizations expand, there is more emphasis on correct coding, DRG assignment, and the use of clinical criteria to support the reported codes, which means these entities need to work together.

The American Hospital Association’s Coding Clinic for ICD-10 instructs coders not to use background clinical information contained in their responses for code assignment. This information is only provided so the coders can make a judgment to query where there is incomplete documentation. Coders and CDI staff should review all chart documentation and data, and query when necessary to clarify inconsistencies in physician documentation.

Query the provi

HCPro.com – Briefings on Coding Compliance Strategies