Home
Welcome to the GP Connect Data Model: FHIR Representation (STU3)
This guide provides a comprehensive overview of the GP Connect data model as represented using the Fast Healthcare Interoperability Resources (FHIR) standard, specifically within the STU3 (Standard for Trial Use 3) version.
What is GP Connect?
GP Connect is a program designed to enable better access to patient information and to improve care coordination across the NHS in England. It facilitates the secure sharing of patient data between different healthcare IT systems, primarily focusing on primary care (GP practices) and other care settings. The aim is to ensure that relevant patient information is available to clinicians at the point of care, regardless of where that care is being delivered.
Why FHIR?
FHIR (pronounced "fire") is a next-generation healthcare interoperability standard developed by HL7. It is designed to be highly flexible, easy to implement, and suitable for a wide range of healthcare use cases, including mobile apps, cloud communications, and EHR-to-EHR information exchange. FHIR achieves this by:
Using modern web technologies: It leverages familiar web standards like RESTful APIs, JSON, and XML for data exchange, making it more accessible to a broader developer community.
Focusing on "resources": FHIR defines discrete "resources" representing common clinical and administrative concepts (e.g., Patient, Observation, Medication). These resources are modular and can be combined to build complex clinical documents and workflows.
Emphasizing implementability: FHIR aims to be quick to implement, with clear specifications and abundant tooling.
Why STU3?
STU3 refers to the third "Standard for Trial Use" release of the FHIR specification. While not yet a normative (fully ratified) standard, STU3 was widely adopted and matured significantly during its trial period. It laid much of the groundwork for subsequent normative releases and is still relevant for many existing implementations, including early phases of GP Connect.
Why this guide exists
This guide serves as a crucial resource for anyone involved in developing, implementing, or understanding systems that interact with GP Connect data. Specifically, it aims to:
- Bridge the gap: Translate the conceptual GP Connect data model into its concrete FHIR STU3 representation.
- Provide clarity: Detail how specific GP Connect data elements map to FHIR resources, profiles, and extensions.
- Facilitate interoperability: Offer a common understanding and reference point to ensure consistent and accurate data exchange between disparate systems.
- Support development: Assist developers in building robust and compliant applications that can effectively consume and produce GP Connect data using FHIR STU3.