In this guide 6 sections
Buy a QMS tool for document control, complaints, CAPA and audits, then build shop floor records, such as the device history record, lot genealogy and UDI label data. Software supports ISO 13485 evidence. It cannot certify your company or replace your auditor.
Split quality system records from production records
Device makers keep two families of records. The first describes how the company runs, covering procedures, training, complaints, corrective actions and audits, while the second covers what happened to each batch on the line.
The first looks alike across companies. The second does not. That gap drives everything below. A syringe assembler, an orthopaedic implant machinist and a diagnostic kit packer each run different routings, inspection plans, packaging seals and sterilisation cycles that no vendor template anticipates.
That difference is the buying rule. Buy where records look alike. Where they follow your own process, you will either build or bend a bought tool, and a bent tool turns every audit request into a workaround.
What a ready QMS tool already handles well
Document control is the clearest win. Controlled procedures, revision history, approval signatures and effective dates are standard features, and so are read-and-understood training records, complaint logs and nonconformance reports with due dates. CAPA workflows come in the same package.
Internal audit schedules, supplier approval lists and management review minutes are also routine, and they are the first records an auditor asks to see. Mature tools format them as auditors expect.
Buying saves months of setup. You also inherit a vendor who tracks changes in the wording of ISO 13485 and the regional rules, which a small quality team rarely has time to follow.
- Controlled documents and revision history
- Training records and sign-off
- Complaint handling and trending
- Nonconformance and CAPA with effectiveness checks
- Internal audit plans and findings
- Approved supplier list and evaluations
What usually needs a build tied to the shop floor
The device history record proves each unit was made as the device master record requires, gathering the work order, component lots, process parameters, inspection results and operator signatures. Generic QMS tools hold files, and they rarely connect to the torque stations, sealers and inspection gauges that produce the numbers going into those records.
Lot and serial traceability has the same problem. When a raw material lot fails, you need finished serial numbers, customers and shipments quickly, drawn from one chain of bill of materials, lot splits and dispatch records.
Label and UDI data come next. Label text, device identifier, production identifier and barcode must match the released record, so a build prints only from released data and blocks labels for lots on hold.
- Device history record per lot or serial number
- Component lot genealogy
- In-process and final inspection results
- Sterilisation batch links
- Label content and UDI barcode data
- Hold, release and quarantine status
Connect the two so evidence lines up
The two sides must talk. A complaint about one serial number should open its device history record in one click, and a CAPA that changes an inspection step should revise the work instruction.
You can connect a bought tool and a built one through exports or an interface, as long as each record carries the same identifiers. Agree the lot and serial format first.
Treat this as support for ISO 13485 evidence. Your quality manual, auditor and regulator decide what counts as compliant, not the software, so where a rule is unclear ask your notified body or a regulatory consultant.
A sensible order of work
Start with the buy. Get document control, complaints and CAPA running in a ready tool, because auditors look there first and a signed procedure then takes seconds to find.
Map one product line from goods receipt to dispatch, marking each point where a record is made, which role makes it and where it is stored today. That map shows what a build must cover.
Next, pick the product with the most complaints in the last year and trace one unit end to end by hand, from supplier lot to customer shipment. Each gap goes on the build list.
Build or buy record map
A one-page grid, one row per quality record. Columns hold record name, owner role, where it is kept today, shop floor link (yes or no), ready tool fit (good, partial, poor) and decision (buy, build, keep). A separate list below names the identifiers each record must carry, such as lot, serial, work order and the supplier lot of every component used.
Open a blank worksheet to printQuestions owners ask
Does using a QMS tool make us ISO 13485 compliant?
No. The standard concerns your system and how you run it, and software only holds records and shows evidence, while certification comes from an audit by a certification body.
Can a ready tool handle device history records?
Some can through configurable forms. They struggle when data must come from machines, scanners and your own bill of materials, which is where a build earns its place.
Who should own the records in the system?
Quality owns the rules and approvals, while production owns each entry made on the line, so every record names one responsible role and audits never stall on ownership.
What about UDI labels for several markets?
Keep the device identifier and production identifier fields separate from label layout, so each market’s format becomes a template instead of a rewrite of the data.