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

Patient Name Field Blank on Chart Desktop issue

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

5 Posts

3 Users

0 Reactions

93 Views

RSS

aroberts

(@aroberts)

Posts: 176

Reputable Member

Topic starter

Good Morning,

We have just switched form cEMR 9.12 to CPS 12.3.3 and have an issue where documents coming in from an interface (Phreesia) now have the patient name field blank when landing on the chart desktop. If we route the document to someone else, the name will show. I think I have seen this issue before but have no idea what can be done to resolve it.

Any ideas would be helpful!

Thank you,

Amy Roberts

[email protected]

Posted : February 16, 2021 10:31 pm

tippenring

(@tippenring)

Posts: 56

Trusted Member

I don't have a solution, but I would start with looking at the database patientprofile table entry for an affected patient to ensure the name fields are populated there. If it is populated, are there any special characters in a field that might break the display of the name in the chart.

Unexpected behavior rather than errors in CPS aren't surprising. We recently had an issue with a new interface which connected directly to the database like Phreesia does (at least in our case). In CPS, the database PID value length is 16 digits, but the last digit is always a 0. In our case the interface was incrementing the value by 1 to create a new patient. This did not result in an error when retrieving records, but instead CPS opened the next patient in sequence, which was the wrong patient.

-dp

Posted : February 17, 2021 2:39 am

aroberts

(@aroberts)

Posts: 176

Reputable Member

Topic starter

Interesting- thank you for the info. I will look into this!

Posted : February 17, 2021 2:52 am

DavidShower

(@davidshower)

Posts: 1255

Noble Member

Amy, on a user desktop, I see that it is probably using PATIENTPROFILE.SEARCHNAME for the Patient Name. I've seen cases where that field in the database is empty. It sometimes doesn't get "built". It may be that when the document appears first on a desktop, that field may be blank or NULL. And then routing it may force something to build that field. If you see a blank one, you might query that patient's record in the database and see if SEARCHNAME has anything in it. A quick fix is to make a change in Registration like adding a period after a middle initial, save it, then back it out, and that usually populates the field.

Posted : February 17, 2021 10:39 am

aroberts

(@aroberts)

Posts: 176

Reputable Member

Topic starter

What is odd is that it only happens when it is coming in from the Phreesia interface. Doesn't happen to the patient internally when routing, etc. I think we had this issue with one practice when working for Medfusion too but I can't remember what we did to fix!

Posted : February 18, 2021 12:50 am

Share:

24 Forums
9,942 Topics
39.9 K Posts
0 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