Connecting Laboratory Analysers to LIS

The short answer

Collect analyser model, software version, interface guide, test codes, units and flags. Test normal, exceptional and amended results before production use.

Three actions to take

Create a code and unit mapping table.
Test disconnection and retransmission.
Trace a result from analyser to final report.

Start with the real scope

Collect analyser model, software version, interface guide, test codes, units and flags. Test normal, exceptional and amended results before production use.

Create a code and unit mapping table.
Test disconnection and retransmission.

Review the points that change the decision

Reviewing protocol, codes, direction and exception results before connecting an analyser to production. Record assumptions clearly and separate confirmed data from items that need checking against the official source or actual operation.

Test disconnection and retransmission.
Trace a result from analyser to final report.

Turn the review into a usable output

Finish with an owner, version, date and follow-up indicator. This keeps the file useful after delivery and allows it to change with the activity, product or system.

Create a code and unit mapping table.
Trace a result from analyser to final report.

Need to apply this to your facility?

Share the activity, city and current stage, and we can help define an appropriate work scope.

Explore healthcare IT solutions