Why document control matters
A procedure that is out of date, unsigned, or different from what staff actually do is one of the most common findings in laboratory inspections. Document control is the system that keeps every policy, procedure and form current, approved and available, and that keeps a history of what was in effect on any given date.
What CLIA requires
42 CFR 493.1251 sets the procedure manual requirements for nonwaived testing:
- A written procedure manual for all tests must be available to and followed by laboratory personnel.
- Procedures must include required elements such as specimen requirements, step-by-step performance, calibration and calibration verification, reportable range, control procedures, corrective action, limitations, reference intervals, critical values and reporting.
- Manufacturer package inserts or operator manuals may be used for parts of the procedure, but any variation must be described in writing.
- Procedures and changes must be approved, signed and dated by the current laboratory director before use.
- Each procedure's dates of initial use and discontinuance must be recorded, and discontinued procedures retained for the period specified in 42 CFR 493.1105 (at least two years after discontinuance).
What CAP adds
The CAP Guide to Accreditation describes document control in which every document is current, accurate and available, and requires that:
- All copies of policies, procedures and forms are current.
- Personnel have read the policies and procedures relevant to their job activities.
- All policies and procedures are authorized by the laboratory director before implementation.
- Policies and procedures are reviewed at least every two years by the laboratory director or designee.
- Discontinued policies and procedures are kept in a separate file for at least two years (five years for transfusion medicine).
COLA labs should check COLA's criteria and its COLA: Documents Necessary for the COLA Survey, which include procedure manuals and package inserts.
A document control workflow that works
- Draft from a standard template that includes every element required by 42 CFR 493.1251.
- Review by the technical consultant or supervisor.
- Approve with the director's signature and date before go-live.
- Train and acknowledge: staff who perform the procedure read and sign it, and training is documented.
- Publish one controlled version; remove old bench copies.
- Review on schedule, at least every two years for CAP labs, and whenever the method, instrument or director changes.
- Retire and retain superseded versions with dates of use.
Where paper and shared drives break down
- Multiple copies with different dates at different benches.
- No proof that staff read the current version.
- Missed two-year reviews because nobody tracks the due dates.
- Retired versions deleted, so the lab cannot show what was in effect when a patient was tested.
Forms, logs and records are documents too
Document control is not limited to procedures. Blank forms such as QC logs, temperature logs, maintenance checklists and competency forms should also be versioned, so that a completed record can be matched to the form that was in effect. Completed records are a separate category: they are not revised, but they must be retained, legible and protected from alteration. Under 42 CFR 493.1105, most test records, QC records and quality assessment records must be kept for at least two years, with longer periods for specific records such as immunohematology and pathology. When a corrected entry is needed, the original entry should remain readable with the correction, date and initials beside it.
What to look for in lab document control software
- Version control with effective and retired dates.
- Electronic signatures and approval routing.
- Read-and-acknowledge tracking linked to personnel training records.
- Review-cycle reminders.
- Audit trail and controlled access.
- Ability to give inspectors access or export documents; CAP's CAP Advance Document Review guidance allows guest access to a document management system.
How myLabCompliance handles documents
myLabCompliance includes centralized document storage, version control, e-signatures, policy and procedure creation with templates, review cycles and document audit trails, according to its published feature pages. Because documents sit next to personnel, training and competency records, you can see who has signed the current version of a procedure and who still needs to.
Related: competency tracking, CAP survey preparation, CLIA checklist.
Frequently asked questions
Who must approve laboratory procedures under CLIA?
The current laboratory director must approve, sign and date procedures and changes before use, under 42 CFR 493.1251.
How often must procedures be reviewed?
CAP requires review at least every two years by the director or designee. CLIA requires approval of new and changed procedures and approval by a new director.
How long must retired procedures be kept?
CLIA requires retention per 42 CFR 493.1105, at least two years after discontinuance. CAP specifies at least two years, five for transfusion medicine.
Can package inserts be used as procedures?
CLIA allows manufacturer inserts or manuals to be used for parts of the procedure, but variations must be documented and the procedure still requires director approval.
Does myLabCompliance support electronic signatures?
Yes. mylabcompliance.io lists e-signatures, version control and document audit trails.
See myLabCompliance with your own lab's workflow
Book a demo and bring the compliance task that takes the most of your week. Product details are on mylabcompliance.io.
Book a demoSources: 42 CFR 493.1251 · 42 CFR 493.1105 · CAP Guide to Accreditation · CAP Advance Document Review guidance · COLA: Documents Necessary for the COLA Survey
This page is general information about laboratory regulations, not legal or regulatory advice. Confirm current requirements with CMS, your state agency, and your accrediting organization.