One of our labs began sending in results with a OBX5 segment over 2000 characters, they add spaces in the field, this causes the labs to error out and I do not want to touch the LL error to get it into the system.
Has anyone encountered this before? If so, how did you handle getting the lab into the EMR?
We also have a problem where one lab send the value as "See note" which pushes to our flowsheet and we can not run reports against it. Any suggestions to stop this?
Thanks Monte!!
One of our labs began sending in results with a OBX5 segment over 2000 characters, they add spaces in the field, this causes the labs to error out and I do not want to touch the LL error to get it into the system.
Has anyone encountered this before? If so, how did you handle getting the lab into the EMR?
We also have a problem where one lab send the value as "See note" which pushes to our flowsheet and we can not run reports against it. Any suggestions to stop this?
As far as length issues, we've always put the burden of the fix on the sender, especially if it's a change made after the interface went live. One argument is that if it affects you, it also affects other Centricity users. This helps to avoid purchasing anything.
There might be an IXP add-on file that forces the result to populate instead of "See note" or "See report". I don't have the specs in front of me, but I would recommend starting there (Managing Interfaces for Centricity EMR / CPS)
IF it is one of the big labs, their Interface team are most of the time pretty capable of fixing this issue.
IE: I had the same issue with Quest months ago. Which i contacted them and they were able to solve the issue.
is a problem in their end and they just need to adjust the Content generator in their parser.
or you can go the other way and put a 3rd party Software like ignis, Egate or Cloverleaf to manage your interface and let you update your interface configuration as it was a wizard