From ef17e246a4a9ed454981ec4d6492f115b564bea4 Mon Sep 17 00:00:00 2001 From: rizzolol Date: Mon, 6 Nov 2023 10:35:01 -0600 Subject: [PATCH 1/3] Solicit feedback Per Jira FHIR-42368, added section to appointment book hook to solicit feedback from users, with exact language specified by FHIR-42368. --- docs/hooks/appointment-book.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/hooks/appointment-book.md b/docs/hooks/appointment-book.md index 8d3ce347..cdc65eca 100644 --- a/docs/hooks/appointment-book.md +++ b/docs/hooks/appointment-book.md @@ -10,6 +10,14 @@ This hook is invoked when the user is scheduling one or more future encounters/visits for the patient. For example, the `appointment-book` hook may be triggered for an appointment with the appointment creator, a clinician within the same organization as the appointment creator or even for an appointment outside the creator's organization. It may be invoked at the start and end of the booking process and/or any time between those two points. This hook enables CDS Services to intervene in the decision of when future appointments should be scheduled, where they should be scheduled, what services should be booked, to identify actions that need to occur prior to scheduled appointments, etc. +### Looking for Feedback + +Hey implementers, we want to hear from you! + +- What obstacles are there to limiting this hook to firing only when the appointment is confirmed or finalized as booked? +- For which users should this hook fire? +- Many appointments are scheduled directly into the EHR by the patient, without provider staff involvement ... + ## Context The Patient whose appointment(s) are being booked, as well as the proposed Appointment records. From ba23c2d4a65c3b5138aa9ea53537d910f8b7f026 Mon Sep 17 00:00:00 2001 From: rizzolol Date: Mon, 6 Nov 2023 10:41:24 -0600 Subject: [PATCH 2/3] Changed section to header --- docs/hooks/appointment-book.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hooks/appointment-book.md b/docs/hooks/appointment-book.md index cdc65eca..511cc3c0 100644 --- a/docs/hooks/appointment-book.md +++ b/docs/hooks/appointment-book.md @@ -10,7 +10,7 @@ This hook is invoked when the user is scheduling one or more future encounters/visits for the patient. For example, the `appointment-book` hook may be triggered for an appointment with the appointment creator, a clinician within the same organization as the appointment creator or even for an appointment outside the creator's organization. It may be invoked at the start and end of the booking process and/or any time between those two points. This hook enables CDS Services to intervene in the decision of when future appointments should be scheduled, where they should be scheduled, what services should be booked, to identify actions that need to occur prior to scheduled appointments, etc. -### Looking for Feedback +## Looking for Feedback Hey implementers, we want to hear from you! From 93c5c82072b6ab9c2aa9d1cc3fa5ab0c9bb8f5aa Mon Sep 17 00:00:00 2001 From: rizzolol Date: Wed, 15 Nov 2023 09:00:31 -0600 Subject: [PATCH 3/3] Revise feedback section as admonition --- docs/hooks/appointment-book.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/hooks/appointment-book.md b/docs/hooks/appointment-book.md index 511cc3c0..4cf6b9d3 100644 --- a/docs/hooks/appointment-book.md +++ b/docs/hooks/appointment-book.md @@ -1,5 +1,11 @@ # `appointment-book` +!!! info "Looking for Feedback" + **Hey implementers, we want to hear from you!**
+ - What obstacles are there to limiting this hook to firing only when the appointment is confirmed or finalized as booked?
+ - For which users should this hook fire?
+ - Many appointments are scheduled directly into the EHR by the patient, without provider staff involvement ... + | Metadata | Value | ---- | ---- | specificationVersion | 1.0 @@ -10,14 +16,6 @@ This hook is invoked when the user is scheduling one or more future encounters/visits for the patient. For example, the `appointment-book` hook may be triggered for an appointment with the appointment creator, a clinician within the same organization as the appointment creator or even for an appointment outside the creator's organization. It may be invoked at the start and end of the booking process and/or any time between those two points. This hook enables CDS Services to intervene in the decision of when future appointments should be scheduled, where they should be scheduled, what services should be booked, to identify actions that need to occur prior to scheduled appointments, etc. -## Looking for Feedback - -Hey implementers, we want to hear from you! - -- What obstacles are there to limiting this hook to firing only when the appointment is confirmed or finalized as booked? -- For which users should this hook fire? -- Many appointments are scheduled directly into the EHR by the patient, without provider staff involvement ... - ## Context The Patient whose appointment(s) are being booked, as well as the proposed Appointment records.