Feedback that a CDS Client POSTs to a CDS Service's feedback endpoint. The request body is an object containing an array of one or more Feedback entries reporting end-user interaction with cards previously returned by the CDS Service.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

An array of Feedback entries reporting end-user interaction with cards previously returned by the CDS Service.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

The card.uuid from the CDS Hooks response. Uniquely identifies the card.

A value of accepted or overridden.

An array of objects identifying one or more of the user's AcceptedSuggestions. Required for 'accepted' outcomes.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

The card.suggestion.uuid from the CDS Hooks response. Uniquely identifies the suggestion that was accepted.

Captures the override reason as a Coding as well as any free-text comment entered by the user.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

The Coding object representing the override reason selected by the end user. Required if the user selected an override reason from the list of reasons provided in the Card (instead of only leaving a userComment).

Free text the clinician provided to further explain why the card was rejected.

ISO8601 representation of the date and time in Coordinated Universal Time (UTC) when action was taken on the card, as profiled in section 5.6 of RFC3339 (e.g. 1985-04-12T23:20:50.52Z).

Feedback that a CDS Client POSTs to a CDS Service's feedback endpoint. The request body is an object containing an array of one or more Feedback entries reporting end-user interaction with cards previously returned by the CDS Service.

An array of Feedback entries reporting end-user interaction with cards previously returned by the CDS Service.

The card.uuid from the CDS Hooks response. Uniquely identifies the card.

A value of accepted or overridden.

An array of objects identifying one or more of the user's AcceptedSuggestions. Required for 'accepted' outcomes.

The card.suggestion.uuid from the CDS Hooks response. Uniquely identifies the suggestion that was accepted.

Captures the override reason as a Coding as well as any free-text comment entered by the user.

The Coding object representing the override reason selected by the end user. Required if the user selected an override reason from the list of reasons provided in the Card (instead of only leaving a userComment).

Free text the clinician provided to further explain why the card was rejected.

ISO8601 representation of the date and time in Coordinated Universal Time (UTC) when action was taken on the card, as profiled in section 5.6 of RFC3339 (e.g. 1985-04-12T23:20:50.52Z).

Feedback that a CDS Client POSTs to a CDS Service's feedback endpoint. The request body is an object containing an array of one or more Feedback entries reporting end-user interaction with cards previously returned by the CDS Service.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

An array of Feedback entries reporting end-user interaction with cards previously returned by the CDS Service.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

The card.uuid from the CDS Hooks response. Uniquely identifies the card.

A value of accepted or overridden.

An array of objects identifying one or more of the user's AcceptedSuggestions. Required for 'accepted' outcomes.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

The card.suggestion.uuid from the CDS Hooks response. Uniquely identifies the suggestion that was accepted.

Captures the override reason as a Coding as well as any free-text comment entered by the user.

A JSON object that has properties where the names are defined by the extension definitions

Extension structures SHOULD use a strategy for naming that ensures global uniqueness, such as reverse-domain-name notation, e.g. com.cds-hooks.sandbox.myextension-practitionerspecialty. How to handle complex extensions (objects) is not defined

The Coding object representing the override reason selected by the end user. Required if the user selected an override reason from the list of reasons provided in the Card (instead of only leaving a userComment).

Free text the clinician provided to further explain why the card was rejected.

ISO8601 representation of the date and time in Coordinated Universal Time (UTC) when action was taken on the card, as profiled in section 5.6 of RFC3339 (e.g. 1985-04-12T23:20:50.52Z).