PACIO Sample Data Depot
0.1.0 - draft

PACIO Sample Data Depot, published by MITRE. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/paciowg/sample-data-fsh/ and changes regularly. See the Directory of published versions

PACIO Sample Data Repository

Official URL: http://mitre.org/paciowg/ImplementationGuide/fhir.paciosampledata Version: 0.1.0
Draft as of 2025-08-26 Computable Name: PACIOSampleData

Background

This is a workbook project to create and manage sample data used in PACIO Connectathons. Prior PACIO Connectathons created sample data by manually crafting FHIR resources in JSON and pushed to a GitHub directory named sample data (https://github.com/paciowg/sample-data) that acted as a data store for these files, organized by each Connectathon. This method proved cumbersome to create and maintain. Furthermore, it was less readable by participants that wanted a quick and easy way to inspect the content.

The PACIO content team proposed a new way to create and maintain FHIR sample data to address these limitations by authoring them in FHIR Shorthand (FSH) using the "SUSHI Unshortens Short Hand Inputs" (SUSHI) FSH authoring reference implementation. This provided several benefits over the original method:

  • auto-generated human-readable FHIR resource examples with a generated narrative.
  • ability to link examples with a storyboard and persona.
  • FHIR resource validation using the FHIR IG Publisher which generates higher-quality data conformant with its tested FHIR implementation guide (IG).

Assumptions and Caveats

  • All examples are based in FHIR 4.0.1 and share the same IG dependencies.
  • The initial version of this release were based on the following Connectathon sample data:
    • September 2024 Connectathon 37 PACIO Standardized Medication Profile (SMP) and Personal Functioning Engagement (PFE) Track
    • January 2025 Connectathon 38 Transitions of Care (TOC) Track
  • Many of the previously created FHIR examples used in past Connectathons contained syntax and semantic errors that were not validated. In some cases, the examples needed to be modified in order to pass validation.

Credits

  • PACIO Project team

Dependencies

IGPackageFHIRComment
.. PACIO Sample Data Depotfhir.paciosampledata#0.1.0R4
... FHIR Extensions Packhl7.fhir.uv.extensions.r4#5.2.0R4Automatically added as a dependency - all IGs depend on the HL7 Extension Pack
... US Core Implementation Guidehl7.fhir.us.core#6.1.0R4
.... HL7 Terminology (THO)hl7.terminology.r4#5.0.0R4
.... FHIR Extensions Packhl7.fhir.uv.extensions.r4#1.0.0R4
.... Bulk Data Access IGhl7.fhir.uv.bulkdata#2.0.0R4
.... SMART App Launchhl7.fhir.uv.smart-app-launch#2.1.0R4
.... VSACus.nlm.vsac#0.11.0R4
.... Structured Data Capturehl7.fhir.uv.sdc#3.0.0R4
.... PHINVadsus.cdc.phinvads#0.12.0R4
.... IHE FormatCode Vocabularyihe.formatcode.fhir#1.1.0R4
... HL7 Terminology (THO)hl7.terminology#5.4.0R4
... Standardized Medication Profile (SMP) FHIR IGhl7.fhir.us.smp#1.0.0-ballotR4
.... HL7 Terminology (THO)hl7.terminology.r4#6.0.2R4
.... FHIR Extensions Packhl7.fhir.uv.extensions.r4#5.1.0R4
... minimal Common Oncology Data Elements (mCODE) Implementation Guidehl7.fhir.us.mcode#3.0.0R4
.... HL7 Terminology (THO)hl7.terminology.r4#5.3.0R4
.... US Core Implementation Guidehl7.fhir.us.core#5.0.1R4
..... HL7 Terminology (THO)hl7.terminology.r4#3.1.0R4
..... SMART App Launchhl7.fhir.uv.smart-app-launch#2.0.0R4
..... VSACus.nlm.vsac#0.7.0R4
.... Genomics Reporting Implementation Guidehl7.fhir.uv.genomics-reporting#2.0.0R4
... PACIO Personal Functioning and Engagement Implementation Guidehl7.fhir.us.pacio-pfe#currentR4
.... HL7 Terminology (THO)hl7.terminology.r4#6.5.0R4
.... SDOH Clinical Carehl7.fhir.us.sdoh-clinicalcare#2.2.0R4
..... US Corehl7.fhir.us.core#3.1.1R4
..... Subscriptions R5 Backporthl7.fhir.uv.subscriptions-backport.r4#1.1.0R4
..... VSACus.nlm.vsac#0.19.0R4
... PACIO Transitions of Care Implementation Guidehl7.fhir.us.pacio-toc#currentR4
.... PACIO Advance Healthcare Directive Interoperability Implementation Guidehl7.fhir.us.pacio-adi#currentR4
..... FHIR Extensions Packhl7.fhir.uv.extensions.r4#5.3.0-ballot-tc1R4
..... US Core Implementation Guidehl7.fhir.us.core#8.0.0R4
...... HL7 Terminology (THO)hl7.terminology.r4#6.4.0R4
...... SMART App Launchhl7.fhir.uv.smart-app-launch#2.2.0R4
....... HL7 Terminology (THO)hl7.terminology#5.5.0R4
...... VSACus.nlm.vsac#0.23.0R4
..... VSACus.nlm.vsac#0.22.0R4
.... PACIO Personal Functioning and Engagement Implementation Guidehl7.fhir.us.pacio-pfe#2.0.0-ballotR4
.... International Patient Summary Implementation Guidehl7.fhir.uv.ips#2.0.0-ballotR4
.... Dental Data Exchangehl7.fhir.us.dental-data-exchange#1.0.0R4
..... C-CDA on FHIRhl7.fhir.us.ccda#1.1.0R4
...... US Corehl7.fhir.us.core#3.1.0R4
..... Da Vinci Health Record Exchange (HRex)hl7.fhir.us.davinci-hrex#0.1.0R4
...... US Core R4hl7.fhir.us.core#3.0.0R4
..... HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.0 (Standard for Trial Use)hl7.fhir.us.odh#1.0.0R4
..... US Core Implementation Guidehl7.fhir.us.core#4.0.0R4
...... FHIR Bulk Data Accesshl7.fhir.uv.bulkdata#1.0.1R4
...... VSACus.nlm.vsac#0.3.0R4
..... HL7 Terminologyhl7.terminology#1.0.0R4
.... C-CDA on FHIRhl7.fhir.us.ccda#2.0.0-ballotR4
..... HL7 Terminology (THO)hl7.terminology.r4#6.1.0R4
... FHIR Tooling Extensions IGhl7.fhir.uv.tools.r4#0.7.1R4for example references

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#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.
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:36+0000+00:00)

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.extensions.r4#5.1.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, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.us.smp#1.0.0-ballot

Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Wed, Aug 14, 2024 18:30+0800+08:00)

