Innovation Lab
Ottobock Innovation Lab is the entry point for early-adopter sites that want to test connected mobility workflows, remote fitting support, patient follow-up dashboards, and service intelligence without losing sight of privacy, procurement, or staff capacity.
Every pilot starts with a care pathway definition: who enrolls users, what data is reviewed, how clinicians respond, what caregivers receive, and how escalation is documented. This prevents innovation from becoming an unowned data stream.
Security planning covers SBOM expectations, access roles, encryption, vulnerability response, and documentation needed by hospital IT teams before connected devices are introduced to a clinical environment.
Pilots define mobility, adherence, service, and satisfaction metrics before launch. The goal is to answer a practical clinical question, not simply deploy technology for its own sake.
Rehabilitation hospital, prosthetic clinic, veterans network, or home health program.
Identify data fields, system interfaces, consent workflow, and security documentation.
Pair product scope with clinician education, caregiver material, and support coverage.
Track usage, workflow friction, service events, and clinical feedback against the plan.
Review evidence, economics, staffing burden, and procurement readiness before expansion.
The strongest pilot sites are ambitious and careful. They want to improve patient mobility, but they also need biomedical engineering, IT security, procurement, and clinical leadership to agree on a controlled plan. Ottobock keeps those stakeholders in the room from the beginning.
That approach makes the Innovation Lab useful for both small proof-of-concept projects and larger multi-site programs. A pilot can start with a narrow device cohort, then expand when training burden, service capacity, and outcomes justify the next step.
Submit Pilot RequestOttobock asks pilot sites to define the measurement method before enrollment. A typical protocol uses a 90-day window, a named clinical owner, and a pre-agreed data dictionary so results can be reviewed by procurement and privacy teams.
| Element | Example pilot definition | Why it matters |
|---|---|---|
| Cohort | 20-40 adult users on one microprocessor knee or orthosis family | Keeps training and service load measurable |
| Primary endpoint | Completed follow-up reviews within 30 days post discharge | Tests remote-care workflow, not marketing anecdotes |
| Secondary measures | Usage-hour completeness, service ticket age, caregiver teach-back pass rate | Separates device issues from staffing issues |
| Data path | De-identified CSV plus optional HL7 FHIR observation export | Supports IT review without forcing full EHR write-back on day one |
| Security package | SBOM, role matrix, encryption summary, vulnerability contact | Required before connected devices join a hospital network |