Clinical
- SpO2 / PR
- ECG / HR
- Respiration
- Temperature (skin)
- Continuous BP (cNIBP)
- Non-invasive, cuff-less, with A-Line accuracy
- On ambulatory patients
- Cuff-based calibration only every 8 hours
- There are already multiple medical devices which are 510(k) approved such as:
- Infusion pumps
- Monitoring devices
- The definite trend over the past several years has been to incorporate 802.11radios into medical devices and make this a part of the overall enterprise infrastructure or solution design. This includes both patient monitoring and smart infusion pumps.
- All companies have either received FDA 510K, or a predicate letter has been filed.
- Finally, all the major infusion pump companies, CareFusion, Hospira, Baxter, Sigma, BBraun, and Smiths Medical have introduced wireless smart infusion pumps to the market.
- The display may be in Quiet Monitoring Mode. Touch the screen with one finger for two seconds to activate display or plug in a sensor to initiate monitoring.
- The display may be in Hibernation Mode. Plug in a sensor to initiate monitoring.
- The battery charge may be too low. Disconnect all sensors from the ViSi Mobile Monitor, clean, and place it in the Charger.
- The ECG electrodes may not be connected to lead wires. Ensure that the lead wires are snapped securely onto the ECG electrodes.
- The ECG electrodes may not be firmly attached to the patient’s chest. Ensure that the ECG electrodes are securely attached to the chest also that the ECG electrode sites are clean and free of excess hair.
- ECG electrode gel may be dry, if so replace the ECG electrodes.
- The lead wires may be broken or damaged, if so replace damaged Chest Sensor Cable.
- Chest Sensor Cable may not be securely plugged into the Monitor. Check to make sure Chest Sensor Cable is securely plugged into the Monitor.
- ECG electrodes are may not be all the same. Check and use all the same ECG electrode type, size, materials, and manufacturer.
- ECG electrode gel may be dry, if so replace the ECG electrodes.
- The ECG electrodes may not be firmly attached to the patient’s chest. Ensure that the ECG electrodes are securely attached to the chest also that the ECG electrode sites are clean and free of excess hair.
- If using a 3-lead Chest Sensor Cable the Lead II may have low amplitude. LD II only available with a 3-lead Chest Sensor Cable. Select alternate ECG electrode sites; prepare skin sites; connect lead wires to new ECG electrodes and place on the chest. Also you can try replacing 3-lead Chest Sensor Cable with 5-lead Chest Sensor Cable.
- If using a 5-lead Chest Sensor Cable the selected lead may have low amplitude. Select a different lead to view.
- The ECG electrodes may not be connected to lead wires. Ensure that the lead wires are snapped securely onto the ECG electrodes.
- The ECG electrodes may not be firmly attached to the patient’s chest. Ensure that the ECG electrodes are securely attached to the chest also that the ECG electrode sites are clean and free of excess hair.
- ECG electrode gel may be dry, if so replace the ECG electrodes.
- The lead wires may be broken or damaged, if so replace damaged Chest Sensor Cable.
- Chest Sensor Cable may not be securely plugged into the Monitor. Check to make sure Chest Sensor Cable not securely plugged into the Monitor.
- The Monitor may not be capable of measuring RESP. See your Bio Med for more information.
- ECG electrode gel may be dry, if so replace the ECG electrodes.
- The ECG electrodes may not be firmly attached to the patient’s chest. Ensure that the ECG electrodes are securely attached to the chest also that the ECG electrode sites are clean and free of excess hair.
- The Chest Module sensor may be placed on the patient with the Temperature Sensor facing away from the patient. If so, place the Chest Module sensor on the patient such that the Temperature Sensor is in direct contact with the patient’s chest.
- The sensor may not be attached to the patient’s chest. If not, secure the Chest Sensor Cable to the chest and make sure that a change in position does not affect the sensor’s contact with the skin.
- Chest Sensor Cable may not be in contact with the skin completely and securely. If not, secure the Chest Sensor Cable to the chest and make sure that a change in position does not affect the sensor’s contact with the skin.
- The skin may not be clean and dry. Clean and dry the skin thoroughly and secure the Chest Sensor Cable to the chest.
- The Thumb Sensor may be broken or damage. Replace the Thumb Sensor.
- Ensure nothing is blocking the optics or detector.
- Make sure the Thumb Sensor is securely in the Thumb Sensor cradle and secured at the base of the thumb.
- Ensure that the Thumb Sensor is securely plugged into the Monitor.
- Ensure nothing is blocking the optics or detector.
- Make sure the Thumb Sensor is securely in the Thumb Sensor cradle and secured at the base of the thumb.
- The Thumb Sensor may not be in the correct location. Reorient the Thumb Sensor at the base of the thumb and secure with the Thumb Wrap.
- The Thumb Sensor may be too tight. Loosen the Thumb Strap making sure that it is still secure.
- The battery charge may be too low. Replace with a charged Cuff Module.
- Make sure that the Cuff Module is plugged securely into the Monitor.
- You may not be set up for automatic measurements. From the NIBP Settings screen, select an automatic interval.
- The time from the last measurement may exceed the period of time to display a measurement. Initiate a measurement from the Vital Signs screen.
- The measurements may not have been taken at the same time. Retake the measurements ensuring they are done at the same time.
- Ensure the measurements were taken on the same arm. Retake the measurements ensuring they are done at the same time and on the same arm.
- Also ensure the BP cuff size is the same on both arms, and the correct size for the arm.
- Both arms may not have been at the same level when the BP was measured. Retake the measurement and ensure the arms are positioned at the same level relative to the heart.
- No, if the proper authentication code is used by the Healthcare worker, the system display can be locked from patient tampering.
- Make sure to lock the screen each time you complete your interactions. Remind the patient that this is a medical device, and that tampering may result in missing important clinical events.
- It’s also possible the patient guessed the PIN correctly. Make sure to define appropriate PIN codes (not 0000 for example).
- Make sure that the Monitor and Cuff Module are securely seated in the Charger in the right direction.
- Ensure that the plug is securely plugged into an active wall socket and there is a green light on the Battery Charger. Also make sure the AC Adaptor is plugged into the Charger.
- Make sure that the power cord is not damaged.
- Inbound: The ViSi Mobile Appliance (Server) communicates via the hospital wired network to the Hospital Admission/Discharge/Transfer (ADT) via the Health Level 7 (HL7) standard. The inbound ADT data is utilized by the Sotera application to provide patient identity information for display on the ViSi Mobile Monitors.
- Outbound: the product roadmap for the ViSi Mobile Appliance (Server) and the Patient Data Software contains plans to send information to various EMR systems.
Technical
-
No, if the proper authentication code is used by the Healthcare worker, the system display can be locked from patient tampering.
-
Make sure to lock the screen each time you complete your interactions. Remind the patient that this is a medical device, and that tampering may result in missing important clinical events.
-
It’s also possible the patient guessed the PIN correctly. Make sure to define appropriate PIN codes (not 0000 for example).
-
Make sure that the Monitor and Cuff Module are securely seated in the Charger in the right direction.
-
Ensure that the plug is securely plugged into an active wall socket and there is a green light on the Battery Charger. Also make sure the AC Adaptor is plugged into the Charger.
-
Make sure that the power cord is not damaged.
- The ViSi Mobile devices integrate with a hospital’s existing 802.3 and 802.11 networks.
- The standard system consist of 3 main components:
- ViSi Mobile Monitor – worn by the patient and communicates with the ViSi Mobile Appliance over the wireless network using an 802.11b radio.
- ViSi Mobile Appliance – a 1U racked server that collects, compiles and distributes patient information to the ViSi Mobile Remote Viewer(s) using multicast.
- ViSi Mobile Remote Viewer – a wired or wireless computer or tablet running Java based software that allows the user to view patient vital signs and other data.
- Yes the devices can operate in a routed environment and be different networks within a hospital.
- However, operating over a WAN or a large campus is not recommended because the data is latency sensitive.
- Only the ViSi Mobile Appliance requires a static IP address for the primary and secondary Ethernet ports.
- All other ViSi Mobile devices will accept an IP address from a DCHP server.
- The ViSi Mobile Monitor can coexist with various medical and enterprise devices based on our lab and live testing. ViSi Mobile Monitor is also Wi-Fi Certified which certifies our ability to interoperate with other Wi-Fi Certified devices.
- In addition, co-existence testing is required for FDA approval. Our co-existence testing involved over 20 different yet common medical devices from differing manufactures.
- The Sotera wireless enterprise solution has been tested and validated on a Cisco network. The testing and output of these findings were submitted to the FDA and gained 510(k) approval in August 2012.
- The ViSi Mobile Monitor is Wi-Fi alliance certified.
- No, the Appliance (Server) based Patient Data Software is not qualified to operate in any “virtual” environment.
- The application requires on-demand CPU cycles to effectively process the waveform data being collected. The CPU cycle time increases as the number of ViSi Mobile Monitor’s increase. This real-time requirement may present issues in a virtual environment where the Server is hosting many sessions across multiple applications.
- 1 U Rack Mount
- CPU: An Intel XEON E5620, 4 Core, 2.4 GHz (or equivalent) is recommended.
- RAM: A minimum of 8GB is recommended.
- Drives: 4 500GB drives configured as Raid 10
- Power Supplies: Dual
- Network Interface Cards: Dual
- Operating System: SUS Linux Enterprise v. 11.4
- No, the Patient Data Software is not compatible with MS Windows Server.
- The Appliance (Server) Operating Systems is SUSE Linux Enterprise Ver. 11.4.
- Inbound: The ViSi Mobile Appliance (Server) communicates via the hospital wired network to the Hospital Admission/Discharge/Transfer (ADT) via the Health Level 7 (HL7) standard. The inbound ADT data is utilized by the Sotera application to provide patient identity information for display on the ViSi Mobile Monitors.
- Outbound: the product roadmap for the ViSi Mobile Appliance (Server) and the Patient Data Software contains plans to send information to various EMR systems.
- CPU Speed -3.10 GHz is recommended to process the real-time waveforms being generated
- RAM – >A minimum of 4GB is recommended.
- Screen Resolution: 1920 x 1080
- Thirty two (32) patient sessions can be displayed simultaneously on one ViSi Mobile Remote Viewer
- ViSi Mobile Remote Viewers are desktop or laptop computers, or tablets that have been qualified for use with our ViSi Mobile Remote Viewer Software. Desktop Computers (maximum display size) that have been qualified include:
- HP 9300 All-in-One Touch Screen Computer with 23” 1920X1080 resolution display
- HP 8200 All-in-One Non-touch screen computer with 23” 1920X1080 resolution display
- Operating System: Microsoft Windows 7, 64 bit only
- Does not require local admin rights for normal usage

