Source | hl7.fhir.us.davinci-crd#current:Da Vinci - Coverage Requirements Discovery (v4.0.1) |
resourceType | CapabilityStatement |
id | crd-client |
canonical | http://hl7.org/fhir/us/davinci-crd/CapabilityStatement/crd-client |
version | 1.1.0 |
status | active |
publisher | HL7 International - Financial Management Work Group |
name | CRDClient |
title | CRD Client |
date | 2022-11-25 |
experimental | false |
description | This statement defines the expected capabilities of systems wishing to conform to the ''CRD Client'' role. This role is responsible for initiating CDS Hooks calls and consuming received decision support. It is *also* responsible for returning data requested by the CRD Server needed to provide that decision support. This capability statement doesn't define the CDS Hooks capabilities as there is no standard way to do that as yet. Instead, it focuses on the 'server' capabilities needed to respond to CRD Server queries. These capabilities are based on US Core. In addition to the U.S. core expectations, the CRD Client **SHALL** support all 'SHOULD' 'read' and 'search' capabilities listed below for resources referenced in supported hooks and order types if it does not support returning the associated resources as part of CDS Hooks pre-fetch. The CRD Client **SHALL** also support 'update' functionality for all resources listed below where the client allows invoking hooks based on the resource. |
jurisdictions | us |
kind | requirements |
fhirVersion | 4.0.1 |
imports | http://hl7.org/fhir/us/core/CapabilityStatement/us-core-server |
formats | json |
Usages | (none) |
This statement defines the expected capabilities of systems wishing to conform to the ''CRD Client'' role. This role is responsible for initiating CDS Hooks calls and consuming received decision support. It is also responsible for returning data requested by the CRD Server needed to provide that decision support. This capability statement doesn't define the CDS Hooks capabilities as there is no standard way to do that as yet. Instead, it focuses on the 'server' capabilities needed to respond to CRD Server queries. These capabilities are based on US Core.
In addition to the U.S. core expectations, the CRD Client SHALL support all 'SHOULD' 'read' and 'search' capabilities listed below for resources referenced in supported hooks and order types if it does not support returning the associated resources as part of CDS Hooks pre-fetch. The CRD Client SHALL also support 'update' functionality for all resources listed below where the client allows invoking hooks based on the resource.
Mode | SERVER |
Description |
A CRD Client provides a FHIR server endpoint, returning patient information to the CRD server, ensuring it has the needed information to perform decision support. |
Transaction | |
System History | |
System Search |
Resource Type | Profile | Read | Search | Update | Create |
---|---|---|---|---|---|
Appointment |
Supported profiles: CRD Appointment |
y | |||
CommunicationRequest |
Supported profiles: CRD Communication Request |
y | |||
Coverage |
Supported profiles: CRD Coverage |
y | |||
Device |
Supported profiles: CRD Device |
y | |||
DeviceRequest |
Supported profiles: CRD Device Request |
y | |||
Encounter |
Supported profiles: CRD Encounter |
y | y | ||
Patient |
Supported profiles: CRD Patient |
y | |||
Practitioner |
Supported profiles: CRD Practitioner |
y | |||
PractitionerRole |
Supported profiles: US Core PractitionerRole Profile |
y | |||
Location |
Supported profiles: CRD Location |
y | |||
MedicationRequest |
Supported profiles: CRD Medication Request |
y | |||
NutritionOrder |
Supported profiles: CRD Nutrition Order |
y | |||
Organization |
Supported profiles: CRD Organization |
y | |||
ServiceRequest |
Supported profiles: CRD Service Request |
y | |||
ClaimResponse |
Supported profiles: HRex Prior authorization |
y | |||
Task |
Supported profiles: CRD Questionnaire Task |
y | |||
VisionPrescription |
Supported profiles: CRD Vision Prescription |
y |
Produced 08 Sep 2023