Pathway navigator
Acute Admission and Discharge
Acute admission, inpatient care and discharge pathways, including entry routes, care transitions, evidence dependencies and service-design questions.
About the collection
A catalogue-oriented view of clinical pathways.
The resources treat pathway definitions as technology-neutral business artefacts rather than as EPR workflows or patient-level records. They are intended to support analysis, service design, architecture and catalogue development.
Reference material
These resources are not clinical guidance. The pathway definitions are draft and unapproved. Their purpose is to make pathway scope, decisions, roles, information requirements, evidence and relationships inspectable.
Across the collection, pathway definitions remain distinct from local implementations and from the actual care experienced by an individual patient. That separation allows organisations to compare intended models of care without assuming that every organisation must use the same systems, workflow engine or local operating model.
DefinitionThe intended model of care and its business meaning.
ImplementationHow a particular organisation realises that definition through services, workforce and technology.
InstanceThe actual course of care experienced by an individual, which sits outside these reference catalogues.
Pathway description
The underlying proposal and demonstrator.
HPDS proposes a consistent way to describe pathways as catalogue-ready business artefacts while remaining neutral about workflow engines, EPR products and exchange technologies.
Working proposal
Healthcare Pathway Description Standard
Explore the proposed information model, its separation of pathway definition, implementation and instance, its relationship with complementary standards and its graded approach to conformance.
Explore HPDS → DemonstratorFrailty and Multimorbidity Demonstrator
See how a synthetic pathway catalogue can remain clinically recognisable while being separated from local delivery arrangements, shared-record capabilities and technical implementation detail.
Open demonstrator →How to use the collection
Use the navigators to investigate pathways, not to prescribe care.
Service design
Inspect boundaries, hand-offs, roles, decisions, outcomes and dependencies before translating a pathway into local operating arrangements.
Architecture and informatics
Relate information requirements and interoperability concerns to the pathway without embedding the pathway definition in a particular application architecture.
Catalogue development
Use the examples to test whether HPDS can support discoverable, comparable and governable pathway catalogues across different clinical domains.
Resource library
Looking for architecture, interoperability or data resources?
Return to the main Agile Health Informatics resource library to browse the wider collection by subject and resource type.