Patient Query

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Revision as of 15:14, 4 June 2015 by Cynthia.Gerson (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Webcast Overview

Let Galen's expert EHR Consultants help you with: MU Stage 2 reporting requirements with Patient Query. We will cover how to Manage Queries, build queries using the Clinical Rules Editor as well as creating or editing Patient Action Sets within the Patient Query workspace in TouchWorks EHR.


Q: I have heard that the transition to V11.4 will include a configuration step to rebuild our queries. Do you know if this is true?

A: Yes, this is correct. Your diagnosis that was used in V11.2 was based on pulling ICD-9 terms. We must now base these queries on ICD-10 IMO terms to correctly query your database once you are on V11.4. There are a few places where this type of configuration must take place. For example, all Assessment forms that are built using ICD-9 terms must now be rebuilt using IMO terms.

Q: Is there a way to create a list of patients that have been prescribed a medication that has been recalled?

A: Most recalls from the FDA need immediate attention, namely those that are Class I drugs that would entail setting up a simple query based on prescription data alone. This would return any patient, seen by any provider and will return a list of patients that you can notify easily. Including their phone number in the query results and assigning this list to a nurse to follow up with these patients, would be very efficient. The medication detail in the clinical rules editor even will let you further the criteria down to the strength to further define the drug you are looking for.

Q: Is there a limit of providers that you can include in your queries, i.e appts under a number of providers?

A: No, there is not a limit to this particular category.

Q: Under Patient Action Sets and Patient Lists, does the "Add to Existing" setting create duplicate patients on the list?

A: No, it should not create duplicate entries to the pursuit lists – Allscripts has implemented logic to prevent that from happening. There is a chance, however, that a patients falls into multiple pursuit lists with multiple reminders and could therefore receive multiple calls, mailed letters, or portal documents.

Q: If we end up with a 3rd party vendor for our Patient Portal does it do any good to even build the Patient Reminder Letters into Patient Query?

A: This really depends on your Patient Portal solution, but in general, the Portal Patient Reminder Letter is not mandatory for the Patient Reminder MU2 Core #12 measure.

Q: Is there any logic as to how the queries are setup i.e. order of criteria, sub groups, include, exclude?

A: Yes, it is important to consider how you are building the criteria for your queries. It is good to be aware that you have the option to choose the and/or option as to how each piece of query criteria relates to the other and of course the include/exclude logic for each query criteria will play a big role in what results you see when running the query itself. Many times this takes trial and error with comparing the actual results (patients included) with the desired results of your query, while also being aware of known issues that could have an affect on those results as well.


View/download powerpoint slides here Presented 2/14/2014

Additional Information

See also Population Health Management