Package hl7.fhir.us.core#5.0.1

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 Wed, Jun 22, 2022 19:44+0000+00:00)

Package hl7.fhir.uv.genomics-reporting#2.0.0

Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Mon, May 9, 2022 16:52+0000+00:00)

Package hl7.fhir.us.mcode#3.0.0

mCODE™ (short for Minimal Common Oncology Data Elements) is an initiative intended to assemble a core set of structured data elements for oncology electronic health records. (built Wed, Oct 25, 2023 23:16+0000+00:00)

Package hl7.fhir.uv.subscriptions-backport.r4#1.1.0

The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Wed, Jan 11, 2023 15:34+1100+11:00)

Package hl7.fhir.us.sdoh-clinicalcare#2.2.0

This HL7 Implementation Guide (IG) defines how to exchange Social Determinants of Health (SDOH) content defined by the Gravity Project using the HL7 FHIR standard.. (built Tue, Aug 27, 2024 16:48+0000+00:00)

Package hl7.fhir.us.pacio-pfe#current

FHIR Implementation Guide to exchange assessments of and data on a person's functioning, including body functions, activities, and participation, between post-acute care (PAC) and other providers, patients, and key stakeholders (built Wed, Jul 23, 2025 15:59+0000+00:00)

Package hl7.fhir.uv.extensions.r4#5.3.0-ballot-tc1

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Aug 3, 2025 06:28+1000+10:00)

