Agile Health Informatics Ltd · Professional resource

Health Data Lifecycle Navigator

A practical guide to keeping health information usable, interpretable, governable, trustworthy and operationally actionable as it is created, linked, transformed, exchanged, reused and preserved across systems, organisations and time.

12lifecycle phases
12cross-cutting capabilities
15standards and frameworks mapped
9problem-led scenarios
Core proposition

Data operability is maintained across a lifecycle, not granted by an interface.

The navigator is based on the Health Data Operability Framework described in Health Data Operability: From Data Exchange to Shared Understanding. The phases are a shared vocabulary, not a rigid sequence. Operational phases may repeat continuously, while governance and preservation evolve on a slower cadence.

Meaning must survive

Semantic fidelity is longitudinal. A record can be technically accessible and still become unsafe if the definition, terminology version, workflow state or interpretive context has been lost.

Quality is contextual

Fitness for purpose must be stated. Data suitable for direct care may not be suitable for research, AI training or regulation. A new use therefore requires a new fitness judgement.

Metadata is infrastructure

Context must outlive applications. Definitions, provenance, lineage, purpose and usage conditions need independent stewardship so that meaning survives system replacement and organisational change.

Decision aid

Start with the work being attempted, not with a technology.

Choose a scenario to see which lifecycle phases become critical, what must be evidenced, and which failure modes deserve explicit assurance.

Choose a scenario to generate a lifecycle-focused assurance view.

The navigator asks four questions
1What was the data originally created to do?
2What meaning and context must remain attached?
3What transformation or boundary is now being crossed?
4What evidence would allow a later user to trust the result?
The metadata envelope

The data item alone is not the unit that must survive.

The book identifies provenance, method, intent and constraints as recurring conditions of meaning. The navigator extends that envelope to include quality, lawful basis and lineage so that a later person or machine can judge whether the data remains fit for use.

Provenance

Who or what created the data, in which role, system, organisation and time context?

Method

How was it observed, calculated, measured or inferred, and under which protocol or instrument?

Intent

Why was it recorded, and what operational or clinical purpose gave the entry significance?

Constraints

Where should it not be relied upon, and what limits its validity across population, place or time?

Quality

For which uses has fitness been assessed, against which expectations, and with what residual uncertainty?

Lawful basis

What permits the processing or disclosure, and do the permitted purposes change when the use changes?

Lineage

Which transformations, mappings, derivations and linkages have altered the data since capture?

Representation

Which models, terminology versions, units and reference definitions are required to interpret it later?

Cross-cutting capabilities

The disciplines that must remain present at every phase.

These are not extra lifecycle stages. They are persistent capabilities whose absence allows operability to decay even when individual technical steps appear successful.

Standards map

No single standard covers the lifecycle.

Standards are shown according to the phases where they make their strongest contribution. This is a scope map, not a maturity ranking. A standard can be excellent within its intended purpose while leaving other phases deliberately untouched.

Failure patterns

Recognise the point at which a sensible local decision creates long-term semantic debt.

The recurring anti-patterns are dangerous because each begins with a reasonable delivery instinct. The navigator makes the deferred lifecycle cost visible.

Quick maturity lens

How capable is the organisation of preserving operability over time?

This lightweight self-assessment uses the six dimensions in the book’s Operability Capability Maturity Model. It is diagnostic rather than an assurance score and deliberately avoids false numerical precision.

Reference summary

The twelve obligations in one view.

PhaseOperability concernGovernance responsibility
Source register

Basis of the navigator.

The lifecycle content is grounded in the supplied Health Data Operability material. Standards references are used to locate established specifications within the lifecycle rather than to imply that they collectively constitute the framework.

SRC-01 · Health Data Operability: From Data Exchange to Shared Understanding

Primary source for the definition of data operability, the twelve-phase lifecycle, the two-ring model, cross-cutting capabilities, transformation anti-patterns, maturity dimensions and preservation argument. Supplied by the author.

SRC-02 · HDOF Strategic Framework working draft v0.1

Supporting source for the explicit lifecycle/governance framing, cross-cutting capability set and mapping of standards and regulatory concerns to lifecycle phases.

Design reference · Healthcare Standards Navigator

Visual and interaction reference for palette, card treatment, responsive structure, navigation and professional-resource presentation. The Health Data Lifecycle Navigator remains a distinct resource with a different conceptual model.

Method note. The standards map is interpretive. It identifies where a specification is particularly relevant, not where it is legally mandated, nor does it assert that listed standards are sufficient to deliver data operability. Jurisdiction-specific legal and regulatory obligations should be assessed separately for each implementation.