From a1cabc87dbe2bb9613b69b7e4ee0a0b2a202bebb Mon Sep 17 00:00:00 2001 From: Lloyd McKenzie Date: Fri, 19 Jan 2024 20:03:47 -0700 Subject: [PATCH] Make dispatch hook contexts lowerCamelCase, same as others --- docs/hooks/order-dispatch.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/hooks/order-dispatch.md b/docs/hooks/order-dispatch.md index e4c46267..a2bc78fc 100644 --- a/docs/hooks/order-dispatch.md +++ b/docs/hooks/order-dispatch.md @@ -19,9 +19,9 @@ Decision support that may be relevant for this hook might include information re Field | Optionality | Prefetch Token | Type | Description ----- | -------- | ---- | ---- | ---- `patientId` | REQUIRED | Yes | *string* | The FHIR `Patient.id` of the current patient in context -`dispatched-orders` | REQUIRED | Yes | *array* | Collection of the FHIR local references for the Request resource(s) for which fulfillment is sought E.g. `ServiceRequest/123` +`dispatchedOrders` | REQUIRED | Yes | *array* | Collection of the FHIR local references for the Request resource(s) for which fulfillment is sought E.g. `ServiceRequest/123` `performer` | REQUIRED | Yes | *string* | The FHIR local reference for the Practitioner, PractitionerRole, Organization, CareTeam, etc. who is being asked to execute the order. E.g. `Practitioner/456` -`fulfillment-tasks` | OPTIONAL | No | *array* | DSTU2/STU3/R4/R5 - Collection of the Task instances (as objects) that provides a full description of the fulfillment request - including the timing and any constraints on fulfillment. If Tasks are provided, each will be for a separate order and SHALL reference one of the dispatched-orders. +`fulfillmentTasks` | OPTIONAL | No | *array* | DSTU2/STU3/R4/R5 - Collection of the Task instances (as objects) that provides a full description of the fulfillment request - including the timing and any constraints on fulfillment. If Tasks are provided, each will be for a separate order and SHALL reference one of the dispatched-orders. ## Examples ### Example (R4)