Urgent.News

What's breaking now, across thousands of outlets.

Tech

Begin with control; the real win is turning it into daily practice

To be fair, "we have a QMS" is the easiest checkbox in a notified‑body audit. The hard part is that regulators, auditors and — most importantly — frontline engineers do not care about your checkbox. They care about whether your system prevents a bad device from reaching a patient tomorrow. I see this every quarter in Technical File reviews and surveillance audits under MDR 2017/745: companies…

In today's regulated industry, merely documenting processes in a QMS (Quality Management System) is insufficient. Auditors and regulators focus not on the paperwork, but on whether the system effectively prevents defective devices from reaching patients. The challenge lies in turning control into a daily practice, rather than just a checkbox in an audit.

Companies often start with control by establishing policies, SOPs, and folders. Auditors nod approvingly, but then a change request, supplier defect, or vigilance report disrupts the system. The paperwork fails to link incidents, risk assessments, change control, and device documentation. Control is indeed necessary, but not sufficient.

Regulations like ISO 13485 and MDR require documented processes, risk management, and post-market surveillance. However, they provide limited guidance on the day-to-day application of these standards. The critical gap auditors note is traceability - showing the connection between a risk control change and the device brochure, clinical evaluation, and other related documents. Without this traceability, corrective evidence is demanded by auditors.

Designing QMS control with practicality in mind involves three key shifts. Firstly, make trace links easy to follow, creating a seamless flow from complaint to investigation, CAPA, risk assessment, and product master. Utilize an eQMS where change impact mapping is the first screen engineers see. Secondly, integrate QMS tasks into the engineers' daily workflow.

Require a brief risk note when design files are updated, and have the system auto-create a change record that the engineer completes in a minute. Lastly, keep risk visible across all artefacts by performing CAPA-driven risk assessments immediately upon non-conformances and explicitly linking CAPA to clinical follow-up.

Simple changes can convert governance into behavior. Replace lengthy CAPA templates with a concise, structured flow, enforcing a one-click traceability check in change approval, and using AI-assisted summaries with human approval for drafting. These incremental steps convert QMS from an abstract document into a practice that protects the patient.

When auditors test a team's daily practice, they look for examples of recent changes and the trace to risk mitigation and labelling updates. Evidence that CAPAs result in verified improvements and that post-market surveillance and product master file data inform decisions is crucial. The ultimate audit-winning artifact is not perfect paperwork, but repeatable practice embedded in everyday work.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

PDF Rendering in browsers

Why was the certificate blank? A user sent me a screenshot of a signed document. The signature was there. The certificate page behind it was empty. Not broken, not garbled.

  • Signed document appeared blank in browsers due to missing fonts in Alpine container.
  • pdftoppm tool failed to render document without substitute fonts.
  • Developers embedded Dancing Script font to match user screen display.

What are your goals for the week? #194

What are your goals for the week? What are you building this week? What do you want to learn? What events are you attending this week? This Week's Goals. Job Search. Network Apply Project work.

  • Job search, networking, and applying are this week's goals
  • Side projects and learning Co-Pilot are on the agenda
  • CSS Battles completion and Slack goal-setting thread encouraged

A fundação esquecida do RAG: Por que você deve estudar Recuperação de Informação (Information Retrieval)

Se você leu os últimos artigos desta série, percebeu um padrão: tentar resolver problemas de RAG (Retrieval-Augmented Generation) apenas trocando o modelo de embedding ou injetando mais dinheiro em…

  • RAG issues stem from over-reliance on complex architectures and expensive infrastructure
  • Information Retrieval (IR) offers classical search engine solutions to RAG problems
  • IR concepts like BM25 and Precision at K provide cost-effective, reliable search engine fundamentals

Arrêtez de choisir une méthode Agile. Choisissez une taille de promesse.

Version originale en anglais : https://dev.to/karkael/stop-picking-a-method-pick-a-promise-size-3956 Commençons par le débat auquel je ne crois plus : Scrum contre Kanban. C'est un débat de vitrine.

  • Experimented with Scrum, Kanban, and Strong Ownership methods
  • Changed only the size of the promise, not methodology
  • Four-person team with lead architect and parallel UX team

More from Monday 31 August →