Core Metadata

These fields are required for any capability to be listed within Health Data Connect, regardless of readiness category.

Title

The official name of the capability.

Category

Shows what kind of resource this is, to help you understand how it is intended to be used. For more details see the categories page. Some resources sit in more than one category if they serve different purposes.

Description

What this is and why it exists.

Primary purpose

The system problem it addresses.

Intended users

Who this is designed for. For example Researchers, NHS teams, Industry, Funders, SDE/TRE teams, Data custodians …

Owner organisation

Who owns / stewards the capability.

Primary contact route

How to initiate engagement. For example email, form, URL, named role.

Links

Authoritative links to further information or documentation.

Context of use

Intended operational or research context.

Readiness tier

The maturity of the capability. The Tiers are Exploratory, Emerging, and Established.

Lifecycle stage/Maturity – TFS

Indicates how ready this resource is to be used. This helps to understand whether it is still being tested or already in routine use.

Decision-support metadata – relevance

Primary use cases

The top 3 concrete situations where this is appropriate.

Intended outcomes

What benefit this enables.

What it is not

Common misunderstandings to avoid.

Evidence of use

Where and by whom it has been used.

Adoption scale (if known)

Indicative level of uptake.

Preconditions

What must be in place before use.

Constraints

Known limitations or exclusions.

Dependencies

External standards or services required.

Cost / commercial model

Cost / commercial model Controlled + text How it is funded or charged Free / cost-recovery / commercial / unclear

Free / cost-recovery / commercial / unclear

Licence / terms

Usage conditions: CC-BY, CC-BY-NC, Open source, Proprietary, N/A

Support level

Support available: None / Community / Light-touch / Supported service

Decision-support metadata – next steps

Engagement pathway

Typical steps from interest to use.

Response expectations

Indicative response time.

Ownership boundary

What the owner will and won’t do.

Related or alternative capability

Comparable or adjacent capability.

Originator Type

The type of organisation that developed or runs this resource. For example, an NHS organisation, research group, charity, industry partner or collaborative programme.

Originator Organisation(s)

Shows who created, owns or maintains this resource. This helps to understand where it comes from and who is responsible for it.

DOI Link

A permanent link to a published output related to this resource. DOIs are commonly used for reports or research outputs and do not change over time.

Use Potential

Explains what this resource is useful for and the kinds of activities it supports. This is intended to help you quickly judge whether it is relevant to your work.

No. Adopting

Gives an indication of how widely this resource has been taken up. This may reflect the number of organisations, teams or settings using it.

Adoption Examples

Shows where this resource has already been used in practice. These examples help illustrate how it has been applied in real-world settings.

Registered Users / Access Numbers

Provides a sense of the scale of use of this resource. This may show how many people or organisations are engaging with or accessing it.

Licence

Explains whether there are any conditions on how this resource can be used. For example, whether it is openly available or subject to specific terms.

Version / Date

Shows when this resource was last updated or reviewed.

Contact Us

Provides a way to ask questions or get guidance about this resource.