forked from pophealth/popHealth
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Question about API workflow #139
Comments
The workflow looks correct. When the measure results are different, you’ll have look the patient data and see why a patient isn’t in the initial patient population, or the numerator / denominator category. There are usually a set of rather complex logic rules keyed on the various elements of the patient data to determine which category a given patient belongs to.
There are logs in the popHealth that can be enabled to support the examination of the logic behind the decisions made for each patient for a given measure. Let me know if you interested.
Peter
From: Adam Aldrich <[email protected]>
Sent: Monday, April 2, 2018 12:47 AM
To: OSEHRA/popHealth <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [OSEHRA/popHealth] Question about Workflow (#139)
I'm trying to use the API's to pass Cypress Validation. I'm getting some issues where the Cat 3 file that is generated doesn't include the expected results. I have a successful working scenario using just the test data. The issue when it doesn't work is when I load in patients using Cat 1 files we generate and feed in. I'm thinking the issue is with our Cat 1 generation but before I go down that path, I would appreciate some advice that I'm following the process correctly.
Scenario that works:
1. Load in 2017 Measures via rake task pophealth:download_update_install
2. Load Test data from Cypress via API call to api/admin/patients
3. Calculate Measures via API call to /api/queries
4. Wait for calculate to finish
5. Generate Cat 3 file via API call to /api/reports/*qrda_cat3.xml passing in the measure id's
6. Generate Cat 1 file via API call to /api/reports/*cat1.zip
Scenario that doesn't work
1. Load in 2017 Measures via rake task pophealth:download_update_install
2. Create records in our system from the Cypress test data
3. Generate Cat 1 files from our system and load into Pophealth via API call to api/patients
4. Calculate Measures via API call to /api/queries
5. Wait for calculate to finish
6. Generate Cat 3 file via API call to /api/reports/*qrda_cat3.xml passing in the measure id's
7. Generate Cat 1 file via API call to /api/reports/*cat1.zip
Is the above workflow what is recommended? And if so, are there recommendations on generating and validating the Cat 1 files to feed into Pophealth?
Thanks for your help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#139> , or mute the thread <https://github.com/notifications/unsubscribe-auth/ABgjbf_UpMYxmjjtAokuUAIbd5z62mv4ks5tka1FgaJpZM4TDJQE> .
|
@petercyli Thank you for the response. The logs would be great. I think that is where I need to focus my effort, in trying to figure out if the data I'm feeding in is correct. So anything you can think of that could help me in that effort would be very much appreciated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to use the API's to pass Cypress Validation. I'm getting some issues where the Cat 3 file that is generated doesn't include the expected results. I have a successful working scenario using just the test data. The issue when it doesn't work is when I load in patients using Cat 1 files we generate and feed in. I'm thinking the issue is with our Cat 1 generation but before I go down that path, I would appreciate some advice that I'm following the process correctly.
Scenario that works:
Scenario that doesn't work
Is the above workflow what is recommended? And if so, are there recommendations on generating and validating the Cat 1 files to feed into Pophealth?
Thanks for your help.
The text was updated successfully, but these errors were encountered: