14% of Aged Care Quality Standards (Australia) you already have
Azure Security Benchmark already covers about 14% of Aged Care Quality Standards (Australia), leaving
36 of 42 controls as genuinely new work.
Already covered 0
Likely covered 6
New work 36
No control in Azure Security Benchmark
maps directly to one in Aged Care Quality Standards (Australia). Everything counted as covered is covered because both
map to the same third standard, which is what a crosswalk is, but it is an inference rather
than a lookup.
What is genuinely new work
Nothing in Azure Security Benchmark reaches these. This is the list to scope.
ACQS-1Consumer Dignity and Choice
ACQS-1-1Dignity and Respect
ACQS-1-2Consumer Choice and Independence
ACQS-1-3Information and Informed Consent
ACQS-2Ongoing Assessment and Planning with Consumers
ACQS-2-1Assessment of Needs
ACQS-2-2Care and Services Planning
ACQS-2-3Regular Reassessment
ACQS-3Personal Care and Clinical Care
ACQS-3-2Antimicrobial Stewardship
ACQS-3-3Minimising Restrictive Practices
ACQS-4Services and Supports for Daily Living
ACQS-4-1Daily Living Services
ACQS-5Organisation's Service Environment
ACQS-5-2Furniture, Fittings, and Equipment
ACQS-6Feedback and Complaints
ACQS-6-1Feedback and Complaints Process
ACQS-7-1Workforce Planning
ACQS-7-2Ongoing Education and Training
ACQS-8Organisational Governance
ACQS-8-1Effective Governance
ACQS-CDCConsumer-Directed Care (Home Care)
ACQS-FINFinancial and Prudential Standards
ACQS-IPCInfection Prevention and Control
ACQS-MEDMedication Management
ACQS-NUTRITIONNutrition and Hydration
ACQS-OPEN-DISCOpen Disclosure
ACQS-PALLIATIVEPalliative and End-of-Life Care
ACQS-QINational Quality Indicators
ACQS-RPRestrictive Practices Authorisation
ACQS-SIRSSerious Incident Response Scheme
ACQS-WORKER-REGAged Care Worker Screening and Code of Conduct
Show the 6 you already have
ACQS-3-1Safe and Effective Care
ACQS-8-2Clinical Governance
ACQS-8-3Continuous Improvement
ACQS-CONT-IMPROVContinuous Improvement Plan
How this is calculated
Already covered means a mapping runs from a control in Azure Security Benchmark to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition