How integrated quality management software supports NATA-accredited pathology services in Australia

A pathology service can have a documented procedure, a completed audit and a corrective action, yet still struggle to show how they relate to one another. Integrated quality management software gives teams a way to connect controlled documents, incidents, equipment, competency and audit records. For an Australian pathology service, the practical test is whether people can trace a quality issue from detection to resolution across the work covered by its accreditation scope.

That test matters because accreditation looks beyond a tidy filing system. NATA's medical laboratory accreditation program is delivered with the Royal College of Pathologists of Australasia (RCPA) and applies ISO 15189 alongside relevant National Pathology Accreditation Advisory Council (NPAAC) standards. The scope and applicable criteria determine what evidence a service must maintain. Software can organize that evidence; it does not confer accreditation.

What does integrated quality management mean in a pathology service?

A pathology quality management system is the set of processes, responsibilities and records used to manage the quality and competence of a service. Integration means that a record can lead a reviewer to the related work without relying on someone to reconstruct the story from email, folders and spreadsheets.

For example, a specimen labeling incident might lead to an investigation, a change to a collection procedure and a competency check for affected staff. These activities need distinct records, but a quality manager should be able to follow the relationships between them. The aim is traceability, not one large form that tries to do everything.

Where do pathology quality records get lost between teams?

The gaps often appear between teams: a collection site reports an incident, a laboratory manager investigates it, a document owner revises the procedure and supervisors confirm that staff have adopted the change. If each step lives in a separate system, the work may be done without leaving a clear chain of evidence. Map who owns each handoff, what triggers the next step and where completion is recorded.

What evidence matters for NATA accreditation and ISO 15189?

NATA's ISO 15189:2022 application document, effective February 2026, explains how its criteria apply to medical laboratories alongside relevant NPAAC standards. The requirements that apply to a service depend on its activities and scope. A software checklist should therefore begin with the service's own requirements, rather than a vendor's generic claim of compliance.

Can staff find the approved procedure used at the time?

Document control should make the approved version, approval history and effective date retrievable for each relevant site. It should also show what happened when a procedure changed. For an example of how controlled versions and approval histories can be managed together, see document version and approval workflows. The page describes document control capabilities; it is not evidence that a particular configuration meets Australian accreditation requirements.

Can the service show competence and equipment status for the work performed?

Records should connect the work to the people, equipment and processes involved. A training attendance record is different from evidence of competence for a defined task. Similarly, an equipment inventory is different from a record of maintenance, calibration or verification relevant to its use. Identify which links are needed for each activity in scope and who is responsible for reviewing them.

Do audits and management reviews lead to documented decisions?

An audit finding is useful only if the organization can trace it through evaluation and action. NATA's application document says an internal audit schedule should ideally cover all ISO 15189 requirements within a 12-month period and that management should review QMS effectiveness at least annually. Those reviews need to encompass the pathology service as a whole, including pre-analytical, analytical and post-analytical processes. A connected system can help surface overdue work and related evidence, but people remain responsible for judging what the findings mean.

How should a pathology service trace an issue from detection to closure?

Take a hypothetical specimen labeling error. The value of integration is visible when each decision points to the record that supports it.

Stage	Question to answer	Evidence to retain
Detection	What happened and where?	Incident record, date, location and affected process
Assessment	What is the potential effect on patients and results?	Documented triage and decisions on immediate action
Investigation	What contributed to the error?	Findings, linked procedures and relevant records
Action	What changes, who approves them and when?	Assigned corrective actions, approvals and revised procedure
Follow-up	Did the change work in practice?	Competency checks, review of recurrence and closure decision

The table is a workflow example, not a prescribed NATA form or a substitute for a service's clinical escalation procedures.

How do corrective actions connect to procedure changes?

The investigation should record why an action was chosen, not just whether a task was marked complete. If the procedure changes, record the approved version, its effective date and which staff need to be informed or assessed. Corrective action tracking from investigation to effectiveness review provides an example of a connected workflow. It should be assessed against the pathology service's own procedures and applicable criteria, not treated as an accreditation shortcut.

When should a pathology corrective action be closed?

Completing an assigned action is not the same as checking whether it prevented recurrence. Set a review point appropriate to the risk and process, document the evidence considered and record who accepted closure. If a similar issue occurs again, the previous investigation should be easy to find so the team can reassess its assumptions.

How can teams assess quality management software without mistaking it for accreditation?

Ask a prospective system to demonstrate one ordinary quality event across sites and roles. Can a collection-site report lead to an investigation, a controlled procedure change, a competency record and a follow-up decision without losing the original record? Can the team see access permissions, review dates and outstanding actions? Can it export the evidence in a form assessors and staff can understand?

Which workflow should a service test first?

Choose a recent event with several handoffs, then walk it through the current process. List the records that had to be found, the people who approved decisions and the points where the team had to reconcile conflicting versions. Use that map to test software configuration, including how it handles local procedures and restricted information. A connected quality management system overview shows the kinds of workflows that may be linked, but the service should test them against its own scope and responsibilities.

The lasting question is whether a quality manager can follow a decision through the evidence behind it. When procedures, investigations, competence and reviews connect, teams spend less time rebuilding the record and more time checking whether the change improved the work. Accreditation still depends on the service's practices, people and assessment against the criteria that apply to it.