"... the cycle time [for quality measure development] could go from years to days"Whoa, Nelly. Days?
From a technical perspective, I'd say months, but it is still a dramatic improvement. What Query Health will do is enable providers to access their data to measure performance quite easily. But delivering a quality measure is much more than being able to access the data and computing a score. Query Health may deliver vast improvements there, but it still won't address the non-IT issues.
One of the major challenges in Quality Measurement is in how to deal with "exceptions" and "exclusions". Exclusions are cases where the measure doesn't apply to a situation where it might otherwise be relevant (e.g., patients with certain types of conditions that don't really fit into the measure criteria). Exceptions are cases where even though everything else fits, there is a good reason not to count that situation as being detrimental to quality (e.g., patient refused treatment) because it is not something that the provider can control.
The collection of situations which may need to be excluded varies depending on the measure. And to be able to apply these to the measure means that providers will likely need to change their workflow to capture the reason why the measure may not apply. To compute the measure means that the data has to be there.
You can still compute the measure without exception or exclusion data. It just results in a different value. Failures to accurately capture the necessary data won't neccessarily be apparent in the computed result. This isn't really a technical problem. Give the computer the data, and it can compute the result. Give it inaccurate data, and it will compute an innacurate result. Query Health doesn't have any special protections against GIGO.
When you implement a measure, you need to avoid GIGO. Doing so may require changes in workflow to capture the neccesary information. Changes in workflow don't happen in days, and that is why I say months.
The Clinical Quality Measure workgroup is looking at improving the overall process for measure development. Exceptions and exclusions are a critical part of that process, because of the challenges they provide for implementation. I don't think the solution here is a technical one. Query Health will help, but it isn't a silver bullet.