1. BB instrument interfaces - setup - workflow - troubleshooting
Presented By:
Ronald Antezana - Instr Interfaces Product Specialist
Krystyna Hagmajer – Instr Interfaces Product Specialist

2. Objectives List of instruments that can be interfaced
Start and end of workflow
Interface implementation process
Responsibility: Client and Soft implementation specialist

3. Which instruments have been interfaced ?
Ortho Clinical Diagnostics- Vision
Ortho Clinical Diagnostics- Provue
Grifols - Erytra
Grifols - WADiana
Grifols - DG Reader
Immucor - Immulink
Immucor - ECHO
Immucor - NEO
Immucor - Galileo
BioRad - Tango

4. Workflow outlined Orders are placed in HIS or in SoftBank
Labels are printed either in HIS or SoftLab application
Specimens are placed on the instruments
Instruments send a query to interface
Interface queries SoftBank and sends response to instrument.
Instrument runs the tests and sends results to interface
Interface posts results to SoftBank
User verifies results in SoftBank/Results/TestVerified

5. Interface worfklow Query Query Query Results Results Results Qrespons

6. Implementation Interfaces (INST and BBIRS ) installed RFQ/SWI tasks
Questionnaire to list all workflow tests completed by the client
Connection established
Configuration and setup build by the implementation specialist
Validation
ICC
Go Live

7. Implementation – at the start
Instr Blank interface installed to establish connectivity only - Setup ID may be suggested by the client
Interface can support serial or tcp connection to accommodate instrument design and client preference
BBIRS – installed to support workflow. This interface is accessing the BB system to either read the order information for query response or post results to BB system. This interface traces provide good information about the workflow status.

8. Implemetation - Connectivity
For serial connection – client will specify xyplex and port number.
Example: terminal server 16xyp: port 07 
For TCP product specialist will assign the port number to be entered in the instrument setup.

9. Interface location
The interfaces are installed in SoftLab module, but can be accessed from SoftBank module

10. Implementation - Interface Setup

11. Implementation - Interface TrnTable
BBIRS server qualifies orders for download based on the tests in the
Instrument Interface/Trn Table/System Column. Only the basic test
are required.

12. Implentation - BBIRS Interface Setup

13. Implementation – specimen label
SoftLab labels :
order number
specimen ID
HIS (Epic) labels
!!! The barcode should
reference the auxiliary
Number in SoftBank
MpiID

14. Implementation – supported test
Client has to provide list of tests to be supported by the interface. The list should include complex/group tests and their corresponding basic/individual tests. SCC suggests making separate test codes for any instrument testing so that it is easy for user to determine weather testing was performed manually or by an instrument
The instrument interface configuration is built to map the instrument test codes to SoftBank tests.
Instrument worksheet is attached to a task for instruments that are designed to support tests listed in their specifications.
Immucor – list of instrument test codes is determined by the vendor
Ortho – list of instrument test codes is customizable. We recommend to present list of BB tests to vendor to use the same mnemonics.
Bio-Rad (Tango) – list of tests is determined by the vendor, but the Infinity model is different then Optimo. If upgrading new script may be required.

15. Implentation - testing
Both interfaces have to be running to support workflow
During validation the interfaces have to be started by the user on the day of testing.
Most instruments support bidirectional workflow, so the instrument has to send a query message to the interface.
The result messages are processed and the results are posted to SoftBank/Results/TestVerify

16. Implementation – posting results
SoftBank will reject results based on certain criteria. If any issues the implementation specialist has to review and apply correction.
Number of phases is incorrect
Number of interpretations is incorrect
Results received do not match a pending order in Softbank
Resulted timestamp is earlier then ordered time
More then one instance of the same resulted test on the order

17. BBIRS
The trace for this interface reveals most common errors, Search it for ERROR
ERROR: bbir_ResSetupGet: Setup for test <YABOD> not found
ERROR: bbir_ResSetupCheckPhInt: SampleID < P> Test <ABID> has incorrect number of phases
ERROR: bbir_ResProcessObx: too many (2) results found for sample
ERROR: bbir_Exception: SampleID < > Test <ABO> : Exception <IREXC>
ERROR: bbir_ResProcessObx: no results found for sample < > <> test <ABO>

18. Configuration ICC
The BB instrument interfaces are custom built – no model interface can be applied
The go live should be planned to allow for 7 business days to process ICC
The ICC – Individual Client Change is applied to the interface configuration. The configuration has to be taken from the client testing environment and reviewed by SCC programming. After the version control is assigned, it is loaded back to the testing environment. SCC implementer runs a test case, and the configuration is moved to production.

19. Responsibilities Action Item Client SCC Interface Setup ID X
Attached worksheet to task
Complete the worksheet to list the tests
Install Interfaces
Establish connectivity
Built the configuration to support the workflow
Validation
Sign off documents
ICC
Move interface to production
Post live support

20. FIN