Social Care Record
There are multiple scenarios where visibility of the social care context for a patient will assist a care giver to make better decisions and hence improve the patient’s experience and level of service received, for example:
- An Emergency Department may be able to avoid an hospital admission if they can identify that the patient has a care package, and they can contact the provider to make sure they have been alerted of the incident and will be checking on the individual later
- A Community Health Worker may be able to see that social care have recently undertaken an Occupational Therapy Assessment, and therefore avoid duplication of activity by discussing the outcome with the appropriate social care team
- A hospital discharge team could use the social care context to help identify the appropriate discharge needs of an individual.
Business Context
The Social Care Data Service supports sharing of the following:
Data Object | Business Context | FHIR Resource |
---|---|---|
Citizen/Service User | Basic demographic details of individual, as per local social care system | Patient |
Packages of Care | Social care packages/services that have been commissioned by the Local Authority | EpisodeOfCare |
Referrals | Details of any referrals received by the Local Authority | ReferralRequest |
Assessments/Tasks | Summary of assessments and tasks/actions that the Local Authority has performed (or is performing) on behalf of a patient | Task |
Warnings/Alerts | Local Authority's view of prospective warnings of potential issues regarding a patient | Flag |
Equipment/Assets | Details of equipment/asset (or modifications) that the Local Authority has provided to the patient. | Device |
Related People | Detail of individuals that the Local Authority have recorded as having a relationship to the patient | RelatedPerson |
Support Reasons | Why Social Care are involved with the Patient, including the ‘Primary’ Support Reason which is used to classify an individual for National Reporting on Short and Long Term Services (SALT) | Procedure |
Key Workers | Key Workers who are involved with a Patient from a Social Care perspective | CareTeam |
Local Authority | Local Authority Responsible for Social Care for the Person | CareTeam |
HTTPS Request
Method:
GET
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:
/CareDataService/v2/Patient
Query Parameters:
Name | Card. | Type | Note |
---|---|---|---|
_format | 0..1 | Coded | Optional parameter for the consumer to specify alternative response formats to the default. Both json and xml formats currently supported. |
identifier | 1..1 | String | The NHS number of the Patient in the format https |
_revinclude | 0..* | Coded | Optional parameter for the consumer to request any additional resource (by type) that reference the requested Patient Resource, see table below for supported resource types.The value SHALL be URL Encoded |
The HTTP GET will consist of 'https
See examples for an illustration of a search query and respective URL encoding
Supported _revinclude Resources
Resource | Property value | Business Context |
---|---|---|
EpisodeofCare | EpisodeOfCare:patient | Packages of Care |
ReferralRequest | ReferralRequest:subject | Referrals |
Task | Task:for | Assessments/Events |
Flag | Flag:subject | Alerts/Warnings |
Device | Device:patient | Equipment/Assets |
RelatedPerson | RelatedPerson:patient | Related People |
Procedure | Procedure:subject | Primary Support Reason |
CareTeam | CareTeam:subject | Key Workers |
Response
The API resposne will be a single Bundle Resource with zero or one Patient entries, plus any resourcs (of the requested types) that reference the Patient:
In addition to the core resources (in blue), those resouces may also refererence supporting resourcse, namely:
- Organization that is providing a care package, has submitted a referral, etc
- Practitioner who is undertaking an assessment, who submitted a referral, or part of a CareTeam etc.
Partial Response
The Social Care Data Service also supports the inclusion of an OperationOutcome to indicate if the provider was unable to provide all the data requested, see below:
Profiles
StructureDefinition | Version |
---|---|
CareConnect-CDS-Patient-1 | 0.0.1 |
CareConnect-CDS-EpisodeofCare-1 | 0.0.1 |
CareConnect-CDS-ReferralRequest-1 | 0.0.1 |
CareConnect-CDS-Task | 0.0.1 |
CareConnect-CDS-Flag-1 | 0.0.1 |
CDS-Device | 0.0.1 |
CareConnect-CDS-RelatedPerson-1 | 0.0.1 |
CareConnect-CDS-Procedure-1 | 0.0.1 |
CareConnect-CDS-Organization-1 | 0.0.1 |
CareConnect-CDS-Practitioner-1 | 0.0.1 |
CareConnect-CDS-Careteam-1 | 0.0.1 |
Extensions | Version |
---|---|
Extension-CareConnect-NHSNumberVerificationStatus-1 | 1.1.0 |
Extension-CDS-PrimarySupportReasonFlag | 0.0.1 |
ValueSets | Version |
---|---|
Care Connect NHS Number Verification Status | 1.1.0 |
Social Care Package Detail Category | 0.0.1 |
Social Care Task Detail Category | 0.0.1 |
Social Care Support Reason | 0.0.1 |
CodeSystems | Version |
---|---|
Care Connect NHS Number Verification Status | 1.1.0 |
Social Care Package Detail Category | 0.0.1 |
Social Care Task Detail Category | 0.0.1 |
Social Care Support Reason | 0.0.1 |
Resource metadata
Each resource contains an element "meta", of type "Meta", which is a set of metadata that provides technical and workflow context to the resource. The metadata items are all optional, though some or all of them may be required in particular implementations or contexts of use.
The table below highlights how the meta element of the resources provided in the CDS Bundle response can be used to support a Shared Care Record implementation:
FHIR Element | Card. | Type | Description/Business Context |
---|---|---|---|
{Resource}.meta.versionId | 0..1 | id | Some shared care record may required the ability to recreate a view of a patient record presented to a clinician at a point in time, the tracking of FHIR resource versions will support that, and therefore a versionId SHOULD be included were possible.The versionId should only change between consecutive resource retrievals if one or more of the properties of the resource have changed. |
{Resource}.meta.lastUpdated | 0..1 | instant | lastUpdated can be used by a shared care record to easily sort and display a timeline of interventions (regardless of resource type) to an end user. A lastUpdated SHOULD be provided wherever possible, where the source system does not provide a full audit log, lastUpdated may be the same as the created or authored DateTime. |
{Resource}.meta.profile | 0..* | uri | An assertion that the content conforms to a resource profile (i.e. StructureDefinition). The profile can be used by the consuming system to validate the resource content and/or apply business rule as to how to treat/display the resource. When the type of the canonical reference is a uri , the URL may include a version, in order be precise about which version of the resource is being referred to. To do this, append the version to the canonical url with a '|' like this:<ProfileUri value="http://hl7.org/fhir/StructureDefinition/my-profile|1.0.1"/> |
{Resource}.meta.tag:dataProvider | 0..* | Coding | The meta ‘dataProvider’ tag is a method of determining the provenance of a FHIR resource. It is especially important in federated shared care record solutions which aggregate data from multiple feeder systems, some of which may also be a federated solution (e.g. sharing LHCR to LHCR).In the absence of a national standard, each local solution will determine it's own dataProvider system and allocate codes accordingly. Some providers may be part of more than one shared care record, and hence include multiple ‘dataProvider’ tags. |
Example of metadata elements in JSON
Example of metadata elements in XML
Examples
Search Query
Unencoded query string
https
URL Encoded version
https
Responses
A JSON example of a resposne to a Social Care Data Service query, in the form of a Bundle Resource is displayed below
A XML example of a resposne to a Social Care Data Service query, in the form of a Bundle Resource is displayed below