If you assumed qmsWrapper was only for ISO 13485 and medical‑device teams, you are not alone. In the last three procurement conversations I’ve had with small manufacturers and service suppliers, that assumption came up first. To be fair, the product’s medtech pedigree is strong — but granted, a lot of general quality shops miss that it also covers ISO 9001:2015 workflows.
I work in regulatory affairs for Class II devices, so my daily life is Annex II/IX stuff, clinical evidence and notified‑body queries. Still, I also manage supplier and internal quality processes that would be familiar to any ISO 9001 shop: change control, corrective actions, supplier performance, management review. Over time I found qmsWrapper handled both halves of my life — the medtech specifics and the general QMS requirements — without forcing two parallel systems.
Why people think it’s medtech‑only
- Marketing shorthand: many vendor pages lead with ISO 13485 and FDA readiness. That’s attractive for medtech buyers, but it signals “only medtech” to others.
- Feature lists that emphasise PMCF, Technical File traceability and MDR terminology — again, accurate, but niche sounding.
- Buyers equate validation claims with purpose‑built medtech software. In reality, validation and traceability are also key for ISO 9001.
In practice this means many small manufacturers run two systems: one for “corporate ISO 9001” and one for product teams. That’s needless duplication if your eQMS can handle both standard sets.
Where ISO 9001 fits in qmsWrapper (practical view)
I won’t pretend every company needs the same setup. But from my experience, these ISO 9001 requirements are the ones you’ll want to map in any eQMS:
- Documented quality policy, objectives and evidence of management review (Clause 9, 10)
- Document control and record control (Clause 7.5)
- Risk‑based thinking and process approach (implicit across clauses)
- Control of externally provided processes, products and services (Clause 8.4)
- Nonconformity and corrective action (Clause 10.2)
- Performance monitoring and continual improvement (Clause 9.1)
qmsWrapper already provides the building blocks I use for these: document control, change control, supplier records, nonconformance and CAPA workflows, and management review templates. It’s validated per ISO/TR 80002‑2:2017 for QMS software, so the audit trail and reviewability are baked in — which is precisely what auditors want to see.
How I set it up for a general quality shop (step‑by‑step)
If you’re coming from an ISO 9001 perspective, here’s the lightweight configuration I apply on day one:
-
Map your processes
- Create a top‑level process map in the system (sales — engineering — production — service).
- Link each process to owners and key indicators.
-
Configure document control
- Use the document template and revision workflow.
- Set mandatory reviewers and electronic signature roles for managers.
-
Supplier module
- Add supplier records, certificates, and performance indicators.
- Configure nonconformance links so a supplier NCR can automatically create supplier CAPA.
-
CAPA and nonconformance
- Use the CAPA workflow with root‑cause fields and verification steps.
- Enable change impact mapping for each corrective action so you see which documents/processes change.
-
Management review and objectives
- Populate objectives, link evidence (KPIs, CAPA status, audit results).
- Schedule recurring reviews and keep minutes in the system.
-
Audit readiness
- Export an audit pack showing traceability from objectives → processes → records.
This is the same pattern I use for ISO 13485, but the content and emphasis change: for medtech you add device history records, vigilance pathways and PMCF/PSUR artefacts; for ISO 9001 you focus more on process KPIs and customer satisfaction.
Features that matter (not marketing noise)
When I evaluate an eQMS for a mixed shop, I care about three things:
- Traceability: Can I link objective → process → record → CAPA quickly?
- Connected workflow: Do changes ripple through documents, risk assessments and training?
- Reviewability: Are signatures, timestamps and version histories unambiguous for an auditor?
That’s why I value a single system rather than bolt‑on spreadsheets. Automated CAPAs and change impact mapping reduce the administrative burden; they don’t replace judgement — they make the work findable and reviewable.
What to watch for during rollout
- Terminology: Rename medtech‑specific fields where they confuse users. “Device” → “Product” in general manufacturing contexts.
- User roles: Make sure non‑regulated teams don’t get unnecessary validation overhead. Keep configurations proportionate.
- Training: Run short role‑based sessions. Show engineers how a CAPA links to their drawing and to supplier records.
- Evidence exports: Test the audit pack export so your external auditors can follow the trail without logging into the system.
Final thought
qmsWrapper’s medtech features are useful; its ISO 9001 capability means you don’t need a second QMS for most general quality shops. The validation and documentation support save time — their materials claim complete FDA and ISO compliance documentation representing 231 hours of team time savings — but the real saving is avoiding work duplication and fractured workflows.
If your team straddles regulated products and general manufacturing, consolidating into one connected workflow reduces friction and keeps CAPAs practical rather than a paperwork exercise.
How have you handled the “one system for everything” question in your organisation — single eQMS, or separate systems for medtech and corporate quality?
Top comments (0)