Patient Care Coordination (PCC) Implementation Guide, published by Virtually Healthcare. This guide is not an authorized publication; it is the continuous build for version 0.1.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Virtually-Healthcare/R4/ and changes regularly. See the Directory of published versions

Home

Official URL: https://fhir.virtually.healthcare/ImplementationGuide/fhir.virtually.healthcare				Version: 0.1.1-current
Draft as of 2025-07-09				Computable Name: VirtuallyHealthcare_IHEPCC

Patient Care Coordination (PCC)

Clinical Process

The Patient Care Coordination (Community) is designed around supporting clinical processes in primary, pharmacy and community care settings. It is aligned with Nursing Process (ADPIE)

Nursing Process (ADPIE)

This uses a series of common data and interaction standards (green in the diagram below) which allows different applications to be connected together. These interfaces will often provide a layer of extraction of over other interfaces such as:

• Consultation Note
  • GP Connect Send Document
  • NHS England Digital Medicines
  • NHS England IM1 Transaction API
• Referral Letter
  • NHS England Booking and Referral Standard (BARS)
  • NHS England Electroninc Referral System (eRS)
• Patient Clinical Data Sharing
  • GP Connect Access Record: HTML
  • GP Connect Access Record: Structured
  • GP Connect Access Record: Document
  • NHS England IM1 Transaction API
• Care and Patient Directory
  • NHS England Personnel Demographic Service (PDS)
  • Directory of Service (DoS)
  • Organisation Data Service
  • Spine Directory Service

Patient Care Coordination Manager (Community)

Enterprise and Data Standards

Enterprise Frameworks

A number of frameworks IHE Patient Care Coordination (PCC) are followed in this guide, including:

• Query for Existing Data for Mobile (QEDm)
• Dynamic Care Planning (DCP)
• Mobile access to Health Documents (MHD) (A REST API for IHE XDS.b and EDMS)
• Mobile Care Services Discovery (mCSD)
• Patient Demographics Query for Mobile (PDQm)

Technical Workflow

The interactions use HL7 FHIR and is designed to be compatible with:

• HL7 v2 Messaging via:
  • FHIR Messaging - a direct conversion of HL7 v2 Messaging
  • HL7 FHIR Workflow which allows Conversation Patterns
  • HL7 FHIR Subscription
• HL7 Clinical Document Architecture via:
  • FHIR Documents

Data Standards

Support for these frameworks includes core canonical data model/domain model which meets general NHS requirements:

• UK SNOMED CT for our clinical terminology.
• NHS Data Dictionary for identifiers and values, such as NHS Number, GMC, GMP, ODS, etc.
• HL7 UK Core.

SNOMED CT

UK edition of SNOMED (83821000000107)

Dependencies

Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package fhir.r4.ukcore.stu3.currentbuild#0.0.19-pre-release UK Core FHIR profiles and Assets

Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. This includes two components: * Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains. *Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:32+0000+00:00)

Package hl7.fhir.uv.ipa#1.0.0 This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Sun, Mar 26, 2023 20:50+0000+00:00)

Credits

Role(s)	Contributor(s)
	Virtually Healthcare
Enterprise Architect	Kevin Mayfield (Mayfield IS)