Da Vinci - Coverage Requirements Discovery
1.0.0 - STU 1

This page is part of the Da Vinci Coverage Requirements Discovery (CRD) FHIR IG (v1.0.0: STU 1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

FHIR Artifacts

Compliance with this implementation guide requires compliance with a number of profiles, extensions, value sets and custom search parameters. This page provides an overview of where these artifacts can be found.

The FHIR artifacts used by CRD are organized according to whether the content was developed as part of the US Core implementation guides or are specific to this CRD implementation guide.

As a result, there are 2 different lists of artifacts - one for this Da Vinci implementation guide and one for the US Core implementation guide.

Artifact Lists

CRD-specific Artifacts
US Core IG

Additional information about the use of these artifacts, coverage requirements discovry (CRD) and the use of US Core can be found in the formal specification.

These FHIR artifacts define the clinical data that can be provided by CRD Clients when invoking CDS hooks, queried (or retrieved using prefetch) from CRD Clients by CRD Services and/or returned to client systems by hook services within cards.

The artifacts are of four types:

  • Profiles constrain FHIR resources to reflect CRD requirements
  • Extensions define additional data elements that can be conveyed as part of a resource
  • Code Systems define terminologies to be used in one or more of the profiles
  • Value Sets define the specific subsets of both CRD-defined and other code systems that must be (or are recommended to be) used within one or more profile elements
  • Search Parameters define additional search criteria needed to allow filtering of FHIR resources to those relevant for CRD use-cases

For the purpose of this implementation guide, Must Support means that CRD Clients must be capable of exposing the data to at least some CRD Services. CRD Services are not obligated to make use of Must Support elements when performing their coverage requirements discovery.