Update Predicted Discharge Date
The Predicted Discharge Date (PDD) is a key data item in for Social Care in planning and prioritising work - if the PDD changes after an initial referral/assessment notice, but before it is confirmed on the Discharge Notice, then Social Care Teams are potentially prioritising the wrong patients. Having real time updates of changes in the PDD on the Health system ensures that teams can make decisions on current information.
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
Examples
Request Body
JSON example of a CareConnect-SHD-Encounter-1
XML example of a CareConnect-SHD-Encounter-1