Open Quality MCP server

Open Quality

An open corpus of healthcare quality measures, and a shared record of what implementers have learned about each one. Founder-stewarded today, with a written commitment to community governance as it grows; see GOVERNANCE and VISION.

Publish a measure in CQL, SQL, or SQL-on-FHIR. Everything is validated, versioned, and open for review. Alongside the measures sits the part that usually gets lost: a typed record of interpretation questions, defects, and test cases, attached to the measure and pinned to a version.

Site: https://openquality.us

Why this exists

Quality measurement is rebuilt from scratch inside every organization that does it. Payers, health systems, and vendors each staff teams to implement the same national measures against their own data, then pay auditors to certify the result. The same ambiguities in the same specifications get rediscovered independently, the code is rarely shared, and what one team learns about a measure rarely reaches the next.

There is no common unit for exchanging measure logic, and no shared place to record what the community has figured out. Open Quality is an attempt at both: a package format anyone can publish, and a knowledge corpus anyone can read.

The goal is an open marketplace for measure logic. Somewhere to find a measure, see what other implementers already learned about it, and take the artifacts, without a vendor contract, a licensing negotiation, or knowing the right person to ask. Today a researcher or a small team has none of those things, and pays for access or goes without.

Browsing and downloading work now, through the library, a machine-readable catalogue, and git. Publishing still goes through a pull request. See Status.

Who this is for

Today, getting an answer about a measure depends on knowing the right person.

A recent example. A PhD candidate wrote a Hospital at Home eligibility library that ran at 30 to 40 seconds per patient. He could not tell whether the cause was his logic, his engine, or his data. Someone made an introduction to an engineer who had spent years optimizing CQL. That engineer explained it in one email: defines cache, functions do not, every retrieve iterates the whole bundle. The library now runs in under a second, and returns the same results.

That answer existed because of one introduction. It is not searchable, it is not attached to a measure, and the next person will not find it.

Most people doing this work are not on Zulip, do not attend connectathons, hold no NCQA support contract, and do not work at an insurer with a staff of analysts. As quality measurement moves from manual abstraction to digital, they need somewhere to go that does not depend on who they happen to know.

This is early and honest about it. The package format and the validation core work; the hosted registry does not exist yet. See Status.

How this fits the ecosystem

Open Quality is not another measure engine and not a competitor to the tools people already rely on. It is the open corpus and community layer that sits alongside them.

Shortened. The full README is on GitHub.