Workflow triggers for decision support interventions — clients

The health IT developer demonstrates the Health IT Module supports the following capabilities as a “CDS Client” in accordance with an implementation specification at § 170.215(f):

1. CDS-1: Registration with a “CDS Service” including all configuration necessary to invoke a CDS Hook, authenticate as a client, and authorize FHIR resource access.
2. CDS-2: Trigger an invocation of a “CDS Service” in accordance with a CDS Hook.
3. CDS-3: Authentication as a client with a “CDS Service” using JSON web tokens (JWT).
4. CDS-4: Authorization of a “CDS Service” to have the FHIR resource access necessary to enable the “CDS Service” including provisioning an access token.
5. CDS-5: FHIR resource access to enable a “CDS Service.” This may include supporting FHIR resource “read” and “search” requests from the “CDS Service.”
6. CDS-6: As applicable, processing and display of clinical decision support provided by a “CDS Service.”

The tester verifies the Health IT Module supports the following capabilities as a “CDS Client” in accordance with an implementation specification at § 170.215(f):

1. CDS-1: Registration with a “CDS Service” including all configuration necessary to invoke a CDS Hook, authenticate as a client, and authorize FHIR resource access.
2. CDS-2: Trigger an invocation of a “CDS Service” in accordance with a CDS Hook.
3. CDS-3: Authentication as a client with a “CDS Service” using JSON web tokens (JWT).
4. CDS-4: Authorization of a “CDS Service” to have the FHIR resource access necessary to enable the “CDS Service” including provisioning an access token.
5. CDS-5: FHIR resource access to enable a “CDS Service.” This may include supporting FHIR resource “read” and “search” requests from the “CDS Service.”
6. CDS-6: As applicable, processing and display of clinical decision support provided by a “CDS Service.”