Note, I'm only considering the standard release range category values for EPT-30 in this message.
Does last visit need to have some human contact (either physical or via phone or electronic communication)? Since visits in i2b2 are generally captured with a provider (unless you're doing genetics sequencing or something), you normally need to have the actual provider. So I think a completed appointment would only be considered with a provider, correct? Since on a canceled, no show, or other that's not completed, would not have a confirmed provider. There are exceptions to this rule. A nurse can be considered a patient's provider for a visit. In that case, we would have no provider, so those visits would likely seem as important as those without a provider. Visit types such as 20-Treatment Plan or Appointment can turn into other visit types. Since we're dealing with NAACR data, a treatment plan could turn into several other visits for chemo treatment (for each visit) for example. But they do not confirm you have an actual visit where the patient was seen. 116-Episode changes might mean there will be future visits, but doesn't necessarily mean we have a visit. For example, we might have a pregnancy, and everything will be billed for that one episode at the end of it. That first encounter might not mean we had actual human contact with the patient, but maybe we did. Are we considering auxiliary (needed for medical staff to access EHR without patient) or ancillary system visit types (needed for interfaces/Bridges to move data into Epic)? We don't really have patient/human contact, but there might have been from the interfaced medical software. I'd personally choose to throw away the following since we're dealing with things outside patient care, or they are just based on Epic Hyperspace workflows, or because they involve potential future visits (e.g. Wait List) or other unrelated patient activity. 5-Canceled 6-Unmerge 7-Contact Moved 10-EMPTY 30-Update 97-Committee Review 98-Post Mortem Documentation 99-Billing Encounter 109-History 110-Referral 112-Rx Refill Authorize 115-Resolute Professional Billing Hospital Prof Fee Then we have the gray area visit types of whether there was human contact or not. This would require more discussion. For example, 60 is the precursor for something scheduled for the future, but we don't know if there was human contact. And Abstract is very abstract! 30-Update 60-Health Maintenance Letter 64-Questionnaire Series Submission 71-Nurse Triage 102-Consent Form 105-Letter (Out) 150-Abstract Then we should consider if the patient is deceased or not. That can change whether or not we have a last visit. But a consent form (visit type 102) from a family member for example for organ donations would technically be considered a last visit in some doctor's books, even if the patient is deceased. I'd like to build a query, but I'd like to weed out what is needed by PCORI first. -----Original Message----- From: Dan Connolly [mailto:dconno...@kumc.edu] Sent: Tuesday, October 28, 2014 5:13 PM To: Wanta Keith M; gpc-dev@listserv.kumc.edu; Mish Thomas; huhick...@nebraskamed.com 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 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 [kwa...@uwhealth.org] Sent: Tuesday, October 28, 2014 4:12 PM To: gpc-dev@listserv.kumc.edu; Mish Thomas; huhick...@nebraskamed.com; 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: gpc-dev-boun...@listserv.kumc.edu [mailto:gpc-dev-boun...@listserv.kumc.edu] On Behalf Of GPC Informatics Sent: Monday, October 27, 2014 10:39 AM To: Mish Thomas; huhick...@nebraskamed.com; dconno...@kumc.edu Cc: tmcma...@kumc.edu; gpc-dev@listserv.kumc.edu; tshire...@kumc.edu; j...@kumc.edu 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 Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
