United States Patient Care Summary (US-PCS) Implementation Guide
1.0.0 - STU 1
United States Patient Care Summary (US-PCS) Implementation Guide
1.0.0 - STU 1
This page is part of the US Patient Care Summary (US-PCS) Implementation Guide (v1.0.0: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Page standards status: Informative |
This Implementation Guide was balloted in May 2026 ballot cycle by HL7.
US-PCS requires the minimal use of US Core Implementation Guide 6.1.0 to populate the Patient, Organization, Practitioner and individual clinical resources within US-PCS sections.
US-PCS derives its Bundle and Composition profiles from FHIR Clinical Documents Implementation Guide 1.1.0. Changes have been made to align these profiles with FHIR IPS 2.0.1 and include edits for the US ecosystem. The definition of "derive" for purposes of US-PCS is "to formally base a specification through defined profiling or inheritance, remaining fully conformant while adding only further constraints."
US-PCS seeks to align with the FHIR IPS International Patient Summary Implementation Guide 2.0.1. The definition of "align" for purposes of US-PCS is "a specification or implementation produces content and behavior that are generally consistent with IPS goals, principles, and expectations, regardless of whether it formally derives from IPS artefacts. Alignment does not, by itself, imply derivation from or conformance to IPS specifications."
All US-PCS document instances will conform to the FHIR IPS International Patient Summary Implementation Guide 2.0.1 with no errors. The definition of "conform" for purposes of US-PCS is "to satisfy the applicable requirements defined by the FHIR IPS implementation guide with no errors"
Specific differences between IPS and US-PCS are described in the US Variance to IPS page.
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 hl7.fhir.uv.extensions.r4#5.3.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, May 16, 2026 18:32+1000+10:00) |
Package hl7.fhir.uv.ipa#1.1.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 Wed, Mar 19, 2025 14:34+0000+00:00) |
Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00) |
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. |
Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00) |
Package hl7.fhir.us.core#6.1.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Fri, Jun 30, 2023 14:02+0000+00:00) |
Package hl7.fhir.uv.xver-r5.r4#0.1.0 Extensions for Using Data Elements from FHIR R5 in FHIR R4 (built Fri, Mar 20, 2026 15:40+1100+11:00) |
Package hl7.fhir.uv.tools.r4#1.1.2 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00) |
This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.us.pcs.r4) and R4B (hl7.fhir.us.pcs.r4b) are available.
There are no Global profiles defined
| Parameter | Value |
|---|---|
| system-version | SNOMED CT[US] |
IG © 2026+ HL7 International / Cross-Group Projects.
Package hl7.fhir.us.pcs#1.0.0 based on FHIR 4.0.1.
Generated
2026-09-15
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change
