From 2604aded5f52826342ce1d618e43d5253419bb36 Mon Sep 17 00:00:00 2001 From: Isaac Vetter Date: Wed, 9 Oct 2019 12:05:37 -0500 Subject: [PATCH 1/3] availability of data and safety Intended to address -- Fixes: #502, #503 --- docs/hooks/patient-view.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/hooks/patient-view.md b/docs/hooks/patient-view.md index 1bc3f6f3..5ba32a0a 100644 --- a/docs/hooks/patient-view.md +++ b/docs/hooks/patient-view.md @@ -12,7 +12,9 @@ The user has just opened a patient's record. ## Context -The patient whose record was opened, including their encounter, if applicable. +The patient whose record was opened, including their encounter, if applicable. + +The FHIR ids referenced in `context` are expected to be available via the FHIR Server (if `fhirServer` is populated in the request) or via prefetch, if supported. However, the specification does not explicitly require this behavior and implementations should be aware that integrations may not fully support this expectation. Field | Optionality | Prefetch Token | Type | Description ----- | -------- | ---- | ---- | ---- @@ -20,6 +22,8 @@ Field | Optionality | Prefetch Token | Type | Description `patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context `encounterId` | OPTIONAL | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context +For information on patient safety issues see [Security & Safety](../../specification/1.0/#security-and-safety). + ### Examples ```json From e34f6997171eb384d569389b1f0b0e644fe16dda Mon Sep 17 00:00:00 2001 From: Isaac Vetter Date: Tue, 15 Oct 2019 15:03:39 -0500 Subject: [PATCH 2/3] availability of FHIR resources from ids in context Rewrite paragraph to better address @bvdh comment --- docs/hooks/patient-view.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hooks/patient-view.md b/docs/hooks/patient-view.md index 5ba32a0a..5484e383 100644 --- a/docs/hooks/patient-view.md +++ b/docs/hooks/patient-view.md @@ -14,7 +14,7 @@ The user has just opened a patient's record. The patient whose record was opened, including their encounter, if applicable. -The FHIR ids referenced in `context` are expected to be available via the FHIR Server (if `fhirServer` is populated in the request) or via prefetch, if supported. However, the specification does not explicitly require this behavior and implementations should be aware that integrations may not fully support this expectation. +The FHIR resources, referenced by ids in `context`, SHOULD be available to the CDS service. If supported by the CDS Client, the CDS service may request these resources through prefetch. Alternatively or additionally the CDS Client may provide a `fhirserver` in the request for RESTful access. Support for both `prefetch` and `fhirServer` are optional. As such, CDS Service implementers need to be aware that CDS Clients may not support this behavior. Field | Optionality | Prefetch Token | Type | Description ----- | -------- | ---- | ---- | ---- From ae0e88e9810e82d1a88ce58fe3575d6259cc4432 Mon Sep 17 00:00:00 2001 From: Isaac Vetter Date: Tue, 15 Oct 2019 15:12:45 -0500 Subject: [PATCH 3/3] safety paragraph - stale clinical data Rewrite safety paragraph per Bas. --- docs/hooks/patient-view.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hooks/patient-view.md b/docs/hooks/patient-view.md index 5484e383..2f254f6a 100644 --- a/docs/hooks/patient-view.md +++ b/docs/hooks/patient-view.md @@ -22,7 +22,7 @@ Field | Optionality | Prefetch Token | Type | Description `patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context `encounterId` | OPTIONAL | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context -For information on patient safety issues see [Security & Safety](../../specification/1.0/#security-and-safety). +The `patient-view` hook allows a CDS Service to provide guidance based on information acquired using a prefetch template and the FHIR server. A variety of factors could cause this information to become outdated. Stale clinical data could result in a risk to patient safety. For information on patient safety issues see [Security & Safety](../../specification/1.0/#security-and-safety). ### Examples