ISO 15189 keeps point-of-care testing inside medical-laboratory governance
ISO 15189:2022 specifies quality and competence requirements for medical laboratories and states that it is also applicable to point-of-care testing. A result produced near the patient can shorten a handoff, but it does not remove method, device, operator, quality, result-review, clinical-use, and accreditation responsibilities.
Editorial figure by Lab Systems Index. Source context: ISO 15189:2022.
Define the point-of-care testing system beyond the device
A point-of-care record should connect the patient and order to the specimen or measurement, device, method, reagent or consumable, lot, operator, location, time, units, reference or decision limits, quality status, result, review, correction, communication, and clinical record. Moving the measurement outside the central laboratory does not make those identities and handoffs optional.
Governance also needs a named medical-laboratory and clinical context, accountable roles, device population, intended use, competency process, quality-control plan, maintenance, connectivity, downtime, exception handling, retention, and applicable regulatory or accreditation basis. The exact scope depends on the organization and jurisdiction.
Keep LIMS, middleware, device, and clinical record roles distinct
A LIMS or laboratory information system may manage orders, tests, results, review, quality, and reports. Middleware may manage devices, operators, quality controls, and result routing. The analyzer owns acquisition within its design, while an EHR or other clinical system may present the result for care. Shared data does not make these systems interchangeable or settle which one is authoritative for every field.
Buyers should trace corrections, patient mismatches, duplicate tests, unit changes, reference-range versions, device downtime, failed quality control, unauthorized operators, disconnected operation, late transmissions, and amended reports. The demonstration should identify which system detects each exception and which accountable person resolves it.
Do not infer accreditation from a standards mapping
A provider may document audit trails, access controls, device connectivity, operator management, quality workflows, or mappings to ISO 15189. That official positioning does not prove the configured implementation, method validation or verification, data integrity, staff competence, scientific validity, conformity, or accreditation of a laboratory or testing service.
An accreditation conclusion belongs to the applicable scheme and accredited scope, based on evidence reviewed by the responsible body. Laboratories should preserve the standard edition, adoption or accreditation context, scope, locations, methods, devices, exclusions, findings, corrective actions, and current status rather than using a product badge as a substitute.
Treat the public ISO record as scope—not implementation text
The official ISO page supports the title, 2022 edition, medical-laboratory purpose, and point-of-care applicability. It does not expose the full licensed requirements or provide an organization-specific implementation method. Readers need authorized access to the applicable standard and current regulator, accreditation-body, manufacturer, clinical, quality, and organizational requirements.
Lab Systems Index rechecked the official record on August 9, 2026; no post-July 30 material status change was identified. The publication uses that record to define a governance boundary and does not determine the validity, safety, interpretation, or clinical use of any point-of-care result.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Lab Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.