International

ISO 13606-5:2019

42 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

42 controls 0 frameworks share controls with it International verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1The boundary test0
1-relationsThree artefacts travel, two models do not0
1-secondarySecondary uses are outside the focus, not forbidden0
2The normative references, and the edition you must pin0
3.1The requester is defined by the act of asking0
3.2The recipient is not always the requester0
4The abbreviations clause is the interface shorthand0
5.1An extract request carries every mandatory parameter0
5.2An archetype request is an interface, not a download0
5.3An audit log request covers the trail, not the record0
5.4Parameters, arguments or segments as the transport requires0
5.4-extensionA local extension stops at its jurisdiction0
6.1-actorsThree roles in one interaction0
6.1-preconditionsFive dependencies the standard does not supply0
6.1-pushPush, notification and delegation are outside the scope0
6.1-refusalA refusal is a privacy control0
6.1-usecasesSeven use cases, and the parameters each one needs0
7.1Clause 7.1: the request for an EHR extract0
7.2Clause 7.2: the request for one or more archetypes0
7.3Clause 7.3: the request for an audit log extract0
7.4Clause 7.4: the term lists0
baselineWhat can be done before the draft text lands0
dateWhy the planning date is an estimate, and how it was derived0
editionThe draft page gives two different edition numbers0
p1-archetype-paramsThe archetype request descriptors0
p1-audit-paramsThe audit log request parameters, and the policies covered0
p1-intersectionConstraints combine as an intersection, not a choice0
p1-paramsThe extract request parameters held in the first edition0
p1-reasonsThree refusal reasons, and what each one may not reveal0
p1-responseThe extract response, the filter note and the recipient0
p1-termsThe first edition defined thirty-seven terms; the second defines two0
pagesTwelve pages, and what the page count does not tell you0
part4-2026Part 4 was revised in 2026, and the audit interface depends on it0
pr-auditThe audit log extract is a separate flow with its own owner0
pr-contractThe contract line that names the edition and the interface0
pr-evidenceThe evidence pack a reviewer opens first0
pr-registerKeep the register, the preview and the held edition together0
pr-supplierSix questions for a supplier that claims conformance0
providerThe provider is used throughout but no longer defined here0
recordWhat the ISO catalogue page records, field by field0
revThe third edition is in ballot; the 2019 edition applies0
seriesThe five parts, and which one holds what0

Tell me when ISO 13606-5:2019 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for ISO 13606-5:2019, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition