KEMBAR78
StatPatch User Interface Application Requirements | PDF | User Interface | Computing
0% found this document useful (0 votes)
27 views6 pages

StatPatch User Interface Application Requirements

The StatPatch User Interface Application document outlines the software requirements for a device that monitors patient vital signs, detailing its two primary modules: firmware and user interface. It describes user personas, operational modes, and specific use cases for triage and maintenance, including how the device interacts with sensors, displays vital data, and communicates with a Base Station. Additionally, it covers user interactions through a menu system and the device's ability to transmit and receive data over LORA radio.

Uploaded by

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

StatPatch User Interface Application Requirements

The StatPatch User Interface Application document outlines the software requirements for a device that monitors patient vital signs, detailing its two primary modules: firmware and user interface. It describes user personas, operational modes, and specific use cases for triage and maintenance, including how the device interacts with sensors, displays vital data, and communicates with a Base Station. Additionally, it covers user interactions through a menu system and the device's ability to transmit and receive data over LORA radio.

Uploaded by

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

StatPatch User Interface Application

Requirements

Overview
The StatPatch device software is composed of 2 modules. The “firmware” module iinterface with
the sensors and hardware to receive and interpret the sensor data and access the LORA radio.
That module is not described in this document. The “user interface” module receives data from
the firmware module, and handles all user interactions and responses to commands received
via LORA radio.

User Personas
There are three user personas for the device: “Triage User”, which is any person interacting
with the device in a triage, ER, or other situation where the device is being applied to a patient
for purposes of monitoring their vital signs data; “Maintenance User”, which is a person who is
performing system configuration and maintenance activities on the StatPatch device at a
customer site, and “Omedus User” who is provisioning or supporting a device.

Operation Modes
The device operates in 2 primary modes: Operations mode, where it is displaying sensor data;
and Management mode, where it is providing a UI for all other functions such as managing the
LORA link, displaying device meta-data (software version , battery life, owner data, etc).
Operations mode is further organized into “Full Operation”, “Partial Operation”, and “Waiting”.

In Full Operations, the device is displaying vitals signs data, transmitting vitals and device
statistics over LORA if connected, reacting to hardware interactions (menu button etc), and
reacting to LORA commands. Icons will be used to indicate battery life and connection status.

In Partial Operations, it is doing all of the activities of Full, but also sending additional
diagnostics over the LORA link, and displaying information about the failed sensors in the UI. At
any time it can switch to Full mode if offline sensors come online.

In Waiting mode, it is not transmitting or displaying any vitals. The device display is turned off.
The device is listening for hardware interactions (menu button etc), and reacting to LORA
commands. When sensor data is detected, it will enter Full or Partial mode.
Requirements

Triage Use Cases

Display Vital Signs


This broad use case covers usage of the device in monitoring patient vital signs.

Detect and verify sensor placement


When powered on, the device will detect if it is attached to a patient and is receiving sensor data
from all sensors. Three conditions are possible: all sensor data being received, partial sensor
data being received, no sensor data being received.

All Sensor Data


If the UI module is receiving valid sensor data from all sensors, it will enter “full operation
mode”.

Partial Sensor Data


If the UI module detects that it is receiving data from some sensors but not all sensors, it
will enter “partial operation mode”.

No Sensor Data
If the UI detects that no sensor data is received, it assumes it is not placed on a patient.
It will enter “waiting mode”, where it may then go into an operation mode or management
mode.

Initial Placement
When powered on the device enters “waiting mode”. When sensor data starts to be received the
device enters partial or full operations mode. As the device leaves operations mode, it will
visually indicate to the applying user that it has exited waiting mode and is now receiving data.
The device will indicate on screen if there are any failing sensors, giving the user a chance to
adjust the sensors or acquire and use another device.

Display Vitals Data


Refer to the visual design documents for specific layout and style of the vitals display.

Sensor data is made available to the user application via a serial connection to a coprocessor.
This processor is responsible for formatting the sensor data into triaging metrics. From the user
application, the coprocessor can be queried for the vital information. This information is then
transmitted over the serial connection and passed to the user application.
Each vital has 3 ranges that control the color of that specific value being displayed: red, yellow
and green. For example, SpO2 between 94-100 is green, 90-94 is yellow, and less than 90 is
red. Each vital will be displayed using the color as determined by that vital’s ranges. Refer to the
“Triage Algorithm” document for complete details of classifying each metric and the patient’s
overall status.

