Part of Recording patients on extended Section 17 leave
Guidance on recording a new period of extended S17 leave
1. Ensure the current open record is up-to-date
The current record needs to be updated with the latest information about the patient’s care reflecting the position before they go on extended S17 leave. This might include, for example, information on the latest Care (Education) Treatment Review (C(E)TR) and commissioner oversight visit, MHA legal status and discharge planning. Questions on planning and discharge should reflect the position when the person is expected to be going on extended S17 leave (for example, Q44, Q45, Q47a and Q47b should reflect the planned date and location where the person will go on extended S17 leave).
We recommended that you check the values in Q13 and Q14 (hospital provider and site) and select the relevant codes from the dropdowns in Q13a/Q14a. If the entries in these fields do not match the Master Provider and Site List (MPSL) you will not be able to create a new record or upload amended/new records in the following steps.
The fields in the table below should always be checked and updated to reflect the position before the patient went on extended S17 leave.
| Question number | Question | Guidance |
|---|---|---|
| Q18b | Is the patient on extended S17 leave (linked to a legal judgment e.g. MM)? | Should be coded N in this record |
| Q42a | Details of a patient's care plan | Should be 7 - Clinically ready for discharge but unable to discharge due to legal restrictions (e.g. MM judgment) |
| Q42b | Date when patient was "Clinically ready for discharge" or "clinically suitable for transfer" | Enter the date when the patient was clinically ready for discharge |
| Q44/Q45 | Where is the patient's planned transfer to? and Full postcode of the proposed community setting | Details should relate to the community setting the patient will be in whilst on extended S17 leave |
| Q48a, Q48b and Q48c | The reason(s) that a patient is not able to be discharged or transferred despite being clinically ready for discharge or suitable for transfer | This will include code 28 (delay due to consideration of specific court judgments) but also record any other reasons that are relevant (such as accommodation or funding) which have delayed the person going into the community on extended S17 leave |
2. Close the current record
When the current record is fully updated it needs to be closed. This can be done directly within the system (user interface), or by extracting a report, editing and re-uploading the record. To close the current record the fields in the table below need to be completed.
| Question number | Question | Guidance |
|---|---|---|
| Q49 | Date of closure of record | Date when patient went on extended S17 leave. If the patient has been on leave for some time and the exact date is not known an estimated value can be used (the last day of the relevant month) |
| Q50 | Record closed | Code 15 = Other |
| Q41r | Discharge | Leave blank (where Q50 is 15, this question is not mandatory) |
If a patient was already on extended S17 leave at the time this guidance was introduced (November 2024) and you cannot estimate the month they went on leave you can use a default date of 31/10/2024 in Q49.
3. Open a new record relating to period of extended S17 leave
A new record relating to the period on extended S17 leave needs to be opened for the patient. The new record can be entered manually but to minimise the burden the previous record can be copied, edited and uploaded as most of the information will be the same as for the record just closed.
Questions relating to the hospital setting (provider, ward type etc) should be left unchanged. The table below lists the questions which should be amended:
| Question number | Question | Guidance |
|---|---|---|
| Q7a | Source of admission code | This relates to the hospital setting before going on leave so should be 49 (secure) or 53 (non-secure) |
| Q7b | Full postcode of source of admission | This should be the postcode for the hospital the patient was in before going on extended S17 leave |
| Q11a | Start Date | Date extended S17 leave started must be the same as the date entered for Q49 (Date of closure of record) in the closed record |
| Q11b | Date of first admission to any hospital | Date first admitted to hospital as part of the current continuous stay (including any previous periods of extended S17 leave) – may already be correctly recorded in closed record. |
| Q18b | Is the patient on S17 extended leave (linked to a legal judgment e.g. MM)? | Enter code Y |
| Q41q | Point 11.2. Community move/discharge: S17 leave underway as part of transition to community placement | Enter code Y |
| Q47a | Is there an agreed date for planned discharge/transfer? | In this record this relates to actual discharge from extended S17 leave, so in almost all cases this will be N |
| Q47b | Date of planned discharge/transfer | Leave blank if 47a is a no/don't know |
| Q48a, Q48b and Q48c | The reason(s) that a patient is not able to be discharged or transferred despite being clinically ready for discharge or suitable for transfer |
Enter code 28 (delay due to consideration of specific court judgments) Note: Other reasons should not be relevant as person is already living in the community, so record code 98 for Q48b and Q48c |
4. Maintain the record relating to period of extended S17 leave
As the patient is living in the community there are likely to be minimal updates required to the patient record, until the point where circumstances change (for example, the patient is recalled to hospital or is discharged). The record will only require updating if, for example, progress on planning for eventual discharge needs to be captured in questions such as Q41 (12 Point Discharge Plan) and Q47 (Date of planned discharge).
Last edited: 18 November 2024 1:13 pm