How do you design a connected medical device when different parts of the system evolve at very different speeds?
Medical devices can remain in the field for years. Meanwhile, cloud services, APIs and security threats can change far more quickly.
In the short video below, Dan Talmage, Head of Software at TTP, explores why lifecycle thinking needs to be built into the architecture from the outset, including defining which parts of the system can change independently and designing for cybersecurity vigilance.
For connected medical devices, planning for change is not something to leave until after launch. It starts with how the system is designed.
