Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

How to pull Encounter/Visit Diagnoses.

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

5 Posts

4 Users

0 Reactions

68 Views

RSS

Jay1785

(@jay1785)

Posts: 2

New Member

Topic starter

I need to create a report that will pull in a patient's encounter/visit diagnoses. So essentially I only want to see a list of diagnoses that were physically assessed by the physician during the office visit and not a running active problems list. How can I specify in my query that only these diagnoses are extracted?

I am running Centricity 9.8 and pulling through SQL

Thanks!

Posted : September 3, 2015 4:14 am

abulsara

(@abulsara)

Posts: 150

Estimable Member

Jason, there are a few ways to handle this:

1. Use the Orders and OrdDx tables to identify the E&M code and the associated Dx codes.

2. You could also use the Assess table to identify what was Assessed.

3. Taking it a step further, you can compare that to the PatientVisitDiag table to see what was billed.

Amar

Posted : September 3, 2015 4:37 am

bruins1986

(@bruins1986)

Posts: 233

Reputable Member

One other thing you can try (I've never done it so definitely review) is attach the Problem table to the Document table via SDID. If the problem was updated or changed during the visit (depending on workflow it may be if "addressed") it should display leaving any that were not updated off of the report.

Just a thought, I've used SDID to associate other fields to specific updates (like Meds and Orders) just never with the problem table itself.

Thanks

Mike

Posted : September 3, 2015 6:45 am

Jay1785

(@jay1785)

Posts: 2

New Member

Topic starter

Thank you Amar, I have been looking at the Assess table thinking it should lead to a correct way to link the diagnoses, but I can't figure out what exactly I would need to do in order to make it work. I don't see any particular fields in there that seem to help. Is linking the SPRID between the problems and assess table enough? I apologize for my lack of SQL knowledge as I am very new to this type of query and any help would be much appreciated.

Thanks,

Jason

Posted : September 4, 2015 8:47 am

aznchewybar

(@aznchewybar)

Posts: 1

New Member

So I am assuming I would join the DOCUMENT table to ORDERS to ORDDX and use the ORDDX.DXCODE to pull all diagnoses and E&M codes?

Thanks,

Jason

Posted : September 14, 2015 3:32 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0