Several dozen questions... for example? i.e. please let's try to have the bulk of the technical discussion in email.
Please do throw a query together, even if only to point out why a simple one isn't adequate. -- Dan ________________________________________ From: Wanta Keith M [[email protected]] Sent: Tuesday, October 28, 2014 4:12 PM To: [email protected]; Mish Thomas; [email protected]; Dan Connolly Cc: Tamara McMahon; Theresa Shireman; Jianghua He Subject: RE: [gpc-informatics] #178: determine whether last.visit is the last fulfilled visit or the last scheduled visit All, This afternoon I got up to speed on visit types. I have several dozen questions that may be relevant for this discussion. I could probably spend some time throwing a query together, but I'd prefer to ask the questions before helping with a query since it would get complicated quickly. This topic might drain our time during the next call, so it might be wise to have a side conversation before then. During today's GPC DEV call, I briefly spoke about release ranges. This is just Epic's term for setting aside id ranges for records and items in Chronicles (Epic's DBMS). We won't care about standard released records since analytical data won't be in these masterfiles which records are set aside. They are typically used for standard workflows or Model System data (which is not relevant to us). We would however be interested in item category values that have a release range. One example of this would be item EPT-30. This is the encounter type item, which gets extracted to PAT_ENC.ENC_TYPE_C column for patient encounters. Epic releases category values 1 through 119, and 150 inclusive. Anything outside that release range, our GPC would not need any mapped concepts for since those visit types are not standard within our GPC Epic sites. Then we would need to find the common visit types of Cerner and Cattails (spelling?), and only include the shared visit types for all three EMRs. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of GPC Informatics Sent: Monday, October 27, 2014 10:39 AM To: Mish Thomas; [email protected]; [email protected] Cc: [email protected]; [email protected]; [email protected]; [email protected] Subject: Re: [gpc-informatics] #178: determine whether last.visit is the last fulfilled visit or the last scheduled visit #178: determine whether last.visit is the last fulfilled visit or the last scheduled visit -----------------------+---------------------------- Reporter: mish | Owner: huhickman Type: problem | Status: assigned Priority: major | Milestone: data-quality2 Component: data-stds | Resolution: Keywords: | Blocked By: Blocking: | -----------------------+---------------------------- Comment (by dconnolly): Tom, you mentioned starting separate calls for quality issues. Do you want to do that right away, or should I continue to track this on the regular Tuesday calls, for now? Hubert, please give us an update on your progress. -- Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/178#comment:3> gpc-informatics <http://informatics.gpcnetwork.org/> Greater Plains Network - Informatics _______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev _______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
