CapabilityStatement-crd-server

Sourcehl7.fhir.us.davinci-crd#current:Da Vinci - Coverage Requirements Discovery (v4.0.1)
resourceTypeCapabilityStatement
idcrd-server
canonicalhttp://hl7.org/fhir/us/davinci-crd/CapabilityStatement/crd-server
version1.1.0
statusactive
publisherHL7 International - Financial Management Work Group
nameCRDServer
titleCRD Server
date2022-11-25
experimentalfalse
descriptionThis statement defines the expected capabilities of systems wishing to conform to the ''CRD Server'' role. This role is responsible for responding to CDS Hooks calls and responding with appropriate decision support. Much of its interactions will be with payer back-end systems over non-FHIR protocols. This CapabilityStatement does not describe these 'server <-> payer' interactions. Instead, it focuses on the ability of the CRD service to interact with the CRD client's FHIR endpoint to retrieve additional data. All such interactions are optional, as their necessity is dependent on what types of information is needed to support payer rules, the types of coverage the payer offers, and the degree of sophistication of the decision support offered by the CRD server. All resources and search parameters supported by US Core are fair game, though [[CapabilityStatement-crd-client|client endpoints]] might vary in which resources they support.
jurisdictionsus
kindrequirements
fhirVersion4.0.1
importshttp://hl7.org/fhir/us/core/CapabilityStatement/us-core-client
formatsjson
Usages(none)

CRDServer

This statement defines the expected capabilities of systems wishing to conform to the ''CRD Server'' role. This role is responsible for responding to CDS Hooks calls and responding with appropriate decision support. Much of its interactions will be with payer back-end systems over non-FHIR protocols. This CapabilityStatement does not describe these 'server <-> payer' interactions. Instead, it focuses on the ability of the CRD service to interact with the CRD client's FHIR endpoint to retrieve additional data. All such interactions are optional, as their necessity is dependent on what types of information is needed to support payer rules, the types of coverage the payer offers, and the degree of sophistication of the decision support offered by the CRD server. All resources and search parameters supported by US Core are fair game, though [[CapabilityStatement-crd-client|client endpoints]] might vary in which resources they support.

Mode CLIENT
Description

A CRD server acts as a client, soliciting patient information from the FHIR endpoint of the CRD client, retrieving additional information needed to provide decision support.

Transaction
System History
System Search
Resource Type Profile Read Search Update Create

Produced 08 Sep 2023