0% found this document useful (0 votes)
31 views5 pages

Roche It 1000

The document outlines the configuration for the ROCHE IT 1000 Point of Care (POC) system, detailing the network structure and communication flow between various devices and the HMIS360 interfacing server. It specifies TCP ports for communication, database connection details, and the structure of relevant database tables for managing patient admissions, discharges, transfers, and test results. Additionally, it includes stored procedures for handling ADT lists and updating patient results in the database.

Uploaded by

Muhammad Nasir
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
31 views5 pages

Roche It 1000

The document outlines the configuration for the ROCHE IT 1000 Point of Care (POC) system, detailing the network structure and communication flow between various devices and the HMIS360 interfacing server. It specifies TCP ports for communication, database connection details, and the structure of relevant database tables for managing patient admissions, discharges, transfers, and test results. Additionally, it includes stored procedures for handling ADT lists and updating patient results in the database.

Uploaded by

Muhammad Nasir
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

ROCHE IT 1000 (POC)

CONFIGURATION DOCUMENT
Network Structure

POC Devices

Device 1
Device 2
HMIS360 Device 3
ROCHE
Interfacing .
HMIS DB IT1000
Server .
.
.
Device N

COMMUNICATION FLOW

ANALYSERS / METERS

METER METER METER METER


….
1 2 3 n

COBAS IT1000
SERVER SERVER

RESULT
ADT MESSAGE
ASTM
HL7 FORMAT
FORMAT

CLIENT CLIENT

HMIS360 GATEWAY
HMIS GATEWAY
SENDER

1 MINUTE TIMER

QUERY DATABASE
FOR CONVERT LIST TO HL7
New Admissions
New Discharges
New Transfers

List YES SEND TO COBAS IT


Has 1000
Item
s

NO MARK ADT AS
SENT IN HMIS

END

HMIS GATEWAY RECEIVER

ASTM MESSAGE RECEIVED


FROM COBAS IT 1000

CONVERT ASTM MESSAGE


TO HMIS FORMAT

SEND TO HMIS

Charge Patient
Update Result in Patient
Chart
HMIS 360 Interfacing Server Methodology

TCP Ports:

1. Receiving (Client) default(14010)

2. Sending (Client) default(15060)

This ports need to be allowed through firewall for communication

IP Address: IP Address of IT1000

Database
Connection:

DB Oracle / SQL / MYSQL


DB Version
User
Password
DB Server
Name / IP

Tables:

1. ADT: Admission, Discharge and Transfer

Field Name Meaning Data Type Example


ADMDATE Admission and Transfer Time DATETIME 2020-01-20 15:17:48.940
YYYY-MM-DD HH:mm:SS.MI
ADMNO Admission No NVARCHAR(30) 081407401-4
ADTEVENT ADT Event Type NVARCHAR(3) A01: Admission
A02: Discharge
A03: Transfer
ADTID Table Primary Key NUMERIC / DOUBLE 1,2,3,
This will be used to update the record once
it is updated in IT1000
BEDNO Patient Current Bed No NVARCHAR (50) B1-W3-PICU-4-3
Patient Current BedNo
DISCHDATE Patient Discharge Date and Time DATETIME 2020-01-20 15:17:48.940
YYYY-MM-DD HH:mm:SS.MI
DOB Patient Date Of Birth DATETIME 1995-07-05 00:00:00.000
YYYY-MM-DD HH:mm:SS.MI
GENDER Patient Gender CHAR(1) F: Female
M: Male
U: Unknown
MRNO Patient Medical Record No NVARCHAR(30) 081407401
PATIENTNAME Patient Full Name NVARCHAR(100) MR. MUHAMMAD ALI
2. POCRESULT: Patient Result At POC

Field Name Meaning Data Type Example


MRNO Patient Medical Record number NVARCHAR(30) 081407401
TESTCODE Test Released From POC NVARCHAR(50) GLU
TESTRESULT Result Released From POC NVARCHAR(20) 195
TESTUNIT Result Unit Released From POC NVARCHAR(30) mg/dL
RESULTTIME Time of Release DATETIME 2020-01-20 18:15:22.222
YYYY-MM-DD HH:mm:SS.MI

Stored Procedures:

Procedure Name Parameters Returns


SPR_GetADTList NONE List of ADT Results all the pending
ADMDate, ADTs that are not sent
ADMNO, to IT1000
ADTEVENT,
ADTID,
BEDNO,
DISCHDATE,
DOB,
GENDER,
MRNO,
PATIENTNAME
SPR_MarkADTSent ADTID NONE It will mark the UPDATE
ADT Status to sent, so
that they are not picked
next time
SPR_ReceiveResult MRNO, NONE It will update Result in
TESTCODE, the DB and can also be
TESTRESULT
TESTUNIT, used to charge patient
RESTULTTIME

You might also like