Notifications
Clear all
Topic starter
LinkLogic Warning: Lab Import: No conversion found for input units 'CELLS/UL' to stored units 'K/uL'. Message Code: 1069 Has anyone encountered this error? The unit coming back from the lab result differs from the unit on the OBSterm we are mapping to. We really don't care but it seems to take a lab a minute or more to process through LinkLogic because of it.
Posted : April 5, 2018 5:07 am
Rob,
i am familiar with these messages. It is a warning as opposed to an error. Basically you get the warning message when a lab result gets mapped to a numeric OBS term as opposed to a textual OBS term and the units are not recognized or if it cannot convert the numeric value to the units associated with the OBS term. This is by design in the event you are plotting or trending the numeric values over time because without this failsafe, data comparisons would be invalid. If you are not trending the data over time, then you might consider remapping the value to a textual OBS term as opposed to a numeric. Just keep in mind that if you want to see historical values in the flowsheet, you will need to look in two different places because your data will be mapped to two different OBS terms. You could run a SQL script to migrate the data from the old OBS term to the new if you were comfortable doing that.
Posted : April 5, 2018 5:34 am
You've mapped your results to an observation term that uses 'K/uL' as its units in the Centricity DB. Your numeric results are arriving with a value that specifies 'CELLS/UL' as the unit. This can be handled be adjusting the LinkLogic unit conversion file. It's found in your llogic\config\local folder. Our file is called "lab.cnv" but I'm thinking that's not universal.
The file format is pretty simple. Each line has three values separated by a comma. The first is the unit that the lab result specifies, the second value is a multiplier, and the third is the unit used by your mapped observation term. So you'd add a line something like the following:
CELLS/UL,0.001,K/uL
Let me know how that works out for you.
Posted : April 5, 2018 8:46 am
Topic starter
Thanks for the info, I was able to update that file and no more errors about conversions but processing still takes 30-60 secs for each lab results
I guess it was another issue?
Posted : April 5, 2018 9:01 am
Yeah, I don't think the unit conversion could have a performance impact of that magnitude. Still, it's good to have those unit conversions working so that your data is as clean as possible.
Posted : April 5, 2018 9:02 am
