Custom HKZ quality manual and audit file development
An HKZ certificate doesn't just call for a quality manual; it calls for proof that work is actually done according to that manual. At most organisations, the manual sits in a folder on the shared drive and the evidence is scraped together six weeks before the audit. Appfront builds the system in which the manual and the evidence belong together.
Where HKZ gets stuck in practice
HKZ stands for Harmonisatie Kwaliteitsbeoordeling in de Zorgsector (Harmonisation of Quality Assessment in the Healthcare Sector) and includes dozens of standards, each for its own subsector: nursing and care homes with home care organisations in a single standard, disability care, mental health care, youth care, and so on down to small practices. The scheme prescribes which topics you must have under control. Your manual describes how you do that; the audit is about whether it matches practice. The certificate is valid for three years, with interim assessments during that period and a recertification at the end. That rhythm shapes your file more than anything else: at recertification, the auditor looks back over three years, and what counts is whether you recorded it at the time. This ties in with your healthcare compliance, which covers statutory frameworks such as NEN 7510 and the Wkkgz (Dutch Quality, Complaints and Disputes in Healthcare Act); HKZ is a voluntary certificate with its own scheme and its own certifying body. The overview of standards can be found at hkz.nl.
That difference is where it goes wrong, and the HKZ scheme puts its finger on exactly that spot. It doesn't just ask for described processes but for the PDCA cycle around them: an internal audit programme, management review, client satisfaction measurements, and demonstrable follow-up of complaints and incidents. That is work that should be spread across the entire three-year period. In practice, the management review is written in a single afternoon, internal audits are planned but never carried out, and the improvement points from the previous external audit sit in a report that nobody reopens.
The auditor from your certification body can tell from the dates. Four internal audit reports drawn up in the same week say more about your quality system than anything written in them.
Where it really goes wrong is the link to the three-year cycle. A finding from the interim assessment in year one must still be traceable at recertification in year three, along with what you did about it and whether it worked. In an organisation with several locations and several standards, the same improvement is tracked separately in three places, so at recertification nobody has the full picture any more.
The mandatory submission of quality indicators follows its own rhythm and has its own source. That is covered on the page about the indicator registration app for the ward.
How we build your HKZ system
Your manual and your standard are the starting point and remain yours. You decide with your quality officer what belongs in them; we build the system that keeps it alive.
Which parts of your standard affect which processes, and where there is nothing in place. That overview is usually the first thing to come out of this, even regardless of software: it shows where the manual describes topics that nobody carries out.
A procedure is linked to a part of the standard, an audit is linked to a procedure, a finding is linked to an audit and an action is linked to a finding. Without those links, it stays a collection of documents.
Everyone goes there, so that is where the build begins: one valid version, easy to find on the shop floor. Your quality officer works with us and checks every sprint against the standard.
We walk through a part of the standard the way an auditor would and look for where you cannot get the evidence out of the system. That is the test that counts, and we run it before the real auditor arrives.
What the system does in practice
Getting from a collection of documents to a working quality system takes these six steps. With one location and one standard you need four; with several of each, all six.
Manual with version control
Every procedure has one valid version, with earlier versions kept and a clear record of who changed what and when. An employee always sees the current version, because an outdated document on the shared drive is a finding at an audit.
Integration with your standard
Every part of your HKZ standard is linked to the procedures and records that put it into practice. Where nothing is linked, that is visible immediately rather than only during the audit.
An annual audit plan that keeps itself up to date
Internal audits, management review, evaluations and revision deadlines on an annual plan with alerts. A missed internal audit stays open instead of quietly disappearing.
Finding with action and verification
A finding is only closed after an action, a person responsible, a deadline and confirmation that it worked. That last part is what an auditor checks the following year and what most systems lack.
Reports from the primary process
Incidents, complaints and improvement suggestions come in where the work happens and end up in the same system. As long as these are three separate routes, nobody sees that the same cause keeps returning.
Audit file per standard requirement
The evidence is arranged the way the auditor looks at it, with the records, the audits and the follow-up together, organised by your standard. If you are looking for a system that plans and carries out audits of any kind, audit software is the broader answer; this page is about the file that one specific HKZ standard requires.
Who we build for
The number of locations determines whether a central manual reaches the shop floor, and the number of standards determines how much is recorded twice. Four situations.
Care for the elderly and home care
Many locations and teams working independently, so a central manual quickly falls out of sight. What matters here is that the current procedure can be found on a phone, not on the shared drive at head office.
Mental healthcare and youth care
Heavier record-keeping and more overlap with other supervisory frameworks. The temptation is to build a separate system for each framework, so the same registration ends up existing three times, separate from your social support and youth care software.
Disability care and small-scale living
Small teams across many locations, with a quality officer who often does this on top of other duties. In that case, ease of use matters more than completeness; a system that asks too much does not get filled in.
Organisations with multiple certifications
HKZ alongside ISO 9001, or alongside an additional scheme per service. A quality management system is generic and follows the ISO structure; an HKZ scheme is written per sub-sector and contains requirements that are not covered there. The gain is that a single registration is linked to both rather than duplicated.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
One design requirement comes first, and it is not technical: the system must be usable for people who are not quality officers. They provide the evidence, and anything that asks too much does not get filled in.
If you also want to show during an internal audit that access to patient records is logged and checked, read more about our NEN 7513 integration.
If you want to record the definition, source and sign-off for each indicator, take a look at our software for the quality indicator submission file.
Why Appfront
Evidence is created in the work itself
An audit file that is compiled after the fact is exactly what an auditor recognises. We make sure records are created where the work happens and organise themselves automatically.
A finding only closes after verification
Most systems let you close a finding as soon as someone writes down a corrective action. We also ask whether it worked, because that is what gets tested the following year.
Built on your own scheme
HKZ has dozens of schemes, and they differ. We adopt yours as a configurable structure instead of imposing a standard layout that does not fit.
Honest about our role
We are not quality consultants and we do not write your manual. We build the system that keeps the manual alive and collects the evidence; the assessment of the content remains with you and your certification body.
Security and privacy
A quality system in healthcare almost always touches client data. An incident report describes what happened to a specific person; a complaint contains a name. That brings it under the GDPR and under medical confidentiality, which means an improvement file cannot be open to the whole organisation. We separate the report from the analysis: whoever works on the improvement usually does not need to know who was involved.
The same applies to audits. An auditor may inspect files, but exporting your entire system to a folder that then stays there is a risk nobody needs. We set up the audit as temporary, limited access to what is being assessed. Registration is also immutable: a correction is visible as a correction, because a finding that can be removed from the system afterwards makes the whole file worthless. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.
Frequently asked questions about HKZ software
No. What belongs in your procedures is subject-matter work for your quality officer or your adviser, and we can't take that over. We build the system in which the manual lives: with version control, linked to your scheme, and connected to the evidence that work is actually done according to it. If you don't have a manual yet, that is the first step, not the software.
Yes, and that is usually where the biggest gain lies. HKZ alongside ISO 9001, or several HKZ schemes for different services, overlap considerably. We link a procedure or record to all the requirements it fulfils instead of duplicating it. When a scheme changes, you can see immediately what is affected.
Because there is only one current version and it can be found where the work happens, including on a phone. Old versions are retained for the file but are not what anyone comes across when searching. When a revision is issued, you can see who has seen the new version, which for important changes is the difference between sending and arriving.
It is given a corrective action, an owner and a deadline, and it is only closed once it has been verified that the action worked. That last step is exactly what is missing in most systems and what an auditor checks the following year. Findings from internal audits, external audits, incidents and complaints all follow the same route, so you can see whether a cause keeps recurring.
Often yes, via integrations, with a limited scope: numbers and signals, not client records. The result is that incident reports from the primary process land in the quality system automatically instead of someone retyping them. What can be integrated depends on your supplier; we map that out before we commit to anything.
Moving the documents is usually the smallest part. The work lies in making the connections: which procedure belongs to which part of the scheme, and which record is the evidence for it. That is work you do together with your quality officer, and it delivers value in itself, because it shows where nothing is attached to a topic.
Then you adapt the structure without the history you have built up becoming worthless. We build the scheme structure as a configurable component and record per period which version applied, so an old audit can still be read against the requirements of the time. That is the reason not to hard-code it.
That depends on the number of locations, the number of schemes and whether integrations with your EHR or HR system are involved. The manual with version control and the audit planning are usually quick to put to use and deliver the most; integrations cost more. We give a well-founded estimate after the discovery phase.
Building an HKZ system?
Bring the findings report from your most recent external audit. It usually shows straight away which part of your file was put together after the fact and which part kept pace with the work. We build this as a standalone system and as part of a broader custom software project. If you are a childcare organisation, the staffing side is handled separately; see BKR software.