1 | The boundary test | 0 |
1-relations | Three artefacts travel, two models do not | 0 |
1-secondary | Secondary uses are outside the focus, not forbidden | 0 |
2 | The normative references, and the edition you must pin | 0 |
3.1 | The requester is defined by the act of asking | 0 |
3.2 | The recipient is not always the requester | 0 |
4 | The abbreviations clause is the interface shorthand | 0 |
5.1 | An extract request carries every mandatory parameter | 0 |
5.2 | An archetype request is an interface, not a download | 0 |
5.3 | An audit log request covers the trail, not the record | 0 |
5.4 | Parameters, arguments or segments as the transport requires | 0 |
5.4-extension | A local extension stops at its jurisdiction | 0 |
6.1-actors | Three roles in one interaction | 0 |
6.1-preconditions | Five dependencies the standard does not supply | 0 |
6.1-push | Push, notification and delegation are outside the scope | 0 |
6.1-refusal | A refusal is a privacy control | 0 |
6.1-usecases | Seven use cases, and the parameters each one needs | 0 |
7.1 | Clause 7.1: the request for an EHR extract | 0 |
7.2 | Clause 7.2: the request for one or more archetypes | 0 |
7.3 | Clause 7.3: the request for an audit log extract | 0 |
7.4 | Clause 7.4: the term lists | 0 |
baseline | What can be done before the draft text lands | 0 |
date | Why the planning date is an estimate, and how it was derived | 0 |
edition | The draft page gives two different edition numbers | 0 |
p1-archetype-params | The archetype request descriptors | 0 |
p1-audit-params | The audit log request parameters, and the policies covered | 0 |
p1-intersection | Constraints combine as an intersection, not a choice | 0 |
p1-params | The extract request parameters held in the first edition | 0 |
p1-reasons | Three refusal reasons, and what each one may not reveal | 0 |
p1-response | The extract response, the filter note and the recipient | 0 |
p1-terms | The first edition defined thirty-seven terms; the second defines two | 0 |
pages | Twelve pages, and what the page count does not tell you | 0 |
part4-2026 | Part 4 was revised in 2026, and the audit interface depends on it | 0 |
pr-audit | The audit log extract is a separate flow with its own owner | 0 |
pr-contract | The contract line that names the edition and the interface | 0 |
pr-evidence | The evidence pack a reviewer opens first | 0 |
pr-register | Keep the register, the preview and the held edition together | 0 |
pr-supplier | Six questions for a supplier that claims conformance | 0 |
provider | The provider is used throughout but no longer defined here | 0 |
record | What the ISO catalogue page records, field by field | 0 |
rev | The third edition is in ballot; the 2019 edition applies | 0 |
series | The five parts, and which one holds what | 0 |