This page is part of the Computable Care Guidelines (CCG) (v1.0.0-comment: Publication Ballot 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

Computable Care Guidelines (CCG) Home

Official URL: https://profiles.ihe.net/QRPH/CCG/ImplementationGuide/ihe.qrph.ccg				Version: 1.0.0-comment
Active as of 2025-05-20				Computable Name: IHE_QRPH_CCG

The IHE Computable Care Guidelines (CCG) Profile specifies a normative grammar and a normative transaction processing model that allows evidence-based care recommendations to be expressed in a way that a digital health solution can ingest and operationalize. This is an implementable and conformance-testable specification. It is targeted to regulated healthcare markets where the support for multiple conditions is an important requirement. The CCG Profile supports jurisdictions that want to leverage digital health to systemically improve the adoption of guideline-adherent best practices across an entire care delivery network.

Organization of This Guide

This guide is organized into the following sections:

1. Volume 1:
   1. Business Description
   2. Actors
2. Volume 2: Transaction Detail
   1. Search for Guidelines [QRPH-61]
   2. Retrieve Guideline [QRPH-62]
   3. Publish Guidelines [QRPH-63]
   4. Apply Guidelines [QRPH-64]
3. Volume 3: Metadata and Content
   1. Content Specifications
4. Volume 4: National Extensions
   1. Jurisdictional Contextualizations
5. Other
   1. Changes to Other IHE Specifications
   2. Download and Analysis
   3. Test Plan

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words: “REQUIRED”, “REQUIRED NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.