Confluence is more than a document storage platform. When properly structured, it can provide a connected quality environment in which procedures, forms, records and technical documentation remain accessible, interlinked and integrated into the company’s daily activities.
1. Connect procedures, forms and references
Each procedure can contain direct links to:
- the forms required to perform the process;
- applicable standards and regulatory guidance;
- related QMS processes;
- the records generated by the process;
- the relevant sections of the technical documentation.
Users no longer need to search through multiple folders to locate the correct form or reference. They can navigate directly from the process to the resources required to perform it.
These links also make the interactions between the different QMS processes more visible.
2. Create meaningful traceability between documents
Confluence pages can be linked to connect, for example:
- user needs;
- product requirements;
- identified risks;
- risk control measures;
- design specifications;
- verification and validation activities;
- product changes;
- decisions made during design and development reviews.
This organisation is particularly useful for medical device software, connected devices and products whose documentation changes frequently.
It also makes navigation easier during audits and documentation reviews.
3. Integrate the QMS with activities managed in Jira
When the development team uses Jira to manage development activities, requirements, anomalies, tasks or software releases, Jira work items can be displayed or referenced directly within Confluence.
This integration can help connect:
- development activities;
- software requirements;
- anomalies and corrections;
- actions arising from risk analyses;
- verification activities;
- change requests;
- CAPAs, where managing them in Jira is appropriate.
This is particularly relevant for manufacturers of medical device software because it reduces the separation between quality documentation and the development team’s actual work.
The integration must nevertheless be clearly defined and validated to establish which system is the official source for each type of information.
4. Maintain a robust version history
Confluence creates a new version whenever a page modification is published. The version history can be used to:
- identify the author and date of a change;
- view a previous version;
- compare two versions;
- identify what was modified;
- restore an earlier version.
This history provides a solid foundation for document control.
However, version history alone does not replace a QMS review and approval process. The organisation must still define document statuses, responsibilities, approval rules and the method used to identify the officially applicable version.
5. Organise reviews, approvals and electronic signatures
Applications available through the Atlassian Marketplace can extend Confluence with:
- review and approval workflows;
- controlled document statuses;
- identification of reviewers and approvers;
- electronic signatures;
- approval records and activity reports;
- periodic review reminders.
These applications allow the lifecycle of procedures and other controlled documents to be managed directly within Confluence.
The applications and their configuration must be appropriate for the organisation’s requirements. When their use can affect QMS compliance or product quality, validation should be considered using a risk-based approach.
6. Export documentation for audits and submissions
Individual Confluence pages can be exported, including to PDF or Microsoft Word. All or part of a Confluence space can also be exported.
This functionality can be used to prepare documentation packages for:
- a notified body;
- a competent authority;
- an auditor;
- a business partner;
- a customer or distributor, where appropriate.
A space dedicated to technical documentation can therefore be exported to prepare a submission or assessment package.
The quality of the export must still be verified, including the presence of attachments, the functioning of references and the readability of tables. When evidence of approval does not appear in the exported document, the approval workflow activity report should be included with the PDF.
7. Reuse common information without duplicating it
The Excerpt, Insert Excerpt and Include Content macros allow information to be defined in one location and displayed on multiple pages.
This functionality can be used to manage shared information such as:
- manufacturer identification;
- the manufacturer’s official address;
- device descriptions;
- intended purpose;
- definitions;
- responsibilities;
- device classification;
- information shared by several documents;
- common regulatory references.
When the source information is updated, the pages displaying it automatically show the revised content.
This approach reduces duplication and the risk of inconsistencies between the QMS, risk management documentation and technical documentation.
Its use must nevertheless remain controlled. Historical information that must remain fixed within an approved record should not be unintentionally replaced by dynamic content that is updated later.
8. Use spreadsheet-style tables
Applications available through the Atlassian Marketplace can add spreadsheet-style tables to Confluence, including, depending on the selected application:
- formulas;
- filters;
- sorting;
- calculations;
- charts;
- pivot tables or consolidated views.
These functions can be useful for managing:
- approved supplier lists;
- training registers;
- audit programmes;
- quality objectives;
- CAPA and change-control registers;
- traceability matrices;
- risk analyses;
- quality indicators;
- post-market surveillance plans.
When a table performs calculations or contributes to a quality or regulatory decision, its functionality and formulas should be verified and, where necessary, validated.
9. Standardise records through templates
Confluence allows organisations to create page templates so that users work from a consistent, approved structure.
Templates can be developed for:
- audit reports;
- CAPAs;
- change requests;
- design and development reviews;
- supplier evaluations;
- validation reports;
- management review minutes;
- post-market surveillance plans and reports.
This standardisation improves the completeness and consistency of records and reduces variation between users.
10. Generate registers and summary dashboards
Content Properties, labels and reporting macros can retrieve information from multiple pages and display it in a central table.
This makes it possible to generate consolidated views such as:
- a list of open CAPAs;
- the change-control register;
- supplier evaluation status;
- documents approaching their review date;
- outstanding audit actions;
- ongoing validation activities;
- the status of technical documentation deliverables.
The detailed information remains within each individual record, while the summary table is generated from the source data.
11. Manage access rights according to responsibilities
Permissions can be organised at site, space and, where necessary, page level.
The organisation can therefore distinguish between:
- QMS administrators;
- document authors;
- reviewers and approvers;
- read-only users;
- development teams;
- external consultants or auditors;
- confidential information requiring restricted access.
This allows the QMS to remain collaborative without granting every user the same modification rights.
12. Improve search and navigation
A consistent page structure, naming convention, use of labels and centralised search functionality make it easier to locate a procedure, form or record.
The page hierarchy can also reflect the organisation of the QMS:
- quality processes;
- procedures and forms;
- quality records;
- CAPA and continuous improvement;
- device-specific documentation;
- Design and Development File;
- Medical Device File;
- MDR or IVDR technical documentation.
This architecture is generally easier to navigate than a succession of folders and subfolders containing files with similar names.
13. Improve collaboration between functions
Comments, mentions, notifications and tasks facilitate communication between Quality, Regulatory, Engineering, Clinical, Operations and Management.
Discussions relating to a document can remain associated with the relevant page instead of being distributed across emails and meeting notes.
This proximity facilitates reviews, issue resolution and the retention of the context in which decisions were made.
14. Clearly separate active documents, records and technical documentation
Separate spaces can be used for:
- active QMS procedures, forms and references;
- records generated through the execution of QMS processes;
- CAPA and continuous-improvement activities;
- technical documentation for each device.
This separation helps users distinguish between a blank form template and a completed record, or between an active procedure and a historical document.
It also improves the clarity of the system during an audit.
15. Allow the QMS to evolve progressively
Confluence allows an organisation to begin with a structure proportionate to its current activities and progressively add:
- new devices;
- additional processes;
- dedicated spaces;
- more advanced workflows;
- dashboards;
- Jira integrations;
- specialised applications.
This scalability is particularly valuable for startups that want to avoid migrating their entire QMS when the organisation grows.
A flexible platform, but not an automatically compliant QMS
Confluence provides a collaborative environment, version history, links, templates, permissions and integration capabilities.
However, these functions do not automatically make a QMS compliant with ISO 13485, the MDR or the IVDR.
The manufacturer remains responsible for:
- defining its processes;
- adapting the procedures to its activities;
- assigning responsibilities;
- configuring permissions and workflows;
- training users;
- controlling quality records;
- validating applications where necessary;
- periodically evaluating the effectiveness of the system.
Confluence provides the technical environment. Compliance depends on how the QMS is designed, implemented, used and maintained.