Stream: cds hooks
Topic: Request to Add Procedure-Request Hook
Sanjay Chadha (Oct 26 2017 at 19:50):
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.
Copied here from: https://chat.fhir.org/#narrow/search/proposed.20hook
Brett Marquard (Nov 08 2017 at 13:56):
Good question -- What type of procedures do you believe this will work best for? Watching some of the scheduling activities under Argonaut I am not quite sure how you would select location, provider, time slot, etc.
Last updated: Apr 12 2022 at 19:14 UTC
