This text is a duplication of the above – I suggest the text is merged in the bullet overview.

Existing Wording:

In CDS Hooks, a CDS Service is a service that provides patient-specific recommendations and guidance through RESTful APIs as described by this specification. The primary APIs are Discovery, which allows a CDS Developer to publish the types of CDS Services it provides, and the Service endpoint that CDS Clients use to request decision support.
A CDS Client is an electronic health record, or other clinical information system that consumes decision support by calling CDS Services at specific points in the application's workflow called hooks. Each hook defines the hook context, contextual information available within the client and specific to the workflow. Each service advertises which hooks it supports and what prefetch data (information needed by the CDS Service to determine what decision support should be presented) it requires