Bas van den Heuvel
Bas van den Heuvel
In various discussions during the Connecthaton and over the last weeks a noticed a large difference in the approach to the CDS Hooks Card dynamics. Some of the variations observed...
As is mentioned in #502 and #506, some guidance is required related to access of Resources that is referred to by id from the hook context. I suggest that we...
The patient-view context provide an optional field `encounter `that provides the encounter.id of the current Encounter. The current specification states in the section "Prefetch Template" (From ): > Regardless of...
Some key CDS-Hooks use cases include: 1. Show card based on FHIR data 2. Show multiple cards relate to the same FHIR/context data, possibly from different CDS-Services This makes the...
The EHR typically views the data of a single patient. If a link on a card is triggered, a second browser session on the same patient may be started. What...
In order for the current CDS-Hooks specification to become a proper standard, We need formalize the document on the following elements: - to be able to refer to a specific...
When a hook is triggered, the related CDS Services are called. They may return one or more Cards. Is the EHR required to show them all? What happens when there...
Attached a printout of the Informal Balot version of CDS Hooks with attached comments. I've created separate issues for the larger comments. References to these issues are included in the...
The HTTP status codes section only states support for "200 OK". What to do in case of an error situation? I suggest to add/allow responses in the 400 and/or 500...
As agreed/discussed in [11 May Q3 CDS hosts CQI](https://confluence.hl7.org/display/CQIWC/11+May+Q3+CDS+hosts+CQI?src=jira) a change that adds Links as a (deferrable) suggestion.