License first, collect the gap.
We match your need against rights-cleared inventory, our own and partner-sourced. What exists is licensed, with traceability from dataset to consent and licence basis. Only the missing part is collected.
Healthcare · Clinical data collection
The data your clinical model needs does not exist yet.We collect it.
Consultation speech, dictation and command audio, cardiology signals, procedure video, wearables and biosignals. Nordic clinical language cannot be scraped at volume, so collection is the only source.
Why clinical collection
Three questions decide whether your model ever sees clinical data.
Clinical data cannot be scraped, bought casually, or borrowed from a benchmark. Whether your program gets it comes down to consent, reach and custody.
-
Does this data exist to buy?
Mostly, no. Real consultations, dictations, cardiology traces and procedure footage are not lying in a marketplace. Where a rights-cleared corpus exists we license it; where it does not, collection is the only source, and we produce only the gap.
-
Will the consent survive our DPO?
Every contributor consents to a stated purpose, under GDPR Article 7, with Article 9 handling where biometrics are involved. The consent record, the withdrawal path and the audit trail ship with the data, not after it.
-
Can you reach this cohort?
Native-speaker contributors, in the languages and settings the model will see: the clinic, the home, the device chain. Quotas and QA are written before capture starts. You judge the files against that, not against a promise.
The modalities
What we capture for clinical AI teams.
Four capture programs we scope most often. Cohort, setting, devices, languages and QA are set per engagement, never assumed.
-
Clinical speech, dictation and commands
The encounters, dictations and spoken commands a clinical voice model must learn from.
Consultation-style dialogue, clinician dictation and command audio from native-speaker contributors in Danish, Norwegian, Swedish, Finnish and the other languages your deployment needs. Consent and rights controls configured for the engagement; diarization and clinical-terminology transcription on request.
-
Cardiology signals
Rhythm and imaging signals for models that watch the heart.
ECG traces and echocardiography recordings captured or sourced where the rights setup holds, timestamp-aligned and delivered against your schema. Annotation by credentialed reviewers is available as a second engagement.
-
Procedure and endoscopy video
What the camera sees in a procedure, captured under the clinic's own rules.
Procedure and endoscopy video collected in clinical environments with ethics, rights and de-identification boundaries agreed before a single frame is captured. Segmentation and annotation live on the imaging route.
-
Wearables and biosignals
The signals a remote-monitoring model lives on, from consented contributors.
Wearable, IoT and environmental sensor streams for monitoring and anomaly-detection programs: self-hosted ingestion plus consent-anchored contributor recruitment, calibrated and timestamp-aligned for training.
- 210,000+ contributors
- 50+ countries
- 150+ languages, including all Nordic
The collection run
One run, five stations. Green only where a person confirms.
Every collection program moves through the same stations. The record accumulates as it goes; nothing reaches delivery without the confirmations that let you defend it.
-
The specification, written with you
Cohort, setting, device chain, languages, quota and QA criteria in one document you sign off before capture starts.
SPEC · AGREED -
A person, consenting to a purpose
GDPR Article 7 consent per contributor, Article 9 handling where biometrics are involved, withdrawal path documented.
CONSENT · ON RECORD -
The clinic, the home, the device chain
Captured in the agreed environments with the agreed devices, staged to quota, edge cases included by design.
TO SPEC · LOGGED -
A reviewer rules on every batch
Agreed quality criteria applied per batch, exceptions surfaced, the ruling recorded.
QA · RULED -
Files with their paperwork
Delivery against the schema with the consent record, the audit trail and lineage on every file.
DELIVERED · WITH LINEAGE
Stations are the engagement's structure, not a live record. Scope, quotas and QA stages are set per engagement.
Before we collect
If the data exists, you should not pay to collect it.
Synthetic, where real data cannot go.
Where privacy, scarcity or consent constrains real data, synthetic clinical data is generated against a defined distribution and calibrated against real-data baselines, with the utility-versus-privacy trade-off stated, not hidden.
Custody
Collected in the clinic. Kept in the strictest room.
A Norwegian company under GDPR. Clinical project data is stored in Europe by default and processed in the EEA where required, with the paperwork to prove both. US healthcare work is handled HIPAA-compliant.
- Jurisdiction
- Norway · GDPR-native
- Storage
- European by default
- Processing
- EEA where required
- Consent
- Documented per contributor
- US engagements
- HIPAA-compliant handling
- Contracts
- Standard DPA terms · SCCs available
- Erasure
- 30-day end-of-contract SLA
- Withdrawal
- Workflow with audit trail
The healthcare hub Clinical AI systems Clinical model evaluation Clinical text and coding Medical imaging annotation Safeguards for US healthcare speech work De-identifying clinical audio
Scope a program
Start with one cohort, one setting, one modality.
We scope against your model program, write the specification with you and prove the pipeline on a pilot batch before full capture.
- Scope
- Specification
- Pilot batch
- Acceptance
- Full capture
A bounded pilot carries its own acceptance criteria. You judge the files against what was agreed, not against a slide.
Briefs are treated as confidential. We are used to data that cannot leave the EEA and programs that cannot be named.
Image 10 · the bench edge, the channel as a floor line
The brief Tell us the model program, the modality and the languages or signals you need. We reply with a feasibility read.