cds-hooks
CDS Hooks should support Infobutton
In discussion with @brynrhodes and @kpshek regarding aligning Clinical Reasoning and CDS Hooks, one of the topics of discussion was around use of CDS Hooks in infobutton-type scenarios.
The HL7 Infobutton (Context aware knowledge retrieval) is a widely implemented standard for an EHR or other system to query an external clinical knowledgebase in realtime in a clinician's workflow. Contextual information (patient demographics, specific diagnosis, allergy, observation, etc) is included in the EHR's HTTP request. The knowledgebase's response is displayed to the clinician.
This is a specific use case of the CDS Hooks info card. Knowledgebases would benefit from having access to the caller's FHIR server, by receiving the OAuth access_token in the CDS Hooks request, the ability to return a full-featured SMART app, as well as the option of the more advanced remote CDS Hooks functionality .
We should consider building dedicated support of Infobutton in CDS Hooks. One approach would be to define an "infobutton" hook, that includes the existing key/value pairs defined by the HL7 Context aware knowledge retrieval (aka Infobutton) standard within the CDS Hooks request's context attribute. This could provide a straightforward path for platforms and knowledgebases to enhance their existing integrations to take advantages of the additional clinical data offered by an EHR's FHIR server, and other features.
@isaacvetter , I like the idea of building dedicated support to infobutton-type capabilities in CDS Hooks. I would be interested in and happy to help define the "infobutton" hook.
Guilherme
@gdelfiol - Can you point me to the data that the EHR passes in the Infobutton URL today? I'm curious to see where the overlap is between that data and what a CDS Service receives today in the request.
@kpshek, the easiest source is the URL implementation guide, which is a PDF available for download at: https://www.hl7.org/implement/standards/product_brief.cfm?product_id=22
There are two tables in the appendix: Appendix 1 lists the URL parameters and Appendix 2 has terminology bindings and value sets.