Begin with provider type and jurisdiction

Identify the licensed provider, services delivered, buildings involved, state and locality, accreditation organization, and survey authority. Hospitals, critical access hospitals, and ambulatory surgical centers use different federal provisions even when related NFPA documents appear in each pathway. Record mixed occupancies and campus relationships instead of applying a hospital label to every building.678

Separate each authority role

Create distinct columns for statute or regulation, incorporated code and edition, referenced standard and edition, CMS survey form or guidance, accreditation requirement, state or local adoption, approved waiver or equivalency, and project-specific authority decision. This prevents a checklist, accreditation evidence request, newer model code, and adopted technical requirement from being cited as though they have identical force.413910

Map topics to exact sources

For each operational topic—such as egress, doors, barriers, alarms, sprinklers, emergency power, medical gas, utilities, or construction—identify the applicable source, section or survey tag, facility scope, responsible interpreter, and current revision. Link to official access rather than copying controlled standards. Mark broad guidance as guidance and preserve the need for project-specific interpretation.513

Record conflicts and unresolved questions

Differences in labels, numbering, editions, or evidence expectations do not automatically create a conflict. Check dates, provider scope, occupancy, adoption, deeming program, and authority role. When uncertainty remains, document the competing sources, operational decision, responsible reviewer, escalation route, and approval needed. Do not silently select the least restrictive statement.4910

Maintain the matrix as a controlled record

Assign an owner and review the matrix after regulatory changes, accreditation updates, code adoption, provider conversions, waivers, major projects, or authority decisions. Record effective dates and preserve prior versions. Use the matrix to guide policies, drawings, inspection programs, assessment scopes, and staff education while recognizing that it organizes authority—it does not replace the complete source or qualified interpretation.4910

Apply the matrix to a real compliance question

Test the matrix with a specific facility condition such as a door modification, generator record, medical-gas feature, delayed-egress arrangement, or construction impairment. Trace the provider regulation to the adopted code, referenced standard, survey tag, accreditation expectation, local adoption, and project decision. Record which source supplies the technical rule and which source defines evidence or survey handling.

If the team cannot complete the trace, revise the matrix structure or escalate the unresolved question. This exercise reveals missing editions, expired links, unsupported local practices, and policies that cite an accreditation label without identifying the underlying authority.5139

Connect exceptions to their approval records

List waivers, equivalencies, variances, alternative methods, and authority approvals with the exact scope, affected locations, conditions, effective and expiration dates, monitoring duties, and controlling correspondence. Do not generalize an approval for one building or opening to a broader campus population. Identify changes that require reassessment.

Link every continuing condition to responsible owners and scheduled evidence. When permanent correction is complete or the approval expires, update the matrix and operational records. A current authority map should distinguish accepted exceptions from informal interpretations and pending requests.4610

Use disciplined citation language

Write each matrix entry so readers can distinguish a requirement, survey reference, accreditation expectation, guidance document, local decision, and facility policy. Include the title, edition or effective date, relevant section or tag, official access location, facility scope, and last verification date. Avoid phrases such as code requires when the cited item is actually a checklist or advisory. Precise labels improve technical review, make updates easier, and keep the matrix from overstating the legal or survey role of a useful source.45910

Related guidance for your next step

Explore the complete topic

Continue from this article into the connected cornerstone guides, detailed conditions, exact questions, and related services.

Continue your healthcare life safety review