Yes. I think I can get it done by the 31st.
I can start on the I2B2 part this week, and think I should wait until this next
CDM refresh is approved before sending it.
Reid
-----Original Message-----
From: GPC Informatics <d...@madmode.com>
Sent: Monday, January 06, 2020 12:56 PM
To: xs...@kumc.edu; Reid Holbrook <reid.holbr...@hsc.utah.edu>;
dconno...@kumc.edu
Cc: lpa...@kumc.edu; schand...@kumc.edu
Subject: Re: [gpc-informatics] #754: GROUSE Refresh 2019 - Utah
#754: GROUSE Refresh 2019 - Utah
-----------------------+-------------------------------
Reporter: xsong | Owner: Reid.Holbrook@…
Type: problem | Status: assigned
Priority: major | Milestone: grouse-refresh-2
Component: data-stds | Resolution:
Keywords: GROUSE | Blocked By:
Blocking: |
-----------------------+-------------------------------
Comment (by xsong):
We have already collected the EDC report from Utah in
[https://redcap.gpcnetwork.org/redcap_v6.11.5/index.php?pid=113 this REDCap
project]
Replying to [comment:1 dconnolly]:
> Song, did you omit the EDC report on purpose? See #744 for example:
>
> 1. i2b2 Datamart
> 2. PCORnet CDM Datamart
> 3. Cross walk: patient_num, date_shift, birth_date, patient_num_hash
[see #597]
> 4. EDC report
>
> Also: I wonder about a 31 Jan expected delivery date with noone assigned. I
> take it you are requesting the data by then, Song? Reid, does
31 Jan look feasible?
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/754#comment:3>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
