Notifications
Clear all
Topic starter
We are importing clinical results via LinkLogic and they are importing with all ! next to the results despite being mapped observation terms. We have the clinical kit, llogic relationship, and cross reference file set up normally. No values pull into the flowsheet. In list changes it shows all the clinical values added but no attached terms. We have confirmed that the terms exist and we are sending the correct associated code.
Any ideas? 
Posted : February 5, 2020 9:17 am
Has it ever worked, or is this something new?
My first guess would be your .xrf file has something in error so it isn't being used at all.
Did you build an .xrs file, then import it as a new cross-ref file? That should show any errors, but since it is extra steps, often that part isn't done.
Edit: I also don't see an obs term called "BLEEDINGHXF5" or similar. It appears your xrf isn't working.
-dp
Posted : February 5, 2020 9:48 am
You also might want to look at your LinkLogic Activity Log. You will want to go to Chart LinkLogic, the Activity Log tab, and then go up to the Options tab and click Organize. Make sure the Stations drop down is set to All Stations, and uncheck the All Tasks check box and just check the Import task under Lab Results that this is coming in on (looks like something to do with IntegrationClient-Phreesia). Or just put a check next to the Lab Results folder. Click Ok. Then you can scroll until you get to February 5th at 9:30 am and look through the messages to see what the issue is.
Posted : February 5, 2020 11:03 am
Topic starter
so this integration has worked before but this is a new set up at a new centricity instance. We did build the xrs and import as a new cross ref file for the given relationship. How would we be able to find what the error is in our xrf?
Posted : February 5, 2020 12:37 pm
I'm not 100% sure, but IIRC if there is an error in the .xrs file, it will not generate the .xrf. So if you ended up with an .xrf, I don't believe there was an error at the time the .xrs was converted.
David Shower has replied (in excellent detail I would add) with the steps I would follow next.
-dp
Posted : February 6, 2020 4:11 am
Topic starter
Thank you for the help! The xrf ended up being badly formatted and we got it resolved.
Posted : February 6, 2020 7:52 am
