A survey on success factors to design application frameworks to develop mobile patient monitoring systems

A study of mobility support in wearable health monitoring systems: Design framework

“…A HMS is typically built of three building blocks namely sensing, communication and data analysis, considered as the three main functionalities enabling HMS to operate [6].…”

“…Through the literature and examining patient's data profile, we propose to define a set of related constraints, namely: (1) Data collection frequency requirement (DF), defining how certain data should be collected in term of time intervals of sensing [8,18,35]; (2) Data processing requirement (DPC), referring to the need to certain data to be processed or not (used directly) as well as the nature of the processing performed [25,37]; (3) Real-time requirement (RT), defining whether a specific monitored data should be on-time delivered and/or processed in real-time or is rather delay tolerant [6,37]; (4) Data reliability requirement (DR), referring to the need of data quality i.e. if a specific monitored data is loss and/or error-tolerant [11,36]; (5) Data prioritization requirement (DPR), where some data or alerts might be more critical than others, and therefore would be more prioritary than routine data such as in emergency cases where some vital signs becomes more sensitive as well as alerts [18]; (6) Data correlation requirement (DC), leading to a need of synchronization between some data, if these are somehow associated and/or need to be combined [18,25]; (7) Data management requirement (DM), defining if monitored data settings are fixed and set only the first time or if it should be manageable such as setting thresholds, enabling/disabling the monitoring of some data … etc.…”