Share Case Note with Social Care
This use case enables health workers/teams to share relevant case notes with the social care team, which may facilitate a Supported Hospital Discharge assessment, help inform the appropriate service required, or provide additional context (reason why an expected discharge date has been changed)
HTTPS Request
Method:
POST
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/Communication
Query String /Parameters:
None
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-Communication-1
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 201
Created 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 422
Unprocessable Entity
XML example of an OperationOutcome for a 422
Unprocessable Entity
Profiles
The Issue Assessment Notice Use Care is supported by the following profiles
StructureDefinition | Version |
---|---|
CareConnect-SHD-Communication-1 | 0.0.1 |
Extensions | Version |
---|---|
None |
ValueSets | Version |
---|---|
None |
CodeSystems | Version |
---|---|
None |
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
FHIR Element | Card. | Type | Description/Business Context |
---|---|---|---|
Communication.status | 1..1 | code | Binding EventStatus Fixed Value: 'completed' |
Communication.subject | 0..1 | Reference | Reference to Patient resource to whom the communication relates. |
Communication.context | 1..1 | Reference | Reference to Encounter resource for the the communication relates. |
Communication.context.identifier | 1..1 | Identifier | Logical reference for Encounter which was included in the CareConnect-SHD-ReferralRequest-1.Constraint: Communication.context.identifier.system = {Local Encounter System}Communication.context.identifier.value= {Encounter ID} |
Communication.context.identifier.type | 1..1 | CodeableConcept | Fixed Value: Communication.context.identifier.type.coding.system = 'http |
Communication.note | 1..1 | Annotation | MUST contain one note |
Communication.note.authorString | 0..1 | string | Optional field for details of who added the note/comment. |
Communication.note.time | 1..1 | dateTime | Date/Time communication was sent to the the Local Authority. SHALL be provided for any CareConnect-SHD-Communication-1 |
Communication.note.text | 1..1 | string | Plain text copy of the note/communication that is being shared with the Loacl Authority. SHALL be provided for any CareConnect-SHD-Communication-1 |
Examples
Request Body
JSON example of a CareConnect-SHD-Communication-1
XML example of a CareConnect-SHD-Communication-1