In a standard operating procedure (SOP), companies define their processes, for example how they develop medical devices or provide services.
Standards such as ISO 9001 and ISO 13485 require standard operating procedures. Companies can define these specifications in their quality management manual directly or in independent documents.
ISO 9000 defines a procedure as follows:
“Specified way to carry out an activity or a process”
Source: ISO 9000:2015 3.4.5
ISO 9000 defines a process as follows:
Definition: Process
"Set of interrelated or interacting activities that uses inputs to achieve an intended output."
Source: ISO 9000:2015 3.4.1
A standard operating procedure thus documents how a company (e.g., a manufacturer) intends to carry out an individual activity or a process (set of activities). The terms standard operating procedure and process description are to be understood synonymously.
Based on the above definitions, a standard operating procedure is equivalent to a process description when describing several interrelated or mutually influencing activities
A process description includes the description of the entire process, e.g., software development process. It defines phases, roles and activities. For example, it requires a software system test at the end of development. How, i.e., with which methods, these tests are carried out (e.g., with equivalence classes) can be part of a referenced work instruction or standard operating procedure.
Work instructions and standard operating procedures differ concerning several aspects:
Table 1: Difference between work instructions and standard operating procedures
The standard operating procedure should describe:
If the description of the activity and method is more comprehensive, we recommend moving this to a work instruction.
In contrast to a work instruction, a standard operating procedure generally describes a required sequence of activities that are often performed by several people.
Johner Institute consultants and auditors generally use the following chapter structure
Use flow charts. They give you a quick overview.
Various modeling languages such as UML activity diagrams, BPMN and classical flow charts can be used. Numerous tools, including free tools (e.g., draw.io), are available.
Fig. 1: Example of Flowchart in a SOP
Tables are an alternative way of showing the information. These are only suitable for sequential processes.
Step | Input | Activity | Output | Role | Comment |
1 | Use scenarios | Specification of the software requirements | Software requirements specification. | User interface designer |
Table 1: Example of section of a tabular description of a procedure
The requirements which SOPs manufacturers have to define and follow can be found in these regulations, among others:
Standards, such as ISO 13485, requires companies to [have] procedures, such as document control, design and development planning, procurement and corrective actions.
Fig. 2: Standard operating procedures required by ISO 13485. Our free starter kit contains this mind map as an enlargeable PDF.
A more general list of the procedures required in given in English below:
The free starter kit includes the above mind map and an infographic that tells you the standard operating procedures that you have to complete or revise to fulfill the requirements of ISO 13485:2016.
Strictly speaking, these standards (e.g., ISO 13485) require that the manufacturers
all the above procedures.
Note that ISO 13485 requires many other activities, but they do not necessarily have to be described by a standard operating procedure.
MDR resp. IVDR requires fewer standard operating procedures than ISO 13485. On the other hand, there are procedures that manufacturers must define according to MDR and IVDR, which ISO 13485 does not mention explicitly, for example, risk management.
It should be noted that ISO 13485 does require risk management as an activity.
Conclusion: If you act in accordance with the current edition of ISO 13485, you fulfill the essential quality management requirements of MDR and IVDR, Article 10 and Annex IX.
There are arguments in favor of integrating these standard operating procedures directly into the QM manual, and there are arguments against it. Arguments against the integration of standard operating procedures into the quality management manual are:
But separating the QM manual and SOPs is not always the best solution. Small companies with only one or a few products are sometimes better served by an integrated document set.
Are you unsure which option is best for you? Please feel free to contact us. We're happy to help.
Common abbreviations are often used in the standard operating procedure to clarify the document. All abbreviations used should be noted separately in a document. Examples: