Wearable & mobile research platform
Bring your signals together.Keep your study in view.
Configure and collect wearable and mobile data, check recordings against your study plan, and export datasets with acquisition metadata and quality documentation.
Tell us about your study and data sources.
Explore the workflowIn development. Preparing first external pilots.
- Direct from device
- Polar H10 · Polar OH1 · Polar Verity Sense · Movesense Medical · Movesense Flash · Colmi Ring
- Imported
- Apple HealthKit · Android Health Connect
- On the phone
- Phone sensors · voice recordings · participant questionnaires
Available streams and checks depend on the source and setup. Direct acquisition and imported health data do not provide the same signals or sampling.
Study overview
See recording coverage across your study.
Illustrates the intended workflow, not the current product interface.
Recording availability & check-ins
- Check-in received
- Check-in overdue
- Recording available
- No data received
A synthetic illustration. For each of 6 participants it shows which parts of the 14-day study period have a recording available and which scheduled daily check-ins have been completed. The two cases called out below the chart are described in text.
Selected: P-004, day 8 — shown in detail below
P-005, day 12: recording available; check-in overdue
Review available recordings and scheduled check-ins separately. A missing upload does not, by itself, explain why data are absent.
Concept preview · Synthetic data
Session detail
Check recordings against your study plan.
An upload can arrive and still need attention.
Compare the received recording with the study plan, then inspect the signals and acquisition context before deciding on follow-up.
Review flag
Duration needs review
All uploads for this session received, including one delayed.
- Scheduled durationScheduled
- 120 s
- per the study plan
- Received session spanReceived span
- 60 s
- session start to session end. Samples are unavailable for an 11-second interval within this span.session start to end
- Unavailable samples
- Samples are unavailable for an 11-second interval within this span.
- Researcher note
- “Recording shorter than scheduled. Cause not established.”
A synthetic illustration of one 60-second recording session. It shows a PPG trace, three accelerometer axes, the protocol step in progress, a voice note and a single participant report against a shared session clock, together with the three states described below.
- 1Data not received
No samples are available in the workspace for this interval. The recording status on the device is unknown.
Earlier in this session, no samples are available in the workspace for an eleven-second interval. The recording status on the device is unknown.
- 2Marked for review
Inspect this interval alongside movement and protocol context before deciding how to use the signal.
Inspect this interval alongside movement and protocol context before deciding how to use the signal.
- 3Delayed upload
The recording arrived after acquisition. Its original recording time and later arrival are shown separately.
The recording arrived after acquisition. Its original recording time and later arrival are shown separately.
Illustrates the intended workflow, not the current product interface. Signals are synthetic and shown for illustration.
Approach
From study expectations to documented data.
Three questions between a scheduled recording and a dataset a collaborator can work with.
Did the recording match the protocol?
Compare submissions with the study's expectations for timing, duration, device and sample count. Surface supported deviations for investigation while collection is still underway.
What happened during acquisition?
Inspect sampling behaviour, sample loss, timing corrections and supported signal-quality checks alongside the recording. Review flagged intervals and document your observations.
What accompanies the data into analysis?
Export per-modality CSV datasets with a codebook, manifest and data-quality report, giving collaborators a documented starting point for analysis.
Deployment
Built to fit your research setup.
- Where it runs
- Deploy under your institution's controls.
- Open-source foundations
- Built using open-source tools.
Configure
Define modalities, sampling, schedules and consent.
Collect
Acquire data from the sources supported for your study.
Review
Investigate quality flags and protocol deviations in context.
Export
Take per-modality data and its documentation into analysis.
- Per-modality CSV files
- codebook.csv · codebook.md
- manifest.json
- quality_report.json
Agree the deployment, data flows and researcher access for your pilot.
Participant-collected payloads are encrypted before upload, consent is recorded per modality, and researcher access is defined for the study. Metadata, annotations and logs do not all share the same encryption boundary — we will walk through exactly what applies where.
Self-hosting is a deployment model, not a compliance statement.
Device support, deployment and data handover are agreed for the proposed pilot.
Planning a wearable or mobile sensing study?
Tell us about your signals, study schedule and data requirements. Let's discuss technical fit and a possible pilot scope.
Discuss your studyOr write to contact@mh2research.com
We'll cover data sources, collection workflow, deployment constraints and an achievable scope. A study outline is enough — please don't send participant data.
We use your message only to answer your enquiry, and delete it 24 months after our last contact. The privacy notice explains your rights under the GDPR.