Dan, during last GPC-NU phone call all sites expressed opinion that this field will be hart to collect. So, it will be removed from the list in the next revision of data dictionary.
Thank you. Alona. On Wed, Jul 19, 2017 at 11:28 AM, Dan Connelly <dconno...@kumc.edu> wrote: > Prof. Black, Alona, > > This facility_id mapping... what will it map *from*? What sort of info > should we add to encounter.facility_id (or elsewhere in the CDM... or > elsewhere altogether?) as input to this mapping? > > Feel free to answer at your convenience. It'll be weeks or months before > we make the relevant changes to our CDM ETL, so there's no particular rush. > > -- > Dan > > > ------------------------------ > *From:* furmanc...@icnanotox.org [furmanc...@icnanotox.org] on behalf of > Al'ona Furmanchuk [alona.furmanc...@northwestern.edu] > *Sent:* Thursday, May 18, 2017 11:16 AM > *To:* gpc-dev@listserv.kumc.edu > *Cc:* Dan Connolly; Mei Liu; a...@nm.org; nicholas-c-sm...@uiowa.edu; > phillip.ree...@utsouthwestern.edu; Lindsey Lynne Cook; Russ Waitman; > brian-gryz...@uiowa.edu; George Kowalski; meye0...@umn.edu; > jay.peder...@unmc.edu; danh...@regenstrief.org; adfre...@regenstrief.org; > mcneele...@health.missouri.edu; Brennan Connolly > *Subject:* Re: [gpc-informatics] #539: Next-D Clinical Variables in EMR: > how to collect? > > Thank you for fast follow up on this. See below my comments that hopefully > might help: > > On 3: > NWM system provides facility_id number in CDM which is could be used just > to distinguish between different facilities. During the meeting it was > decided that better characterization (beyond PCORNET CDM) of facility > should be done. Prof. Black will provide proper mapping on this. > > On 9: > It was in distributed for the in-person meeting materials (attaching > relevant file here as well). I added two extra columns specifying what > variable from what PCORNET CDM tables should be used for each data element > of CMS measurement. I also provided corresponding analogues values in case > if theirs standards codings are varied from PCORNET ones. > > Thank you. > Alona. > > On Thu, May 18, 2017 at 10:27 AM, GPC Informatics <d...@madmode.com> > wrote: > >> #539: Next-D Clinical Variables in EMR: how to collect? >> --------------------------+----------------------- >> Reporter: dconnolly | Owner: meiliu >> Type: design-issue | Status: assigned >> Priority: minor | Milestone: next-d >> Component: data-sharing | Resolution: >> Keywords: | Blocked By: 542 >> Blocking: | >> --------------------------+----------------------- >> Changes (by meiliu): >> >> * cc: lindsey.cook@… (removed) >> * cc: cgladfelter, bconnolly@… (added) >> * owner: afurmanchuk => meiliu >> >> >> Comment: >> >> reviewing May 16 in-person meeting version of //Proposed Formats for Data >> Extraction// with Dan and Brennan: >> >> by table: >> 1. summary information is relatively clear; see #545 >> 2. demographics seems like a straightforward extract from CDM >> - date structure (year-month, days since 1st encounter) is novel but >> workable >> 3. **CDM encounter.facility_id is all "no information" NI at KUMC** >> 4. meds - all CDM columns OK >> - Dan recalls seeing requirements for all these columns in the EDC >> report >> 5. vitals - smoking seems to be OK at KUMC >> 6. labs is a little tricky, but see #551 >> a. from CDM short-list >> b. Glucose etc. >> 7. non-urgent visits >> - some variability among GPC sites was noted regarding what counts as >> `enc_type=AV` >> - codes are in table B1; e.g. 993385 New Patient, Adult >> 8. immunization >> - draws from CDM PROCEDURES table; eg px_type=C3/C4/CH pc=90732 for >> Pneumococcal conjucate vaccine >> 9. Health outcomes: Glycemic control, LDL control, Pneumococcal >> vaccinations >> - this table is less well-defined: no sketch of which CDM tables / >> columns are relevant >> - much material draws from CMS122v5 >> 10. diagnosis >> - note: CDM DIAGNOSIS is only billing diagnoses; problem list >> diagnoses go in the CONDITION table, which was not characterized in >> milestone:cdm-c2r2 >> >> >> Mei to follow up on options regarding missing `facility_id` data. >> >> -- >> Ticket URL: <https://urldefense.proofpoint.com/v2/url?u=http-3A__ >> informatics.gpcnetwork.org_trac_Project_ticket_539-23comm >> ent-3A9&d=DwIDaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_ >> d012z2PA6ws&r=-aRkmw3Ob1oZRrrYmR1wHysw9FWMRlmk_CMIVWKi32KhS_ >> EbXW7cMBGcBAmqh95W&m=s1Kzf1392oP6F3gs6uqK2scaV9R3WbcrypgMOf8 >> Lx10&s=uVWtTRnqaZbOOebENIN3dHG5jYXbhSLuD5xG1OiO5V0&e= > >> gpc-informatics <https://urldefense.proofpoint.com/v2/url?u=http-3A__ >> informatics.gpcnetwork.org_&d=DwIDaQ&c=yHlS04HhBraes5BQ9ueu5 >> zKhE7rtNXt_d012z2PA6ws&r=-aRkmw3Ob1oZRrrYmR1wHysw9FWMRlmk_ >> CMIVWKi32KhS_EbXW7cMBGcBAmqh95W&m=s1Kzf1392oP6F3gs6uqK2scaV9 >> R3WbcrypgMOf8Lx10&s=B1mVEpFHig575645iWM5OD3tKEzXgwfj8a34J__yHpk&e= > >> Greater Plains Network - Informatics >> > > > > -- > Al’ona Furmanchuk, Ph.D. > Research Associate > > Department of Electrical Engineering and Computer Science > Northwestern University > 2145 Sheridan Road, Tech L359 > Evanston, IL 60208 > Web: http://furmanchuk.com/ > <https://urldefense.proofpoint.com/v2/url?u=http-3A__furmanchuk.com_&d=DwMF-g&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=-aRkmw3Ob1oZRrrYmR1wHysw9FWMRlmk_CMIVWKi32KhS_EbXW7cMBGcBAmqh95W&m=x0WvEUVu3S8ZVsBxKT-YFT-72TWWW8sWHhd7TyI1Wh4&s=8mR4VM6PORhAHT0GViSpDLDwHvT4Q68ciCo9SaNLZLo&e=> > E-mail: alona.furmanc...@northwestern.edu <furmanc...@icnanotox.org> > Phone: 847-467-2299 <(847)%20467-2299> > -- Al’ona Furmanchuk, Ph.D. Research Associate Department of Electrical Engineering and Computer Science Northwestern University 2145 Sheridan Road, Tech L359 Evanston, IL 60208 Web: http://furmanchuk.com/ E-mail: alona.furmanc...@northwestern.edu <furmanc...@icnanotox.org> Phone: 847-467-2299
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
