transfer documentation

- clinician documentation to explain transfer child workflow
- bug fix where more than one child transferred to same organisation

documentation/docs/clinician-users/entering-patient-data.md

@@ -24,6 +24,28 @@ If you are unable to provide a postcode, click the **No postcode** button and yo
 
 The NHS number is checked against the NHS number [checksum](https://www.datadictionary.nhs.uk/attributes/nhs_number.html) to confirm that it is a valid NHS number. We also use this to check if the patient has already been entered into the audit at a previous date, to avoid duplication.
 
+### Transfering a patient between centres
+
+Only the lead clinician has permissions to transfer children to another centre. 
+
+The steps to do this for the lead clinician in Organisation A
+
+1. Find the child to transfer in the cohort view and navigate to their audit view
+2. Select the 'transfer' button to reveal a dropdown of organisations to transfer the child to. 
+3. Select the organisation to transfer the child to (Organisation B) and click 'Select Secondary Care NHS Trust Centre'
+4. Confirm the transfer by clicking 'Allocate organisation'
+5. You will be redirected back to the organisation view, where a message box will confirm a transfer email has been sent to the lead clinician of the target organisation (Organisation B). Note if there is no lead clinician currently in post, the email will be sent to the Epilepsy12 team.
+6. The child will nolonger be visible to you in Cohort View for Organisation A.
+
+The steps for the lead clinician in Organisation B
+
+1. You receive an email from your colleague who leads Epilepsy12 at Organisation A, notifying you that a transfer has been made.
+2. Log in to Epilepsy12. You are greeted with a popup message informing you of the name of the child requesting transfer.
+3. Navigate to the Cohort View and identify the child - they are highlighted in the list and have 2 extra icons.
+4. Click whichever applies (accept or reject), and acknowledge the confirmation popup.
+5. You will be redirected to the organisation view where a confirmation message will acknowledge successful outcome.
+6. An email is sent to the lead of Organisation A is sent to notify the outcome. Note, if the transfer is rejected, an email also is sent to the Epilepsy12 team.
+
 ### Entering audit data
 
 Only clinician and lead clinician users will be able to do this.

epilepsy12/migrations/0016_alter_site_transfer_origin_organisation.py

@@ -0,0 +1,25 @@
+# Generated by Django 4.2.7 on 2023-11-10 20:06
+
+from django.db import migrations, models
+import django.db.models.deletion
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("epilepsy12", "0015_historicalsite_transfer_origin_organisation_and_more"),
+    ]
+
+    operations = [
+        migrations.AlterField(
+            model_name="site",
+            name="transfer_origin_organisation",
+            field=models.ForeignKey(
+                blank=True,
+                default=None,
+                null=True,
+                on_delete=django.db.models.deletion.PROTECT,
+                related_name="origin_organisation",
+                to="epilepsy12.organisation",
+            ),
+        ),
+    ]

epilepsy12/models_folder/epilepsy12_site.py

@@ -41,7 +41,7 @@ class Site(TimeStampAbstractBaseClass, UserStampAbstractBaseClass):
     site_is_general_paediatric_centre = models.BooleanField(default=False, null=True)
 
     active_transfer = models.BooleanField(default=False)
-    transfer_origin_organisation = models.OneToOneField(
+    transfer_origin_organisation = models.ForeignKey(
         to="epilepsy12.Organisation",
         on_delete=models.PROTECT,
         default=None,