BB instrument interfaces - PowerPoint Presentation

BB instrument interfaces - setup- traces- troubleshooting Presented By: Dino Janos- Instr Interfaces Product Specialist Krystyna Hagmajer – Instr Interfaces Product Specialist

ObjectivesList of instruments that can be interfacedStart and end of interface workflowInterface implementation processResponsibility: Client and Soft implementation specialist

Which instruments have been interfaced ?Ortho Clinical Diagnostics- VisionOrtho Clinical Diagnostics- ProvueGrifols - ErytraGrifols - WADiana Grifols - DG Reader Immucor - Immulink Immucor – ECHO, ECHO Lumena Immucor – NEO, NEO IRIS Immucor - Galileo BioRad – Tango BioRad – IH1000 with IH COM

Interface worfklow I n s t r u ment SoftBank BBIRSInterface InstrumentInterface Query Query Query Results InstrumentInterface Results Results Results Qresponse Qresponse Qresponse

Workflow outlined•Orders are placed in HIS or in SoftBank•Labels are printed either in HIS or SoftLabapplication•Specimens are placed on the instruments•Instruments send a query to interface – direct connection •Interface queries SoftBankand via BBIRS (BB server) and sends response to instrument . P|1|18011745|||YPOCT^RUSTY||19690318|M^CB7^M O|1|M01200190A||TYP|||||||N||||CENTBLOOD^CFA^M

Workflow outlined•Instrument runs the tests and sends results to interface O|1|E9100000639||^^^Weak D|R||| R|1|^^^Anti-D|4+^4+^95|||| R|2|^^^ Ind Ctrl|4+^4+^100|||||F || R|3|^^^Weak D Interp|Positive ….•Interface posts results to SoftBank via BBIRS (BB server) OBX|1|ST|CRH^Weak D||POS^0~0~4+||||||F|| BBIRS trace:bbir_ResProcessResult: (P) Order# <E91000006> Resno 2 Test <CRH> Status Vbbir_ResultMerge: workstation <RLUM2> -> <RLUM2>OK: bbir_ResultUpdate: SampleID <E9100000639> Test <CRH> : Result updated (P) Order# <E91000006> Test <CRH> Resno 2 Status V •User verifies results in SoftBank/Results/TestVerified

Implementation stepsImplementation process starts with SWI task and ends at go-live. RFQ/SWI tasks Interface package installed Connection established List of all workflow tests provided by the client Interface setup and configuration built Validation performed by the client ICC (Individual Client Change) applied to interface configuration Go Live

Implementation InstrBlank interface installed to establish connectivity only -Setup ID may be suggested by the clientInterface 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.

Implementation - ConnectivityFor serial connection - client will specify xyplex and port number. Connectors may be shipped by Soft Example : terminal server 16xyp: port 07 For TCP product specialist will assign the port number to be entered in the instrument setup.

Where is the interface setup located ?The interfaces are installed in SoftLab module, but can be accessed from SoftBank module

Implementation – Interface Setup

Interface parametersTwo parameters are used in the instrument interface to define the format of specimen IDsORDSEARCH used options-          A - auxiliary order#-          D - dynamic barcode -          E - order# with extension -          O - order #2. UNITSEARCH-          B – barcoded donation#-          E – eye readable donation#-          O – inventory order#

Interface TrnTableBBIRS server qualifies orders for download based on the tests in the Instrument Interface/TrnTable/System Column. Only the basic test are required.

BBIRS – supporting interface

Labels Soft labels lists order number and specimen ID – the barcode can represent specimen ID or order number. HIS (Epic) labels – the barcode should reference the auxiliary number stored in SoftBank

Supported testsClient has to provide list of tests to be supported by the interface. This list should specify instrument panel (test) and the SoftBank test that will be linked with particular instrument panel.The list should include all orderable complex/group 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

ValidationBoth interfaces have to be running to support workflow During validation the interfaces have to be started by the user on the day of testing and stopped when testing completed.Most instruments support bidirectional workflow, so the instrument has to send a query message to the interface. The result messages are processed and if the tests are built to interface configuration, the results will be posted to SoftBank /Results/ TestVerify

Validation - continuedSoft Bank will reject any result messages if: The order is assigned to worksheet The order status is complete (tests previously resulted and verified)Resulted timestamp is earlier then ordered time More then one instance of the same test on the order to be resulted

Go liveValidation sign off attached to task is signedInstrument interface checklist attached to task completedICC – 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.

Responsibilities Action item Client SCC Setup ID ( VISN, ECHO, IMLN…) name X Provide worksheet templateXComplete the workisheet to list the supported testsXInstall interface package XEstablish connectivityXXBuilt the custom configuration XValidationXX Sign off documentsXICCX XMove interface to productionX Support X

Questions? ?

Please remember to take a few moments to fill out the session survey. You can find the QR code in your Conference Brochure as well as hyperlinks to the survey online at www.snuginconline.org with the SNUG 2019 handouts.