Package hl7.fhir.us.core#8.0.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 Tue, Jun 10, 2025 15:32+0000+00:00)

Package hl7.fhir.us.pacio-adi#current

PACIO Advance Directive Interoperability Implementation Guide (built Mon, Aug 4, 2025 19:13+0000+00:00)

Package hl7.fhir.us.pacio-pfe#2.0.0-ballot

FHIR Implementation Guide to exchange assessments of and data on a person's functioning, including body functions, activities, and participation, between post-acute care (PAC) and other providers, patients, and key stakeholders (built Tue, Aug 13, 2024 15:07+0000+00:00)

Package hl7.fhir.us.ccda#1.1.0

Consolidated CDA (C-CDA) is one of the most widely implemented implementation guides for CDA and covers a significant scope of clinical care. Its target of the 'common/essential' elements of healthcare is closely aligned with FHIR's focus on the '80%'. There is significant interest in industry and government in the ability to interoperate between CDA and FHIR and C-CDA is a logical starting point. Implementers and regulators have both expressed an interest in the ability to map between FHIR and C-CDA.

This Implementation Guide (IG) defines a series of FHIR profiles on the Composition resource to represent the various document types in C-CDA. This release does not directly map every C-CDA template to FHIR profiles, rather tries to accomplish the C-CDA use case using Composition resource profiles created under this project (the equivalent of Level 2 CDA documents), and begins by linking to the profiles created under the US Core project for any coded entries that would normally be included in C-CDA sections. To have a simpler, more streamlined standard that reuses existing work and focuses on the 80% that implementers actually need in production systems, the resources of US Core represents a portion of the 80% needed for coded entries for coded entries of CCD, Care Plan & Discharge Summary).

The Composition profiles in this IG do not require coded data in any section. This is a departure from C-CDA, which requires coded data for Problems, Results, Medications, etc. This departure is intentional, as the C-CDA requirement for one or more coded entries in these sections resulted in some very complicated workarounds using nullFlavors to handle the fact that sometimes a patient is not on any medications, or has no current problems. In general, FHIR takes the approach that if something is nullable, it should simply be optional to ease the burden on implementers, thus C-CDA on FHIR does not require any coded entries, but rather uses the "required if known" approach, meaning that if an implementer's system has data for a section that requires data under Meaningful Use, they need to send it, but if they have no data there is no need for a null entry.

We encourage feedback on these Composition profiles, and the general approach to the project as a whole. We also encourage implementers who wish to see more of the coded data from C-CDA mapped to FHIR to comment on the US Core project and make their requests known there. Once US Core creates new profiles, this project can reference them.

Scope

To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles.

This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections.

Any coded data used by sections will be represented using relevant U.S. Core FHIR profiles where they exist. FHIR profiles defined by other work groups or unconstrained FHIR resources may also be referenced if no appropriate US Core Profile exist.

For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408.

(built Wed, Oct 21, 2020 22:01+0000+00:00)

Package hl7.fhir.us.davinci-hrex#0.1.0

The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case.

Da Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications.

The HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications were appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations.

HRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Thu, Jun 20, 2019 08:10-0400-04:00)

Package hl7.fhir.us.core#4.0.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 Mon, Jun 28, 2021 19:09+0000+00:00)

Package hl7.fhir.us.dental-data-exchange#1.0.0

This implementation guide provides HL7 FHIR resources to define standards for bi-directional information exchange between a medical and a dental provider or between dental providers. This publication provides the data model, defined data items and their corresponding code and value sets specific to a dental referral note and dental consultation note. This guide describes constraints on the C-CDA on FHIR header and body elements for dental information, which are derived from requirements developed by the Dental Summary Exchange Project of the Health Level Seven (HL7) Payer/Provider Information Exchange Work Group (PIE WG). Resources in this US Realm implementation guide are specific to dental referral and consultation notes for exchange and interoperability among dental providers and with medical providers.

