-
Notifications
You must be signed in to change notification settings - Fork 3
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
QDM based Patient data sample that would work with AIS Measure CQL #122
Comments
Ganesh, Based on your description, it sounds like you are trying to test a measure that uses CQL-based logic. This can be done on either https://bonnie.healthit.gov or https://bonnie-prior.healthit.gov/ depending on what version of CQL and QDM the measure was written in. -Matt |
Thanks Matt for the responses.
Would you be able to tell us what version the Ruby codes are written? Below are the steps we are following to generate data, could you pls. tell us if are we missing any step or on right track:
Also, when we try to execute generate_patients.rb we get below error, is there any additional package(s) that needs to be installed?
Thanks. |
Ganesh, For cqm-models we target ruby version 2.6.3. The current version of CQM-Models contains models for QDM 5.4 by default so you shouldn’t have to run the models generator unless you want to use a different version of QDM. The PatientGenerator class is not intended to be run the way you are trying to run it. The PatientGenerator class contains helpful methods that will return data elements or patients with dataelements populated with random data. You can look at these methods to figure out how to use the models and populate the with your own data, or call these methods from your own program if you want to use QDM patients or data elements that do not contain meaningful QDM data. -Matt |
Hi Matt, We were able to generate data in JSON format, pasted a snippet of that as below, using QDM 5.4 model info by default. In Parallel, We are also trying to generate data for QDM 5.3, would you be able to provide any references to "oids_qdm_5.4.json" for 5.3 If we have to change any defaults, would this be the right file to change the values? What is the use of CQM model libraries "/server/userhomedir/userid/cqm-models/app/models/cqm" used in patient generator - are these libraries required if we have to generate data only for QDM 5.3/5.4 NCQA Measures (non CMS measures)?
|
Hi Matt, We were able to successfully generate patient data for QDM modelinfo v5.4 but facing issues while trying to generate patient data for QDM v5.3. Following are couple of ways we did. We are getting following error when we try to generate patient data (after generating models with QDM 5.3 modelinfo). Can you pls help.
` Looks like we shouldn't be generating models again with QDM 5.3 modelinfo. So I re-ran bin/validate_genererator.sh and ran lib/patient_execute_qdm53.rb
` Sent with GitHawk |
Hi @ramanathanga, Could you please tell how you are able to generate patient data for QDM 5.4 model version? Are you able to any new patients with this version? Please help to clarify. We have C-CDA XML file with patient data, Is there any way we can generate it based on QDM 5.4? Thanks. |
Hi,
We are trying to execute a measure CQL that uses QDM data as input.
We already tested a sample based on Readme as below, this was successful:
[(https://github.com/projecttacoma/cqm-execution/blob/master/README.md)]
Below are the 6 CQL measures published by NCQA which we have access to, and while trying to execute AIS measure CQL we understand we need a QDM based Patient and other related data.
Measures: AIS, ASF, DMS, DRR, DSF, PRS
**We are trying to get a QDM based Patient data sample that would work with AIS Measure CQL, can you pls. share a sample that we could use to test.
Larger picture, we are trying to understand how to create/generate QDM based data for Patient and other types as inputs to NCQA measures CQL (like AIS, ASF, DMS, DRR, DSF, PRS etc..). Are there any resources which you can point us to.**
Thanks,
Ganesh Ramanathan, Balaji Venkata Yadalla.
The text was updated successfully, but these errors were encountered: