#439: Demographics breakdown for population andvby cohort for PCORI Reporting
------------------------+-----------------------------
Reporter: mish | Owner: bzschoche
Type: problem | Status: new
Priority: major | Milestone: data-quality-q3
Component: data-stds | Keywords:
Blocked By: | Blocking: 327
------------------------+-----------------------------
See attached spreadsheet from PCORI. They are requesting we fill out some
basic demographic for our entire populations as well as by cohort.
----
Brittany,
First Page (overall demographics):
The grouping on the ages is different from (a) what we’ve gathered in the
past, and (b) our default groupings within the GPC standard ontology (See
Babel). However, it’s a relatively simple change to make. Debbie is in the
quality code anyway making her final touches, I was about to create the
new REDCap definitions for the new fields, so we can adopt this change
relatively quickly. (Debbie tells me it’ll take a day to add this. It’ll
add maybe 15minute of my type to create these new categories within our
REDCap database.) Debbie has already started work on adding this code into
the quality query
I’ll create a ticket for it in a moment and add it to the list of things
to accomplish.
Second Page (demographics by cohort):
More complicated is the question of cohorts. I look at the second page and
I’m not sure that’s something I feel comfortable tackling with the quality
query in this go around. I know that Dan & Co. had a hard time wrangling
the exact query needed from each site for the breast cancer cohort. The
ALS cohort was also problematic in that it included (at least at our site
and I believe others) data that did not lie within the i2b2 database. In
our case, this included going back and query for specific PCP
relationships that do not reside within i2b2.
It might be easier (and probably more accurate) to have each site break
down the cohorts given the data that they supplied back to the GPC. They
will have either the exact criteria used at their site or presumably the
exact cohort they sent and can fairly easily break it down for themselves
at their site.
I’m assuming that this something that they want us to report on quarterly?
If so, in the long run I believe we should tackle the second page. I’m not
sure if we can automate the second page in the next day or two, which was
our timeline for getting the quality query out.
Dan/George do you guys want to comment on this here? Dan is this something
we want to put to the entire group this coming Tuesday before proceeding?
-TM
--
Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/439>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
