Hi Debbie, Marshfield isn't an Epic site, but I can tell you that our approach from the beginning was to artificially create encounters based on patient, date, provider, place of service - rather than trying to pull events, which we've found on other projects/network collaborations to generate noise.
We've discussed this with the coordinating center as part of our Data Characterization review. Their direction is that for the CDM every encounter should be a patient-provider interaction. Our numbers were inflated by things like demographics records. Our ratio of procedures to encounters was further thrown off by our Dental records, because our CDT dental procedures don't count for their analysis. >From what I've seen, encounter definition is one of the items that requires >guidance/recommendations at the DRN OC/coordinating center level. For that >reason, we haven't made any adjustments yet (but we are open to doing so). I'm not sure if this is helpful, but it's our experience... If you have any questions, please let me know. Thanks, Laurel From: gpc-dev-boun...@listserv.kumc.edu [mailto:gpc-dev-boun...@listserv.kumc.edu] On Behalf Of Debbie Yoshihara Sent: Friday, June 10, 2016 10:59 AM To: 'gpc-dev@listserv.kumc.edu' Subject: CDM v3 procedures/encounter EPIC installations Hi, We've noticed that we have a lot of procedures but they are not tied to any encounters in EPIC. So our PX/Encounter is very low. What did other GPC sites do about this? 1) Leave it as it is 2) Tie procedures to encounters using dates 3) Other We were going to leave it as it is, but if other sites had some way of associating procedures to encounters, we'd like to try it. Thanks, Debbie Yoshihara ______________________________________________________________________ The contents of this message may contain private, protected and/or privileged information. If you received this message in error, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained within. Please contact the sender and advise of the erroneous delivery by return e-mail or telephone. Thank you for your cooperation.
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
