ISO 17025 implementation, analytical laboratory systems, and practical tools for laboratories.
I help analytical laboratories implement and strengthen ISO 17025 systems so they are technically coherent, operationally robust, and proportional to risk.
My work combines analytical chemistry, laboratory management, metrology, quality assurance, and software-supported process control. I work in English and Spanish.
Notes
Software
About
Chemist, laboratory director, university teacher.
My current work focuses on ISO 17025 implementation and analytical laboratory systems — specifically on the point where quality systems, metrology, analytical chemistry, documentation, competence, and practical laboratory work meet.
I currently lead an analytical chemistry laboratory in Argentina, which gives me a practical view of ISO 17025: not as a documentation exercise, but as an operating system that must function under real technical, economic, and human constraints.
My background includes analytical and physical chemistry, scientific research, and university teaching. I have worked across environmental monitoring, oilfield water analysis, food chemistry, and industrial process control.
I also develop small software tools for laboratory and regulatory workflows, when software can make correct work easier, more traceable, or less error-prone.
ISO 17025 implementation and gap analysis — measurement uncertainty and metrological coherence — method validation and verification — risk-based quality control — laboratory documentation systems — LIMS design and implementation — competence development — analytical problem diagnosis.
English and Spanish.
Approach
ISO 17025 implementation for analytical laboratories
ISO 17025 provides structure: traceability, validation, uncertainty, documentation, competence, and impartiality. But compliance alone does not guarantee operational robustness.
Many laboratories operate accredited systems that still face over-control in low-risk areas, under-control in critical steps, weak links between uncertainty and reporting, insufficient verification of critical reagents, or training programs that focus on procedures rather than technical sensitivity.
The gap between a compliant system and a robust one is not filled with more documentation. It is filled with technical judgment applied proportionally.
A laboratory that is compliant, efficient, technically proportional, and robust under audit and under stress.
ISO 17025 is the foundation. Technical judgment is the architecture.
Interested in working together? Get in touch.
Notes
Notes /
I have seen accredited laboratories report chemically impossible results without triggering any internal alarm.
The instrument was calibrated.
The quality controls were within range.
The report was formally compliant.
And yet, the result made no chemical sense.
The issue was not the instrument. The issue was structural.
In many regulated laboratories, quality assurance is designed around procedure validation: calibration curves meet statistical criteria, control samples fall within predefined limits, documentation satisfies ISO 17025 requirements.
All of this is necessary.
But none of it automatically guarantees coherence.
Accreditation does not guarantee coherence. The gap often appears between analytical logic, regulatory structure, and operational workflow.
Consider a common example.
A laboratory defines a "lot" as a sequence of up to 20 samples processed in one instrumental run. From an operational perspective, this is efficient. From a chemical perspective, it may be wrong.
A chemical lot should represent a homogeneous matrix group — samples that behave similarly and require matrix-specific validation through duplicates and spikes.
Imagine a lot containing seven drinking water samples and three produced water samples from an oilfield operation. Very different matrices. The spike recovery is performed on one of the drinking water samples — it is the same instrumental run, after all.
The spike passes. The system records compliance.
But the spike says nothing about the produced water samples. Their matrix was never tested. Any matrix-specific distortion — suppression, interference, incomplete extraction — remains invisible.
The lot definition was operationally convenient and analytically wrong.
The problem compounds when field decisions enter the picture.
The same produced water sample goes out of range on the first aliquot. The analyst takes 10 mL, reads above the calibration limit, and adjusts: 1 mL instead, dilution factor applied, result reported.
Reasonable under pressure. But the method was validated for 10 mL aliquots.
At 1 mL, the uncertainty is no longer the same. Volumetric contribution increases. Any surface effect or contamination in the vessel matters more. The relative uncertainty of the aliquot itself has changed by an order of magnitude.
The report carries the same uncertainty statement as always.
The number looks precise. The chemistry behind it is not.
Most technical failures in regulated environments do not originate in the instrument. They originate at interfaces — between the chemistry and the procedure, between the procedure and the operational decision, between the operational decision and the reported result.
When these layers are not aligned, compliance can coexist with fragility.
The instrument was fine. The calibration was valid. The controls passed.
And the result was still wrong.
The solution is not more documentation.
It is structural alignment: lot definitions that reflect chemical reality, dilution decisions that trigger uncertainty reassessment, and reporting practices that communicate what the number actually represents.
Quality systems validate procedures. Coherence requires understanding what happens when the procedure meets the real sample.
If we measure, it must matter.
Notes /
Autoclaves, culture media, and the gap between compliance and operational robustness
In several laboratories in my region, I have noticed the same pattern: larger and larger autoclaves are being used to process microbiological culture media, but very few laboratories routinely use control strains to verify the actual performance of the medium after sterilization.
I should clarify one point first: I am not a microbiologist.
But I do try to understand the technical processes that support the results we report. And this one deserves attention.
The issue is not the size of the autoclave itself. A large autoclave can be perfectly appropriate. The problem appears when large liquid loads take much longer to cool than expected.
Some studies on laboratory autoclave cooling have reported cooling times of up to 260 minutes just to reach 95 °C under common loading conditions. That additional time at elevated temperature may be enough to affect heat-sensitive components of culture media: carbohydrates, indicators, selective agents, and other compounds that are not only sterilized by heat, but also chemically changed by it.
The result can be uncomfortable:
The medium may be sterile, but not necessarily fit for microbiological recovery.
This distinction matters.
Sterility confirms that contaminating microorganisms were eliminated. It does not automatically confirm that the medium still supports the growth, inhibition, differentiation, or recovery performance expected from it.
A culture medium is not just a sterile liquid or gel. It is a functional analytical system.
If that system contains heat-sensitive components, then the real sterilization cycle includes more than the programmed holding time at 121 °C. It includes heating, exposure, and cooling. In large liquid loads, the cooling phase may become analytically relevant.
This is a useful example of a broader problem.
Many laboratory systems are designed around formal compliance:
The cycle was completed.
The procedure was followed.
The record exists.
The autoclave reached temperature.
The batch was labeled as sterilized.
All of that may be true.
But the real question is different:
Did the process still produce a medium that performs as intended?
This is where operational robustness begins.
A technically coherent system does not stop at asking whether the procedure was followed. It asks whether the procedure, under real operating conditions, still produces the intended analytical outcome.
For microbiological media, that usually means functional verification with appropriate control strains, especially when the laboratory changes autoclave size, load configuration, container volume, cooling conditions, or medium formulation.
This is not about adding paperwork.
It is about detecting a failure mode that paperwork alone will not reveal.
A medium degraded by excessive thermal exposure may look normal. The autoclave record may look normal. The procedure may look compliant. But recovery may be affected, selectivity may change, or indicator response may weaken.
The failure becomes visible only when the medium is challenged functionally.
This same pattern appears in many areas of laboratory quality systems.
A calibration certificate may exist, but not be interpreted.
A method may be validated, but not under the matrix currently being tested.
A control sample may pass, but not represent the critical risk.
A procedure may be followed, but not reflect the real workflow under pressure.
Compliance is necessary.
But compliance alone does not guarantee coherence.
In this case, the lesson is simple:
Sterility is not the same as microbiological fitness for purpose.
And in a broader sense:
A laboratory process is not robust because it is documented. It is robust when it continues to work correctly under the real conditions in which the laboratory actually operates.
Contact
Initial conversations are for evaluating fit and project viability. I work with laboratories looking to implement or strengthen ISO 17025 systems in a technically coherent, operationally realistic way.
I work in English and Spanish.