From 2be754c23b97b77d3768663bd6f953f0f5beb079 Mon Sep 17 00:00:00 2001 From: Jonny Rylands Date: Sat, 13 Oct 2018 14:18:28 +0100 Subject: [PATCH] Branch surgery model explanation #561 --- pages/development/development_branch_surgeries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/development/development_branch_surgeries.md b/pages/development/development_branch_surgeries.md index 427fa2e6c..09df2bbc2 100644 --- a/pages/development/development_branch_surgeries.md +++ b/pages/development/development_branch_surgeries.md @@ -47,4 +47,4 @@ Because a GP practice's appointment book can hold appointments across multiple s In order to do this, every `Schedule` resource has an associated `Location` resource which represents the surgery that the appointment will take place at, including the surgery's name, address and contact details. -To retrieve the patient's preferred surgery (assigned when they registered with the practice), a reference to the surgery `Location` is held in `Patient.registrationDetails.preferredBranchSurgery`. This can be used to identify appointments at their preferred surgery by comparing the logical id against that of `Location` resources held in a `Schedule`. +To retrieve the patient's preferred surgery (assigned when they registered with the practice), a reference to the surgery `Location` is held in `Patient.registrationDetails.preferredBranchSurgery`. This can be used to identify appointments at the patient's preferred surgery by comparing it's logical id with that of the `Location` resource referenced from a `Schedule`.