NOTE: All in-article links open in a new tab.

Updated Guidelines for Achieving a Compliant Query Practice

Published on 

Tuesday, April 16, 2019

 | Coding 

The kicker to the saying that “time flies when you’re having fun,” is that time also flies when you are not. However, I have been extremely fortunate over the past 10 years to actually enjoy my job. Last October marked my 10-year anniversary as an employee of Medical Management Plus, Inc. (MMP). Yes, it is nerdy that I actually enjoy reading Medicare regulations, but I do. I enjoy even more writing articles, such as this one, which I hope share Medicare and related guidance in an easy-to-read and understandable format and help our readers do their own challenging healthcare jobs better. The rapid passing of time is relevant because the very first article I wrote at MMP over ten years ago was about the 2008 AHIMA (American Health Information Management Association) article, “Managing an Effective Query Process.”

In February of this year, the Association of Clinical Documentation Improvement Specialists (ACDIS) and the American Health Information Management Association (AHIMA) jointly produced “Guidelines for Achieving a Compliant Query Practice (2019 Update).”  This Practice Brief is the recommended industry standard for provider queries and describes best practices for coding and clinical documentation improvement (CDI) professionals performing query functions. It supersedes the 2016 and all prior versions.

Coders and CDI professionals should carefully review and follow the practices described in this Brief, but other healthcare team members also need to be aware of this guidance. For example, case management, quality management professionals, and infection control clinicians educate physicians to document a certain way. Since these interactions could ultimately affect coding, these healthcare professionals need to be aware of and comply with query compliance standards. Other healthcare professionals, such as compliance, revenue cycle, patient financial services, physician groups, facility leaders, and any who work with documentation and coding also need to be familiar with this guidance. The Brief also points out that it serves as a resource for external reviewers, such as the Office of Inspector General (OIG), government contractors, payor review agencies, and others.

According to the Brief, a query is a communication tool “used to clarify documentation in the health record for documentation integrity and accurate code assignment.” In addition to ensuring a medical record that accurately reflects patient complexity and the facts of the encounter, an effective query process ensures appropriate reimbursement and accurate risk-adjustment and quality of care statistics derived from claims data.

The Practice Brief states, “The objective of a query is to ensure the reported diagnoses and procedures derived from the health record documentation accurately reflect the patient’s episode of care.” Among other functions, some of the main uses of queries are to:

  • Determine if a clinical condition is present when supported by clinical indicators within the record,
  • Clarify conflicting documentation,
  • Add specificity in certain situations,
  • Establish “cause and effect” relationships, and
  • Clarify when a documented diagnosis does not appear to be clinically supported.

I am not going to list all of the requirements of a compliant query and encourage those affected to read the entire Practice Brief for all the guidance provided. Here are some of the main points from the Brief that caught my attention.

Leading Queries

Bearing in mind that my background is compliance, I will start with the rule that queries should not be leading – they should not “lead” the physician or other practitioner to the preferred answer or to a specific diagnosis or procedure. Multiple choice queries are acceptable, but be sure to include options that allow the provider to explain other clinical options or to reply that the answer may be clinically undetermined. In the words of the Brief, “the choices provided as part of the query must reflect reasonable conclusions specific to the clinical scenario of the individual patient.”

Impact on Reimbursement

At one time, reimbursement seemed to be the major driver of the query process. This should not be – querying is about obtaining accurate documentation and coding, which often can affect a facility’s payment. However, keep your focus on accuracy and completeness and never include the impact on reimbursement or on quality measures in the query. It is best not to even discuss the effects of querying on reimbursement or quality measures with your physicians or others. If your records are accurate and complete, your facility will receive the appropriate reimbursement and accurate quality measures.

Specificity

Queries can be helpful for determining a more specific code in some situations. However, bear in mind “that code accuracy is not the same as code specificity.” Although some payors resist unspecified codes, there are times when unspecified codes are appropriate based on the clinical situation.

Clinical Indicators

When querying for documentation of medical diagnoses or conditions that are clinically evident, be sure to include clinical indicators that:

  • “Are specific to the patient and episode of care
  • Support why a more complete or accurate diagnosis or procedure is sought
  • Support why a diagnosis requires additional clinical support to be reportable”

Clinical indicators can be such things as the physical exam and assessment, diagnostic findings, and treatments. Clinical indicators should be relevant and clearly support the clinical condition. More is not always better, as the Brief states, “The quality of clinical indicators—how well they relate to the condition being clarified—is more important than the quantity of clinical indicators.”

Patient History and Prior Encounters

Coding from prior encounters without documentation in the current record is not allowed, but generating a query based on information from a prior encounter may be acceptable, but only if the information is clinically pertinent to the current encounter. The Brief includes a list of example situations where information from a prior encounter could be used to query, such as specificity, baseline status, present on admission (POA) status, cause and effect, and etiology. The Brief cautions that “it is inappropriate to “mine” a previous encounter’s documentation to generate queries not related to the current encounter.”

Documentation and Retention of Queries

Sometimes it is easier to explain a situation to a provider in person. Verbal queries are acceptable, but the exchange, including the provider’s response, should be documented and maintained. And like written queries, conversations should not be leading. When documenting these interactions, be sure to include the same components you would include in a written query – the details of the discussion, the reason for the query, the clinical indicators, options discussed and the provider’s decision. Also, date, time, and sign your documentation.

It is recommended the query be part of the permanent medical record. Another option is to keep queries as part of the business record. They should be easily retrievable for auditing, monitoring, and compliance. Facilities should have a policy that addresses query retention and it should apply to all queries, regardless of provider response.

Clinical Validation and Escalation

Sometimes it may appear that a documented diagnosis is not clinically supported. These clinical validation queries can be more challenging than other types of queries. AHIMA has developed a separate Practice Brief to address these concerns titled “Clinical Validation: The Next Level of CDI.” AHIMA members can view this Brief in the AHIMA HIM Body of Knowledge at http://bok.ahima.org.  

Clinical validation may be a good time to involve a physician advisor or the chief medical officer. Facilities should have a documented escalation policy for certain situations, which may include clinical validation situations, failure to respond, or other issues. There should also be policies defining the role and expectations of those issuing the queries and the responders.

Again, this is a high-level overview of the Practice Brief on Compliant Queries. The Brief contains much more information, including query examples in Appendix B, which I found to be particularly enlightening. Be sure to read the entire Brief carefully – study it, discuss it with other stakeholders within your facility, and use it to develop your policies, procedures and practices. Be sure to include initial training for new employees and on-going education for all employees. Also, watch for updated guidance - I will not promise to be around in another 10 years to share the information.

Article Author: Debbie Rubio, BS MT (ASCP)
Debbie Rubio, BS MT (ASCP), was the Manager of Regulatory Affairs and Compliance at Medical Management Plus, Inc. Debbie has over twenty-seven years of experience in healthcare including nine years as the Clinical Compliance Coordinator at a large multi-facility health system. In her current position, Debbie monitors, interprets and communicates current and upcoming regulatory and compliance issues as they relate to specific entities concerning Medicare and other payers.

This material was compiled to share information.  MMP, Inc. is not offering legal advice. Every reasonable effort has been taken to ensure the information is accurate and useful.