The Global Centre for Risk and Innovation (GCRI)
The Nexus Foundry systems that serve Health Nexus, what an authorized project can do with them, and how access is requested.
Build in Nexus Foundry · Workspace WS-62
| Indicator-based surveillance | v5.1 | To check | OBSERVED |
| Event-based signals | v2.3 | To check | UNVERIFIED |
| Hospital capacity returns | v2.1 | Open | REPORTED |
| Laboratory results | v5.4 | Open | OBSERVED |
share used vs alert level
Health Nexus · PipelinePipeline, in outline: domain structure with placeholder names and illustrative values, not a record.
Building in Nexus Foundry is how authorized Health Nexus projects use the shared technical systems that serve health and biosecurity: GRIx, EWS, DSS and Hub. Access requires an accountable project owner, data terms and a review plan, and allocations open only when their terms and review capacity exist. Foundry work produces designs and analyses with their limits, not operational services.
Fig.A programme from scoping to the owner's decision. Design, not a record.
How far each division sits from a large city, with the roads and airports that carry patients and supplies, shown for the Congo Basin as an example geography for this subject.
Describe the project and its owner to contact@therisk.global.
Access requires an authorized project with an accountable owner, data terms and a review plan.
Compute and data allocations open when their terms and review capacity exist.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Digital twin | A computational representation of a physical system that is updated with data from it and used to explore its behaviour. |
| Provenance | Information about the entities, activities and people involved in producing a record, used to judge its quality and reliability, in the W3C PROV model. |
| Least privilege | Granting each user or process only the access needed for its current task. |
| Workflow orchestration | Automated management of the order, execution and recovery of computational tasks. |
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.