This guide contains a library of FHIR profiles and is compliant with FHIR Release 4. At a minimum, a document bundle (C-CDA on FHIR Referral Note or Consultation Note) will be exchanged along with a ServiceRequest, Patient, and associated medical and dental information. This guide specifies how and where these resources are included within the C-CDA on FHIR profiles.

This guide defines 7 new profiles:

  • Dental Bundle
  • Dental Referral Note
  • Dental Service Request
  • Dental Consult Note
  • Dental Condition
  • Dental Finding
  • Dental Communication

All proprietary documents, guides, guidance, standards, codes, and values contained herein remain the property of their respective Standards Developing Organization (SDO). HL7 does not make any claim to ownership herein.

This HL7 FHIR® R4 Implementation Guide: Dental Data Exchange is developed in parallel to the HL7 CDA® R2 Implementation Guide: Dental Data Exchange. (built Tue, Nov 2, 2021 16:19+0000+00:00)

Package hl7.fhir.us.ccda#2.0.0-ballot

Consolidated CDA (C-CDA) is one of the most widely implemented implementation guides for CDA and covers a significant scope of clinical care. Its target of the 'common/essential' elements of healthcare is closely aligned with FHIR's focus on the '80%'. There is significant interest in industry and government in the ability to interoperate between CDA and FHIR and C-CDA is a logical starting point. Implementers and regulators have both expressed an interest in the ability to map between FHIR and C-CDA.

This Implementation Guide (IG) defines a series of FHIR profiles on the Composition resource to represent the various document types in C-CDA. This release does not directly map every C-CDA template to FHIR profiles, rather tries to accomplish the C-CDA use case using Composition resource profiles created under this project (the equivalent of Level 2 CDA documents), and begins by linking to the profiles created under the US Core project for any coded entries that would normally be included in C-CDA sections. To have a simpler, more streamlined standard that reuses existing work and focuses on the 80% that implementers actually need in production systems, the resources of US Core represents a portion of the 80% needed for coded entries for coded entries of CCD, Care Plan & Discharge Summary).

The Composition profiles in this IG do not require coded data in any section. This is a departure from C-CDA, which requires coded data for Problems, Results, Medications, etc. This departure is intentional, as the C-CDA requirement for one or more coded entries in these sections resulted in some very complicated workarounds using nullFlavors to handle the fact that sometimes a patient is not on any medications, or has no current problems. In general, FHIR takes the approach that if something is nullable, it should simply be optional to ease the burden on implementers, thus C-CDA on FHIR does not require any coded entries, but rather uses the "required if known" approach, meaning that if an implementer's system has data for a section that requires data under Meaningful Use, they need to send it, but if they have no data there is no need for a null entry.

We encourage feedback on these Composition profiles, and the general approach to the project as a whole. We also encourage implementers who wish to see more of the coded data from C-CDA mapped to FHIR to comment on the US Core project and make their requests known there. Once US Core creates new profiles, this project can reference them.

Scope

To represent Consolidated CDA Templates for Clinical Notes (C-CDA) 2.1 templates using FHIR profiles.

This first stage of the project defines all the C-CDA document-level profiles on the Composition resource and contained sections.

Any coded data used by sections will be represented using relevant U.S. Core FHIR profiles where they exist. FHIR profiles defined by other work groups or unconstrained FHIR resources may also be referenced if no appropriate US Core Profile exist.

For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408. (built Tue, Dec 17, 2024 21:40+0000+00:00)

Package hl7.fhir.us.pacio-toc#current

Implementation Guide for exchanging Transitions of Care minimum data set for patients transitioning between health organizations. (built Wed, Aug 20, 2025 20:10+0000+00:00)

Package hl7.fhir.uv.tools.r4#0.7.1

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 Sat, Jul 26, 2025 06:59+1000+10:00)

Cross Version Analysis

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 (fhir.paciosampledata.r4) and R4B (fhir.paciosampledata.r4b) are available.

Global Profiles

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.