Clinical Decisions

This data model communicates real-time, immediate clinical decision support (CDS). Providers rely on the Request event type while vendors respond with the Response event type to complete the CDS workflow.

A clinical decision is useful when a provider wants to recommend alternative medications/procedures or identify drug interactions before placing an order.

This data model has event types that allow you to:

request information from a third-party app offering CDS data; and
return clinical insights, observations, and recommendations.

EHR support

The EHR system must have a corresponding CDS API that can map to the ClinicalDecisions data model. This typically works with Epic EHR systems, but since we built ClinicalDecisions on FHIR® or CDS Hook specifications, it's possible for other EHR systems to support, too.

ClinicalDecisions vs. SSO data model

ClinicalDecisions returns discrete data to offer CDS within the EHR system. It’s part of a typical ordering workflow.

SSO is triggered when the user clicks a specially-configured button to launch an app within the EHR system. It returns a URL for the EHR system to launch the app's system.

Events in Clinical Decisions

Request

Beta

Response

Beta

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.