Skip to content
StandardStandard sul rischio sanitarioStandard che si applicano
Rischio sanitario

Rischio sanitario: norme applicabili

The 6 standards listed for health risk in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

Standard sul rischio sanitario
Di cosa si compone quest'area: i Nexus Standards che applica (contrassegnati), gli standard aperti che nomina, i dati e i flussi che legge, quindi le aree con cui si integra.Fonte: il registro dei Nexus Standards: la scheda dell'area.
  • Nexus Standards: NS-0, NS-1, NS-3, NS-9, NS-10, NS-11.
  • Standard aperti: Regolamento sanitario internazionale (2005); Strumento di valutazione esterna congiunta, terza edizione; HL7 FHIR; Classificazione internazionale delle malattie, 11ª revisione (ICD-11); Health Emergency and Disaster Risk Management Framework; IASC Operational Guidance on Data Responsibility in Humanitarian Action.
  • Dati e flussi: WHO Disease Outbreak News; eventi di sanità animale WAHIS; popolazione su griglia WorldPop; rianalisi ERA5 (Copernicus Climate Data Store).
  • Si collega a: Pericolo biologico; Acqua; Atmosfera e qualità dell'aria; Rischio per le catene di approvvigionamento e il commercio.
Nexus Standards
6
NS-0, NS-1, NS-3
Standard aperti
6
indicati, mai copiati
Dati e flussi
4
elencato per riferimento
Accoppiamenti
4
con altre aree
01NS-0

Costituzione e principi

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.

RegolaTesto
NS0-P1Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied.
NS0-P2Prima di tutto leggibile da una macchina · Ogni elemento normativo esiste come dato (registro, schema, clausola) prima di esistere come testo; il testo spiega, i dati governano. Uno standard privo di forma leggibile da una macchina non è un Nexus Standard.
NS0-P3Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
NS0-P4Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the supported claim level of the implementation bounds every statement it makes.
NS0-P5Zero trust · Authenticated is not authorised; entitled is not authorised; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate.
NS0-P6Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant.
NS0-P7Provenance everywhere · Every artefact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten.
NS0-P8Onesto · Un UNI identifica e risolve; non certifica mai. legalState defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge.
NS0-P9Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artefacts in another domain, and cascades are first-class.
NS0-P10Names are governed · Codes are never names. Public names follow the marks policy (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone’s mark.
NS0-P11Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed.
NS0-P12Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass.

Leggi NS-0 per intero

02NS-1

L’UNI e il catalogo degli artefatti (grammatica v0.2: segmenti di dominio, settore, regione e ambiente)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000001.

RegolaTesto
NS1-R1One UNI shall identify one artefact concept; versions share the UNI and differ in @VERSION.
NS1-R2UNIs shall be allocated only through a catalogue (mint) or a record allocation authority (NS-3); they shall not be typed by hand.
NS1-R3UNIs shall not be deleted or reused. A withdrawn artefact keeps its record (WITHDRAWN); a replaced one records supersededBy.
NS1-R4Every record shall carry the required metadata; legalState per impostazione predefinita richiede un esame; claimCeiling stays inside the claim registry.
NS1-R5The UNI shall be embedded in the artefact itself so that machines and people can find the record (section 6).
NS1-R6A regional artefact shall carry REGION; public regional or national use still follows the geographic rules of the marks policy.
NS1-R7Codes are classification and shall not be used as product names.
NS1-R8A new scope, domain, sector or environment code shall meet the allocation rules CA-1 to CA-10 (section 1.1) and shall enter through an NS-13 proposal.
NS1-R9A code shall not be reassigned or deleted; a retired code is deprecated with supersededBy, and identifiers that use it remain valid.
NS1-R10A PROPOSED identifier may be used and shall be shown with its status until the registry change is adopted.

Leggi NS-1 per intero

03NS-3

UNI dei record di rischio (grammatica, corrispondenza con il pregresso, autorità di assegnazione)

Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.

NS-3 formula i propri requisiti in sezioni anziché in una tabella di regole.

Leggi NS-3 per intero

04NS-9

UNI contestuali (distribuzioni, istanze, istanze di programma)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.

RegolaTesto
NS9-R1Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve.
NS9-R2Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand.
NS9-R3The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context.
NS9-R4Closing a context shall not delete it: context.validUntil è impostata e lo stato diventa WITHDRAWN or SUPERSEDED con supersededBy.
NS9-R5Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere.

Leggi NS-9 per intero

05NS-10

Politiche e clausole (obblighi leggibili dalle macchine: definizione, vincolo, valutazione e applicazione)

Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.

RegolaTesto
NS10-R1Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it.
NS10-R2Subjects shall be contextual UNIs; names, labels or free text shall not bind.
NS10-R3The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs.
NS10-R4External obligations shall be cited, not copied.
NS10-R5Failure effects shall be typed; refuse è l'impostazione predefinita per blocking clausole in contesti di produzione.
NS10-R6A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review.
NS10-R7Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record.

Leggi NS-10 integralmente

06NS-11

Verifica e monitoraggio (evidenze, attestazioni, osservazione della conformità zero-trust)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.

RegolaTesto
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
NS11-R5Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.

Leggi NS-11 per intero

07Domande

Domande e risposte.

Are these all the rules for health risk?
Sono le regole enunciate dagli standard elencati. I principi di NS-0 vincolano ogni standard; le clausole specifiche dell'area, ove necessarie, sono scritte in NS-10 e valutate in NS-11.
Che cosa indica un identificativo di regola come NS1-R5?
Il numero dello standard e il numero della regola al suo interno. Gli identificatori delle regole sono stabili, in modo che clausole, attestazioni e pubblicazioni possano citarli.
Standard

Contribuisci a definire gli standard sui rischi per la salute.

Governi, autorità di regolamentazione, organismi di normazione, industria, mondo accademico e comunità sono invitati a contribuire a plasmare il catalogo prima della sua prima pubblicazione ufficiale, prevista per il 2030: commentare una bozza, proporre una modifica, aderire a un gruppo di lavoro o ospitare un'esercitazione sul campo.

Stato e uso. I Nexus Standards sono standard proposti, sviluppati con un processo aperto ai sensi di NS-13 e pubblicati per uso volontario; non costituiscono certificazione, accreditamento né approvazione regolamentare, e l’adozione resta una decisione del Global Standards Council e, in ogni paese, del suo National Standards Council. Un UNI (Unique Nexus Identifier) identifica un artefatto; non lo certifica. I nomi degli enti di normazione e dei loro standard appartengono ai rispettivi titolari e sono usati solo per identificare i documenti; nessun testo di standard esterni è riprodotto qui. Nexus Standards non è affiliato, sostenuto né certificato da alcun ente di normazione qui citato.

Licenze: CC BY 4.0 per il testo degli standard, i registri, gli schemi e i dati; Apache-2.0 per il codice di riferimento. Gli standard esterni sono citati per nome, numero e link secondo le rispettive licenze. Dati, librerie e font di terze parti mantengono le proprie licenze: vedi Avvisi di terze parti.