| Literature DB >> 30862019 |
Mario Vega-Barbas1, Jose A Diaz-Olivares2, Ke Lu3, Mikael Forsman4,5, Fernando Seoane6,7,8, Farhad Abtahi9,10.
Abstract
Preventive healthcare has attracted much attention recently. Improving people's lifestyles and promoting a healthy diet and wellbeing are important, but the importance of work-related diseases should not be undermined. Musculoskeletal disorders (MSDs) are among the most common work-related health problems. Ergonomists already assess MSD risk factors and suggest changes in workplaces. However, existing methods are mainly based on visual observations, which have a relatively low reliability and cover only part of the workday. These suggestions concern the overall workplace and the organization of work, but rarely includes individuals' work techniques. In this work, we propose a precise and pervasive ergonomic platform for continuous risk assessment. The system collects data from wearable sensors, which are synchronized and processed by a mobile computing layer, from which exposure statistics and risk assessments may be drawn, and finally, are stored at the server layer for further analyses at both individual and group levels. The platform also enables continuous feedback to the worker to support behavioral changes. The deployed cloud platform in Amazon Web Services instances showed sufficient system flexibility to affordably fulfill requirements of small to medium enterprises, while it is expandable for larger corporations. The system usability scale of 76.6 indicates an acceptable grade of usability.Entities:
Keywords: P-Ergonomics; disease prevention; musculoskeletal disorders; occupational healthcare; precision ergonomics; smart textiles; wearable sensors; wellbeing at work
Mesh:
Year: 2019 PMID: 30862019 PMCID: PMC6427483 DOI: 10.3390/s19051225
Source DB: PubMed Journal: Sensors (Basel) ISSN: 1424-8220 Impact factor: 3.576
Figure 1The proposed system architecture, hardware layers, and information flow.
Figure 2Vest (top) and t-shirt (bottom), including textrodes and ECGZ2 and IMUs.
Figure 3Distribution of the four layers that comprise the Edge node.
Resources provided by the Identity Manager Module.
| Resource | Method | Description |
|---|---|---|
| /auth/login | POST | Performs the login in the system. As a response, the system sends an authentication token. |
| /auth/register | POST | Registers new simple users in the system. |
| /auth/logout | GET | Log out from the system. |
| /auth/status | GET | Obtain the current status of the user and it informs users if they are logged or not. |
| /auth/regdevice | PUT | Register a new mobile device in the system. This mobile is syndicated to the user (authenticated previously) that uses this resource. See |
Data Structure of a Sensory Measurement.
| Data Field | Description | Value Example |
|---|---|---|
| tstamp | Time stamp when the data is stored into the system. |
|
| type | Short description or type of the measurement, i.e., calories, sleep time, etc. |
|
| position | Location of the sensor, if relevant, such as left arm, right wrist, back, etc. |
|
| sensor | Sensor type, i.e., IMUs, Polar watch, etc. |
|
| value | Final value stored in the system and its interpretation, conditioned by the type of data (type field). |
|
| id_user | User from whom the measure is taken. |
|
Data Structure of a Questionnaire Response.
| Data Field | Description | Value Example |
|---|---|---|
| id_response | Unique identification of the stored response. |
|
| id_user | User who completed the form. |
|
| response_tstamp | Time stamp when the response is stored into the system. |
|
| response | Response structure, e.g., 5#4#5#2#2#3#1. |
|
| q_type | Type of form, indicating the policy to be applied for its analysis. |
|
Figure 4Data Warehouse and Business Logic Server overview and its interoperation with the other elements of the system.
Figure 5Distribution of the modules that comprise the analytical server and the interactive processes between them.
Resources provided by the Data Management Module.
| Resource | Method | Description |
|---|---|---|
| /api/v1/data/logs | GET | Obtain the logs of the system in CSV format. |
| /api/v1/data/msr | GET | Obtain all measures of all users. Only administrators can perform this action. |
| /api/v1/data/msr | POST | Store measurements in the database. This resource admits a set of several measurements or a single one. |
| /api/v1/data/msr/{id} | GET | Obtain all responses stored in the system. Only administrators can perform this action. |
| /api/v1/data/qtn | GET | Obtain the current status of the user, i.e., this resource informs users if they are logged or not. |
| /api/v1/data/qtn | POST | Store responses of a questionnaire in the database. This resource admits a set of several measurements or a single one. |
Resources provided by the External Communication Module.
| Resource | Method | Description |
|---|---|---|
| /external/polar/auth | GET | Connect with Polar AccessLink API and start the authentication process. |
| /external/polar/callback | GET | Stores authentication credential (access token and user identification) of the user from the Polar AccessLink API. |
| /external/polar/register/{id} | GET | Registers a worker in the Polar AccessLink system. This action is mandatory to allow users to access their data. |
| /external/polar/delete | GET | Revokes the authorized access token provided by Polar. |
| /external/polar/listOf/{performance} | GET | Access and process the user’s daily activity data from the Polar AccessLink and store them in the system database. |
Resources provided by the Analysis and Action Policy Module.
| Resource | Method | Description |
|---|---|---|
| /api/v1/notification/pmh/{msg} | GET | Send notifications and messages (msg) to external services. The system uses an external notification API based on Firebase [ |
| /api/v1/notification/pmh | GET | Perform analysis related to the health at work policy associate. The policy is defined as a main function in a library. |
Figure 6Sequence diagram of the action policy execution and interactions involved.
Figure 7State diagram of common user activity with the Edge App.
Characteristics of the Amazon EC2 instances.
| Amazon EC2 instance | CPUs | Credits/hour | Memory (GiB) | Upfront Price ($) |
|---|---|---|---|---|
| T2.nano | 1 | 3 | 0.5 | 39.00 |
| T2.micro | 1 | 6 | 1 | 77.00 |
| T2.small | 1 | 12 | 2 | 156.00 |
| T2.medium | 2 | 24 | 4 | 312.00 |
| T2.large | 2 | 36 | 8 | 625.00 |
Figure 8Distribution of the measures according to the type (a) and sensor that generated it (b).
Figure 9The SUS score of the system (dashed red line), with a visual explanation of adjective ratings, acceptability scores, and school grade scales in relation to the average SUS score [35].
Figure 10Graphic representation of the scores given by the users to each question of the SUS questionnaire. The questions are detailed in the Table A2.
SUS questionnaire.
| Item | Question |
|---|---|
| Q1 | I think that I would like to use this system frequently. |
| Q2 | I found the system unnecessarily complex. |
| Q3 | I thought the system was easy to use. |
| Q4 | I think that I would need the support of a technical person to be able to use this system. |
| Q5 | I found the various functions in this system were well integrated. |
| Q6 | I thought there was too much inconsistency in this system. |
| Q7 | I would imagine that most people would learn to use this system very quickly. |
| Q8 | I found the system very cumbersome to use. |
| Q9 | I felt very confident using the system. |
| Q10 | I needed to learn a lot of things before I could get going with this system. |
Summary of the performance test results.
| Amazon EC2 Instance | User/sec | CPU Usage | Amazon EC2 Credits Used | Average Latency (ms) |
|---|---|---|---|---|
| T2.nano | 50 | 37% | 1.6 | 3.5 (p95 = 174.6) |
| T2.micro | 120 | 72% | 3.6 | 93.7 (p95 = 548.5) |
| T2.small | 200 | 72% | 3.5 | 61.3 (p95 = 420.7) |
| T2.medium | 300 | 42% | 3.5 | 75.2 (p95 = 468.8) |
| T2.medium | 500 | 52% | 3.6 | 154.7 (p95 = 658.8) |
| T2.large | 500 | 59% | 4.2 | 591.8 (p95 = 2485.7) |
| T2.nano | 50 | 37% | 1.6 | 3.5 (p95 = 174.6) |
Figure 11Graphical representation of difference between Amazon EC2 CPU credits offered by upfront payment for reserved Linux instances (type t2).