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

Default MIK Map setting for PatientID

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

73 Views

RSS

gfishback

(@gfishback)

Posts: 70

Estimable Member

Topic starter

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?

Posted : August 12, 2016 7:16 am

SLHV

(@slhv)

Posts: 478

Honorable Member

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.

Posted : August 12, 2016 8:05 am

Share:

24 Forums
9,940 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