Re: [gpc-informatics] #604: snow shrine prod hub public cert renewal - spoke server keystore updates

#604: snow shrine prod hub public cert renewal - spoke server keystore updates -+- Reporter: kwanta | Owner: kwanta Type: task | Status: new Pr

DROC Breast Cancer CRG Request (#596)

Hello, Everyone: I believe a couple of sites had stated on the dev call today that they were able to upload their Query3 results into Redcap. But as of about 30 minutes ago I had not seen any results uploaded to the Query3 project. I was able to upload UIOWA's results into the "Cancer CRG DROC

Re: [gpc-informatics] #596: targeted cancer therapy study - Query 1, 2, 3

#596: targeted cancer therapy study - Query 1, 2, 3 --+ Reporter: dconnolly | Owner: schandaka Type: task | Status: assigned Priority: major | Milestone: gpc-phase2-h4 Component: data-sharing | Res

Re: [gpc-informatics] #596: targeted cancer therapy study - Query 1, 2, 3

#596: targeted cancer therapy study - Query 1, 2, 3 --+ Reporter: dconnolly | Owner: schandaka Type: task | Status: assigned Priority: major | Milestone: gpc-phase2-h4 Component: data-sharing | Res

Re: [gpc-informatics] #596: targeted cancer therapy study - Query 1, 2, 3

#596: targeted cancer therapy study - Query 1, 2, 3 --+ Reporter: dconnolly | Owner: schandaka Type: task | Status: assigned Priority: major | Milestone: gpc-phase2-h4 Component: data-sharing | Res

Re: Question on CDMv3.1 Run

I can verify that the RESULT_NUM data type conversion in data_step_view_prep.sas was the source of the data check exception being thrown in the EDC mentioned as Alex mentioned. I have updated the code, which is available at https://github.com/kumc-bmi/i2p-transform/blob/master/SAS/data_step_view_p

Re: Question on CDMv3.1 Run

Alex, Thanks for the response, that¹s exactly the fix I am currently testing. If it works for us here at KUMC as well, I will update the code at (https://github.com/kumc-bmi/i2p-transform/blob/result_num_fix/SAS/data_ste p_view_prep.sas) and send another email confirming that the issue originates i

RE: Question on CDMv3.1 Run

MCW had the exact same problem with RESULT_NUM being seen by SAS as a character field despite being numeric in our source RDMS table (Oracle). For us this was caused by the data_step_view_prep.sas code which explicitly forces the RESULT_NUM field to character (which was how it was originally m

RE: [gpc-informatics] #570: collect expanded obesity cohort data: demographics, income, insurance / financial class

I have a call scheduled with Mike Bingham - the GPC IRB rep - to talk this through. Unfortunately, the first available time we can speak is 7/25 - but I hope to have an update for the 7/25 dev call. BG -Original Message- From: GPC Informatics [mailto:d...@madmode.com] Sent: Monday, Jul

Re: Question on CDM v3.1 Run

Nevermind. It looks like our definition for the view LAB_RESULT_CM still had the old value of varchar instead of numeric. --- Debbie Yoshihara University of Wisconsin - Madison From: Gpc-dev on behalf of Yoshihara Deborah L Sent: Tuesday, July 11, 201

Question on CDM v3.1 Run

When running CDM 3.1, the EDC is reporting an error: Required Numeric field is character: LAB_RESULT_CM RESULT_NUM However, LAB_RESULT_CM.RESULT_NUM is already defined as numeric(15,8) Is this a possible error in the EDC Report? How can we fix this error? Thanks, Debbie Yoshihara Universi

Re: Question on CDM v3.1 Run

Hi Don, We are getting the same error here at KUMC. Are you using data step views? I am currently testing whether a small change to our data_step_view_prep.sas will fix this. Best, Michael From: Gpc-dev mailto:gpc-dev-boun...@listserv.kumc.edu>> on behalf of Steger Donald A mailto:dsteg...

Question on CDM v3.1 Run

Hello: When running CDM 3.1, the EDC is reporting an error: Required Numeric field is character: LAB_RESULT_CM RESULT_NUM However, LAB_RESULT_CM.RESULT_NUM is already defined as numeric(15,8) Is this a possible error in the EDC Report? How can we fix this error? Thanks, Don Don Steger S