Six service categories. One controlled loop underneath.
Whatever the engagement, the method is the same — every technology assessed against the same seven regulatory perimeters, with the reasoning recorded rather than asserted.
regulatory perimeters — assessed in every engagement, whichever service line
6
service categories — entered at different points of the study
5
steps in the loop: inventory, assess, register, monitor, re-assess
2–3 weeks
to a Snapshot Regulatory Impact Assessment (RIA) — the usual way in
Six ways in. One method underneath — the same loop, the same seven perimeters, whichever line you engage.
Six service lines, one method underneath
Every engagement runs the same controlled loop — Inventory, Assess, Register, Monitor,
Re-assess — across the same seven regulatory perimeters. What changes between categories is
where in the lifecycle you are and which obligations dominate, not how the decision gets made.
That matters commercially: you can start with one device on one protocol and expand into full
portfolio governance without ever re-doing the groundwork, because the register you build in week
one is the register you keep.
Buyers think in study phases. This is where each line enters and how far it runs — DHT in Trials in teal, because it is the one that spans the study and the one most engagements start with.
How to choose the right supporting capability
The practice is DHT governance — governing the digital health technologies a clinical trial
relies on. The five supporting capabilities below are where the loop finds work that has to be
closed: quality systems that cannot evidence the decision, software that was never validated,
an economic-operator role nobody accepted, participant-facing technology that changes what the
data means, or a transformation programme that introduced regulated systems without a register.
Most engagements start with DHT
governance in trials because that is where the device inventory and the Snapshot assessment
live. The other capabilities are engaged when the assessment names a gap — not because a
checklist says you should buy five things at once.
Quality & Regulatory Assurance — when the quality system, technical
documentation or submission needs to match what the device decision requires.
Regulated Software & Data Systems — when validation, data integrity or
the AI Act conformity route is the binding constraint.
EU Authorised Representative — when EU market access or trial supply
creates a manufacturer, importer or AR obligation you have not staffed for.
Patient Engagement — when participant-facing technology changes endpoint
reliability, deviations or missing data.
Digital Transformation — when the same controls must run across an entire
clinical operation, not one device.
What we do
Digital Health Technologies in Trials
End-to-end DHT governance: compliance assessment, regulatory classification, fit-for-purpose validation, logistics and lifecycle, data interoperability, training and inspection readiness. The core service, and where most engagements start.
QMS implementation under ISO 13485:2016 and the FDA QMSR (21 CFR Part 820, in force since 2 February 2026), pre-market submissions, risk management to ISO 14971, gap analysis and CAPA, supplier engineering, post-market surveillance, audits, mock inspections and PRRC services.
Medical device software under IEC 62304, computer system validation under GAMP 5, 21 CFR Part 11 and EU GMP Annex 11 compliance, ALCOA+ data integrity programmes, and the move from document-heavy CSV to risk-based CSA.
Education, remote monitoring, support programmes and patient-reported outcomes — designed around human factors and use safety, so participants stay in the study and the data keeps arriving.
Full-scope EU AR services for non-EU manufacturers under EU MDR 2017/745 and IVDR 2017/746 — EUDAMED registration, technical documentation review, vigilance and the accountable economic-operator role.
Moving sponsors and CROs from fragmented, paper-heavy or partially validated environments to a single controlled loop covering every DHT, eClinical system and data flow. Five gated, fixed-fee phases, with regulatory and quality running as a workstream rather than a review at the end.
Each has a moment. Three of the six route to DHT governance — which is why most engagements start there. The register is what lets you see one coming rather than read about it in a finding.
Where a device usually goes wrong
Six situations that bring sponsors to us. If one of them is familiar, you already know which service line you need.
A firmware or app update lands mid-study
Someone has to decide that week whether it needs documentation only, bridging evidence or full revalidation — and defend that call later.
The data lands in the vendor’s cloud, not in your trial
Raw readings sit under the vendor’s retention rules while the eClinical backbone waits. Data integrity expects you to control provenance from sensor to submission — not to inherit it.
The study ends and the devices come home — with data on them
Return, wiping and disposition are part of the device lifecycle. A handset with subject data in a courier bag is a privacy finding waiting to be written.
Capabilities differ; artefacts do not. Every run of the loop produces the same controlled
documents — versioned, attributable, and indexed so an inspector, a notified body or your own
quality team can find the reasoning without asking us for it:
A recorded decision per perimeter, with the residual uncertainty named.
A trigger register — firmware, app, OS, algorithm, supplier, protocol and
country changes that would reopen the assessment.
An evidence index that links requirements to tests, records and owners.
That is what makes a supporting capability expandable: the register you build for one device
in week one is the register you keep when the portfolio grows.
Two papers behind the practice
A free account opens both — no approval step, no sales call attached.
qointa's full service portfolio across quality management, regulatory compliance, software development, contract research, patient engagement and digital transformation.
