Update Safe for Discharge Status
In order to facilated a timely discharge, the acute trust should notify the parties responsible for supporting the discharge (e.g. Local Authotity and Community Health) as soon as the patient no longer meets any of the clinical criteria to reside in Hospital and any required rehabilitation in the acute hospital has been completed.
Every person on every general ward should be reviewed on a twice daily ward round against the following clinical criteria:
- Requiring ITU or HDU care?
- Requiring oxygen therapy/NIV?
- Requiring intravenous fluids?
- NEWS2 > 3? (clinical judgement required in persons with AF and/or chronic respiratory disease)
- Diminished level of consciousness where recovery realistic?
- Acute functional impairment in excess of home/community care provision?
- Last hours of life?
- Requiring intravenous medication > b.d. (including analgesia)?
- Undergone lower limb surgery within 48hrs?
- Undergone thorax-abdominal/pelvic surgery with 72 hrs?
- Within 24hrs of an invasive procedure? (with attendant risk of acute life- threatening deterioration)
Any person not meeting the clinical criteria to reside (see Hospital Discharge Service: Policy and Operating Model (Annex A)) and who has no requirement for further rehabilitation in the acute hospital, will be deemed safe for discharge.
HTTPS Request
Method:
PUT
Request URL:
The request URL will consist of 'https
Host Environments:
The Host URLs will determined by the service provider, for example the host URLs for the Nottinghamshire County Council Social Care Data Service are:
Environment | Host |
---|---|
Test | health-interoperability-test.nottscc.gov.uk |
Live | health-interoperability.nottscc.gov.uk |
Base URL:
/ReferralService/v3/Encounter
Query String /Parameters:
Name | Value |
---|---|
identifier | The identifier as per Encounter the asscoiated ReferralRequest, in the format {identifier.system |identifier.value} |
Example Request Url:
https
Request Body:
The Request body should be in either json or xml format
The primary base FHIR resource is a CareConnect-SHD-Encounter-1 with references to other resources as per the Entity Relationship Model below:
See Examples for an illustration of the Request body of a typical Referral to Social Care for a Supported Hospital Discharge.
Response
Success
SHALL return a HTTP status code 200
OK on successful execution of the request
Error
An Error SHALL return one of the following HTTP Status Codes and an OperationOutcome with details of the issue:
HTTP Code | Display | Description |
---|---|---|
400 |
Bad Request | Poor Syntax or breaks a core FHIR constraint |
401 |
Unauthorized | User is not authorised to perform the request. |
403 |
Forbidden | The request is forbidden, authorization will not help. |
409 |
Conflict | User has requested to create a resource that already exists. |
422 |
Unprocessable Entity | The syntax is valid, but cannot be processed, e.g. breaks a business rule. |
500 |
Internal Error | The server encountered an unexpected condition which prevented it from fulfilling the request. |
JSON example of an OperationOutcome for a Unprocessable Entity
XML example of an OperationOutcome for a 422
Unprocessable Entity
Profiles
The Refer Patient (to Social Care for Supported Hospital Discharge) Use Care is supported by the following profiles
StructureDefinition | Version |
---|---|
CareConnect-SHD-Encounter-1 | 0.0.1 |
CareConnect-SHD-Location-1 | 0.0.1 |
CareConnect-SHD-Organization-1 | 0.0.1 |
CareConnect-SHD-Practitioner-1 | 0.0.1 |
Extensions | Version |
---|---|
Extension-SHD-MedicallyFitDetails | 0.0.1 |
ValueSets | Version |
---|---|
Supported Hospital Discharge Medically Fit Status | 0.0.1 |
CodeSystems | Version |
---|---|
Supported Hospital Discharge Medically Fit Status | 0.0.1 |
Rules and Mappings
The generic business context data mappings for the 'Madatory' and 'Must Support' elements are detailed in the Profiles section, however the section below deatils any specific rules or contrains that apply to this use case.
Pre-requisites
The patient MUST have an Active Referral Request
Data Mappings
CareConnect-SHD-Encounter-1
FHIR Element | Card. | Type | Description/Business Context |
---|---|---|---|
Encounter.extension |
1..1 | Extension-SHD-MedicallyFitDetails | Extension to share whether the patient is safe for discharge, i.e. no longer meeting ony of the clinical criteria to reside in hospital. |
Encounter.extension |
1..1 | Coding | Binding Supported Hospital Discharge Medically Fit Status |
Encounter.extension |
0..1 | DateTime | Constraint The dateDeemedMedicallyFit SHALL be provided when medicallyFitStatus="Medically Fit". |
Encounter.status | 1..1 | code | Encounter.status SHALL be "in-progress" |
Encounter.statusHistory | 0..0 | BackboneElement | Status History is Not Required on update where Encounter.status="in-progress" |
Encounter.period.end | 0..1 | dateTime | Where Encounter.status="in-progress", the Encounter will be in-progress, the Encounter.period.end will relate to the Target Discharge Date i.e. the Predicted Date that the Patient is expectided to no longer meet any of the criteria to reside in hospital (see Hospital Discharge Service: Policy and Operating Model (Annex A)).Note: The FHIR dateTime data type supports date and partial date, as well as a full date-time value. Hence the time element is not required if the source system only captures a date. |
Examples
Request Body
JSON example of a CareConnect-SHD-Encounter-1
XML example of a CareConnect-SHD-Encounter-1