Platform
One approach behind every Nubiss solution.
Nubiss solutions are separate systems built on a common approach, not one product with four front doors. This page sets out the ideas they share, and which solution to reach for.
The common approach
Six ideas that show up in every product.
Structured data models
Named fields with defined types and permitted values — free text where it belongs, not as a substitute for structure.
Configurable protocols
Configured once, then followed. The definition is data, so changing it does not mean changing the software.
Longitudinal records
Sessions, visits, measurements and consultations accumulate against the same subject — a history, not disconnected entries.
Role-based collaboration
Access follows role and organisation; a request for another organisation's record returns not-found, never leaking that it exists.
Data-quality controls
Validation at entry, required items surfaced as tasks, review steps where a second pair of eyes is needed.
Auditability
A time-stamped change history, attributed to a named user, on a separate database whose records reject alteration.
Where each idea lives
Four solutions, four jobs.
The approach is shared; the products are not interchangeable. This is what each one brings to its own setting.
Nubiss Clinical
Treatment units and clinics
- Protocol definition with real clinical parameters
- Session, safety and assessment capture
- Patient-reported outcomes charted over time
- Scheduling, chambers and staff roles around them
- A FHIR R4 read interface over the clinical record
Nubiss StudyCore
Clinical trials
- Versioned case report forms and visit windows
- Edit checks, queries and source data verification
- Electronic signature bound to the data as signed
- Block randomisation, blinding, governed unblinding
Nubiss TelMed
German practices Germany only
- Structured doctor-to-doctor Telekonsil requests
- Rückfrage loop and linked written assessments
- Generated documents for both patient files
- Consent capture under § 367 SGB V
- FHIR R4 exchange with German profiles
Nubiss Longevity
Individuals and their clinicians
- A Longevity Score from eight measured daily signals
- Whoop, Oura, Apple Health and Health Connect data
- Blood biomarkers against reference ranges
- Protocols with daily adherence check-ins
How it runs
Separate systems, deliberately.
Each solution is its own application with its own database. A change to one cannot destabilise another, and a clinic running Nubiss Clinical is never exposed to a study team's activity in StudyCore.
The trade-off is honest: because they are separate, data does not flow between them automatically. The one link that exists — between Nubiss Clinical and Nubiss Longevity — covers account creation and sign-on only.
So there is no confusion
- No single shared data platform beneath the products
- No automatic data exchange or federation between them
- No cross-product or cross-organisation cohort comparison
- Capabilities described on one solution page belong to that solution — not automatically to the others
- The FHIR interfaces in Nubiss Clinical and Nubiss TelMed exchange data with external systems. They are separate interfaces and do not connect the Nubiss solutions to each other
Not sure which solution fits?
Tell us the workflow you need to support and we will point you at the right one — or tell you plainly if Nubiss is not the right fit.