In Partial Operations mode, we have no data for one or more vitals. In the space where a
reading would be displayed, we will display a simple icon that indicates the sensor is not
functioning. It will be colored using the base display color (white?)

When new vitals data is available, the UI module will apply the Triage Algorithm across all
current data to determine the Patient Triage Level. Patient Triage levels are : Red, Yellow,
Green, Black, and Unknown. The UI module will activate a colored display element to indicate
the level as follows:

● Red, Yellow and Green levels will use the corresponding color (specific RGB values are
TBD).
● Black will use a dark blue RGB value.
● Unknown will use white.

(the physical implementation of the colored display is still under design)

Other Display Elements


Refer to the visual design documents for specific layout and style of the vitals display.

In order to promote maximum clarity when assessing patient status, other data displayed in any
Operations mode is kept to a minimum and done through use of icons.

Battery life is displayed using a battery icon that indicates a typical bar-graph style fill of the
icon.

LORA connection is indicated by the presence or absence of a LORA icon. The icon is yet to be
chosen, but perhaps a simple fan icon as seen to indicate WiFi connection on your typical
phone or computer is sufficient.

Locator Mode
In reaction to a command from the Base Station, a device can activate “Locator Mode’”. In
Locator mode the device performs as usual, with the following exception:

The LED light ring will flash in 2 second intervals between the Triage level color and a bright
blue color reserved for Locator Mode.
This will continue until either: the Base Station sends a command to end Locator Mode, or the
user triggers the Locator Mode Acknowledge action from the UI menu.

Connect to Base Station


● When the device powers on, it will broadcast a connection request over LORA radio.

● We need to understand how devices remember their connections to gateways.

● We need to understand how a device joins a gateway if it has no remembered


connection

Transmit Data to Base Station


When connected to a Base Station, the device will transmit a JSON package to the Base
Station via LoraWan radio. The specific interaction between the firmware drivers that control the
LORA hardware and the UI module is not yet defined.

When connected to a Base Station, the device will periodically send diagnostics and status data
to the Base Station, such as battery life or sensor malfunction. Diagnostics packets will be
transmitted at an interval no shorter than 90 seconds apart. Vital signs data will be transmitted
every 60 seconds for patients in green and black status, every 30 seconds for yellow, and every
10 seconds for red.

Refer to the StatPatch LoRaWAN Interface Specification document for the specific JSON
schema and contents for messages between the StatPatch and Base Station.

Receive Commands From Base Station


The Base Station can transmit commands to the devices. Refer to the StatPatch LoRaWAN
Interface Specification document for the specific JSON schema and contents for messages
between the StatPatch and Base Station.

User Activity Menu Operations


A user can interact with the device using the device menu.The device’s physical interactions will
be determined as part of hardware design; this document only assumes that a menu will be
present and is agnostic of the specific implementation.

The user can take the following actions using the device menu:

Power off the device


The device powers down.
Make or Reset Base Station Connection
The device performs the Base Station connection steps. See ‘Connect To Base Station” section.

Exit Locator mode


This menu option is only available when the device has been put into Locator Mode by a Base
Station Command. Activating this option will turn off the Locator light, and will send a Status /
Diagnostic message to the Base Station that the device has been located. Refer to the
StatPatch LoRaWAN Interface Specification document for details of the messaging interface.

Exit Ambulance mode


This menu option is only available when the device has been put into Ambulance Mode by a
Base Station Command. Activating this option will send a Status / Diagnostic message to the
Base Station indicating that the device should no longer be flagged as “on ambulance”. Refer to
the StatPatch LoRaWAN Interface Specification document for details of the messaging
interface

Toggle triage status light


Activating this option will turn off the triage status color light, or turn it back on if it is off.

Maintenance Use Cases

Link devices to Base Station in bulk (Omedus only)

Link single new device to Base Station (Omedus or Customer)

Remove device from Base Station

Push software update to devices

Test device LORA connectivity

You might also like