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

Resolving Errors in LinkLogic

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

6 Posts

4 Users

0 Reactions

66 Views

RSS

jfernandes

(@jfernandes)

Posts: 80

Estimable Member

Topic starter

Has anyone found an easy way to resolve errors in LinkLogic? If you wouldn't mind sharing I would greatly appreciate it.

Thanks,

Posted : March 29, 2016 4:35 am

cecild

(@cecild)

Posts: 314

Reputable Member

Can you expand on this. What are the errors. There can be different methods based on the error.

Posted : March 29, 2016 4:42 am

tmarkovina

(@tmarkovina)

Posts: 20

Eminent Member

The best way to keep LinkLogic under control is to actually fix the root cause of each error and not just click on resolve, find patient.

Not sure how deep you go in resolving llogic errors. A proper resolution involves reviewing the llogic details attached to the error, possibly opening the HL7 file, finding the field that centricity does not like, determining whether a cross reference file needs adjustments or working with the sending facility such as a lab vendor who may be inserting data in an incorrect field.

Just takes some patience but eventually you'll notice a lot less errors coming in.

I'm sure there are llogic manuals somewhere on GE's website for you to read if you haven't done so already. It does help a lot when understanding everything involved with llogic.

Posted : March 29, 2016 4:49 am

jfernandes

(@jfernandes)

Posts: 80

Estimable Member

Topic starter

Sorry, I forgot to put that in ... we are manning the errors from our interface with the hospital for labs ... we have starting using the external ID from the hospital and placing it on the additional tab so this has cut down on some errors. But our main problem is that we and the hospital use difference source of identification and Centricity does not allow us to enter the other source in our system to match theirs and the hospital field where they enter the other ID does not go through the HL7.
I was just curious to see if others are having the same issue.

Thanks so much.

Posted : March 29, 2016 5:05 am

cecild

(@cecild)

Posts: 314

Reputable Member

Sounds like you need to create a cross reference file that contains the hospitals code mapped to your code in centricity. Then attach that cross reference file to your interface. As long as you are getting some unique code in the HL7 from the hospital you should be able to create a map.

Posted : March 29, 2016 5:19 am

SLHV

(@slhv)

Posts: 478

Honorable Member

tmarkovina is correct. Spend a little time correcting the root cause and you'll save a lot more time in the long run.

https://engage.gehealthcare.com/docs/DOC-43125 is a link to the managing interfaces PDF. It's semi-helpful.

I've posted this before but it doesn't hurt to mention it again: We use Mirth Connect (www.mirthcorp.com) between all of our interfaces to/from CPS--even if we don't need Mirth to modify any data.

Mirth provides a standard means to manipulate data in many ways that cross-ref files can't. It also provides a very simple means to visualize, archive, and search HL7 data, and re-process anything at any time.

Regarding your lab interface, are you sending lab orders to the hospital via Linklogic/DTS? If so, the patient name, sex, and DOB (and hopefully order numbers so CPS auto-completes them) should match when the hospital sends you the results. Configure CPS not to look at the external ID at all and match only on name, sex DOB. That may resolve your issue.

Posted : March 29, 2016 5:44 am

Share:

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