You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2022. It is now read-only.
When working on Sero examples for CDS hooks, different client flows and scenarios begin to emerge that utilize suggestions and links that might involve some extra functionality. A basic example:
if I hook into patient-view and the hook request prefetch contains more than one patient name in the return body, a suggestion from CDS hooks could be to remove one of the names. This could involve adding in some extra functionality.
another one could be suggesting a deletion of a patients record if they have not made an appointment in a number of years.
even suggesting to mark the patient as deceased.
more examples will emerge as more work is done on the other hooks
This might involve the addition of some helper functions/a class that helps process data in a specific way. In all this saves developers some time needing to worry about edge cases with implementing smart apps.
The text was updated successfully, but these errors were encountered:
if I hook into patient-view and the hook request prefetch contains more than one patient name in the return body, a suggestion from CDS hooks could be to remove one of the names. This could involve adding in some extra functionality.
I like the idea of trying to find a simple example of a Suggestion with an Action that updates the resource (if the client listens...). Updating something based on an action is an important example.
another one could be suggesting a deletion of a patients record if they have not made an appointment in a number of years.
even suggesting to mark the patient as deceased.
Deletes are possible too - just I think less interesting
more examples will emerge as more work is done on the other hooks
This might involve the addition of some helper functions/a class that helps process data in a specific way. In all this saves developers some time needing to worry about edge cases with implementing smart apps.
I think that's one of the other examples - launching a SMART App from a CDS Suggestion link
When working on Sero examples for CDS hooks, different client flows and scenarios begin to emerge that utilize suggestions and links that might involve some extra functionality. A basic example:
patient-view
and the hook request prefetch contains more than one patient name in the return body, a suggestion from CDS hooks could be to remove one of the names. This could involve adding in some extra functionality.This might involve the addition of some helper functions/a class that helps process data in a specific way. In all this saves developers some time needing to worry about edge cases with implementing smart apps.
The text was updated successfully, but these errors were encountered: