Re: [gpc-informatics] #473: PCORnet CDMv3 SAS Readiness

#473: PCORnet CDMv3 SAS Readiness ---+ Reporter: lv | Owner: lv Type: task | Status: assigned Priority: major | Milestone: gpc-phase2-h1 Component: data-stds | Resolution: Keywords: | Block

RE: SCILHS i2b2 to CDM on Oracle

Our plans are a little rough in this area. We have a closely related ticket scheduled for our March 16 release, but it's assigned to me, and I'm struggling to fit ETL development time in between project management stuff. The ticket was opened May 2015 and it has slipped releases 9 times since th

Re: SCILHS i2b2 to CDM on Oracle

I'd vote to go ahead and make the required schema and ETL changes. But I don't want to do so if the GPC/KUMC/etc are not going to do the same. The alternative would be for someone to maintain a GPC fork of the code. Or create some additional SQL to create a view with those schema changes. What'

RE: SCILHS i2b2 to CDM on Oracle

At HackathonThree we considered our evaluation of the SCILHS approach (#381) and decided yes, it looks good. We considered the patient dimension stuff (e.g. Sep 18 c

Re: [gpc-informatics] #462: validate ADAPTABLE computable phenotype with chart review

#462: validate ADAPTABLE computable phenotype with chart review --+ Reporter: schandaka | Owner: kosinski Type: task | Status: assigned Priority: major | Milestone: adaptable-accrual Component: d

Re: [gpc-informatics] #462: validate ADAPTABLE computable phenotype with chart review

#462: validate ADAPTABLE computable phenotype with chart review --+ Reporter: schandaka | Owner: mish Type: task | Status: assigned Priority: major | Milestone: adaptable-accrual Component: data-

Re: SCILHS i2b2 to CDM on Oracle

Dan/Russ, >From a GPC perspective, are we adopting this as the new standard? It involves >modifying our i2b2 ETL processes and adding columns to tables. I want to make >sure everyone is on board. Phillip Sent from my iPhone On Feb 10, 2016, at 2:07 PM, Larose, Eric R mailto:larose.e...@mcrf.m

Re: [gpc-informatics] #462: validate ADAPTABLE computable phenotype with chart review

#462: validate ADAPTABLE computable phenotype with chart review --+ Reporter: schandaka | Owner: mish Type: task | Status: assigned Priority: major | Milestone: adaptable-accrual Component: data-

Re: [gpc-informatics] #473: PCORnet CDMv3 SAS Readiness

#473: PCORnet CDMv3 SAS Readiness ---+ Reporter: lv | Owner: lv Type: task | Status: assigned Priority: major | Milestone: gpc-phase2-h1 Component: data-stds | Resolution: Keywords: | Block

RE: SCILHS i2b2 to CDM on Oracle

Our Encounter Types were in our INOUT_CD, so those worked correctly for us. This would definitely be frustrating if not the case. Those other columns are mentioned about being added in the "SCILHS i2b2 CDM Documentation v2.0.2.pdf" document on the MSSQL side. Not sure if these directions were

Re: [gpc-informatics] #473: PCORnet CDMv3 SAS Readiness

#473: PCORnet CDMv3 SAS Readiness ---+ Reporter: lv | Owner: lv Type: task | Status: assigned Priority: major | Milestone: gpc-phase2-h1 Component: data-stds | Resolution: Keywords: | Block

Re: SCILHS i2b2 to CDM on Oracle

For the pmnencounter table, It assumes ENCTYPE is in the INOUT_CD field of the visit_dimension. Not the case for us. Also, where are DISCHARGE_STATUS,DISCHARGE_DISPOSITION, ADMITTING_SOURCE supposed to come from? Are these added into the visit_dimension table somewhere in the SCILHS process?

RE: SCILHS i2b2 to CDM on Oracle

Thanks for your feedback Phillip. #2 got me digging a little deeper. I had mapped these to our local codes like needed, but the script to generate the CDM doesn't fully utilize the metadata table for its logic (the IN vs. LIKE issue you mentioned). It is making some assumptions as to how thes

Re: [gpc-informatics] #462: validate ADAPTABLE computable phenotype with chart review

#462: validate ADAPTABLE computable phenotype with chart review --+ Reporter: schandaka | Owner: schandaka Type: task | Status: new Priority: major | Milestone: adaptable-accrual Component: data-

SCILHS i2b2 to CDM on Oracle

Has anyone else attempted the SCILHS i2b2 to CDM code on Oracle? I'm focusing on the demographics table to start with have run into a few things I wanted to share. #1) SCILHS relies on the patient_dimension for the demographics, not the observation_fact. Just something to be aware of, not re

Re: [gpc-informatics] #462: validate ADAPTABLE computable phenotype with chart review

#462: validate ADAPTABLE computable phenotype with chart review --+ Reporter: schandaka | Owner: schandaka Type: task | Status: new Priority: major | Milestone: adaptable-accrual Component: data-