Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Clinical Quality Language (CQL) #6966

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

antvaset
Copy link

Adding support for the Clinical Quality Language, a high-level language used in health IT with the focus on clinical quality measures and clinical decision support.

Checklist:

@antvaset antvaset requested a review from a team as a code owner July 24, 2024 02:14
@antvaset antvaset marked this pull request as draft July 24, 2024 02:23
@antvaset antvaset force-pushed the add-clinical-quality-language branch from e72dbd0 to 5832774 Compare July 24, 2024 02:33
@antvaset antvaset marked this pull request as ready for review July 24, 2024 02:33
@antvaset
Copy link
Author

Hi @lildude, thank you for having a look at this! Just wanted to highlight that CQL is used on GitHub by folks like Google (1, 2), IBM (3), WHO (4), and CMS (5). It's an HL7 and ANSI normative standard and is important in health IT together with FHIR. Perhaps you could reconsider the "pending popularity" status? What do you think? :)

@lildude
Copy link
Member

lildude commented Jul 24, 2024

Perhaps you could reconsider the "pending popularity" status? What do you think? :)

No. This would set a precident that defeats the point of having usage requirements which I'd need to defend time and time again.

I only reached this conclusion based on your search query and saw that the creator of the language has a significant impact on the usage which isn't really surprising as it's in the creator's best interests to promote their language as much as possible. Excluding them drops the usage significantly.

Things don't look far off inclusion so things might be high enough when it comes to reviewing pending PRs when I make the next release (likely to be the end of August/early September) or the one after that if things are really as popular as you're suggesting.

Copy link
Member

@lildude lildude left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address the test failures. The comments at the top of the languages.yml file should help you with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants