MEDTECH
Explain the adjustment.
During the treatment session.
Xpdeep models estimate evolving patient and device state, report attributed domain conditions and compute minimal feasible interventions under stated constraints, with structural justification. The clinician or authorized device system determines the action.
THE CLINICIAN OR AUTHORIZED DEVICE SYSTEM DETERMINES THE ACTION
01 PATIENT / DEVICE STATE
A treatment session is not one data point.
Its state evolves minute by minute.
Medical devices generate temporal signals that reflect both the patient state and the machine state.
Xpdeep can read which variables, temporal windows and signal morphology carry the model output.
ILLUSTRATIVE · SYNTHETIC SESSION SIGNALS
- MULTIVARIATE SESSION SIGNALS
- STRUCTURAL READING
- CURRENT STATE ESTIMATE
An explained estimate helps the clinician or authorized device system assess a feasible adjustment during the session.
02 DOMAIN
A clinical or device model should know
when the current case has moved
beyond what it learned.
Xpdeep can expose not only that the model has moved outside its trained domain, but which variables and temporal patterns drove that departure, whether the case remains inside known conditions.
TECHNICAL BOUNDARY: Domain information is a decision input, not clinical authorization. The clinician or authorized device system determines the action inside and outside the learned domain.
03 INTERVENTION
Prediction tells you what may happen.
Xpdeep computes what could change now.
PRIMARY INFERENCE
PATIENT / DEVICE STATE
PREDICTSTRUCTURAL EXPLANATIONCHECK DOMAIN
WHEN AN INTERVENTION IS USEFUL
PRESCRIBEJUSTIFY
CLINICAL / DEVICE DECISION
CLINICIAN OR AUTHORIZED DEVICE SYSTEM DETERMINES THE ACTION
Prediction and structural explanation share one forward pass. Prescription is a separate inference, invoked when useful on temporal and tabular stages.
Xpdeep computes a minimal feasible input change under stated constraints and returns the structural justification of why that intervention changes the predicted outcome.
IMPORTANT BOUNDARY
Structural, not automatically causal.
Minimal means minimal feasible under the specified constraints and optimization procedure, not a unique global optimum.
04 DEVICE INTELLIGENCE
The model can become part of the device
without becoming a black box.
- DEVICE SIGNALS
- XPDEEP MODEL
- PREDICTION + EXPLANATION + DOMAIN STATE
- DEVICE / CLINICIAN DECISION
WHERE APPLICABLE ON TEMPORAL / TABULAR STAGES → CONSTRAINED INTERVENTION → STRUCTURAL JUSTIFICATION
POTENTIAL VALUE SURFACES
- Explained adjustments during the session
- Explained device-adjustment inputs
- Device-function differentiation
- Intelligence that can be integrated across the installed base
- Customer-defined clinical or device KPIs
EMBEDDED
The intelligence can travel with the device.
Xpdeep models can run in cloud, on-premises or embedded environments, subject to customer profiling and integration.
- Prediction + explanation in one artefact.
- Where relevant: domain state.
- Where relevant: prescriptive output on temporal / tabular stages.
POTENTIAL ECONOMIC SURFACE: Intelligence that can be integrated across the installed base.
PROGRAMME EVIDENCE · SESSION-BASED TREATMENT DEVICE
A patient-state profile
you can inspect during the session.
DATA
Real session data read minute by minute from a treatment device.
MODELS
Two models built on real session data: one made patient-state profiles structurally understandable; the other computed feasible device-parameter interventions and explained their predicted effect.
PLATFORM
Core model capabilities used in the programme are live.
Decisions remain with the clinician or the authorized device system. On time-series data, Xpdeep models achieve accuracy at least equivalent to standard deep learning and frequently superior.
MedTech engineering boundaries.
EXPAND
- Clinician or authorized device-system control applies inside and outside the learned domain.
- Prescription applies to temporal and tabular stages; image-level prescription not available; under study.
- “Explainable abstention” is not a live capability.
- Structural integration requires read access to the PyTorch architecture and weights, or a Native model.
- The customer’s surrounding system defines and authorizes actions.
- Attributed domain state covers the retained model inputs; alone, it does not authorize action or establish system safety.
- Structural justification does not automatically establish physical causality.
- Minimal means minimal feasible under the stated constraints and optimization procedure.
- Targeted editing and controlled correction require Native mode.
- Regulatory approval, clinical validation and certification remain with the customer and relevant authorities.
- Reduced requalification scope requires application-specific evidence and acceptance.
START WITH ONE MEDTECH DECISION
Start with a patient or device decision
you already measure.
PATIENT STATE
A temporal model tied to session or physiological state
DEVICE STATE
A learned model tied to equipment or treatment behavior
TREATMENT ADJUSTMENT
A bounded temporal / tabular decision about what could change
DOMAIN VALIDITY
A model that needs explicit awareness of when the current case leaves known conditions
EMBEDDED MODEL
A model intended to travel with the device or installed base
Run an Xpdeep model alongside your existing model for an agreed number of weeks. Compare performance on the same data against agreed KPIs, using your own validation chain.
An Xpdeep model is a PyTorch model with a different architecture. Customers can validate it using their own tools and test processes.
01 →
One funded decision
A model or decision loop the business already owns.
02 →
Agreed comparison
Data, duration and KPIs defined at scoping.
03 →
Evidence on your application
Side-by-side results using the customer’s validation process.
04
Define the extension
Identify the possible Phase 2 scope at the start; use Phase 1 evidence to determine its scope.