Carequality Healthcare Directory ImplementationGuide
1.9.0 - Release 1

Carequality Healthcare Directory ImplementationGuide - Local Development build (v1.9.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## Downloads

Full Implementation Guide

The entire implementation guide (including the HTML files, definitions, validation information, etc.) may be downloaded here.

In addition there are format specific definitions files.

- XML
- JSON
- TTL

Examples: all the examples that are used in this Implementation Guide available for download:

- XML
- JSON
- TTl

### 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 (sequoia.fhir.us.cq.r4) and R4B (sequoia.fhir.us.cq.r4b) are available.

### Dependency Table

IG | Package | FHIR | Comment
--- | --- | --- | ---
Carequality Healthcare Directory ImplementationGuide | sequoia.fhir.us.cq#1.9.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#7.0.1 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.2.0 | R4 |
Sequoia Project Healthcare Directory Implementation Guide | sequoia.fhir.us.sphd#dev | R4 |
US Core Implementation Guide | hl7.fhir.us.core#4.0.0 | R4 |
FHIR Bulk Data Access | hl7.fhir.uv.bulkdata#1.0.1 | R4 |
VSAC | us.nlm.vsac#0.3.0 | R4 |
HL7 Terminology (THO) | hl7.terminology#5.5.0 | R4 |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#1.0.0 | R4 |
FHIR Tooling Extensions IG | hl7.fhir.uv.tools.r4#0.9.0 | R4 | for 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.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.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.tools.r4#0.9.0 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, Dec 16, 2025 23:18+1100+11:00)

### Globals Table

There are no Global profiles defined

### IP Statements

This publication includes IP covered under the following statements.

- This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  - Contact entity type: Connection Hospital and Implementer Hospital
  - Endpoint Connection Type: Patient Discovery
  - NullFlavor: Patient Discovery