MétaCan
Menu
Back to cohort

MCEP: A Mobile Device Based Complex Event Processing System for Remote Healthcare

2018· article· en· W2948074875 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Database Systems and Queries
Canadian institutionsTelus (Canada)Carleton University
Fundersnot available
KeywordsComputer scienceHealth careEvent (particle physics)Complex event processingEmbedded systemReal-time computingOperating systemProcess (computing)

Abstract

fetched live from OpenAlex

This paper introduces an edge-computing based Complex Event Processing (CEP) architecture for Remote Patient Monitoring (RPM) which is an important issue in the context of remote healthcare. In this architecture, the detection of complex events, that may indicate impending health problems, is performed on a mobile device that receives data from sensors attached to the body of a patient. The detected complex events are sent to a back-end hospital server running on a cloud for further processing. Current state-of-the-art RPM techniques use the mobile device as an IoT gateway agent to forward data streams from health sensors to a remote hospital server where complex events are detected. A drawback of this existing methodology is that the mobile phone always needs to remain connected to the hospital server. Also, the mobile network consumption is increased while transferring large volumes of sensor data streams thus leading to an increase in the user cost. Additionally, it leads to an increase in the workload at the hospital server that serves multiple patients. This research investigates a mobile device based CEP system for addressing these issues and demonstrates its viability through a proof-of-concept prototype. A thorough performance analysis is performed using a synthetic workload that provides insights into system scalability and the relationship between system/workload parameters and performance.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.765
Threshold uncertainty score0.496

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.049
GPT teacher head0.339
Teacher spread0.290 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Quick stats

Citations15
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Database Systems and QueriesFrench-language works237,207