Medical apps on smartphones and smartphone-like platforms are driving growth in medical devices development. Are the tools available now adequate to deal with the serious safety and security issues involved?

The authors describe the software development of an FDA compliant Class III medical software application that was successfully ported from a Windows CE environment to an Android 4.1 tablet platform.

In the second in a two-part series, the authors describe the lessons learned about how to coordinate in-house and out-source components and expertise without affecting design goals.

How existing languages for Programmable Logic Controllers (PLCs) can be extended with domain-specific constructs for medical devices and used to generate native code that runs on both Intel and ARM processors.

Medical devices should be of interest to any embedded software developer as they encapsulate a great many of the techniques that characterize modern embedded systems development.

A Body Area Network (BAN) gateway to Android mobile phones for mobile health applications based on a Secure Digital Input Output (SDIO) interface.

Analysis of the security of software that controls a modern Automated External Defibrillator (AED) used for cardiac arrhythmias revealing several vulnerabilities including acceptance of counterfeit firmware updates.

Ravi Patel describes a holistic approach to the systems engineering and software development of a medical device.

A data-centric sensor fusion architecture is essential for building situationally-aware applications.

In this Product How-To design article, Jay Abraham of Mathworks uses the company’s Polyspace code verifier to explain the use formal methods-based static code analysis to ensure high quality and verifiable embedded software.

Researchers at the FDA's Office of Science and Engineering Laboratories investigating new techniques for analyzing software in medical devices are using static analysis tools to uncover potential flaws in a device under review.

How to use formal methods”based abstract interpretation techniques to mathematically prove the absence of a defined set of run-time errors and a comparison with techniques as code review, static analysis, and dynamic testing.