#155: Define Encounter type terms and Epic ETL
--+--
Reporter: lv| Owner: huhickman
Type: design-issue | Status: assigned
Priority: major | Milestone: drn-basic-query
Component: data-stds | Reso
#155: Define Encounter type terms and Epic ETL
--+
Reporter: lv| Owner: huhickman
Type: design-issue | Status: assigned
Priority: major | Milestone: data-domains3
Component: data-stds | Resoluti
#155: Define Encounter type terms and Epic ETL
--+
Reporter: lv| Owner: campbell
Type: design-issue | Status: reopened
Priority: major | Milestone: data-domains2
Component: data-stds | Resolutio
The linked definition doesn't preclude redundant entries resulting from
multiple encounters taking place on the same day (and these are not
rare, at least at the two GPC sites I've worked with so far). This is
deeper than terminology. The pragmatic question is: what should be in
each row of the
#155: Define Encounter type terms and Epic ETL
--+-
Reporter: lv| Owner: campbell
Type: design-issue | Status: reopened
Priority: major | Milestone: data-stds-gov-plan
Component: data-stds |
#155: Define Encounter
--+-
Reporter: lv| Owner: campbell
Type: design-issue | Status: closed
Priority: major | Milestone: data-stds-gov-plan
Component: data-stds | Resolution: invalid
Key
y, September 16, 2014 2:33 PM
To: verhagen.lau...@mcrf.mfldclin.edu; campb...@unmc.edu; Dan Connolly
Cc: gpc-dev@listserv.kumc.edu
Subject: Re: [gpc-informatics] #155: Define Encounter
#155: Define Encounter
--+-
Reporter: lv
#155: Define Encounter
--+-
Reporter: lv| Owner: campbell
Type: design-issue | Status: new
Priority: major | Milestone: data-stds-gov-plan
Component: data-stds | Resolution:
Keywords:
