docs
docs copied to clipboard
cds-hooks
CDS Hooks website & specification
The [CDS Hooks Maturity Model](https://cds-hooks.org/specification/1.0/#hook-maturity-model) level of 'Tested - 2' has these requirements: Maturity Level | Maturity title | Requirements --- | --- | --- 2 | Tested | _The...
I was thinking about the need to associate a card response to a particular resource in context when there is more than one resource (FHIR bundle) in the context. I...
Currently we define a "fhirAuthorization" object with a `subject` property:  This is the only place in the specification where the CDS Service's `client_id` (as issued by the EHR at...
AUC Criteria include a "categorization", which is effectively the interpretation of the score. For the radiology use case, this corresponds to the display text for the score. Update the example...
It wasn't immediately clear in the spec how to differentiate between suggestions to replace a resource with something new vs. adding an additional action while leaving the current resource in...
Are there any thoughts on how to advertise/handle the CDS Hooks service version? This could be handled as part of the service discovery -- e.g. include the version as an...
During the connectathon, communicating the OAuth 2.0 scope that the CDS hook required involved some back and forth. The spec mentions this managed out-of-band when the EMR connects with a...
In some cases different services will provide cards that recommend updating the same resource instance. E.g. changing a dose, adding a coverage, adding a link to a clinical trial. The...
At present, the specification says `Only root-level fields with a primitive value within the context object are eligible to be used as prefetch tokens`. This would seem to preclude the...