Glossary · ISO and IEC standards for MedTech and pharma
Software of unknown provenance (SOUP)
Also known as: SOUP, Software of unknown pedigree
German: Software unbekannter Herkunft
In IEC 62304, software of unknown provenance (SOUP) is a software item that is already developed and generally available and that has not been developed for the purpose of being incorporated into the medical device, or a software item previously developed for which adequate records of the development processes are not available. Operating systems, libraries and open-source components are typical SOUP.
- Standards
- EU
- USA
- Technical documentation
In one sentence
SOUP (IEC 62304): software items not developed for the device, or without adequate development records, such as libraries and operating systems.
Example
A wearable ECG app uses an open-source signal-processing library and a mobile operating system; both are listed as SOUP with their versions, the functional and performance requirements the device relies on, the known anomalies and the risk analysis of their failure.
Explained in context
This term is a station of a mini course
- The medical-device evidence chain: from intended purpose to post-market evidenceStation: Software lifecycle and SOUPStart the course
Context cards connect this term with others to answer one question. Also in British English and German.
- The medical-device evidence chain: from intended purpose to post-market evidenceHow do the parts of a medical device’s technical documentation connect — and what has to be in place before an AI function may answer from it?UKDeutsch
- Model version, software version, device version: three numbers that are not the sameWhat is the difference between the model version, the software version and the device version of an AI-enabled medical device?UKDeutsch
How it applies
- What IEC 62304 asks: Identify each SOUP item with its title, manufacturer and unique designator (version); state the functional and performance requirements the device needs from it and the hardware and software it requires; evaluate the published anomaly lists; and analyze, in the risk management, how its failure could contribute to a hazardous situation.
- Configuration and change: SOUP items are configuration items. Updating a library is a software change with its own impact analysis.
- Security: An SBOM lists components for vulnerability management; IEC 81001-5-1 adds security activities. The SOUP list and the SBOM overlap but serve different questions.
- Technical documentation: Release notes and the IFU's system requirements often depend on SOUP (supported operating system versions, browsers). Derive them from the SOUP list, not from memory, and update them with each SOUP change.
SOUP vs. SBOM
A SOUP list is a safety record: which third-party items the device relies on, for what, and what happens if they fail. An SBOM is an inventory of components and versions for supply-chain and vulnerability purposes. A complete SBOM doesn't replace the SOUP risk analysis.