Care Coordination Implementation Guide

Closing the loop on referrals: an IHE-based look at care coordination in England (proof of concept)

I’ve been using Claude to help build an experimental FHIR Implementation Guide. It asks one question: what would patient care coordination in England look like if we started from international standards and then checked NHS England’s services against them?

:link: Home - Care Coordination and 360 Referrals (Proof of Concept) v0.1.0

The core pattern is the closed-loop referral, adapted from IHE 360X:

  • A referrer sends a patient to another provider.
  • The provider accepts or declines, then delivers care.
  • The outcome comes back to the referrer, because a referrer can’t evaluate care they never hear about.

The guide treats referrals, lab orders and imaging requests as one “order out, report back” pattern.

It follows the IHE layout, so different people can start in different places:

:stethoscope: Clinical informatics: Volume 3 (Data Models)

  • PRSB Standards (PRSB Standards - Care Coordination and 360 Referrals (Proof of Concept) v0.1.0): about 30 PRSB standards (referral, letters and discharge, care plans, screening and cross-cutting). Each is mapped to the workflow interaction that would carry it, and to EU artefacts such as the HL7 Europe Hospital Discharge Report and the International Patient Summary. Gaps and open questions are flagged openly.
  • Templates and Forms (Templates and Forms - Care Coordination and 360 Referrals (Proof of Concept) v0.1.0): PRSB standards keep reusing the same sections (demographics, allergies, medications, diagnoses, social context, individual requirements). Clinical facts become FHIR resources. Sets of questions answered at one time become Questionnaire forms. The page also separates a care assessment from a care plan, two things we often blur in the NHS.

:laptop: Developers: Volume 2 (Interactions)
How IHE profiles guide the use of every flavour of HL7: v2 messaging (360X, following NW GMSA conventions), CDA/XDS document sharing, and FHIR R4 (MHD, QEDm). It covers each transaction: referral request, decline, outcome, cancellation, interim note, appointment and no-show, and querying existing data.

:clipboard: Business analysis: Volume 1 (Analysis and Design)
Clinical Process (Clinical Process - Care Coordination and 360 Referrals (Proof of Concept) v0.1.0) gives high-level pathway descriptions built on the nursing process: Assess, Diagnose, Plan, Implement, Evaluate. It shows where lab and imaging orders, referrals, virtual wards (Hospital at Home), prescribing and team care coordination fit in.

:hospital: NHS England alignment
The appendices map the generic model onto NHS England services: e-Referral Service, BaRS, Transfer of Care, MESH, GP Connect, EPS, PDS and diagnostic order services. NHS England standards aren’t assumed to be right. They’re checked against the general pattern, and conflicts and gaps are called out, not hidden.

:warning: This is a draft proof of concept for discussion only. It isn’t endorsed by NHS England, IHE, HL7 or PRSB, and it isn’t for implementation or clinical use.

I’d welcome comments from PRSB, IHE, HL7 UK/Europe and NHS colleagues, especially on the PRSB mappings still marked “to confirm”.

FHIR #IHE #HL7 #PRSB #InteroperabilityNHS #ClinicalInformatics #EHDS #DigitalHealth

Hi Kev,

This is very interesting work. It is amazing what can be done one level up from code by using LLMs. A natural progression I feel from reading binary → assembly → higher level languages → LLMs.

I am keen to read what you have written and will get back to you when I do.

Mark

Had some feedback from PRSB and it took around 10 mins to add in links to FDP Canonical Data Model - was a bit surprised it was that easy.

I might add in openEHR? @ian any tips?
It’s this page I think is useful for informatics Templates and Forms - Care Coordination and 360 Referrals (Proof of Concept) v0.1.0