1. SXA 3.5 Sunrise XA Monitored Device Interface Technical Airlift –Washington Conference Room Presented by Monisha Ghuman
2.
3.
4. Monitored Devices Workflow eLink Translator (MonDevDB.exe) eLink Translator (MonDevClient.exe) XA DB eLink Queue (MonitorInbound) HL7 Messages sent via TCP/IP with Devices Data from Devices TCP/IP Translator Listening on specified Port and IP Address for Inbound message Queued Reads Reads HL7 message for PID, PV1, OBR, OBX segments retrieving appropriate fields End User pulls the data from DB via Flowsheets 30 minutes prior to or after the time column Store Device Stats
16. Documentation Workbook( DevIntfBedMapList) MSH|^~amp;|INST-CAR|EnConcert|SCM|SCM|||ORU^R01|HP1012910670670815|P|2.3||||||8859/1 PID|||103-23-12||JEANNE ALLEN||||||||||||||||||||||||| PV1||I |^^CCU 8&8&1 ||||||||||||||||||||||||||||||||||||||||||||||||| OBR|||||||20020205070430|||||||||||||||||||||||||||||||||||| OBX|1|NM|92^RR^SDN|0|16|||||||||||| OBX|2|NM|44^PULSE^SDN|0|80|||||||||||| The patient location CCU881 in HL7 message(PV1-3) would map to the location NGH Unit 1E Room 21 Bed B See Appendix F, “Documentation Workbook Fields” in the SunriseXA Express Load Reference Guide for complete information on the data needed for these worksheets.
01/12/10 -. DataCaptor is a software that pings these monitor devices and polls the data from these devices, translates the data into HL7 format and then this data is sent to MonDev Engine thru a socket or a TCP/IP connection. - Monitor Device Interface is a process that allows observations from the devices like heart rate monitor etc which are connected to data captor .Data captor polls the data from these monitor devices ,translates the data into standard Hl7 format and sends this data thru a socket to the MonDev engine . So data captor acts as a middleware between medical device and our Elink Monitor Device engine . -MonDev does all the data validations in terms of the required segments and fields ,in terms formatting errors, in terms of mappings using location identifier PV1-3 to match the active patient visit in the DB and mappings using channel identifier to match the observation data with the XA Flowsheet parameter and then when a message is matched the observation data is stored in the XA unvalidated database . Once it gets into the database the user is able to pull the data on the flowsheets by a double click time column header within a window of +/- 30mins i.e. 30 minutes prior to or after the time column but not beyond the current date and time
01/12/10 -Devices send the data -Data Captor polls the data from the devices, translates the data into HL7 format and sends the data thru the TCP/IP connection to the Elink MonDevClient translator -MonDevClient translator outputs the data to the Monitor inbound Q -MonDevDB translator reads the data from the Monitor Inbound Q ,validates the data using the location identifier PV1-3 and channel identifier and once the data is mapped successfully it gets stored into the temp location called unvalidated database -The user can go into the application ,flowsheet tab and pull the data with a double click time column header
01/12/10 -Data Captor is a software that collects data from around 250 bed side medical devices and then that data could be used in the clinical applications used by different ancillaries -Monitor Inbound Q –Messages in this Q pass the QA check in terms all the mappings and formatting. These are well formatted messages
01/12/10 -Its imp to remember over here that Monitor Garbage Format Q records the formatting errors but these message do get forwarded to XA.This Q just flags the warnings that there some errors in the message -Monitor Garbage Q –This Q records all the critical errors in the message and these are never forwarded to XA -Monitor Inbound Queue- -All the messages that pass the QA check in terms of formatting, location mappings, channels mappings get forwarded to Monitor Inbound Queue
01/12/10 -MonDevClient Translator-It receives the messages from datacaptor and writes the messages to Monitor Inbound Q
01/12/10
01/12/10
01/12/10
01/12/10 This GUI tools is used to modify INI file. .Do not have to manually go to the INI file to make a change in terms of the Database connections etc.
01/12/10
01/12/10
01/12/10 This table is facility based. Each facility in the hospital can define a unique description for the same in-coming message
01/12/10 Some hospitals use MRN which is the PID-3 to identify the patient whereas some hospitals might use PV1-3 to identify the patients. Typically, devices do not supply Medical Record Numbers so PV1-3 is used to identify which patient should receive data contained in a message.
01/12/10
01/12/10 Demo the Config Tools
01/12/10
01/12/10
01/12/10
01/12/10 -Verify if the data is populating into the table “SCMDEVINTFDATA” table. If data is not accumulating in this table, check the MonDevDB translator. -If PV1-3 is used for mapping purposes then its very imp to remember that the patient has to be in that location at the time of the observation. If not the stored proc will fail and the data will never be seen on the flowsheet
01/12/10
01/12/10
01/12/10 1.For Example if data captor is configured to pull the data every sec then data captor pings the device every sec to spit out the data to it. Right now data captor is configured to ping the device every 2 secs and during that time it appears that we are receiving 3 records . If we want pulse rate every fifteen minutes, we can tell DataCaptor to give us the highest value during that time, or the average, or a few other options .
01/12/10 -We will take the data 15 secs prior and not after as it is clinically more correct to take data in the past than in the future. -Demo the channels number column of the documentation workbook and show that RR which is OBX-3.2 WOULD BE thrown in ,in the channel number column if mapping is done based on OBX-3.2 and not OBX-3.1.
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)