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

Hang ups in LinkLogic!

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

7 Posts

3 Users

0 Reactions

80 Views

RSS

[email protected]

(@kwilliamsimnm-net)

Posts: 18

Eminent Member

Topic starter

We receive the following error message: Error: No existing data could be found to match incoming data on all of our transcribed documents received via an interface with LIAISON. These are unsolicited reports that do not have internal or external ids that will match. They will only match using name, DOB, and sex. When resolving these errors, no manual matching is needed. Using the resolve button matches them correctly without intervention which generally means the interface is good. VOW blames the interface and will not help further. LIAISON has worked with us to tweaked everything we can think of and still have not found resolution.
Has anyone else had this issue and found a solution? Thanks for your help. 🙂

Posted : February 15, 2016 9:21 am

SLHV

(@slhv)

Posts: 478

Honorable Member

Is this new behavior, or has it been this way from the beginning?

Make sure the interface isn't set to require intervention for each message. I don't recall offhand where that setting is at, but it's in the interface settings in CPS.

Posted : February 15, 2016 9:30 am

lpruittms

(@lpruittms)

Posts: 13

Active Member

We had this issue with an interface and worked on it for weeks before we realized the location was not in the list of clinics to import for. Make sure that location is selected under Locations of Care under that interface.

Posted : February 15, 2016 9:43 am

[email protected]

(@kwilliamsimnm-net)

Posts: 18

Eminent Member

Topic starter

This has been a problem for awhile. It used to be more intermittent but now every transcribe document has to be touched. We have had a couple service pack updates which may or may not factor into this. The confirm patient matches before importing data button may be what you are referring to. This is not selected.

Thanks for your input.

Posted : February 15, 2016 10:11 am

[email protected]

(@kwilliamsimnm-net)

Posts: 18

Eminent Member

Topic starter

Our location of care is set to ALL. You have me wondering about what is listed in the HL7 message for location in PV1.7
Oddly, the xray reports are not affected despite coming in via the same interface. The difference is what is in PV1.7. In xray rpts, this segment lists one of our providers. In the transcribe document it lists the dictating provider from the hospital. These providers would not be part of our location of care. Thanks for the input.

Posted : February 15, 2016 10:43 am

SLHV

(@slhv)

Posts: 478

Honorable Member

Confirm patient matches is what I was thinking of. Your thoughts on the content of PV1.7 makes sense.

Posted : February 15, 2016 10:58 am

[email protected]

(@kwilliamsimnm-net)

Posts: 18

Eminent Member

Topic starter

Unfortunately, this issue is still unresolved. We went almost a week without any of these type of errors without changing a thing. Then just as mysteriously as it stopped, it started again. I contacted VOW and the tech mentioned a known issue with BISCOM interference. He made some setting changes in the patient matching in BISCOM and it seemed like it helped the transcribed documents however it created errors with the BISCOM message. UGH!

I have found that this issue affects any MDM hl7 file that is not supplying a external ID in PID 2. These files can only match on Last Name, First Name, DOB and Sex. Oddly, it doesn't happen to everyone of them making it difficult to troubleshoot. I have long suspected that something is interfering with the matching of this files but am unable to pin point the root cause. Has anyone heard about a BISCOM interference within LinkLogic?

Posted : February 29, 2016 9:44 am

Share:

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