Interoperable registries
Nexus Registry is the platform of The Global Centre for Risk and Innovation (GCRI) for public-safe records of programmes, evidence, publication status and correction histories, subject to owner authority. Records are useful only if others can cite and reuse them reliably. This page describes the stable references and permitted interfaces the Registry is designed to offer, and publishes each interface and its documentation as it is released. No interface is shown as available until it is released. The current service level is R0: information and enquiries.
- 01FieldsGovernance and institutions, Research and evidence
- 02STEM methods3 canonical methods applied
- 03Topics8 subject pages
- 04Counterparts5 platforms in shared fields
- 05PublisherThe Global Centre for Risk and Innovation
GCRI · Established · service level R0
The short answer.
Nexus Registry interfaces are the stable references and permitted machine interfaces through which others can cite and reuse released records. Each interface and its documentation is published only when it is released, with its version and terms of use; until then none is shown as available.
Jurisdictions in West Africa.
The jurisdictions that hold authority over this question: countries, their first-level divisions and capitals, shown for West Africa as an example geography for this subject.
Every public record is designed to keep one address.
A permanent identifier
Each record has one identifier that is never reused, even if the record is withdrawn.
A resolvable address
The identifier resolves to the record's public page, or to a notice explaining why it is no longer shown.
Version-aware citation
Citations can point to the current version or to a specific earlier one.
What machine access is designed to cover.
- 01
Read access to public records
Retrieval of released public records and their metadata, never restricted or protected records.
- 02
Exports
Machine-readable exports in open formats, such as JSON-LD and the Data Catalog Vocabulary (DCAT), with provenance in W3C PROV.
- 03
Change notices
Notices when a record is corrected, superseded or withdrawn, so copies elsewhere can be updated.
- 04
Documented semantics
Each field's meaning, allowed values and version, published with the interface.
No interface is released yet.
Interfaces and their documentation will be listed here as each is released, with its version and terms of use. Until then, records can only be cited by their public pages, once public records are released. Technical interfaces across Nexus Foundry are described on developers and integrations.
Reusing a record through an interface carries its rights and limits with it. Interface access confers no authority, endorsement or certification.
Terms used on this page.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Persistent identifier | A long-lasting reference to a digital object, person or organisation, such as a DOI, ORCID iD or ROR ID, that resolves even when locations change. |
| Interoperability | The ability of health information systems to exchange data and use it with the same meaning, using standards such as HL7 FHIR. |
| DCAT | The W3C Data Catalog Vocabulary for describing datasets and data services in catalogues. |
Designed to work with other registries.
Registries held by statistics offices, libraries, research funders and programme partners keep their own authority. The Nexus Registry is designed to link to their records by reference rather than copying them, with aliases preserved so an external identifier still resolves.
Questions and answers.
Is there an API I can use now?
Will restricted records be available through an interface?
Can my registry link to Nexus records?
What happens to a link if a record is withdrawn?
Will interfaces change without warning?
Around Nexus Registry.
Bring your expertise to this field.
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.