And if you wanted to JOIN on the actual encounter fact, take a look at charge slip number.
________________________________________ From: [email protected] [[email protected]] on behalf of Wanta Keith M [[email protected]] Sent: Thursday, July 03, 2014 12:30 PM To: Ahuja, Monika; Dan Connolly; [email protected] Subject: RE: [gpc-informatics] #139: insurance status This would be accurate from an HB perspective, for clinical charges that get routed via the Charge Router. If we're referring to Epic. I can't speak for Cerner or Cattails. For PB charges, the CLARITY_TDL (view) is what is generally used. This view contains records from tables CLARITY_TDL_TRAN and CLARITY_TDL_AGE. CLARITY_TDL_TRAN shows transaction level data, so that's what you want. Not all charges have the same coverage responsibility, because each charge can have separate NRP actions. So it's important to look at each transaction (of type 1-charge). ________________________________________ From: [email protected] [[email protected]] on behalf of Ahuja, Monika [[email protected]] Sent: Thursday, July 03, 2014 12:19 PM To: Dan Connolly; [email protected] Subject: RE: [gpc-informatics] #139: insurance status Dan, Try using PAT_ACCT_CVG , COVERAGE, HSP_ACCOUNT tables. Following SQL works for me at UI:: NOTE: Following SQL assumes that you have a list of encounter numbers (PAT_ENC_CSN_ID's ) for visits/admissions that you plan to check insurance for in a temp table #TEMP_PATS_ARRIVED_AT_CLINIC .. select distinct PATIENT.PAT_MRN_ID,PAYOR_NAME, #TEMP_PATS_ARRIVED_AT_CLINIC.PAT_ENC_CSN_ID, HOSP_ADMSN_TIME , HOSP_DISCHRG_TIME --PAT_ACCT_CVG.*, COVERAGE.* from #TEMP_PATS_ARRIVED_AT_CLINIC JOIN PATIENT ON #TEMP_PATS_ARRIVED_AT_CLINIC.PAT_ID =PATIENT.PAT_ID LEFT OUTER JOIN PAT_ACCT_CVG ON PATIENT.PAT_ID = PAT_ACCT_CVG.PAT_ID LEFT OUTER JOIN CLARITY_EPM ON PAT_ACCT_CVG.PAYOR_ID = CLARITY_EPM.PAYOR_ID LEFT OUTER JOIN COVERAGE ON COVERAGE.COVERAGE_ID = PAT_ACCT_CVG.COVERAGE_ID LEFT OUTER JOIN HSP_ACCOUNT ON COVERAGE.COVERAGE_ID= HSP_ACCOUNT.COVERAGE_ID WHERE #TEMP_PATS_ARRIVED_AT_CLINIC.PAT_ENC_CSN_ID = HSP_ACCOUNT.PRIM_ENC_CSN_ID Order by PAT_ACCT_CVG.PAT_ID , #TEMP_PATS_ARRIVED_AT_CLINIC.PAT_ENC_CSN_ID -Monika 319 356 1895 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dan Connolly Sent: Thursday, July 03, 2014 12:09 PM To: [email protected] Subject: RE: [gpc-informatics] #139: insurance status I don't know how to get insurance status from clinic data at KU. Do any other sites have this data? Which part of the clinical workflow do you get it from? Is it stored in Epic? If so, where? If not, where? -- Dan ________________________________________ From: GPC Informatics [[email protected]] Sent: Thursday, July 03, 2014 11:12 AM To: Dan Connolly Cc: Russ Waitman; [email protected] Subject: [gpc-informatics] #139: insurance status #139: insurance status --------------------------+---------------------------- Reporter: dconnolly | Owner: dconnolly Type: enhancement | Status: new Priority: major | Milestone: Component: data-stds | Keywords: obesity-cohort Blocked By: | Blocking: 33 --------------------------+---------------------------- This has come up in recent discussions: Dan Hale Wednesday, July 02, 2014 5:11 PM: > ... > Furthermore during this progression, does the population drift toward > middle class, insured, white, suburban, etc. ... -- Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/139> gpc-informatics <http://informatics.gpcnetwork.org/> Greater Plains Network - Informatics _______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ _______________________________________________ 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 _______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
