Software of unknown pedigree
Software of unknown pedigree (SOUP) is a pre-existing software which development process or safety-related properties are not sufficiently documented or known.
SOUP in medical device software
The term SOUP is discussed in the context of safety-critical and high-integrity systems such as medical software – especially in a medical device. In the medical device development standard IEC 62304, SOUP is defined more specifically as software of unknown provenance and includes generally available software not originally developed for incorporation into a medical device, as well as previosuly developed software lacking adequate development process records[1].
SOUP poses a risk when used for safety-related functions. It may prevent other software, hardware, or firmware from performing their safety-related functions.[2] But classification as SOUP does not necessarily indicate that a software component is defective or unsafe.
Addressing this risk involves insulating the safety-involved parts of a system from potential undesirable effects. Rather than prohibiting SOUP, organizations often impose additional controls to mitigate risk. Practices may include static program analysis and review of the vendor's development process, design artifacts, and safety guidance.[3]
Under the IEC 62304, manufacturers must identify SOUP components used in medical device software and maintain appropriate configuration records. Depending on the applicable software safety class, additional activities include specifying functional and performance requirements, documenting the hardware and software environment needed for proper operation, and evaluating known anomalies that could contribute to hazardous situations.
These requirements are addressed in several clauses of IEC 62304, including 5.3.3., 5.3.4., 7.1.3., and 8.1.2[4].
SOUP and OTS/COTS
SOUP is closely related to the use off-the-shelf (OTS) and commercial off-the-shelf-software (COTS) software in medical devices. OTS refers to generally available software components, such as operating systems, third-party libraries, and other pre-exising components integrated into a medical device[5]. COTS is a commercialy supplied category of off-the-shelf software.
The terminology differs between regulatory and standarization frameworks. The U.S. Food and Drug Administration (FDA) primarly uses the term OTS[6], whereas SOUP comes from the IEC 62304.
Although these concepts overlap, they are not entirely interchangeable. OTS primarly decribes software availability and the manufacturer's control over its development lifecycle, while SOUP classification considers the software's original purpose and development documentation.
References
- ↑ "IEC 62304:2006". ISO. Retrieved 2026-11-09.
- ↑ Hall, Ken (June 1, 2010). "Developing Medical Device Software to IEC 62304". EMDT - European Medical Device Technology. Retrieved 2012-12-11.
- ↑ Hobbs, Chris (2011-11-01). "Device makers can take COTS, but only with clear SOUP". Medical Design. Archived from the original on 2013-01-23.
- ↑ "IEC 62304:2006". ISO. Retrieved 2026-11-09.
- ↑ "What is Software of Unknown Provenance (SOUP)?". Revolve Healthcare. 2024-04-16. Retrieved 2026-11-09.
- ↑ Health, Center for Devices and Radiological (2023-08-08). "Off-The-Shelf Software Use in Medical Devices". www.fda.gov. FDA. Retrieved 2026-11-09.
Further reading
- D. Frankis (2007-11-05). "Safety in the SOUP". Institution of Engineering and Technology Seminar on Pros and Cons of Using Commercial 'Off the Shelf' Components in Aviation Applications, London, UK, 4 Sept. 2007. pp. 9–21. ISBN 978-0-86341-801-3. ISSN 0537-9989.
Notes
This article is a direct transclusion of article and therefore may not meet the same editing standards as LIMSwiki.









