All, we have a clinic with a split CPS/EMR system with an increasing problem of patient demographic data on the PM side getting overwritten. I notice that they do in fact have a dynamic map applied to both send and recieve for ExternalPatienID(PatientId). In the setup guide, GE doesn't state what these SHOULD be, just that they SHOULDNT be cahnged from out of the box. Well, in an out of the box config. Unfortunately I don't have an out-of-the-box config and quite honestly, GE hasn't been certain either. When compared to a CPS install, both are blank. Can someone out there with the split system take a quick peek and verify there should be no dynamic map assigned?
And the next question as this seems to keep popping up with 3rd party products.. The PatientProfileID and PatientID used to always be the same. 90% of the patients are but we about a year ago, we were starting to see them shift by a single digit which has caused some issues with patient matching queries. Anyone know the history of what changed and why?
Ah yes. The extremely well-documented MIK interface engine.
I'm assuming you are talking about MIK inbound messages overwriting demo data on the PM side. I'm no expert, but I've had to figure out a few of these, so I'll give it a shot.
If your PID's between systems don't match, I would try disabling that mapping altogether. As I recall, a PID match always wins over any other value matches.
That said, I just checked one of my MIK inbound demographic configurations, and I am set up for dynamic map on ExternalPatientId(PatientId), and ExternalPatientID(PatientProfileId).
Briefly comparing the dynamic maps for each (PatientId and PatientProfileId), they match, with patient name and internal ID in the table. The external ID and alternate ID columns are blank.
I've talked about Mirth before. It's worth mentioning again because it has the potential to really help you in this case.
We use Mirth Connect as an intermediate interface engine. It allows us to do any data manipulation we need to between systems. We run all interfaces through it even if we need no data manipulation, just for Mirth's archiving and search functionality. I highly recommend it.