This wiki has undergone a migration to Confluence found Here
CDS Hooks Interface for Hacking Health Brisbane 2017 Track 6
This page describes the interface for track 6 for Hacking Health Brisbane 2017 (see [[1]])
Basics
The cds-hook is 'order-review' - see [[2]].
Given the scenario described in the track, we assume that there's no call back to the EHR - so all data is provided via pre-fetch. Therefore, the EHR provides the following information:
- hook = order-review
- a hook instance
- a user id
- a patient
- an encounter (e.g. information about the GP consultation)
- a patient and and encounter resource matching those in the pre-fetch data
- at least one Condition - (problem list for the patient, also in the prefetch data
- one or more ProcedureRequest resources, for each test (or panel) requested by the clinician (in the context)
- no oauth/redirect details
The service returns a set of cards (no profile on the response yet).
Implementations
There's an implementation at http://test.fhir.org/r3/cds-services/hacking-health. All that implementation does is return a card that describes technical issues with the submission from the EHR.