Bryn Rhodes

Part of a potential resolution here is to add documentation around concurrency expectations and the potential issues associated with inferencing on outdated data to the Security & Safety discussion in...

Add documentation to note: For more information on patient safety issues see [Security & Safety](https://cds-hooks.hl7.org/1.0/#security-and-safety).

Agreed, all for a simple change that will decrease confusion downstream. It would be good to know whether there are any systems that actually check it now.

We have a CDS Hooks reference implementation that plugs in to the HAPI-FHIR server and would be happy to help get that available in the sandbox. The public endpoint is...

Add to the patient-view documentation a note that the encounter referenced by the encounterId context field is expected to be available via the FHIR Server (if an endpoint is used)...

In the HL7 Decision Support Service specification, this information is communicated with an organization id as part of the request. When we expressed that in the clinical reasoning module, we...

@grahamegrieve, where is the work to define this set of triggers being done?

@gdelfiol, do you know whether the ActTaskCode value set was developed specifically for InfoButton, or was it already present and InfoButton used it?

@gdelfiol, that's great! Do you have a sense for how well supported the codes are within EHR implementations? Do the InfoButton integrations actually implement workflow points at these codes?

Rather than calling it 1.1, we should rename it to current, since it is the current draft version of the specification.