Ortopedico
A brace that talks to your doctor
An app for a smart orthopedic brace: sensor readings, data sharing with a specialist and peer-to-peer video teleconsultation in one place. Ortopedico is a company from Olsztyn, founded in 2020. It is developing a smart brace with sensors that measure pressure, joint angle and position. The brace comes with a free app through which patients share their data with a doctor. Our job was the software layer: the app, data transfer and teleconsultation.
Rehab data stopped at the follow-up visit.
- Data stopped at the appointment. The specialist could only see the patient's condition in the office. Between follow-up visits, there was no insight into what was happening with the limb.
- Two audiences for the same data. Patients need a simple picture, doctors need detailed readings. One app had to serve both needs without cluttering the screen.
- Connecting hardware and software. The brace's sensors generate data that has to be received, organized and displayed. Every link in that chain has to work reliably.
- No course correction between visits. Without contact with a specialist, patients had no one to ask about their current readings. Remote conversations had to be possible.
- Security and consent. This is health data. Transmission had to be secure, and sharing data with a doctor had to be based on the patient's explicit consent.
Brace, app and video consultation as one product.
- The app as a bridge. We built an app that receives data from the brace and passes it on. Patients do not have to export or retype anything. All they need to do is wear the brace and keep their phone nearby.
- Consent-based sharing. The patient decides who sees their readings. A specialist's access stems from the patient's informed decision, not from default settings.
- Teleconsultation in the app. Video runs inside the same app, on WebRTC. Patients do not install a separate messenger or switch between programs.
- Peer-to-peer connection. Video and audio flow directly between devices. The server only sets up the connection, so no recording of the call ends up on the server.
- STUN and TURN for difficult networks. Home routers and mobile networks often block direct connections. STUN and TURN servers make it possible to establish the call even under those conditions.
- A combined view for the specialist. The doctor sees the patient on video and their sensor readings at the same time. They can compare what the patient says with what the data shows.
- Sensor readings. The app shows data on pressure, joint angle and position. Patients see it in a simple form, without raw numbers front and center. Detailed values are available in the specialist's view.
- Sharing data with the doctor. The patient selects a specialist and consents to access to their readings. The doctor can view the data between visits too.
What we built it with.
How it came together.
Analysis
We established what data the brace sends, who needs it and in what form. We documented the requirements for consent and transmission security. We also mapped the patient's journey from putting on the brace to the first conversation with a specialist.
Patient app
We built a mobile app that receives readings and presents them in an easy-to-understand form. We added a mechanism for sharing data with a specialist. We designed the screens for people who do not need to be tech-savvy.
Teleconsultation
We implemented WebRTC video with STUN and TURN servers. The server sets up the connection, but the call itself runs directly between the parties.
Specialist view
We built a screen where the doctor sees the call video and the patient's data at the same time. A shared API and backend tie it all together.
What changed.
See other projects.
Do you have a device that collects data?
We will design an app that turns readings into real value for users and specialists. If you are building a device with sensors, its value depends on what happens to the data. Hardware without a well-designed app remains a gadget. It pays to plan from the start who views the data, on what basis and in what view. With sensitive data, a peer-to-peer architecture and explicit consent often solve more problems than extra security on the server.
Let's talk about your product →