Issue Assessment Notice
The Assessment Notice will often be sent with the ReferralRequest, however it is not uncommon for the Social Care Practitioners to get involved early in the discharge process, e.g. to help triage pathway and/or have visibility that one of their service users has been admitted to hospital and may need an early review. By enabling the referral to be sent separately to the Assessment Notice allows Social Care Teams to undertake any Primary care duties, before the patient has formally consented to an assessment.
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/QuestionnaireResponse
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 SHD-QuestionnaireResponse-AssessmentNotice
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 |
---|---|
SHD-QuestionnaireResponse-AssessmentNotice | 0.0.1 |
Extensions | Version |
---|---|
None |
ValueSets | Version |
---|---|
Assessment/Discharge Notice Carer Consultation Status | 0.0.1 |
Assessment Notice Patient Consent Status | 0.0.1 |
Assessment Notice Third Party Consent Source | 0.0.1 |
CodeSystems | Version |
---|---|
Assessment/Discharge Notice Carer Consultation Status | 0.0.1 |
Assessment Notice Patient Consent Status | 0.0.1 |
Assessment Notice Third Party Consent Source | 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 NOT already have been issued an Assessment Notice for the referral
Data Mappings
SHD-QuestionnaireResponse-AssessmentNotice
FHIR Element | Card. | Type | Description/Business Context |
---|---|---|---|
QuestionnaireResponse.basedOn | 1..1 | Reference (CareConnect-SHD-ReferralRequest-1) | Reference to the ReferralRequest the Assessment Notice relates to SHALL be provided when sent after the ReferralRequest.Note: Absolute or Relative referencing is supported |
Examples
Request Body
JSON example of a SHD-QuestionnaireResponse-AssessmentNotice
XML example of a SHD-QuestionnaireResponse-AssessmentNotice