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

Scheduling Import Interface

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

3 Posts

3 Users

0 Reactions

64 Views

RSS

mtooley

(@mtooley)

Posts: 62

Estimable Member

Topic starter

We recently went live with scheduling interface into our GE EMR (Oracle) and are having issues when an appointment is rescheduled for another book at the same date/time. When we reschedule in the originating system - the old appointment under the original Book (provider) is still there along with the appointment for the new provider. It never removes the original one. Has anyone come across this or know how we can fix this? Thanks Peg

Posted : March 30, 2017 4:31 am

SLHV

(@slhv)

Posts: 478

Honorable Member

I'm looking at the CPS version of the Linklogic documentation, so it may vary from EMR a bit.

In CPS 12.2, Linklogic ignores the SIU MSH-9.2 component, so that's not particularly useful. Instead it looks at SCH-25 for the purpose of the message.

The SCH-25 status that creates or modifies an appointment is "BOOKED." An SCH-25 value of "DELETED" is described as "When a status of DELETED is received for an existing appointment, the appointment is removed from the doctor/resource identified by the AIG, AIP, or AIS segment (in Chart only mode) or the Centricity Practice Solution resource identified by the AIP segment. "

So, my guess is that you are receiving HL7 SIU messages with a "booked" status, but CEMR may not have enough data to know if it is a modified appointment or a new one, so it simply creates a new one.

Perhaps the originating system can be reconfigured to send two HL7 messages (deleted and booked) for an appointment change.

If that isn't an option, it's possible there is enough data in the HL7 to determine if an appointment is new or modified and help CEMR figure it out by modifying the HL7 before it goes to Linklogic. Alternately you might be able to create an HL7 SIU message with an SCH-25 value of "deleted" for the original appointment and send that to CEMR.

Which way you go depends a lot on what is in the HL7 and other considerations like what will require the least maintenance and provide the most reliability.

Posted : March 30, 2017 8:03 am

ganewman

(@ganewman)

Posts: 25

Eminent Member

We use the "core" appointment outbound interface from Group Management to Centricity EMR 9.8. I had a case on this issue when we first started several years ago. The GE explanation was that a "reschedule" on an appointment does not create an HL7 message to send and change the appointment status in the receiving application. Only "arrive", "cancel", and "delete" will send a message to change the status in the receiving application.

Posted : March 31, 2017 9:01 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