<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="atom.xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://openqms.thelabguy.org/es/blog</id>
    <title>OpenQMS 17025 Blog</title>
    <updated>2026-04-10T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://openqms.thelabguy.org/es/blog"/>
    <subtitle>OpenQMS 17025 Blog</subtitle>
    <icon>https://openqms.thelabguy.org/es/img/favicon.svg</icon>
    <entry>
        <title type="html"><![CDATA[Procedures 04, 05, and 06 — Plus a New Way to Read Them]]></title>
        <id>https://openqms.thelabguy.org/es/blog/procedures-04-05-06-insight-blocks</id>
        <link href="https://openqms.thelabguy.org/es/blog/procedures-04-05-06-insight-blocks"/>
        <updated>2026-04-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Three procedures now complete — competence, risk, and supplier control — and a new Insight section that explains why each one exists.]]></summary>
        <content type="html"><![CDATA[<p>Three more procedures are complete, covering competence management, risk assessment, and supplier control. We also introduced a new element to the documentation: <strong>Insight blocks</strong>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-new">What's new<a href="https://openqms.thelabguy.org/es/blog/procedures-04-05-06-insight-blocks#whats-new" class="hash-link" aria-label="Enlace directo al What's new" title="Enlace directo al What's new" translate="no">​</a></h2>
<p><strong>Procedure 04 — Competence, Training and Awareness</strong> is fully developed with four appendices: Training Program, Training Record, Record of Attendance, and Competence Approval and Authorization Record. It covers the full competence lifecycle from recruitment through ongoing monitoring.</p>
<p><strong>Procedure 05 — Addressing Risks and Opportunities</strong> is complete with a risk and opportunity registry appendix. It walks through identification, assessment, treatment, and the connection between risk management and the rest of the QMS.</p>
<p><strong>Procedure 06 — Externally Provided Products and Services</strong> is new in this release. It covers supplier evaluation and approval, incoming verification, periodic re-evaluation, and subcontracting controls — all scoped to a battery materials characterization laboratory. Two appendices provide the Supplier Evaluation Record and the Approved Supplier List.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="insight-blocks">Insight blocks<a href="https://openqms.thelabguy.org/es/blog/procedures-04-05-06-insight-blocks#insight-blocks" class="hash-link" aria-label="Enlace directo al Insight blocks" title="Enlace directo al Insight blocks" translate="no">​</a></h2>
<p>Every procedure in a QMS tells you <em>what</em> to do. But without understanding <em>why</em> a section exists, the procedure becomes a compliance exercise rather than a working tool.</p>
<p>We've added <strong>Insight blocks</strong> at the end of each procedure — visually distinct commentary sections that explain the reasoning behind the requirements. They cover the failure modes the section is designed to prevent, the connections to other sections, and the common mistakes laboratories make in implementation.</p>
<p>These are not part of the controlled procedure text. They are the conversation a mentor would have with you after you've read the procedure — the context that makes the difference between implementing a rule and understanding a system.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-intro-page-now-links-forward">The intro page now links forward<a href="https://openqms.thelabguy.org/es/blog/procedures-04-05-06-insight-blocks#the-intro-page-now-links-forward" class="hash-link" aria-label="Enlace directo al The intro page now links forward" title="Enlace directo al The intro page now links forward" translate="no">​</a></h2>
<p>A small but important change: the introduction page now includes an explicit link to <a class="" href="https://openqms.thelabguy.org/es/docs/understanding-the-system">Understanding the System</a> — the conceptual guide that explains how ISO 17025 thinks and how the procedures connect. If you're new to the project, start there.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-next">What's next<a href="https://openqms.thelabguy.org/es/blog/procedures-04-05-06-insight-blocks#whats-next" class="hash-link" aria-label="Enlace directo al What's next" title="Enlace directo al What's next" translate="no">​</a></h2>
<p>We continue working through the People and Resources group: Procedure 07 (Facilities and Environmental Conditions), Procedure 08 (Equipment Maintenance, Calibration and Verification), and Procedure 09 (Customer Service). After that, we move into the Analytical Process group.</p>]]></content>
        <author>
            <name>Pablo J. Lebed</name>
            <uri>https://github.com/pablojlebed</uri>
        </author>
        <category label="ISO/IEC 17025" term="ISO/IEC 17025"/>
        <category label="QMS" term="QMS"/>
        <category label="Release" term="Release"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Why We Develop OpenQMS with AI]]></title>
        <id>https://openqms.thelabguy.org/es/blog/ai-assisted-development</id>
        <link href="https://openqms.thelabguy.org/es/blog/ai-assisted-development"/>
        <updated>2026-04-03T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Our approach to using artificial intelligence as a core tool in developing an open Quality Management System — and why we think it produces better results.]]></summary>
        <content type="html"><![CDATA[<p>OpenQMS is developed with the assistance of AI. Here's why, and how.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-honest-answer">The honest answer<a href="https://openqms.thelabguy.org/es/blog/ai-assisted-development#the-honest-answer" class="hash-link" aria-label="Enlace directo al The honest answer" title="Enlace directo al The honest answer" translate="no">​</a></h2>
<p>AI is faster, more detailed, and more consistent than writing everything by hand. A single procedure in a Quality Management System can take days to draft from scratch. With AI, the first draft takes minutes — leaving more time for what actually matters: reviewing, correcting, and refining the content until it's right.</p>
<p>We don't use AI to replace expertise. We use it to express expertise faster.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-it-works-in-practice">How it works in practice<a href="https://openqms.thelabguy.org/es/blog/ai-assisted-development#how-it-works-in-practice" class="hash-link" aria-label="Enlace directo al How it works in practice" title="Enlace directo al How it works in practice" translate="no">​</a></h2>
<p>Our development process looks like this:</p>
<ol>
<li class=""><strong>A human defines the scope</strong> — what procedure to write, what it needs to cover, which ISO/IEC 17025 clauses it maps to.</li>
<li class=""><strong>AI produces a draft</strong> — structured, detailed, and consistent with the rest of the QMS.</li>
<li class=""><strong>A human reviews and corrects</strong> — checking technical accuracy, practical applicability, and alignment with how real laboratories operate.</li>
<li class=""><strong>The result is published openly</strong> — so anyone can inspect, challenge, or improve it.</li>
</ol>
<p>This is not "AI-generated content" in the way people usually mean. It's human-directed, AI-assisted development — the same way a programmer uses a compiler or an engineer uses CAD software. The tool amplifies the work; it doesn't replace the thinking.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-transparency-matters">Why transparency matters<a href="https://openqms.thelabguy.org/es/blog/ai-assisted-development#why-transparency-matters" class="hash-link" aria-label="Enlace directo al Why transparency matters" title="Enlace directo al Why transparency matters" translate="no">​</a></h2>
<p>We could have said nothing. Most projects that use AI don't disclose it. But we think transparency is a strength, not a vulnerability — especially for a project about quality management, where integrity and traceability are foundational principles.</p>
<p>If you're evaluating this QMS for your laboratory, you deserve to know how it was made. And if you find an error — whether introduced by AI or by us — the entire project is open for you to flag it, fix it, or improve it.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-bigger-picture">The bigger picture<a href="https://openqms.thelabguy.org/es/blog/ai-assisted-development#the-bigger-picture" class="hash-link" aria-label="Enlace directo al The bigger picture" title="Enlace directo al The bigger picture" translate="no">​</a></h2>
<p>ISO/IEC 17025 QMS documents are expensive to develop. Consultants charge thousands. Small laboratories and those in developing countries are often priced out entirely.</p>
<p>If AI can help produce high-quality, openly licensed QMS documentation that any laboratory can adopt and adapt — the net benefit far outweighs anyone's discomfort with the method. Access to quality should not depend on budget.</p>
<p>We'd rather develop, correct, and improve in the open than wait for a perfect process that never ships.</p>]]></content>
        <author>
            <name>Pablo J. Lebed</name>
            <uri>https://github.com/pablojlebed</uri>
        </author>
        <category label="QMS" term="QMS"/>
        <category label="Release" term="Release"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Welcome to OpenQMS 17025]]></title>
        <id>https://openqms.thelabguy.org/es/blog/welcome</id>
        <link href="https://openqms.thelabguy.org/es/blog/welcome"/>
        <updated>2026-04-02T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Introducing OpenQMS 17025 — a free, open-source Quality Management System built step by step around ISO/IEC 17025:2017 for testing and calibration laboratories.]]></summary>
        <content type="html"><![CDATA[<p>We are starting to openly build a complete Quality Management System based on <strong>ISO/IEC 17025:2017</strong>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-problem">The problem<a href="https://openqms.thelabguy.org/es/blog/welcome#the-problem" class="hash-link" aria-label="Enlace directo al The problem" title="Enlace directo al The problem" translate="no">​</a></h2>
<p>Every laboratory that pursues accreditation to ISO/IEC 17025 faces the same challenge: the standard defines <em>what</em> you need, but not <em>how</em> to document it. Most labs either hire expensive consultants or adapt internal documents that are never shared with anyone else.</p>
<p>This means thousands of laboratories around the world are solving the same problems independently — writing the same procedures, the same policies, the same forms — from scratch.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-were-building">What we're building<a href="https://openqms.thelabguy.org/es/blog/welcome#what-were-building" class="hash-link" aria-label="Enlace directo al What we're building" title="Enlace directo al What we're building" translate="no">​</a></h2>
<p><strong>OpenQMS 17025</strong> is a fully open Quality Management System, developed incrementally and transparently. We will work through each clause of the standard and produce:</p>
<ul>
<li class="">Plain-language explanations of each requirement</li>
<li class="">Ready-to-adapt policy and procedure templates</li>
<li class="">Implementation guidance for common lab types</li>
</ul>
<p>All content is licensed under <strong>CC BY-NC 4.0</strong> — you can use it, adapt it, and redistribute it freely for non-commercial purposes.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-to-contribute">How to contribute<a href="https://openqms.thelabguy.org/es/blog/welcome#how-to-contribute" class="hash-link" aria-label="Enlace directo al How to contribute" title="Enlace directo al How to contribute" translate="no">​</a></h2>
<p>OpenQMS is built in the open on GitHub. If you have experience with ISO 17025, laboratory accreditation, or quality management, we welcome your contributions:</p>
<ul>
<li class="">Open an issue to suggest improvements</li>
<li class="">Submit a pull request with new content or corrections</li>
<li class="">Share this project with colleagues who might benefit</li>
</ul>
<p>Let's build this together.</p>]]></content>
        <author>
            <name>Pablo J. Lebed</name>
            <uri>https://github.com/pablojlebed</uri>
        </author>
        <category label="ISO/IEC 17025" term="ISO/IEC 17025"/>
        <category label="QMS" term="QMS"/>
    </entry>
</feed>