Confirm patient discharge (on clinical advice or with clinical consent)
Until a patient is physically discharged, there is a possibility that the proposed discharge date will not be realised as it is subject to change – in which case social care teams may need to review and re-arrange any planned packages of care ./ services. Confirmation of discharge informs the social care team that they no longer have to keep a watching brief on such cases.
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
The patient MUST have been diacharge in the Health System (i.e. with a Discharge Method of “PATIENT discharged on clinical advice or with clinical consent”).
Data Mappings
CareConnect-SHD-Encounter-1
FHIR Element | Card. | Type | Description/Business Context |
---|---|---|---|
Encounter.status | 1..1 | code | Encounter.status SHALL be "finished" |
Encounter.statusHistory | 0..0 | BackboneElement | Status History is Not Required on update where Encounter.status="finished" |
Encounter.period.end | 1..1 | dateTime | MUST be provided where Encounter.status="finished", and in which case the Encounter.period.end will relate to the Actual Discharge Date.Note: The FHIR dateTime data type supports date and partial date, as well as a full date-time value. When confirming a discharge the time element MUST be provided if available in the source system. |
Examples
Request Body
JSON example of a CareConnect-SHD-Encounter-1
XML example of a CareConnect-SHD-Encounter-1