When a practitioner documents a diagnosis that does not appear to be supported by the clinical indicators in the health record, a coder has four choices: (1) Code the diagnosis; (2) Ignore the diagnosis; (3) Generate a query to confirm clinical validation of a diagnosis; (4) Follow the facility’s escalation policy for clinical validation.
read more
All queries require at least two elements – clinical indicators and a query question. Coders can also include multiple choice options for response or leave the query open-ended for a free text response. The order in which these elements are listed in a query is open to coder or facility preference.
read more
The key to choosing reasonable options for a query response is to remember that the query must stand alone. Any clinical indicators supporting the options must be included in the query itself. In this week’s Query Tip, we provide examples of two queries in which the options for response are not reasonable based on clinical indicators used by coder.
read more
One way to shorten a lengthy query is by avoiding repetition in the supporting documentation. Does the same diagnosis really need to be mentioned multiple times in the clinical indicators? Is it necessary to list the results of a chest x-ray twice? Does listing the same documentation multiple times give further specification or explanation to the query?
read more
A query question that is directive in nature, indicating what the provider should document, rather than asking for his/her professional determination of clinical facts, constitutes a leading query. The provider should not be made to feel obligated to document anything.
read more
Tissue findings interpreted by a pathologist are not equivalent to the attending physician’s medical diagnosis based on the patient’s clinical condition. If the attending physician has not indicated the significance of an abnormal finding within a pathology report…
read more
Conflicting documentation occurs when health care providers call the same condition different things. When none of the documented conditions are clearly ruled out by the physician, coders may find it necessary to query for the most appropriate diagnosis.
read more
Queries in a Yes/No format are limited to use in the four specific circumstances. This format may not be used when only clinical indicators of a condition are present, but the diagnosis has not been documented in the health record.
read more When a practitioner documents a diagnosis that does not appear to be supported by the clinical indicators in the health record, a coder has four choices: (1) Code the diagnosis; (2) Ignore the diagnosis; (3) Generate a query to confirm clinical validation of a diagnosis; (4) Follow the facility’s escalation policy for clinical validation.
All queries require at least two elements – clinical indicators and a query question. Coders can also include multiple choice options for response or leave the query open-ended for a free text response. The order in which these elements are listed in a query is open to coder or facility preference.
The key to choosing reasonable options for a query response is to remember that the query must stand alone. Any clinical indicators supporting the options must be included in the query itself. In this week’s Query Tip, we provide examples of two queries in which the options for response are not reasonable based on clinical indicators used by coder.
One way to shorten a lengthy query is by avoiding repetition in the supporting documentation. Does the same diagnosis really need to be mentioned multiple times in the clinical indicators? Is it necessary to list the results of a chest x-ray twice? Does listing the same documentation multiple times give further specification or explanation to the query?
A query question that is directive in nature, indicating what the provider should document, rather than asking for his/her professional determination of clinical facts, constitutes a leading query. The provider should not be made to feel obligated to document anything.