FHIR Chat · Request to Add to Proposed Hooks · implementers

Stream: implementers

Topic: Request to Add to Proposed Hooks

Sanjay Chadha (Oct 25 2017 at 21:24):

This is request to add the following hooks to https://github.com/cds-hooks/docs/wiki/Proposed-Hooks:
(Below is the rationale for this request)

procedure-request-create
Purpose: This hook informs an external CDS service that the clinician has created a procedure request. The CDS service schedules procedures to performed based on the created procedure request.
Contextual data: Required Patient, procedure request being created.
{
"name": "context",
"resource": procedurerequest/123
}

procedure-request-modify (this should include delete)
Purpose: This hook informs an external CDS service that the clinician has modified a procedure request. The CDS service modifies the scheduled procedures based on the modified procedure request.
Contextual data: Required Patient, procedure request being created.
{
"name": "context",
"resource": procedurerequest/123;
}

1. Patient comes out of an operation and is sent to a nursing care or t home (cost reduction)
2. Clinician requires scheduled vitals collection hence created procedure request for the vital collection
3. Above hooks invokes a cloud server, which obtains the details and Timing of the procedure request
4. The cloud server coordinates with the gateway at home to collect the Vitals.

We look forward to your comments.

Bryn Rhodes (Oct 25 2017 at 21:57):

These are great suggestions, there is a specific stream for cds-hooks. I'd also suggest submitting these as issues on the cds-hooks github.

Abbie Watson (Oct 26 2017 at 18:12):

Seems like it's defining a generic API though, no? In the Meteor framework, we've implemented a generic event hook pattern like the following:

Collection[resourceType].before.insert();
Collection[resourceType].before.update();
Collection[resourceType].before.find();
Collection[resourceType].before.findOne();
Collection[resourceType].after.insert();
Collection[resourceType].after.update();
Collection[resourceType].after.find();
Collection[resourceType].after.findOne();

The proposed hooks are of the format:

CarePlan.after.insert();
DiagnosticReport.after.findOne();
DiagnosticReport.after.insert();
Encounter.after.update();
Observation.after.insert();
Patient.before.update();

Can't we just say that there should be create/update/read hooks for every resource type?

Last updated: Apr 12 2022 at 19:14 UTC