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
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
Interesting- thank you for the info. I will look into this!
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.
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!