International

ISO 13606-1:2019

44 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.

44 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
0.5-archThe archetype identifier labels a record component0
0.5-baseIdentity, version and attestation on the base component0
0.5-demoDemographics use the record mechanics0
0.5-extExternal links carry non-record references0
0.5-folderA folder carries its subject of care0
0.5-linkLinks have their own identity0
0.5-nullNull flavour is a reference archetype0
0.5-policySensitivity and policy belong to the composition0
0.6-auditAudit information travels with the extract0
0.6-typesData values are a profile of the harmonised types0
1The communication boundary0
10.1Demographics rebuilt on the record mechanics0
10.2The demographic folder0
10.3The demographic entity0
10.4The demographic item0
10.5The demographic cluster0
10.6The demographic element0
11What a claim of conformity has to say0
2The dated data type reference0
3.1Composer, committer, attester: who is accountable0
3.2Generic versus local: where the model stops0
3.3Archetype, archetype model and the client application0
4The abbreviations a reviewer will meet0
5.1The reference model in one picture0
5.2Roles and responsibilities inside an extract0
5.3How the model uses data types0
6.1Base, record and structure components0
6.2Attestation, attested views and proof0
6.3Audit information that a reviewer can follow0
6.4Links, external links and the thread of a record0
7.1Elements, optionality and the null flavour0
8.1The EHR components in overview0
8.2The folder, and the subject of care it carries0
8.3The composition, one agent and one session0
8.4Content and sections under a clinical heading0
8.5The entry, one clinical action or statement0
8.6Clusters, nested data and tables0
8.7The element and the single value it carries0
9.1The EHR extract: what actually travels0
9.2The extracted component set0
9.3The demographic extract0
AAnnex A and the data type profile0
BAnnex B and alignment with HL7 FHIR0
CAnnex C and cross-domain interoperability0

Tell me when ISO 13606-1: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-1: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