From 99e2fe525ccfb6d58655dd78680cd30d9e59fd86 Mon Sep 17 00:00:00 2001 From: jldanford Date: Tue, 27 Jun 2023 15:21:30 -0400 Subject: [PATCH 1/8] Create order-start Initial draft --- docs/hooks/order-start | 46 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 docs/hooks/order-start diff --git a/docs/hooks/order-start b/docs/hooks/order-start new file mode 100644 index 00000000..36f733df --- /dev/null +++ b/docs/hooks/order-start @@ -0,0 +1,46 @@ +`order-start` + +!!! info + This page defines a workflow [hook](../../specification/current/#hooks) for the purpose of providing clinical decision support using CDS Hooks. This is a build at the level of [Draft](http://hl7.org/fhir/versions.html#std-processs). + +| Metadata | Value +| ---- | ---- +| specificationVersion | 1.0 +| hookVersion | 0.1.0 +| hookMaturity | [0 - Draft](../../specification/current/#hook-maturity-model) + +## Workflow + +The `order-start` hook fires when the clinician has reached the point in the workflow where they are ready to begin adding new orders (including orders for medications, procedures, labs and other orders) for the patient. This point in the workflow will usually occur during the encounter when the clinician has completed the examination and assessment, but before they have searched for or selected a given order. The purpose of the hook is to allow guidance services to make order recommendations to the clinician at the point where sufficient clinical data for the patient has been collected but before any orders have been selected. + +## Context +CDS Services should consider including the patient's current active problems, current medication list, lab results, and allergy/intolerance information as prefetch data. Given that these items will necessarily vary they should all be considered as optional values. + +Field | Optionality | Prefetch Token | Type | Description +----- | -------- | ---- | ---- | ---- +`userId` | REQUIRED | Yes | *string* | The id of the current user.
For this hook, the user is expected to be of type [Practitioner](https://www.hl7.org/fhir/practitioner.html) or [PractitionerRole](https://www.hl7.org/fhir/practitionerrole.html).
For example, `PractitionerRole/123` or `Practitioner/abc`. +`patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context +`encounterId` | REQUIRED | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context +`activeProblems` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active problems.
DSTU2 - FHIR Bundle of Condition.
STU3 - FHIR Bundle of Condition.
R4 - FHIR Bundle of Condition.
R5 - FHIR Bundle of Condition. +`activeMedications` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active medications.
DSTU2 - FHIR Bundle of MedicationStatement.
STU3 - FHIR Bundle of MedicationStatement.
R4 - FHIR Bundle of MedicationRequest.
R5 - FHIR Bundle of MedicationRequest. +`labResults` | OPTIONAL | No| *object* | FHIR Bundle with the patient's most recent lab results.
DSTU2 - FHIR Bundle of Observation.
STU3 - FHIR Bundle of Observation.
R4 - FHIR Bundle of Observation.
R5 - FHIR Bundle of Observation. +`patientAllergyIntolerances` | OPTIONAL | No| *object* | FHIR Bundle with the patient's active allergies and intolerances.
DSTU2 - FHIR Bundle of AllergyIntolerance.
STU3 - FHIR Bundle of AllergyIntolerance.
R4 - FHIR Bundle of AllergyIntolerance.
R5 - FHIR Bundle of AllergyIntolerance. + + +## Examples + +### Example (R4) + +```json +{ + "context":{ + "userId":"PractitionerRole/123", + "patientId":"12345", + "encounterId":"98765", + } +} +``` +## Change Log +Version | Description +---- | ---- +0.1.0 | Proposed From a02f7a20960c015680da76384ae441217cfa73e4 Mon Sep 17 00:00:00 2001 From: jldanford Date: Tue, 27 Jun 2023 15:56:00 -0400 Subject: [PATCH 2/8] Add files via upload Initial draft --- docs/hooks/OrderStart.md | 184 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 184 insertions(+) create mode 100644 docs/hooks/OrderStart.md diff --git a/docs/hooks/OrderStart.md b/docs/hooks/OrderStart.md new file mode 100644 index 00000000..37ec8fbd --- /dev/null +++ b/docs/hooks/OrderStart.md @@ -0,0 +1,184 @@ +`order-start` + +!!! info + This page defines a workflow [hook](../../specification/current/#hooks) for the purpose of providing clinical decision support using CDS Hooks. This is a build at the level of [Draft](http://hl7.org/fhir/versions.html#std-processs). + +| Metadata | Value +| ---- | ---- +| specificationVersion | 1.0 +| hookVersion | 0.1.0 +| hookMaturity | [0 - Draft](../../specification/current/#hook-maturity-model) + +## Workflow + +The `order-start` hook fires when the clinician has reached the point in the workflow where they are ready to begin adding new orders (including orders for medications, procedures, labs and other orders) for the patient. This point in the workflow will usually occur during the encounter when the clinician has completed the examination and assessment, but before they have searched for or selected a given order. The purpose of the hook is to allow guidance services to make order recommendations to the clinician at the point where sufficient clinical data for the patient has been collected but before any orders have been selected. + +## Context +CDS Services should consider including the patient's current active problems, current medication list, lab results, and allergy/intolerance information as prefetch data. Given that these items will necessarily vary they should all be considered as optional values. + +Field | Optionality | Prefetch Token | Type | Description +----- | -------- | ---- | ---- | ---- +`userId` | REQUIRED | Yes | *string* | The id of the current user.
For this hook, the user is expected to be of type [Practitioner](https://www.hl7.org/fhir/practitioner.html) or [PractitionerRole](https://www.hl7.org/fhir/practitionerrole.html).
For example, `PractitionerRole/123` or `Practitioner/abc`. +`patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context +`encounterId` | REQUIRED | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context +`activeProblems` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active problems.
DSTU2 - FHIR Bundle of Condition.
STU3 - FHIR Bundle of Condition.
R4 - FHIR Bundle of Condition.
R5 - FHIR Bundle of Condition. +`activeMedications` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active medications.
DSTU2 - FHIR Bundle of MedicationStatement.
STU3 - FHIR Bundle of MedicationStatement.
R4 - FHIR Bundle of MedicationRequest.
R5 - FHIR Bundle of MedicationRequest. +`labResults` | OPTIONAL | No| *object* | FHIR Bundle with the patient's most recent lab results.
DSTU2 - FHIR Bundle of Observation.
STU3 - FHIR Bundle of Observation.
R4 - FHIR Bundle of Observation.
R5 - FHIR Bundle of Observation. +`patientAllergyIntolerances` | OPTIONAL | No| *object* | FHIR Bundle with the patient's active allergies and intolerances.
DSTU2 - FHIR Bundle of AllergyIntolerance.
STU3 - FHIR Bundle of AllergyIntolerance.
R4 - FHIR Bundle of AllergyIntolerance.
R5 - FHIR Bundle of AllergyIntolerance. + + +## Examples + +### Example (R4) + +```json +{ + "context":{ + "userId":"PractitionerRole/123", + "patientId":"12345", + "encounterId":"98765", + } +} +``` +## Change Log +Version | Description +---- | ---- +0.1.0 | Proposed + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From 4eae20432acdd0b8f8c30cce434dff53dbaff5c0 Mon Sep 17 00:00:00 2001 From: jldanford Date: Tue, 27 Jun 2023 15:59:35 -0400 Subject: [PATCH 3/8] Update OrderStart.md --- docs/hooks/OrderStart.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hooks/OrderStart.md b/docs/hooks/OrderStart.md index 37ec8fbd..8b1724b8 100644 --- a/docs/hooks/OrderStart.md +++ b/docs/hooks/OrderStart.md @@ -5,7 +5,7 @@ | Metadata | Value | ---- | ---- -| specificationVersion | 1.0 +| specificationVersion | 2.0 | hookVersion | 0.1.0 | hookMaturity | [0 - Draft](../../specification/current/#hook-maturity-model) From f7178a25b348e632d89ba6c11be1acd2487f374e Mon Sep 17 00:00:00 2001 From: jldanford Date: Tue, 27 Jun 2023 16:02:19 -0400 Subject: [PATCH 4/8] Rename OrderStart.md to order-start.md --- docs/hooks/{OrderStart.md => order-start.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/hooks/{OrderStart.md => order-start.md} (100%) diff --git a/docs/hooks/OrderStart.md b/docs/hooks/order-start.md similarity index 100% rename from docs/hooks/OrderStart.md rename to docs/hooks/order-start.md From db2f5abd8dce4ae675fa77c4b3a901cde196e12c Mon Sep 17 00:00:00 2001 From: jldanford Date: Tue, 27 Jun 2023 16:13:41 -0400 Subject: [PATCH 5/8] Update order-start.md Minor edits --- docs/hooks/order-start.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/hooks/order-start.md b/docs/hooks/order-start.md index 8b1724b8..a631b471 100644 --- a/docs/hooks/order-start.md +++ b/docs/hooks/order-start.md @@ -1,7 +1,6 @@ `order-start` -!!! info - This page defines a workflow [hook](../../specification/current/#hooks) for the purpose of providing clinical decision support using CDS Hooks. This is a build at the level of [Draft](http://hl7.org/fhir/versions.html#std-processs). +This page defines a workflow [hook](../../specification/current/#hooks) for the purpose of providing clinical decision support using CDS Hooks. This is a build at the level of [Draft](http://hl7.org/fhir/versions.html#std-processs). | Metadata | Value | ---- | ---- @@ -18,18 +17,18 @@ CDS Services should consider including the patient's current active problems, cu Field | Optionality | Prefetch Token | Type | Description ----- | -------- | ---- | ---- | ---- -`userId` | REQUIRED | Yes | *string* | The id of the current user.
For this hook, the user is expected to be of type [Practitioner](https://www.hl7.org/fhir/practitioner.html) or [PractitionerRole](https://www.hl7.org/fhir/practitionerrole.html).
For example, `PractitionerRole/123` or `Practitioner/abc`. +`userId` | REQUIRED | Yes | *string* | The id of the current user.
For this hook, the user is expected to be of type [Practitioner](https://www.hl7.org/fhir/practitioner.html) or [PractitionerRole](https://www.hl7.org/fhir/practitionerrole.html).
For example, `PractitionerRole/123` or `Practitioner/abc`. `patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context `encounterId` | REQUIRED | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context -`activeProblems` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active problems.
DSTU2 - FHIR Bundle of Condition.
STU3 - FHIR Bundle of Condition.
R4 - FHIR Bundle of Condition.
R5 - FHIR Bundle of Condition. -`activeMedications` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active medications.
DSTU2 - FHIR Bundle of MedicationStatement.
STU3 - FHIR Bundle of MedicationStatement.
R4 - FHIR Bundle of MedicationRequest.
R5 - FHIR Bundle of MedicationRequest. -`labResults` | OPTIONAL | No| *object* | FHIR Bundle with the patient's most recent lab results.
DSTU2 - FHIR Bundle of Observation.
STU3 - FHIR Bundle of Observation.
R4 - FHIR Bundle of Observation.
R5 - FHIR Bundle of Observation. -`patientAllergyIntolerances` | OPTIONAL | No| *object* | FHIR Bundle with the patient's active allergies and intolerances.
DSTU2 - FHIR Bundle of AllergyIntolerance.
STU3 - FHIR Bundle of AllergyIntolerance.
R4 - FHIR Bundle of AllergyIntolerance.
R5 - FHIR Bundle of AllergyIntolerance. +`activeProblems` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's current active problems.
DSTU2 - FHIR Bundle of Condition.
STU3 - FHIR Bundle of Condition.
R4 - FHIR Bundle of Condition.
R5 - FHIR Bundle of Condition. +`activeMedications` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's current active medications.
DSTU2 - FHIR Bundle of MedicationStatement.
STU3 - FHIR Bundle of MedicationStatement.
R4 - FHIR Bundle of MedicationRequest.
R5 - FHIR Bundle of MedicationRequest. +`labResults` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's most recent lab results.
DSTU2 - FHIR Bundle of Observation.
STU3 - FHIR Bundle of Observation.
R4 - FHIR Bundle of Observation.
R5 - FHIR Bundle of Observation. +`patientAllergyIntolerances` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's active allergies and intolerances.
DSTU2 - FHIR Bundle of AllergyIntolerance.
STU3 - FHIR Bundle of AllergyIntolerance.
R4 - FHIR Bundle of AllergyIntolerance.
R5 - FHIR Bundle of AllergyIntolerance. ## Examples -### Example (R4) +### Example ```json { From 6cc2bb9e8fb172f09ded45e90051838d97e60324 Mon Sep 17 00:00:00 2001 From: jldanford Date: Tue, 27 Jun 2023 16:15:25 -0400 Subject: [PATCH 6/8] Delete order-start --- docs/hooks/order-start | 46 ------------------------------------------ 1 file changed, 46 deletions(-) delete mode 100644 docs/hooks/order-start diff --git a/docs/hooks/order-start b/docs/hooks/order-start deleted file mode 100644 index 36f733df..00000000 --- a/docs/hooks/order-start +++ /dev/null @@ -1,46 +0,0 @@ -`order-start` - -!!! info - This page defines a workflow [hook](../../specification/current/#hooks) for the purpose of providing clinical decision support using CDS Hooks. This is a build at the level of [Draft](http://hl7.org/fhir/versions.html#std-processs). - -| Metadata | Value -| ---- | ---- -| specificationVersion | 1.0 -| hookVersion | 0.1.0 -| hookMaturity | [0 - Draft](../../specification/current/#hook-maturity-model) - -## Workflow - -The `order-start` hook fires when the clinician has reached the point in the workflow where they are ready to begin adding new orders (including orders for medications, procedures, labs and other orders) for the patient. This point in the workflow will usually occur during the encounter when the clinician has completed the examination and assessment, but before they have searched for or selected a given order. The purpose of the hook is to allow guidance services to make order recommendations to the clinician at the point where sufficient clinical data for the patient has been collected but before any orders have been selected. - -## Context -CDS Services should consider including the patient's current active problems, current medication list, lab results, and allergy/intolerance information as prefetch data. Given that these items will necessarily vary they should all be considered as optional values. - -Field | Optionality | Prefetch Token | Type | Description ------ | -------- | ---- | ---- | ---- -`userId` | REQUIRED | Yes | *string* | The id of the current user.
For this hook, the user is expected to be of type [Practitioner](https://www.hl7.org/fhir/practitioner.html) or [PractitionerRole](https://www.hl7.org/fhir/practitionerrole.html).
For example, `PractitionerRole/123` or `Practitioner/abc`. -`patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context -`encounterId` | REQUIRED | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context -`activeProblems` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active problems.
DSTU2 - FHIR Bundle of Condition.
STU3 - FHIR Bundle of Condition.
R4 - FHIR Bundle of Condition.
R5 - FHIR Bundle of Condition. -`activeMedications` | OPTIONAL | No| *object* | FHIR Bundle with the patient's current active medications.
DSTU2 - FHIR Bundle of MedicationStatement.
STU3 - FHIR Bundle of MedicationStatement.
R4 - FHIR Bundle of MedicationRequest.
R5 - FHIR Bundle of MedicationRequest. -`labResults` | OPTIONAL | No| *object* | FHIR Bundle with the patient's most recent lab results.
DSTU2 - FHIR Bundle of Observation.
STU3 - FHIR Bundle of Observation.
R4 - FHIR Bundle of Observation.
R5 - FHIR Bundle of Observation. -`patientAllergyIntolerances` | OPTIONAL | No| *object* | FHIR Bundle with the patient's active allergies and intolerances.
DSTU2 - FHIR Bundle of AllergyIntolerance.
STU3 - FHIR Bundle of AllergyIntolerance.
R4 - FHIR Bundle of AllergyIntolerance.
R5 - FHIR Bundle of AllergyIntolerance. - - -## Examples - -### Example (R4) - -```json -{ - "context":{ - "userId":"PractitionerRole/123", - "patientId":"12345", - "encounterId":"98765", - } -} -``` -## Change Log -Version | Description ----- | ---- -0.1.0 | Proposed From adc9fe41aaa717fe424e92b88f00831dd3e3199e Mon Sep 17 00:00:00 2001 From: jldanford Date: Wed, 28 Jun 2023 16:10:06 -0400 Subject: [PATCH 7/8] Update order-start.md Add prefetch documentation and examples; cleanup --- docs/hooks/order-start.md | 42 +++++++++++++++++++++++++++++---------- 1 file changed, 32 insertions(+), 10 deletions(-) diff --git a/docs/hooks/order-start.md b/docs/hooks/order-start.md index a631b471..90f5c91e 100644 --- a/docs/hooks/order-start.md +++ b/docs/hooks/order-start.md @@ -10,35 +10,57 @@ This page defines a workflow [hook](../../specification/current/#hooks) for the ## Workflow -The `order-start` hook fires when the clinician has reached the point in the workflow where they are ready to begin adding new orders (including orders for medications, procedures, labs and other orders) for the patient. This point in the workflow will usually occur during the encounter when the clinician has completed the examination and assessment, but before they have searched for or selected a given order. The purpose of the hook is to allow guidance services to make order recommendations to the clinician at the point where sufficient clinical data for the patient has been collected but before any orders have been selected. +The `order-start` hook fires when the clinician has reached the point in the workflow where they are ready to begin adding new orders (including orders for medications, procedures, labs and other orders) for the patient. This point in the workflow will usually occur during the encounter when the clinician has completed the examination and assessment, but before they have searched for or selected a given order. -## Context -CDS Services should consider including the patient's current active problems, current medication list, lab results, and allergy/intolerance information as prefetch data. Given that these items will necessarily vary they should all be considered as optional values. +Post-order alert/change has been determined a major cause of alert fatigue and is cited specifically in studies on physician burnout. The purpose of the hook is to allow guidance services to make order recommendations to the clinician at the point where sufficient clinical data for the patient has been collected but before any orders have been selected. +## Context Field | Optionality | Prefetch Token | Type | Description ----- | -------- | ---- | ---- | ---- `userId` | REQUIRED | Yes | *string* | The id of the current user.
For this hook, the user is expected to be of type [Practitioner](https://www.hl7.org/fhir/practitioner.html) or [PractitionerRole](https://www.hl7.org/fhir/practitionerrole.html).
For example, `PractitionerRole/123` or `Practitioner/abc`. `patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context -`encounterId` | REQUIRED | Yes | *string* | The FHIR `Encounter.id` of the current encounter in context -`activeProblems` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's current active problems.
DSTU2 - FHIR Bundle of Condition.
STU3 - FHIR Bundle of Condition.
R4 - FHIR Bundle of Condition.
R5 - FHIR Bundle of Condition. -`activeMedications` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's current active medications.
DSTU2 - FHIR Bundle of MedicationStatement.
STU3 - FHIR Bundle of MedicationStatement.
R4 - FHIR Bundle of MedicationRequest.
R5 - FHIR Bundle of MedicationRequest. -`labResults` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's most recent lab results.
DSTU2 - FHIR Bundle of Observation.
STU3 - FHIR Bundle of Observation.
R4 - FHIR Bundle of Observation.
R5 - FHIR Bundle of Observation. -`patientAllergyIntolerances` | OPTIONAL | Yes | *object* | FHIR Bundle with the patient's active allergies and intolerances.
DSTU2 - FHIR Bundle of AllergyIntolerance.
STU3 - FHIR Bundle of AllergyIntolerance.
R4 - FHIR Bundle of AllergyIntolerance.
R5 - FHIR Bundle of AllergyIntolerance. +`encounterId` | REQUIRED | No | *string* | The FHIR `Encounter.id` of the current encounter in context + +## Prefetch +CDS clients should consider including the patient's current active problems, current medication list, lab results, and allergy/intolerance information as prefetch data. Given that these items will necessarily vary, they should all be considered as optional values. + +Field | Type | Description +----- | ---- | ---- +`patient` | *object* | The patient's demographic information. A FHIR Patient. +`conditions` | *object* | The patient's current active problems. A FHIR Bundle of Condition. +`medications` | *object* | The patient's current active medications.
DSTU2/STU3 - A FHIR Bundle of MedicationStatement.
R4/R5 - A FHIR Bundle of MedicationRequest. +`observations` | *object* | The patient's most recent lab results, vitals and social history observations. A FHIR Bundle of Observation. +`allergyintolerances` | *object* | The patient's active allergies and intolerances. A FHIR Bundle of AllergyIntolerance. +`goals` | *object* | The patient's goals. A FHIR Bundle of Goal. ## Examples -### Example +### Example (context) ```json { "context":{ - "userId":"PractitionerRole/123", + "userId":"Practitioner/123", "patientId":"12345", "encounterId":"98765", } } ``` +## Example (prefetch) +```json +{ + "prefetch": { + "patient": "Patient/{{context.patientId}}", + "conditions": "Condition?patient={{context.patientId}}&category=problem-list", + "medications": "MedicationRequest?patient={{context.patientId}}", + "observations": "Observation?patient={{context.patientId}}&category=vital-signs,laboratory,social-history", + "allergyintolerances": "AllergyIntolerance?patient={{context.patientId}}", + "goal": "Goal?patient={{context.patientId}}" + } +} +``` + ## Change Log Version | Description ---- | ---- From ffe6142b4f47fbeb9b8ddefa70368273497ba12b Mon Sep 17 00:00:00 2001 From: jldanford Date: Wed, 5 Jul 2023 10:51:02 -0400 Subject: [PATCH 8/8] Update order-start.md --- docs/hooks/order-start.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/hooks/order-start.md b/docs/hooks/order-start.md index 90f5c91e..423f60c2 100644 --- a/docs/hooks/order-start.md +++ b/docs/hooks/order-start.md @@ -12,9 +12,10 @@ This page defines a workflow [hook](../../specification/current/#hooks) for the The `order-start` hook fires when the clinician has reached the point in the workflow where they are ready to begin adding new orders (including orders for medications, procedures, labs and other orders) for the patient. This point in the workflow will usually occur during the encounter when the clinician has completed the examination and assessment, but before they have searched for or selected a given order. +## Context + Post-order alert/change has been determined a major cause of alert fatigue and is cited specifically in studies on physician burnout. The purpose of the hook is to allow guidance services to make order recommendations to the clinician at the point where sufficient clinical data for the patient has been collected but before any orders have been selected. -## Context Field | Optionality | Prefetch Token | Type | Description ----- | -------- | ---- | ---- | ---- `userId` | REQUIRED | Yes | *string* | The id of the current user.
For this hook, the user is expected to be of type [Practitioner](https://www.hl7.org/fhir/practitioner.html) or [PractitionerRole](https://www.hl7.org/fhir/practitionerrole.html).
For example, `PractitionerRole/123` or `Practitioner/abc`. @@ -22,7 +23,7 @@ Field | Optionality | Prefetch Token | Type | Description `encounterId` | REQUIRED | No | *string* | The FHIR `Encounter.id` of the current encounter in context ## Prefetch -CDS clients should consider including the patient's current active problems, current medication list, lab results, and allergy/intolerance information as prefetch data. Given that these items will necessarily vary, they should all be considered as optional values. +CDS clients should consider including the patient's current active problems, current medication list, lab results, allergy/intolerance and patient goal information as prefetch data. Given that these items will necessarily vary, they should all be considered as optional values. Field | Type | Description ----- | ---- | ---- @@ -36,7 +37,7 @@ Field | Type | Description ## Examples -### Example (context) +### Example (R4) (context) ```json { @@ -47,7 +48,7 @@ Field | Type | Description } } ``` -## Example (prefetch) +## Example (R4) (prefetch) ```json { "prefetch": {