| Name | Description | MRO | Cardinality | Implementation Guidance | Data Type | Value Sets | Information Type | Derived From |
|---|---|---|---|---|---|---|---|---|
|
Person demographics
|
The person's details and contact information. |
M | 1…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section contains the person’s demographic and contact details including key identifiers (e.g., name, date of birth, sex at birth, NHS number, address etc.). It also includes a person’s gender identity and pronouns, where stated. NHS number (or equivalent, e.g. CHI number in Scotland) is likely to be the primary identifier however existing national guidance should be followed, including how to handle patients without an NHS number, for example, overseas visitors. |
Label Concept
|
|
Record
|
|
|
Person name
|
Details of the person's name. |
M | 1…1 |
|
Person Name
|
|
|
|
|
Date of birth
|
The date of birth of the person. |
M | 1…1 |
|
Date Time
|
NHS Data Dictionary
—
PERSON BIRTH DATE
|
|
|
|
Sex at birth (observed)
|
The phenotypic sex of the person. |
M | 1…1 |
This is as observed by clinical examination and assessment at birth. Where there is no health and care record from birth, and clinical examination and assessment is not possible, this can be stated by the person or proxy. |
Coded Element
|
NHS Data Dictionary
—
PERSON PHENOTYPIC SEX
|
|
|
|
Administrative gender
|
This is the ‘Person Administrative Gender’ held on the Personal Demographics Service (PDS). |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
PERSON GENDER CODE CURRENT
|
|
|
|
NHS number
|
The unique identifier for a person within the NHS in England and Wales. |
R | 0…1 |
|
Identifier
|
NHS Data Dictionary
—
NHS NUMBER
|
|
|
|
NHS number status indicator
|
Provides an indication of the reliability of an NHS Number. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
NHS NUMBER STATUS INDICATOR CODE
|
|
|
|
Other identifier
|
Country specific or local identifier, e.g. Community Health Index (CHI) in Scotland. |
R | 0…* |
|
Identifier
|
NHS Data Dictionary
—
LOCAL PATIENT IDENTIFIER (EXTENDED)
NHS Data Dictionary
—
COMMUNITY HEALTH INDEX NUMBER
NHS Data Dictionary
—
HEALTH AND CARE NUMBER
|
|
|
|
Person address
|
Person’s usual place of residence, and where relevant temporary and correspondence addresses. |
M | 1…* |
A person's contact details (including email address, address and telephone number) may change or become inactive, so where possible details should be checked to ensure they are up to date. |
Address
|
|
|
|
|
Person contact details
|
Details of the person's contact information. |
R | 0…1 |
A person's contact details (including email address, address and telephone number) may change or become inactive, so where possible details should be checked to ensure they are up to date. |
Label Concept
|
|
|
|
|
Preferred contact method
|
Preferred contact method, e.g. email, letter, phone, text message etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
COMMUNICATION CONTACT METHOD
|
|
|
|
Person telephone number
|
The person's telephone number. |
R | 0…* |
|
Telecom
|
|
|
|
|
Person email address
|
The person's email address. |
R | 0…* |
|
Telecom
|
|
|
|
|
Other contact information
|
Other contact details (e.g., via fax, SMS, URL). |
R | 0…* |
|
Telecom
|
|
|
|
|
Gender identity
|
The person's stated gender identity. |
O | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
GENDER IDENTITY CODE
|
|
|
|
Additional information about gender identity
|
Any additional information stated by the person about their gender identity. |
O | 0…1 |
|
Text
|
|
|
|
|
Pronouns
|
The person's stated pronouns. |
O | 0…1 |
|
Text
|
|
|
|
|
Ethnicity
|
The ethnicity of the person as specified by the person. |
R | 0…1 |
Please note:
|
Coded Element
|
NHS Data Dictionary
—
ETHNIC CATEGORY
Public Health Scotland Data Dictionary
—
Ethnic Group
NHS Wales Data Dictionary
—
Ethnic Group
HSE Data Dictionary
—
PLACEHOLDER
(Draft)
|
|
|
|
Religion
|
The religious affiliation as specified by the person. |
R | 0…1 |
Please note:
|
Coded Element
|
|
|
|
|
Marital status
|
An indicator to identify the legal marital status of the person. |
O | 0…1 |
Please note:
|
Coded Element
|
NHS Data Dictionary
—
PERSON MARITAL STATUS
Public Health Scotland Data Dictionary
—
Marital Status
NHS Wales Data Dictionary
—
Marital Status
HSE Data Dictionary
—
PLACEHOLDER
(Draft)
|
|
|
|
GP practice
|
Details of the person's GP practice. |
M | 1…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section contains details of the GP practice where the person is registered. This information would be sourced from PDS. This will include the GP practice identifier code. In situations where a person is not registered with a GP practice, the GP practice identifier would contain the appropriate code to indicate this. This section would also need to accommodate details for temporary GP where the patient is registered away from their usual place of residence. |
Label Concept
|
|
|
|
|
GP practice record entry
|
This is a GP practice record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Record
|
|
|
GP name
|
The name of the person's GP. If the person is registered with a GP practice, their usual GP name will be something volunteered by the person or their representative. |
R | 0…1 |
|
Person Name
|
|
|
|
|
GP practice details
|
Name and address of the person's registered GP Practice. Registered GP practice details are available from the Person Demographics Service (PDS), or volunteered from the person or their representative. Include details of the practice name and address. |
R | 0…1 |
|
Address
|
|
|
|
|
GP practice identifier
|
The identifier of the registered GP practice. |
M | 1…1 |
|
Coded Element
|
NHS Data Dictionary
—
GENERAL MEDICAL PRACTICE (PATIENT REGISTRATION)
|
|
|
|
About Me
|
This is a record of the things that a person feels it is important to communicate about their needs, strengths, values, concerns and preferences to others providing support and care. |
R | 0…1 |
Completing an ‘About Me’ is an important part of palliative and end of life planning and therefore needs to be available for a person to complete and share as part of care planning for palliative and end of life care. The expectation is that this information would be written or recorded by an individual, supported by a professional or carer (or by someone on behalf of the person if they do not have capacity). It includes options to use multimedia files which are particularly useful when a person has difficulties expressing themselves, or for showing how to do things or actions and reactions. It is recommended that About Me information is reviewed and updated at key transition points for example for children and young people with Education, Health and Care (EHC) plans when transitioning from primary to secondary school, moving onto college and whenever their home circumstances change (for example moving into supported living or residential care). The transition process from children’s social care to adult’s social care is also a recommended time for reviewing and updating About Me information. For adults, it should be reviewed and updated at planned reviews or when circumstances change. It should be possible for the individual to update their information whenever they want or need to. It is recommended the individual (or the person supporting them to write the information) is prompted to consider:
About Me elements are free text to allow the person to elaborate on their preferences (e.g. what matters to them). To help individuals to structure their information within the sections a set of possible prompt questions have been included with this guidance, but please note that these are intended as a guide and should not constrain a person's responses to the sections in About Me. If implementers are working with a particular cohort, they may wish to consult guidance from relevant bodies or charities and tailor the prompt questions accordingly. |
Label Concept
|
|
|
|
|
About Me record entry
|
About Me record entry. |
R | 0…1 |
The cardinality is 0 to 1 as viewers of an About Me should only see the latest version/record entry (not all the record entries). However, systems should hold previous versions of About Me as an audit trail. |
Label Concept
|
|
Event.Record
|
|
|
What is most important to me
|
A description of what is most important to you. Key Information: Include any essential information that any professional in health and social care should know about you in any situation, including emergencies. Other Information: This could include: values, spirituality/religion, ethnicity, culture, pets, goals and aspirations, meaningful activities including leisure activities, visiting places, sport and exercise, listening to music, employment, education, volunteering. |
R | 0…1 |
Prompt questions: 1. What does someone caring for, or supporting you, need to know about you in an emergency? Consider including any important preferences, needs and wishes that indicate how you need to be cared for and supported in an emergency such as the need to avoid any disturbing stimuli e.g., noise, visual, smell, taste or touch etc. For example by being seen in a quiet or darkened room, the need for visual aids, the need for a translator or the need for vegan appropriate medications etc. Consider including any food allergies or risk of choking. Consider referencing other documents in which you have already recorded any needs, wishes and preferences such as an advance decision, a lasting power of attorney, a communication or hospital passport or an end-of-life plan. 2. What’s most important to you? This is just as important as emergency information. Think about your core values, spiritual beliefs, culture, ethnicity and religion as they relate to your care. Think about what makes you happy, for example meaningful activities you enjoy, pets, objects, computer games, exercise or sport, places you like to visit, education or spending time with family and friends. There may be a specific stimulating sensory item or activity you enjoy. 3. What are your aspirations and goals for the future? |
Label Concept
|
|
|
|
|
Coded value
|
The coded value for what is most important to me. |
R | 0…1 |
|
Code no Text
|
SNOMED CT
—
1515861000000103 |What is most important to me|
|
|
|
|
About Me response
|
About Me response. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Free text
|
Free text. |
R | 0…1 |
|
Text
|
|
|
|
|
Multi-media
|
Multi-media. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Multi-media filename
|
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
R | 0…1 |
|
String
|
|
|
|
|
Media type
|
The media type of the multi-media file. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Multi-media file
|
The actual multi-media file if it is stored in the system. |
R | 0…1 |
The multi-media file can either be stored in the system using this element, or using a URL. |
MultiMedia
|
|
|
|
|
Multi-media URL
|
The URL or link to the multi-media file where it is stored in a different system. |
R | 0…1 |
The multi-media file can either be referenced with a URL or link using this element, or by storing the actual file using the muti-media file element. |
String
|
|
|
|
|
People who are important to me
|
Details of who is important to you and why. They could be family members, carers, friends, members of staff etc. Include how you want the people important to you to be engaged and involved in your care and support in both emergency and normal situations. Include how you stay connected to the people important to you. Who should not be contacted or consulted about your care and support and why, if you wish to say. |
R | 0…1 |
Prompt questions: 1. Who are the important people in your life and why? Think about family, friends, staff in the care home and people who support you at home or in the community or at a club. 2. Who should be contacted in an emergency and why? 3. Who do you want to be consulted on, and involved in, your care and support in an emergency and in normal situations? 4. Is there anyone that should not be contacted or consulted about your care and support and why (if you wish to say)? |
Label Concept
|
|
|
|
|
Coded value
|
The coded value for people who are important to me. |
R | 0…1 |
|
Code no Text
|
SNOMED CT
—
1515871000000105 |People who are important to me|
|
|
|
|
About Me response
|
About Me response. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Free text
|
Free text. |
R | 0…1 |
|
Text
|
|
|
|
|
Multi-media
|
Multi-media. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Multi-media filename
|
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
R | 0…1 |
|
String
|
|
|
|
|
Media type
|
The media type of the multi-media file. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Multi-media file
|
The actual multi-media file if it is stored in the system. |
R | 0…1 |
The multi-media file can either be stored in the system using this element, or using a URL. |
MultiMedia
|
|
|
|
|
Multi-media URL
|
The URL or link to the multi-media file where it is stored in a different system. |
R | 0…1 |
The multi-media file can either be referenced with a URL or link using this element, or by storing the actual file using the muti-media file element. |
String
|
|
|
|
|
How I communicate and how to communicate with me
|
A description of how you communicate normally including any communication aids you use, for example a hearing aid.
Describe how you would like others to engage and communicate with you, including how you would like to be addressed. |
R | 0…1 |
Prompt questions: 1. What do people caring for you and supporting you need to know about how you communicate and how they should communicate with you? Consider:
2. How do you let people know you are in pain, anxious or in distress? For example, do you communicate it verbally, facially or through body language? 3. How do you make choices? When offered a verbal choice do you always make an informed choice, or do you need those supporting you to explain choices in detail? 4. How do you indicate yes and no? 5. How do you give feedback or raise a concern? 6. What support would help you understand what is happening and what treatment you might need in hospital? 7. When is a good and bad time to have important conversations with you? |
Label Concept
|
|
|
|
|
Coded value
|
The coded value for how I communicate and how to communicate with me. |
R | 0…1 |
|
Code no Text
|
SNOMED CT
—
1515881000000107 |How I communicate and how to communicate with me|
|
|
|
|
About Me response
|
About Me response. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Free text
|
Free text. |
R | 0…1 |
|
Text
|
|
|
|
|
Multi-media
|
Multi-media. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Multi-media filename
|
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
R | 0…1 |
|
String
|
|
|
|
|
Media type
|
The media type of the multi-media file. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Multi-media file
|
The actual multi-media file if it is stored in the system. |
R | 0…1 |
The multi-media file can either be stored in the system using this element, or using a URL. |
MultiMedia
|
|
|
|
|
Multi-media URL
|
The URL or link to the multi-media file where it is stored in a different system. |
R | 0…1 |
The multi-media file can either be referenced with a URL or link using this element, or by storing the actual file using the muti-media file element. |
String
|
|
|
|
|
My wellness
|
A description covering what you are able to do, how you engage with others and how you feel on a typical day through to on a day when you are unwell or really unwell.
|
R | 0…1 |
Prompt questions: 1. What shows the good things in your life and who you are as a person? Think about photos, videos, letters from people you value, Facebook pages, Twitter or Instagram accounts. 2. What are you able to do and how do you feel on a typical day? 3. How do any conditions or symptoms you live with affect you and how do you manage them? 4. Do you have any long-term pain, if so, how do you manage it? 5. Do you have past events or health issues that affect you, if so, how do you manage them? 6. What triggers or vulnerabilities can cause you to become unwell, how do you avoid or address them? 7. What might indicate that you are becoming unwell, how do you manage it? 8. What are you able to do and how do you feel on a bad day, how do you want to be supported? 9. What helps and hinders you to be well? |
Label Concept
|
|
|
|
|
Coded value
|
The coded value for my wellness. |
R | 0…1 |
|
Code no Text
|
SNOMED CT
—
1515891000000109 |My wellness|
|
|
|
|
About Me response
|
About Me response. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Free text
|
Free text. |
R | 0…1 |
|
Text
|
|
|
|
|
Multi-media
|
Multi-media. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Multi-media filename
|
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
R | 0…1 |
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
String
|
|
|
|
|
Media type
|
The media type of the multi-media file. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Multi-media file
|
The actual multi-media file if it is stored in the system. |
R | 0…1 |
The multi-media file can either be stored in the system using this element, or using a URL. |
MultiMedia
|
|
|
|
|
Multi-media URL
|
The URL or link to the multi-media file where it is stored in a different system. |
R | 0…1 |
The multi-media file can either be referenced with a URL or link using this element, or by storing the actual file using the muti-media file element. |
String
|
|
|
|
|
Please do and please do not
|
A description of things you want someone supporting you to do (or not to do). Things you want someone to do might include (for example): Talk to me not to my carer, remind me to take my medication, encourage me to wash my hands regularly, explain to me what is happening and why, respond to my communication. A description of things you do not want someone supporting you to do might include (for example): Discussing or asking questions about certain topics, making assumptions about something, providing support when it is not wanted, talking to you in a certain way, or asking you to undergo a specific intervention or to take a medication that you do not want. |
R | 0…1 |
Prompt questions: 1. What are the really important things that you want someone to do when caring for or supporting you? 2. What are the really important things that you don’t want someone to do when caring for or supporting you? |
Label Concept
|
|
|
|
|
Coded value
|
The coded value for please do and please do not. |
R | 0…1 |
The coded value for please do and please do not. |
Code no Text
|
SNOMED CT
—
1515901000000105 |Please do and please do not|
|
|
|
|
About Me response
|
About Me response. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Free text
|
Free text. |
R | 0…1 |
|
Text
|
|
|
|
|
Multi-media
|
Multi-media. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Multi-media filename
|
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
R | 0…1 |
|
String
|
|
|
|
|
Media type
|
The media type of the multi-media file. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Multi-media file
|
The actual multi-media file if it is stored in the system. |
R | 0…1 |
The multi-media file can either be stored in the system using this element, or using a URL. |
MultiMedia
|
|
|
|
|
Multi-media URL
|
The URL or link to the multi-media file where it is stored in a different system. |
R | 0…1 |
The multi-media file can either be referenced with a URL or link using this element, or by storing the actual file using the muti-media file element. |
String
|
|
|
|
|
How and when to support me
|
A description of how and when you want someone caring for you to support you.
|
R | 0…1 |
Prompt questions: 1. What do people caring for and supporting you in an emergency need to know about how and when to support you? 2. What are your important routines? What are you able to do for yourself, what do you need support with and how do you want to be supported? Think about:
Think about eating and drinking:
Think about sleeping:
Think about taking medication:
Think about your mobility:
Think about memory and thoughts:
Think about your emotions, moods and behaviours:
Think about work, college and/or leisure activities:
3. What works well and what doesn’t work for you when someone is supporting you? 4. What triggers could result in you needing further support and strategies for avoiding or addressing the triggers? 5. How do your support needs change in different environments? |
Label Concept
|
|
|
|
|
Coded value
|
The coded value for how and when to support me. |
R | 0…1 |
|
Code no Text
|
SNOMED CT
—
1515911000000107 |How and when to support me|
|
|
|
|
About Me response
|
About Me response. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Free text
|
Free text. |
R | 0…1 |
|
Text
|
|
|
|
|
Multi-media
|
Multi-media. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Multi-media filename
|
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
R | 0…1 |
|
String
|
|
|
|
|
Media type
|
The media type of the multi-media file. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Multi-media file
|
The actual multi-media file if it is stored in the system. |
R | 0…1 |
The multi-media file can either be stored in the system using this element, or using a URL. |
MultiMedia
|
|
|
|
|
Multi-media URL
|
The URL or link to the multi-media file where it is stored in a different system. |
R | 0…1 |
The multi-media file can either be referenced with a URL or link using this element, or by storing the actual file using the muti-media file element. |
String
|
|
|
|
|
Also worth knowing about me
|
A description of what is also worth knowing about you for people caring or supporting you.
|
R | 0…1 |
Prompt questions: 1. Provide a short summary of your past life. Think about:
2. Provide a short profile of your current life. Think about:
3. What do you like to do? Think about people you like to see, places you like to visit, activities you enjoy doing and your favourite tv programmes etc. 4. What are your food preferences or requirements? 5. What do you like to talk about? 6. What do you not like? Think about environments you do not like to be in, food, places, things you do not like to do and things you do not like to talk about. |
Label Concept
|
|
|
|
|
Coded value
|
The coded value for what is also worth knowing about me. |
R | 0…1 |
|
Code no Text
|
SNOMED CT
—
1515921000000101 |Also worth knowing about me|
|
|
|
|
About Me response
|
About Me response. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Free text
|
Free text. |
R | 0…1 |
|
Text
|
|
|
|
|
Multi-media
|
Multi-media. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Multi-media filename
|
The filename of the multi-media file. This should not include the suffix or extension showing the file type (e.g. .MP4). |
R | 0…1 |
|
String
|
|
|
|
|
Media type
|
The media type of the multi-media file. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Multi-media file
|
The actual multi-media file if it is stored in the system. |
R | 0…1 |
The multi-media file can either be stored in the system using this element, or using a URL. |
MultiMedia
|
|
|
|
|
Multi-media URL
|
The URL or link to the multi-media file where it is stored in a different system. |
R | 0…1 |
The multi-media file can either be referenced with a URL or link using this element, or by storing the actual file using the muti-media file element. |
String
|
|
|
|
|
Supported to write this by
|
Where relevant, this is a record of name, relationship/role and contact details of the individual(s) who supported the person to write this section e.g. carer, family member, advocate, professional. |
R | 0…1 |
This data item records the information about who supported the person to write the About Me. This could pick up an individual's details if they exist in a system being used to create an About Me. Where someone does not have the capacity or capability to do their About Me themselves or with support, this should be used to explain how it was completed (e.g. from their experience of caring for the person supported by notes from their record etc). Note that getting the views of the person as much as possible should remain the aim. |
Text
|
|
|
|
|
Date last updated
|
This is a record of the date that this About Me was created or last updated. |
R | 0…1 |
This is a record of the date that this About Me was created or last updated. |
Date Time
|
|
|
|
|
Individual requirements
|
The individual requirements section supports recording and flagging of a person's key reasonable adjustment needs and any related significant impairments (disabilities) or underlying conditions. |
R | 0…1 |
This section is currently under review to ensure alignment with DAPB4019: Reasonable Adjustment Digital Flag. Any further additions or updates will be included in the Core Information Standard v3 major release and next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . Implementers are advised to review the key documents and further information in the current releases of DAPB4019: Reasonable Adjustment Digital Flag [ https://digital.nhs.uk/data-and-information/information-standards/governance/latest-activity/standards-and-collections/dapb4019-reasonable-adjustment-digital-flag/ ] and FHIR Patient Flag Implementation Guide [ https://packages.fhir.org/guide/patient-flag-implementation-guide-beta/Home?version=0.2.0-Beta ]. For palliative and end of life care, an individual’s requirements may change over time and will need constant review. |
Label Concept
|
|
|
|
|
Reasonable adjustments
|
A record of reasonable adjustments that must be provided by the service to comply with the Equality Act 2010. Under the Equality Act 2010, organisations have a legal duty to make changes in their approach or provision to ensure that services are as accessible to people with disabilities as they are for everybody else. These changes are called reasonable adjustments. Reasonable adjustments can mean alterations to buildings by providing lifts, wide doors, ramps and tactile signage, but may also mean changes to policies, procedures and staff training to ensure that services work equally well for people with physical or sensory disabilities, learning disabilities or long-term conditions such as dementia. Other adjustments include longer appointments, providing easy read materials or communications via a carer. This legal duty is anticipatory which means a service should know about a person’s need for adjustments when they are referred or present for care. For this to happen, and for optimum care to be delivered, adjustments need to be recorded and shared across the NHS. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Reasonable Adjustments Digital Flag record entry
|
This is a Reasonable Adjustments Digital Flag record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…1 |
|
Label Concept
|
|
Event.Record
|
|
|
Reasonable Adjustments Digital Flag
|
A coded flag to indicate that the person has an impairment with substantial and long term adverse effect(s) on their normal day to day activity meeting the threshold for disability under the Equality Act 2010. I.e. an impairment or disability requiring reasonable adjustments is present. |
M | 1…1 |
|
Coded Element
|
SNOMED CT
—
1326341000000105 |Impairment with substantial and long term adverse effect on normal day to day activity (Equality Act 2010)|
(Mandatory)
|
|
|
|
Consent for reasonable adjustments information sharing record entry
|
This is a consent for reasonable adjustments information sharing record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…1 |
|
Label Concept
|
|
Event.Record
|
|
|
Objects to sharing information to Reasonable Adjustments Digital Flag
|
This is a record of the person's refusal to consent for information sharing including upload of data to the reasonable adjustment digital flag on the NHS Spine. |
M | 1…1 |
|
Coded Element
|
SNOMED CT
—
1853781000000107 |Declined consent to upload data to Reasonable Adjustment Digital Flag|
(Mandatory)
|
|
|
|
Reasonable adjustment record entry
|
This is a reasonable adjustment record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Reasonable adjustment category
|
The adjustment category code of the reasonable adjustment as per DAPB4019: Reasonable Adjustment Digital Flag. E.g. requires specific contact method, requires communication professional. |
M | 1…1 |
|
Coded Element
|
FHIR
—
EnglandFlagCategoryProgramme
(Recommended)
|
|
|
|
Reasonable adjustment
|
The reasonable adjustment required. |
M | 1…1 |
|
Coded Element
|
FHIR
—
EnglandFlagCodeRA
(Mandatory)
|
|
|
|
Reasonable adjustment additional detail
|
Further detail about the support required. |
R | 0…1 |
Any supplementary information for context and personalisation relating to the coded reasonable adjustment SHOULD be provided as free text. Supplementary free text with detail about the support required MUST be provided if the bespoke reasonable adjustment code and associated SNOMED CT concept (1108111000000107 |Requires reasonable adjustment for health and care access (Equality Act 2010)|) is used. |
Text
|
|
|
|
|
Reasonable adjustments review record entry
|
This is a reasonable adjustments review record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Reasonable adjustments review
|
Indicates that a review of a person's reasonable adjustment needs has been done. |
M | 1…1 |
|
Coded Element
|
SNOMED CT
—
1833271000000103 |Review of Reasonable Adjustments needs|
(Recommended)
|
|
|
|
Impairments
|
A record of any impairments that the person has meeting the threshold for disability under the Equality Act 2010. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Impairment record entry
|
This is an impairment record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Impairment category
|
The category of the impairment or disability e.g. physical (such a mobility or dexterity), sensory (such as sight or hearing) or social or behavioural (for example associated with autism spectrum disorder) etc. |
M | 1…1 |
|
Coded Element
|
FHIR
—
EnglandFlagConditionCode
(Recommended)
NHS Data Dictionary
—
Impairment Harmonised Standard
(Recommended)
|
|
|
|
Impairment
|
The specific impairment or disability e.g. night blindness or anterograde amnesia. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
<< 404684003 |Clinical finding|
(Draft)
|
|
|
|
Impairment additional detail
|
Further detail about the impairment. |
O | 0…1 |
|
Text
|
|
|
|
|
Underlying conditions
|
A record of any underlying conditions that the person has related to an impairment or disability, if known. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Underlying condition record entry
|
This is an underlying condition record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Underlying condition category
|
Identifies the category of the condition. |
O | 0…1 |
|
Coded Element
|
FHIR
—
EnglandFlagConditionCategory
(Example)
|
|
|
|
Underlying condition
|
Underlying condition related to the impairment or disability, if known. |
M | 1…1 |
|
Coded Element
|
SNOMED CT
—
1127601000000107 |Healthcare matters simple reference set|
(Draft)
|
|
|
|
Underlying condition additional detail
|
Further detail about the underlying condition. |
O | 0…1 |
|
Text
|
|
|
|
|
Alerts
|
Details of alerts. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section allows for the sharing of alerts (e.g with a shared care record). It is unlikely that all alerts generated for a person would be shared (e.g. as some alerts are dynamically generated in local systems, for example within decision support systems. The alerts that are shared should be determined locally. They might, for example, include, the fact that the person has a dangerous dog or that a person requires reasonable adjustments. |
Label Concept
|
|
|
|
|
Alerts record entry
|
This is an alerts record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Alert
|
Any significant information meriting a specific and highly visible warning to any user (e.g. metallic implant, potential dangerous pet). |
M | 1…1 |
|
Text
|
|
|
|
|
Legal information
|
The legal information relating to the person. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section identifies where there is legal or formal documentation relating to the care of the person. This includes consent relating to child, mental capacity assessment, lasting power of attorney and Advance Decision to Refuse Treatment. Copies of the legal documents should be made available where possible as these may have a direct bearing on treatment. |
Label Concept
|
|
|
|
|
Consent relating to child
|
Details of the person's consent relating to child. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Consent relating to child
|
The person with parental responsibility or appointed guardian where a child lacks competency. Consideration of age and competency, applying Gillick competency or Fraser guidelines. |
R | 0…1 |
|
Text
|
|
|
|
|
Location of document
|
The location of the consent document. |
R | 0…1 |
|
String
|
|
|
|
|
Mental capacity assessment
|
Details of the person's mental capacity assessment(s). |
R | 0…* |
Mental capacity needs to be assessed at each instance where treatment decisions need to be made. Hence there should be provisions for more than one mental capacity assessment to be recorded and shared. If sharing the outcome of a mental capacity assessment it is important to record to which decision it relates. This is particularly important for end of life care planning where a person’s capacity to make decisions for themselves may change at short notice or where they have capacity to make some decisions but not others at the time. |
List
|
|
Event.Record
|
|
|
Mental capacity assessment
|
Whether an assessment of the mental capacity of the (adult) person has been undertaken, if so, what capacity the decision relates to and the outcome of the assessment. Also record best interests decision if person lacks capacity. There can be multiple assessments carried out for a person over time. |
R | 0…1 |
|
Text
|
|
|
|
|
Location of document
|
The location of the mental capacity assessment information. |
R | 0…1 |
|
String
|
|
|
|
|
Lasting power of attorney for health and welfare or court-appointed deputy (or equivalent)
|
Details of the person's lasting power of attorney (LPA) for health and welfare (or equivalent). |
R | 0…1 |
The following is a general overview of lasting power of attorney or equivalent to support implementation of the Palliative and End of Life Information Standard. It may not be fully accurate or up to date and MUST not be considered legal advice. Lasting Power of Attorney (or equivalent) refers to the appointment of one or more people (attorneys) to take decisions on their behalf if they subsequently lose capacity. This is known as ‘Lasting Power of Attorney’ (LPA) under the provisions of the Mental Capacity Act 2005 (England and Wales) [ https://www.legislation.gov.uk/ukpga/2005/9/contents ] and the Mental Capacity Act (Northern Ireland) 2016 [ https://www.legislation.gov.uk/nia/2016/18/contents ], 'Enduring Power of Attorney' (EPA) under The Enduring Powers of Attorney (Northern Ireland) Order 1987 [ https://www.legislation.gov.uk/nisi/1987/1627/crossheading/enduring-powers-of-attorney/made ] and 'Continuing Power of Attorney' (CPoA) or 'Welfare Power of Attorney' (WPoA) under the Adults with Incapacity (Scotland) Act 2000 [ https://www.legislation.gov.uk/asp/2000/4/contents ]. There are LPAs (or WPoAs) for health and welfare and LPAs (or CPoAs / EPAs) for property and affairs. Northern Ireland has not adopted the LPA model for health and welfare. Only health and welfare attorneys can make healthcare decisions, and they can only make decisions about life-sustaining treatment if this has been specifically allowed in the LPA (or equivalent document in Scotland). LPAs (or equivalent) come into effect only when the person in question loses capacity to make the decision(s) to which the powers of attorney relate. An LPA (or equivalent) must be in a prescribed form and (to be valid) be registered with the Office of the Public Guardian (OPG) in England and Wales, the OPG Scotland or the Office of Care and Protection (OCP) in Northern Ireland. If life-sustaining treatment is being considered the LPA (or equivalent document) must state specifically that the attorney has been given power to consent to or refuse life-sustaining treatment. The name and contact details for any appointed attorney should be included in the record. Alternatively, details of any deputy (or equivalent, i.e. guardian in Scotland or controller in Northern Ireland) appointed by court order to make decisions about the person’s health and welfare should be recorded where no LPA (or equivalent) is in place. A deputy (or equivalent) does not have the power to refuse life-sustaining treatment. Information such as the document location and the date that the LPA was registered with the OPG /OCP is important to record. Knowing who to consult with and who is the key decision maker on a person’s health and welfare is very important to decision making if the person lacks capacity to make their own decisions. |
Label Concept
|
|
Record
|
|
|
Lasting power of attorney for health and welfare (or equivalent) flag
|
A coded flag to indicate that the person has a lasting power of attorney for health and welfare (or equivalent) in place. |
M | 1…1 |
|
Coded Element
|
SNOMED CT
—
816361000000101 |Has appointed person with personal welfare lasting power of attorney (Mental Capacity Act 2005)| OR 816381000000105 |Has appointed person with personal welfare lasting power of attorney with authority for life sustaining decisions (Mental Capacity Act 2005)|
(Recommended)
|
|
|
|
Person(s) appointed
|
Record of one or more people who have been given power (LPA or equivalent) by the person, when they had capacity, to make decisions about their health and welfare should they lose capacity to make those decisions. Also details of any person (deputy or equivalent) appointed by the Court of Protection (or equivalent) to make decisions about the person’s health and welfare when they lack capacity. |
R | 0…* |
Where there are multiple appointed attorneys the LPA (or equivalent) itself should be referred to in order to understand how their responsibilities are held, which could be jointly, jointly or severally or jointly for some decisions but jointly and severally for other decisions relating to health and/or welfare. |
List
|
|
|
|
|
Name
|
The name of the appointed person. |
M | 1…1 |
|
Person Name
|
|
|
|
|
Relationship
|
The relationship the appointed person has to the person, e.g. father, grandmother, family friend etc. |
R | 0…1 |
|
Coded Element
|
FHIR
—
UKCorePersonRelationshipType
|
|
|
|
Contact details
|
The contact details (UK telephone number) of the appointed person. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
UK TELEPHONE NUMBER
|
|
|
|
Location of document
|
The location of the lasting power of attorney (LPA or equivalent) for health and welfare. |
R | 0…1 |
|
String
|
|
|
|
|
Lasting power of attorney for property and financial affairs or court-appointed deputy (or equivalent)
|
Details of the person's lasting power of attorney (LPA or equivalent) for property and financial affairs. |
R | 0…1 |
The following is a general overview of lasting power of attorney for property and financial affairs or equivalent to support implementation of the Palliative and End of Life Information Standard. It may not be fully accurate or up to date and MUST not be considered as legal advice. Lasting Power of Attorney (or equivalent) refers to the appointment of one or more people (attorneys) to take decisions on their behalf if they subsequently lose capacity. This is known as ‘Lasting Power of Attorney’ (LPA) under the provisions of the Mental Capacity Act 2005 (England and Wales) [ https://www.legislation.gov.uk/ukpga/2005/9/contents ] and the Mental Capacity Act (Northern Ireland) 2016 [ https://www.legislation.gov.uk/nia/2016/18/contents ], 'Enduring Power of Attorney' (EPA) under The Enduring Powers of Attorney (Northern Ireland) Order 1987 [ https://www.legislation.gov.uk/nisi/1987/1627/crossheading/enduring-powers-of-attorney/made ] and 'Continuing Power of Attorney' (CPoA) or 'Welfare Power of Attorney' (WPoA) under the Adults with Incapacity (Scotland) Act 2000 [ https://www.legislation.gov.uk/asp/2000/4/contents ]. There are LPAs (or WPoAs) for health and welfare and LPAs (or CPoAs / EPAs) for property and affairs. Northern Ireland has not adopted the LPA model for health and welfare. Only health and welfare attorneys can make healthcare decisions. LPAs (or equivalent) come into effect only when the person in question loses capacity to make the decision(s) to which the powers of attorney relate. An LPA (or equivalent) must be in a prescribed form and (to be valid) be registered with the Office of the Public Guardian (OPG) in England and Wales, the OPG Scotland or the Office of Care and Protection (OCP) in Northern Ireland. The name and contact details for any appointed attorney should be included in the record. Alternatively, details of any deputy (or equivalent, i.e. guardian in Scotland or controller in Northern Ireland) appointed by court order to make decisions about the person’s property and financial affairs should be recorded where no LPA (or equivalent) is in place. Information such as the document location and the date that the LPA was registered with the OPG /OCP is important to record. Lasting power of attorney for property and financial affairs is included in the Palliative and End of Life Care Information Standard to record if one or more people have been given power to make decisions about a person’s property and financial affairs. |
Label Concept
|
|
Record
|
|
|
Lasting power of attorney for property and financial affairs (or equivalent) flag
|
A coded flag to indicate that the person has a lasting power of attorney for property and financial affairs (or equivalent) in place. |
M | 1…1 |
|
Coded Element
|
SNOMED CT
—
816341000000102 |Has appointed person with property and affairs lasting power of attorney (Mental Capacity Act 2005)|
(Recommended)
|
|
|
|
Person(s) appointed
|
Record of one or more people who have been given power (LPA or equivalent) by the person, when they had capacity, to make decisions about their property and financial affairs should they lose capacity to make those decisions. Also details of any person (deputy or equivalent) appointed by the Court of Protection (or equivalent) to make decisions about the person’s property and financial affairs when they lack capacity. |
R | 0…* |
Where there are multiple appointed attorneys the LPA (or equivalent) itself should be referred to in order to understand how their responsibilities are held, which could be jointly, jointly or severally or jointly for some decisions but jointly and severally for other decisions relating to property and/or financial affairs. |
List
|
|
|
|
|
Name
|
The name of the appointed person. |
M | 1…1 |
|
Person Name
|
|
|
|
|
Relationship
|
The relationship the appointed person has to the person, e.g. father, grandmother, family friend etc. |
R | 0…1 |
|
Coded Element
|
FHIR
—
UKCorePersonRelationshipType
|
|
|
|
Contact details
|
The contact details (UK telephone number) of the appointed person. |
R | 0…1 |
|
String
|
FHIR
—
UK TELEPHONE NUMBER
|
|
|
|
Location of document
|
The location of the lasting power of attorney (LPA or equivalent) for property and affairs. |
R | 0…1 |
|
String
|
|
|
|
|
Advance decision to refuse treatment (ADRT)
|
Details of the person's ADRT status. |
R | 0…1 |
This is a decision to refuse a specific treatment made in advance by a person who has capacity to do so. This decision only applies at a future time when that person lacks capacity to consent to, or refuse, the specified treatment, and provided it remains valid and applicable. This is set out in section 24 (1) of the Mental Capacity Act. Specific rules apply to advance decisions to refuse life-sustaining treatment. A clinician should satisfy themselves that the Advance Decision to Refuse Treatment (ADRT) is valid and that the circumstances that they are dealing with are those envisaged when the person made the ADRT. A valid and applicable ADRT is legally binding. The record should include the location of the legal document. |
Label Concept
|
|
Event.Record
|
|
|
Advance decision to refuse treatment
|
A record of an advance decision to refuse one or more specific types of future treatment, made by a person who had capacity at the time of recording the decision. The decision only applies when the person no longer has the capacity to consent to or refuse the specific treatment being considered. An ADRT must be in writing, signed and witnessed. If the ADRT is refusing life-sustaining treatment it must state specifically that the treatment is refused even if the person’s life is at risk. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Location of document
|
Location of the advance decision to refuse treatment document. |
R | 0…1 |
|
String
|
|
|
|
|
Professional contacts
|
The details of the person’s professional contacts. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section includes current and historic details of health and care professionals, teams or organisations involved in the care of the person. Third sector organisations can be included. The name of the person’s current care coordinator or key worker should be included here. For people with palliative and end of life care needs it is important to record professionals involved in the care of the person and involved in decision making. It may be helpful to include any usual working days/hours for the professional/service alongside contact details. |
Label Concept
|
|
|
|
|
Professional contacts record entry
|
This is a professional contacts record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Record
|
|
|
Name
|
The name of the professional with responsibility for the care of the person. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Role
|
The role the professional has in relation to the person e.g. GP, physiotherapist, community nurse, social worker, key worker, care home manager, care coordinator, LA hospital liaison person, care home contact, hospital clinician, Independent Mental Capacity Advocate (IMCA) etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Key worker
|
A flag that identifies the professional contact is the key worker assigned to the person. |
R | 0…1 |
|
Coded Element
|
FHIR
—
Hl7VSYesNoIndicator
|
|
|
|
Speciality
|
The specialty of the professional e.g. physiotherapy, oncology, mental health etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
ACTIVITY TREATMENT FUNCTION CODE
|
|
|
|
Team
|
The name of the team. |
R | 0…1 |
|
Text
|
|
|
|
|
Organisation details
|
The details of the organisation providing the service. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Organisation name
|
The name of the organisation providing the service. |
R | 0…1 |
PRSB recommends use of Organisation Data Service (ODS) codes to retrieve organisation names, where available. |
Organisation Name
|
|
|
|
|
Organisation identifier
|
The Organisation Data Service (ODS) code (unique identifier) for the organisation providing the service. |
R | 0…1 |
Implementers are advised to review the key documents maintained and published by the ODS [ https://digital.nhs.uk/services/organisation-data-service ] including about the Data Search and Export Service [ https://digital.nhs.uk/services/organisation-data-service/data-search-and-export ] and FHIR R4 implementation guide [ https://simplifier.net/guide/organisation-data-services/Home?version=1.2.0-beta ]. |
Identifier
|
NHS Data Dictionary
—
ORGANISATION IDENTIFIER
(Recommended)
|
|
|
|
Contact details
|
Contact details of the professional (e.g. telephone number, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Start date
|
The start date of the professional relationship with the person. |
R | 0…1 |
|
Date Time
|
|
|
|
|
End date
|
The end date of the professional relationship with the person. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Personal contacts
|
The details of the individual's personal contacts. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section includes the personal contacts (e.g. family, friends, relatives etc). Comments should be used to share information such as if a particular contact should be called in an emergency etc. For people with palliative and end of life care needs, it is important to record all care givers and family members important to decision making and those who are advocates for the person, if this is what the person would like. All contact information including emergency contact details should be recorded. This is particularly important where a person is the nominated Lasting Power of Attorney. |
Label Concept
|
|
|
|
|
Personal contacts record entry
|
This is a personal contacts record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Record
|
|
|
Name
|
The name of the personal contact. |
M | 1…1 |
|
Person Name
|
|
|
|
|
Relationship
|
The relationship the personal contact has to the person, e.g. father, grandmother, family friend etc. Includes additional roles the person performs on behalf of the other (e.g. carer, next of kin, emergency contact, dependent, etc.). |
R | 0…* |
|
Coded Element
|
FHIR
—
UKCorePersonRelationshipType
|
|
|
|
Contact details
|
Contact details of the personal contact (e.g. telephone number, address, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Comments
|
Notes on the significance of the personal contact to the person. |
O | 0…1 |
|
Text
|
|
|
|
|
Problem list
|
A summary of the problems that require investigation or treatment. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section allows for all relevant diagnoses, symptoms, conditions, problems and issues. |
Label Concept
|
|
|
|
|
Problem list record entry
|
This is a problem list record entry. There may be 0 to many record entries under problem list. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Problem
|
A condition which needs addressing and so is important for every professional to know about when seeing the person. Problems may include diagnoses, symptoms, and social or behavioural issues |
M | 1…1 |
|
Coded Element
|
|
|
|
|
Onset date
|
A date or estimated date that the problem began. |
R | 0…1 |
|
Date Time
|
|
|
|
|
End Date
|
The date or estimated date the problem was resolved. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Stage of disease
|
The stage of the disease where relevant. |
R | 0…1 |
|
Text
|
|
|
|
|
Comment
|
Supporting text may be given covering the problem. |
R | 0…1 |
|
Text
|
|
|
|
|
Primary palliative care diagnosis
|
Details of the primary palliative care diagnosis. |
R | 0…1 |
Primary Palliative Care Diagnosis is the principal diagnosis that is contributing to a person’s need for palliative care or is the key contributor to their end-of-life prognosis. There may be other comorbidities but identifying the primary palliative care diagnosis could support clinician decision making in an emergency situation so that appropriate care and intervention can be provided. Primary Palliative Care Diagnosis is likely to be one of the problems already recorded in the record. So, as such this is not a new entry, but effectively ‘identifying’ a diagnosis already recorded to have this status. When implementing the Palliative and End of Life Care Information Standard it is expected that the ‘primary palliative care diagnosis’ is tagged or highlighted from the list of problems already included in a shared care record. A new SNOMED CT concept for this purpose is not required. |
Label Concept
|
|
|
|
|
Primary palliative care diagnosis record entry
|
This is primary palliative care diagnosis record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…1 |
|
|
|
Event.Record
|
|
|
Primary palliative care diagnosis
|
The primary end of life problem for the person. |
M | 1…1 |
|
Coded Element
|
|
|
|
|
Description of palliative care diagnosis
|
Further details may be included on the person's palliative or end of life diagnosis. |
R | 0…1 |
|
Text
|
|
|
|
|
Social context
|
The social setting in which the person lives, such as their household, occupational history, and lifestyle factors. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . |
Label Concept
|
|
|
|
|
Accommodation status
|
Details of the type of accommodation where the person lives. |
R | 0…1 |
Accommodation status is an indication of the type of accommodation that a person normally lives in, including if they are homeless, in prison or do not have a home address. It may change and can be updated when this changes or whenever the care plan is reviewed. It has been highlighted for specific inclusion in the Palliative and End of Life Care Information Standard to help distinguish people who live in a communal setting such as a nursing home or those who are homeless, thus enabling comparisons in end-of-life care and interventions for different people and ensuring equity of access and quality of care. |
Label Concept
|
|
Event.Record
|
|
|
Accommodation status
|
An indication of the type of accommodation where the person lives. This should be based on the main or permanent residence. |
M | 1…1 |
|
Coded Element
|
NHS Data Dictionary
—
ACCOMMODATION STATUS CODE
|
|
|
|
Allergies and adverse reactions
|
Allergies and adverse reactions. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . FHIR R4 UK Core has used the PRSB model for allergies to define the structure of the FHIR message, which transfers allergy/intolerance information. Implementers are advised to review the key documents and further information in the current release of DAPB4013: Medicine and Allergy/Intolerance Data Transfer [ https://digital.nhs.uk/data-and-information/information-standards/governance/latest-activity/standards-and-collections/dapb4013-medicine-and-allergy-intolerance-data-transfer/ ] A record should be provided of all allergic and adverse reactions relevant to the person. Coded information on causative agents is important to healthcare professionals to enable safe prescribing of medications. Guidance on good practice recording of allergies and adverse reactions is provided by NICE [ https://www.nice.org.uk/guidance/CG183/chapter/1-Recommendations ]. |
Label Concept
|
|
|
|
|
Allergies and adverse reactions record entry
|
This is an allergies and adverse reactions record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Type of reaction
|
The type of reaction experienced by the person (allergic, adverse, intolerance). |
R | 0…1 |
|
Coded Element
|
FHIR
—
AllergyIntoleranceType
|
|
|
|
Causative agent
|
The agent such as food, drug or substances that has caused or may cause an allergy, intolerance or adverse reaction in this person or “No known drug allergies or adverse reactions” or “Information not available”. |
M | 1…1 |
|
Coded Element
|
DM&D
—
Any code from the VTM, VMP, AMP, VMPP, AMPP and ingredient concept classes.
SNOMED CT
—
<105590001 |Substance| OR <373873005 |Pharmaceutical / biologic product| OR <<716186003 |No known allergy| OR 196461000000101 |Transfer-degraded drug allergy| OR 196471000000108 |Transfer-degraded non-drug allergy|
|
|
|
|
Reaction details cluster
|
Details of the reaction. |
R | 0…* |
|
List
|
|
|
|
|
Substance
|
The substance, or a class of substances, that is considered to be responsible for the adverse reaction. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
<105590001 |Substance| or <373873005 |Pharmaceutical / biologic product|
|
|
|
|
Description of reaction
|
A description of the manifestation of the allergic or adverse reaction experienced by the person. For example, skin rash. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Onset date
|
Date and time when manifestations showed e.g could be at home a few days earlier than the contact. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Severity
|
The severity of the reaction. |
R | 0…1 |
|
Coded Element
|
FHIR
—
AllergyIntoleranceSeverity
|
|
|
|
Certainty
|
The certainty that the stated causative agent caused the allergic or adverse reaction. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Route of exposure
|
The route by which the person was exposed to the substance. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Comment
|
Any additional comment or clarification about the adverse reaction. |
O | 0…1 |
|
Text
|
|
|
|
|
Evidence
|
Results of investigations that confirmed the certainty of the diagnosis. Examples might include results of skin prick allergy tests. |
R | 0…1 |
|
Text
|
|
|
|
|
Date first experienced
|
When the reaction was first experienced i.e. this may not be the first time this has happened. May be a date or partial date (e.g. year) or text (e.g. during childhood). |
R | 0…1 |
|
Date Time
|
|
|
|
|
Allergy end date
|
The date the allergy was diagnosed as ended. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Comment
|
Any further comments on the person's allergies or adverse reactions. |
O | 0…1 |
|
Text
|
|
|
|
|
Medications and medical devices
|
Medications and medical devices. |
R | 0…1 |
This section is currently under review to ensure alignment with DAPB4013: Medicine and Allergy/Intolerance Data Transfer. Any further additions or updates will be included in the Core Information Standard v3 major release and next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . Implementers are advised to review the key documents and further information in the current releases of DAPB4013: Medicine and Allergy/Intolerance Data Transfer [ https://digital.nhs.uk/data-and-information/information-standards/governance/latest-activity/standards-and-collections/dapb4013-medicine-and-allergy-intolerance-data-transfer/ ] and Implementation guide for interoperable medicines [ https://simplifier.net/guide/ukcoreimplementationguideformedicines/home?version=current ]. The medications section allows for using structured dose and timing information that is machine readable to facilitate the reading and transfer of medications information between systems and providers of care, through the structured dose direction cluster. |
Label Concept
|
|
|
|
|
Medication item entry
|
All medications and devices that have been issued to be entered via this Medication item entry. Handles details of continuation / addition / amendment of admission medications. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Medication item cluster
|
Medication item cluster. |
R | 0…1 |
|
Label Concept
|
|
Event.Record
|
|
|
Medication name
|
May be generic name or brand name. |
R | 0…1 |
|
Coded Element
|
DM&D
—
Any code from the VTM, VMP, AMP, VMPP and AMPP concept classes.
|
|
|
|
Form
|
The form of the medication e.g. capsule, drops, tablet, lotion etc. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Route
|
The route by which the medication is administered e.g. oral, IM, IV. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Site
|
The anatomical site at which the medication is to be administered. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Method
|
The technique or method by which the medication is to be administered. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Over the counter medication flag
|
Indicates if the medication or device is acquired without a prescription i.e. got by the person over the counter. |
R | 0…1 |
|
Coded Element
|
FHIR
—
Hl7VSYesNoIndicator
|
|
|
|
Structured dose direction cluster
|
A structural representation of the elements carried by the dose syntax in 'parsable dose strength / timing' i.e. dose strength, dose timing, dose duration and maximum dose. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Structured dose amount
|
A structural representation of dose amount, e.g. 20mg or 2 tablets. This element will generally only be used when persisting data within systems with 'parsable dose directions' being used to exchange the same information between systems. As per FHIR Dose Syntax Implementation Guidance (NHS Digital). https://simplifier.net/guide/ukcoreimplementationguideformedicines/home?version=current |
R | 0…1 |
|
Quantity
|
|
|
|
|
Structured dose timing
|
A slot containing a structural, computable representation of dose timing and maximum dose. This element will generally only be used when persisting data within systems with 'parsable dose directions' being used to exchange the same information between systems. As per FHIR Dose Syntax Implementation Guidance (NHS Digital): https://simplifier.net/guide/ukcoreimplementationguideformedicines/home?version=current |
R | 0…1 |
|
General Timing Specification
|
|
|
|
|
Dose duration direction
|
Recommendation of the time period for which the medication should be continued, As per FHIR Dose Syntax Implementation Guidance (NHS Digital): https://simplifier.net/guide/ukcoreimplementationguideformedicines/home?version=current |
R | 0…1 |
Direction not to discontinue should be recorded using additional instructions. |
General Timing Specification
|
|
|
|
|
Dose directions description
|
Describes the entire medication dosage and administration directions including dose quantity and medication frequency and optionally duration e.g. “1 tablet at night" or “2mg at 10pm”. |
R | 0…1 |
|
String
|
|
|
|
|
Additional instructions
|
Allows for: requirements for adherence support, e.g. compliance aids, prompts and packaging requirements, additional information about specific medicines e.g. where specific brand required, person requirements, e.g. unable to swallow tablets. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Course details cluster
|
Details of the overall course of medication. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Course status
|
The status of this prescription. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Indication
|
Reason for medication being prescribed, where known. |
R | 0…1 |
|
Text
|
|
|
|
|
Start date/time
|
The date and/or time that the medication course should begin. |
R | 0…1 |
|
Date Time
|
|
|
|
|
End date/time
|
The date and/or time that the medication course should finish. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Link to indication record
|
A link to the record which contains the indication for this medication order. |
R | 0…1 |
|
String
|
|
|
|
|
Comment/recommendation
|
Suggestions about duration and/or review, ongoing monitoring requirements, advice on starting, discontinuing or changing medication. Additional comment or recommendation about the medication course e.g. 'Patient named supply', 'unlicensed medication', 'Foreign brand' or monitoring recommendations. |
R | 0…1 |
|
Text
|
|
|
|
|
Medication change summary cluster
|
Records the changes made to medication. |
R | 0…1 |
|
Label Concept
|
|
Event.Record
|
|
|
Status
|
The nature of any change made to the medication. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Indication
|
Reason for change in medication, e.g. sub-therapeutic dose, person intolerant. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Date of change
|
The date of the change - addition, or amendment. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Description of amendment
|
Where a change is made to the medication i.e. one drug stopped and another started or eg dose, frequency or route is changed. |
R | 0…1 |
|
Text
|
|
|
|
|
Total dose daily quantity
|
The total daily dose of this medication. This is helpful for estimating optimal adherence to dosing guidance. It may be computed from product/dose strength and frequency or entered manually. |
R | 0…1 |
|
String
|
|
|
|
|
Medical devices entry
|
Medical devices. |
R | 0…* |
|
List
|
|
Record
|
|
|
Medical device
|
Any medical device that isn't prescribed. |
R | 0…1 |
|
Text
|
|
|
|
|
Comments
|
Any information regarding the medical device. |
R | 0…1 |
|
Text
|
|
|
|
|
Medication discontinued entry
|
Medication discontinued entry. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Name of discontinued medication
|
The name of the medication or medical device being discontinued. |
R | 0…1 |
|
Coded Element
|
DM&D
—
Any code from the VTM, VMP, AMP, VMPP and AMPP concept classes.
|
|
|
|
Status
|
The status of any change made to the medication. MUST CONTAIN STOPPED. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Indication
|
The clinical indication for any changes in medication status. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Date of change
|
The date of the discontinuation. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Comment
|
Any additional comment about the discontinuation or amendment. |
R | 0…1 |
|
Text
|
|
|
|
|
Care and support plan
|
This records the decisions reached during conversation between the individual and health and care professional about future plans and also records progress. |
R | 0…1 |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . The personalised care and support plan is a digital record, which is intended to be used to support a person’s care. The record should be available across disciplines, different providers and health and care professionals. It should support integrated communication and care packages so that referrals between different professionals can be mapped and any advice, recommendations or treatment plans can be supported by all those who see the individual. The personalised care and support plan includes the person’s priorities at the time and is not a detailed record of the person’s care needs. It should not be confused with the person’s integrated shared care record (also called integrated digital care record), which will hold the demographic and care delivery information. It is anticipated that there will be a single care and support plan for a person. Linked to this there can be multiple additional supporting plans (that may be for a specific condition e.g., dementia or asthma). There may also be multiple contingency plans. See the detailed guidance in the Personalised Care and Support Plan Standard for further information. PRSB recommends that a person requiring palliative care or end of life care, develops and shares a personalised care and support plan. This will support a person’s palliative care and end of life care when they are approaching the end of their life. However, if a person does not have a personalised care and support plan at the time of being identified as likely to be in their last year of life, the focus should be on discussion and recording of information specific to the Palliative and End of Life Care Information Standard as well as other key relevant information in the sections on About Me, legal information, advance statement, etc. |
Label Concept
|
|
Event.Record
|
|
|
Strengths
|
Any strengths and assets the person has relating to their goals and hopes about their health and well-being. |
R | 0…* |
|
Coded Element
|
|
|
|
|
Needs, concerns or problems
|
Details of the person needs, concerns or problems. |
R | 0…* |
|
Coded Element
|
|
|
|
|
Goals and hopes
|
The overall goals, hopes, aims or targets that the person has. Including anything that the person wants to achieve that relates to their future health and wellbeing. Each goal may include a description of why it is important to the person. Goals may also be ranked in order of importance or priority to the person. |
R | 0…* |
|
Coded Element
|
SNOMED CT
—
^999002111000000103 |Occupational therapy goals simple reference set|
(Example)
SNOMED CT
—
^999002931000000108 |Podiatric goals simple reference set|
(Example)
SNOMED CT
—
^991171000000107 |Speech and language therapy goals simple reference set|
(Example)
SNOMED CT
—
413350009|Finding with explicit context|: 246090004|Associated finding|=300798006 |Able to participate in sporting activities (finding)|, 408729009|Finding context|=410518001|Goal|
(Example)
|
|
|
|
Goal importance score
|
Assessment of the person's motivations to achieve this goal, how important the goal is to the person on a scale of 1-10. |
R | 0…1 |
|
String
|
|
|
|
|
Actions and activities
|
Actions or activities the person or others plan to take to achieve the person's goals and the resources required to do this. |
R | 0…* |
|
List
|
|
|
|
|
What
|
What the action is and how it is to be carried out? |
R | 0…* |
|
Coded Element
|
SNOMED CT
—
<<71388002 |Procedure| OR <<129125009 |Procedure with explicit context|
|
|
|
|
Who
|
Name and role (e.g. person, carer, GP, OT, etc.) of the person, or a team, carrying out the proposed action, and, if relevant where action should take place. |
R | 0…* |
|
List
|
|
|
|
|
Name
|
The name of the professional or person carrying out the proposed action. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Role
|
The role of the person providing the service. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Team
|
The name of the team. |
R | 0…1 |
|
Text
|
|
|
|
|
Contact details
|
Contact details of the professional (e.g. telephone number, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
When
|
Planned date, time, or interval, as relevant. |
R | 0…1 |
|
General Timing Specification
|
|
|
|
|
Suggested strategies
|
Suggested strategies for potential problems. |
R | 0…1 |
|
Text
|
|
|
|
|
Status
|
The status of the action or activity e.g. in progress, done, refused. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Confidence
|
How confident the person feels to carry out the action associated to the goal. |
R | 0…1 |
|
String
|
|
|
|
|
Date last updated
|
Date when action/activity record was last updated. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Review date
|
When the action evaluation needs to be reviewed. SNOMED CT tag : - 425268008 |Review of care plan|. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Stage goal
|
Details of the person's stage goals. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Stage goal
|
A specific sub-goal that is related to the overall goal as agreed by the person in collaboration with a professional. |
R | 0…* |
|
Coded Element
|
SNOMED CT
—
413350009|Finding with explicit context|: 246090004|Associated finding|=300798006 |Able to participate in sporting activities (finding)|, 408729009|Finding context|=410518001|Goal|
(Example)
PLACEHOLDER
—
|
|
|
|
Outcome
|
The outcome of the stage goal. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Goal status
|
The status associated with the person's stage goal. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Outcomes
|
Outcomes of each of the person’s goals, aims and targets. Includes comments recorded by the person, date and status. |
R | 0…* |
|
Coded Element
|
|
|
|
|
Goal status
|
The status associated with the person's overall goal. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Agreed with person or legitimate representative
|
Indicates whether the plan was discussed and agreed with the person or legitimate representative. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Person or legitimate representative
|
Indicates whether the plan was discussed and agreed with the person or legitimate representative. |
R | 0…1 |
|
String
|
|
|
|
|
Person full name
|
The full name of the person in text representation. |
R | 0…1 |
|
Person Name
|
NHS Data Dictionary
—
PERSON FULL NAME
|
|
|
|
Role
|
The role the professional has in relation to the person. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Care funding source
|
A reference to the funding source and any conditions or limitations associated. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
ORGANISATION CODE
|
|
|
|
Date this plan was last updated
|
This is a record of the date that this care and support plan was last updated. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Other care planning documents
|
Reference other care planning documents, including the type, location and date.
This may include condition-specific plans, advance care plans, end of life care plan, etc. |
R | 0…1 |
|
Text
|
|
|
|
|
Planned review date/interval
|
This is the date/interval when this information will next be reviewed. SNOMED CT tag : - 425268008 |Review of care plan|. |
R | 0…1 |
|
General Timing Specification
|
|
|
|
|
Responsibility for review
|
This is a record of who has responsibility for arranging review of this information. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Name
|
The name of the professional with responsibility for the care of the person. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Role
|
The role the professional has in relation to the person e.g. GP, physiotherapist, community nurse, social worker, key worker, care home manager, care coordinator, LA hospital liaison person, care home contact, hospital clinician, Independent Mental Capacity Advocate (IMCA) etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Contact details
|
Contact details of the professional (e.g. telephone number, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Contingency plans
|
These are the things to do and people to contact, should an individual’s health or other circumstances get worse. |
R | 0…* |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section includes contingency/crisis plans for those people who have specific and predictable risks associated with their health and wellbeing. It describes how disruptions to the care and support plan should be addressed. A contingency plan sets out what should be done if the person’s condition or other circumstances get worse. Not everyone who has a care and support plan will need a contingency/crisis plan. It is, however, widely used in mental health. See the detailed guidance in the Personalised Care and Support Plan Standard for further information. If a person has a contingency plan (for any health condition) and is then recognised as requiring palliative or end of life care they may record a specific advance care plan for end of life while continuing to maintain their contingency plan for the health issue that was originally identified as requiring a contingency care planning. Details of a person’s healthcare plans should be available as part of a person’s healthcare record and shared as part of their shared care record. |
List
|
|
Event.Record
|
|
|
Trigger factors
|
Signs to watch out for that may indicate a significant change in health or other circumstances. These could include physical health conditions, environmental factors, or mental health problems, (e.g. feeling anxious). |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Contingency plan name
|
The name of the contingency plan. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
What should happen
|
Guidance on specific actions or interventions that may be required or should be avoided in specific situations. This may include circumstances where action needs to be taken if a carer is unable to care for the person. A statement of suggested actions. Usually expressed as: in the event of X do Y. |
R | 0…* |
|
Coded Element
|
SNOMED CT
—
<<71388002 |Procedure| OR <<129125009 |Procedure with explicit context|
|
|
|
|
Who should be contacted
|
Who should be contacted in the event of significant problems or deterioration in health or wellbeing. e.g. name, role and contact details. |
R | 0…* |
|
List
|
|
|
|
|
Name
|
The name of the professional with responsibility for the care of the person. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Role
|
The role the professional has in relation to the person e.g. GP, physiotherapist, community nurse, social worker, key worker, care home manager, care coordinator, LA hospital liaison person, care home contact, hospital clinician, Independent Mental Capacity Advocate (IMCA) etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Contact details
|
Contact details of the personal contact (e.g. telephone number, address, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Agreed with person or legitimate representative
|
Indicates whether the plan was discussed and agreed with the person or legitimate representative. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Person or legitimate representative
|
Indicates whether the plan was discussed and agreed with the person or legitimate representative. |
R | 0…1 |
|
String
|
|
|
|
|
Person full name
|
The full name of the person in text representation. |
R | 0…1 |
|
Person Name
|
NHS Data Dictionary
—
PERSON FULL NAME
|
|
|
|
Role
|
The role the professional has in relation to the person. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Date this plan was last updated
|
The date that this contingency plan was last updated. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Planned review date/interval
|
This is the date/interval when this contingency plan will next be reviewed. SNOMED CT tag : - 425268008 | Review of care plan| |
R | 0…1 |
|
General Timing Specification
|
|
|
|
|
Responsibility for review
|
This is who has responsibility for arranging review of this information. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Name
|
The name of the professional with responsibility for the care of the person. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Role
|
The role the professional has in relation to the person e.g. GP, physiotherapist, community nurse, social worker, key worker, care home manager, care coordinator, LA hospital liaison person, care home contact, hospital clinician, Independent Mental Capacity Advocate (IMCA) etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Contact details
|
Contact details of the professional (e.g. telephone number, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Coping strategies
|
Details of coping strategies used. |
R | 0…* |
|
List
|
|
|
|
|
Coping strategy
|
The coping strategies are defined as thoughts and behaviours that people use to manage the internal and external demands of situations that are appraised as stressful. This should also include a record of any tools used to carry out the coping strategy. |
R | 0…1 |
|
Text
|
|
|
|
|
Start date
|
The date when the coping strategy started. |
R | 0…1 |
|
Date Time
|
|
|
|
|
End date
|
The date when the coping strategy ended. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Relapse indicators / early warning signs
|
Details of the relapse indicators for the person. These may also be called 'early warning signs'. |
R | 0…* |
|
Coded Element
|
|
|
|
|
Anticipatory medicines/equipment
|
Medicines or equipment available that may be required in specific situations and their location. A statement regarding the availability or location of the anticipatory medicines/equipment. SNOMED CT Tag : - 871021000000106 |Prescription of palliative care anticipatory medication|. |
R | 0…1 |
|
Text
|
|
|
|
|
Additional support plans
|
Additional support plans. |
R | 0…* |
This section is currently under review for inclusion in the Core Information Standard v3 major release. Any further additions or updates will be included in the next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . This section includes additional supporting plans, which may be linked to an end of life care plan. Examples of additional supporting plans include: a mental health plan. a nutrition plan, a falls prevention plan, a hospital or other service transfer of care plan etc. See the detailed guidance in the Personalised Care and Support Plan Standard for further information. |
List
|
|
Event.Record
|
|
|
Additional support plan name
|
The name of the particular additional supporting plan, e.g. dietitian's plan, wound management plan, discharge management plan and behaviour support plan. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Additional support plan content
|
This is the content of any additional care and support plan, which the person and/or care professional consider should be shared with others providing care and support. May be structured in different ways, e.g. tables, diagrams, images. This is the content of any additional care and support plan, which the individual and/or care professional consider should be shared with others providing care and support. It should be structured as recommended for the care and support plan and if contains additional detail, it may be referenced here. |
R | 0…1 |
|
Text
|
|
|
|
|
Planned review date/interval
|
This is the date/interval when this information will next be reviewed. SNOMED CT tag : - 425268008 | Review of care plan|. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Responsibility for review
|
This is a record of who has responsibility for arranging review of this information. Should include their name, role and contact details. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Name
|
The name of the professional with responsibility for the care of the person. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Role
|
The role the professional has in relation to the person e.g. GP, physiotherapist, community nurse, social worker, key worker, care home manager, care coordinator, LA hospital liaison person, care home contact, hospital clinician, Independent Mental Capacity Advocate (IMCA) etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Contact details
|
Contact details of the professional (e.g. telephone number, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Date this plan was last updated
|
This is a record of the date that this information was last updated. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Advance statement
|
Written requests and preferences made by a person with capacity conveying their wishes, beliefs and values for their future care should they lose capacity. |
R | 0…1 |
An Advance Statement is recorded in the section on contingency planning and should be drawn upon if and when someone loses their mental capacity. It may be created as an outcome of an advance care planning conversation and should be recorded as part of the Palliative and End of Life Care Information Standard. It contains written statements (either written down by the person themselves or written down for them with their agreement) the person might make before losing capacity about their wishes and feelings (Mental Capacity Act Code of Practice 2007, P291) regarding issues they wish to be considered in the case of future loss of capacity due to illness, such as the type of medical treatment they would want or not want, where they would prefer to live or how they wish to be cared for. It is not binding but allows professionals to view and acknowledge a person’s advance wishes around their care, and to use this information to guide their decision making. |
Label Concept
|
|
|
|
|
Advance statement record entry
|
This is an advance statement record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…1 |
|
Label Concept
|
|
Record
|
|
|
Advance statement
|
Whether the person has an advance statement. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Location of document
|
The location of where the advanced statement is held. |
R | 0…1 |
|
String
|
|
|
|
|
Palliative and end of life care
|
Information relating to palliative and end of life care. N.B. This is not an end of life care plan or a palliative care plan but contains information that would be found in an end of life care or palliative care plan. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Involvement in advance care planning
|
Details of the person's, their family's or carer's involvement in advance care planning. |
R | 0…* |
Advance care planning (ACP) is a voluntary process of person-centred discussion between an individual and their care providers about their preferences and priorities for their future care. ACP conversations are relevant for any individual who wishes to plan for their future care but should be offered to all patients considered to be approaching the end of life (last year of life). People may have different levels of preparedness for these conversations. Some may not yet have a clear idea of what matters to them for their future care. Some may not wish to discuss their future care and treatment, and this must be respected and clearly recorded. This can sensitively be revisited at a later stage. Details of the person's, their family’s or carer’s involvement in advance care planning are recorded in this section of the standard using the appropriate data fields, using SNOMED CT concepts or free text where no codes are available. Where more than one person is involved then more than one record is made. The ‘Name ’ of the person involved, their ‘Relationship’ to the patient, their Role’ (if professional) may be recorded here. This allows for the record to reflect that a patient has declined discussion around ACP, including why ACP conversations may be inappropriate at a particular time (e.g. fluctuating capacity). |
List
|
|
Event.Record
|
|
|
Person and personal contacts involved in advance care planning
|
The person, their legitimate representative, family member or carer involved in advance care planning. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
713662007|Discussion about advance care planning| OR 714747005|Discussion about advance care planning declined| OR 714361002|Discussion about advance care planning with carer| OR 713665009|Discussion about advance care planning with family member| OR 922321000000108|Discussion about advance care planning not appropriate at this time|
|
|
|
|
Name
|
The name of the personal contact. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Relationship
|
The relationship the personal contact has to the person, e.g. father, grandmother, family friend etc. Includes additional roles the person performs on behalf of the other (e.g. carer, next of kin, emergency contact, dependent, etc.). |
R | 0…* |
|
Coded Element
|
FHIR
—
UKCorePersonRelationshipType
|
|
|
|
Role
|
The role of the person involved in advance care planning. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
JOB ROLE CODE
|
|
|
|
End of life care plans
|
Details of a person's palliative and end of life care plans. |
R | 0…* |
The following plans: Advance Care Plan, Treatment Escalation Plan, Emergency Care and Treatment Plan, Recommended Summary Plan for Emergency Care and Treatment (ReSPECT) are included as part of the Palliative and End of Life Care Information Standard. This is not an exhaustive list and localities may choose to add other tools in use. Paper based versions of end of life care plans may be added to the clinical record as a separate document but it is recommended that services use SNOMED CT concepts to support information sharing between IT systems and to inform professionals of their existence. The advance care planning process is likely to involve a number of conversations over a period of time and plans may be revised and updated by different members of the multi professional team. Care must be taken to ensure that the record is reviewed and updated in a timely manner. Advance Care Plan It is important to specifically record that an individual has an advance care plan with the date the plan was created, any review date and if a particular individual has responsibility for the review, including their name, role, and contact details. The ‘Plan contents’ field can be used to record specific details or other supporting information about a person’s advance care plan. ‘Plan last updated’ should include the date the plan was created or last edited. ‘Planned review date’ should record the next date for review of the plan (if appropriate). The data item ‘Responsibility for review’ includes details of the person with responsibility for reviewing the plan, their ‘Role’, ‘Grade’, ‘Specialty’, ‘Organisation’ and ‘Contact details’. Treatment Escalation plan (ceilings of treatment) Treatment escalation planning is a clinician-led process, which is helpful when a person with serious illness has the potential for acute deterioration or may be coming towards the end of their life. It provides the opportunity for the clinician to agree a plan with the person, or if they lack capacity, with their Lasting Power of Attorney, advocate and those important to them, to guide decision making about what treatments the person would receive should their condition deteriorate. The ‘Plan name’ is “Treatment Escalation Plan” with equivalent SNOMED CT concept recorded. In the ‘Plan contents’ field it is possible to record details on the ceilings of treatment and associated actions or give a brief description of the plan and if it is an attached document. Other items ‘Plan last updated’, ‘Planned review date’ and ‘Responsibility for review’ are as described under ‘Advance Care Plan’ above. Emergency Care and Treatment Plan (for palliative or end of life care) Emergency Care and Treatment Plans can take the form of ‘in the event of X happening do Y’. The information may be particularly useful for professionals called in an emergency or due to sudden change in the condition of a patient e.g. a paramedic or Out of Hours GP where full access to the patient record may be limited. The plan may include guidance on specific interventions or actions that may be required or should be avoided in specific situations that may arise as a person’s illness progresses, e.g. seizures, bleeding, etc. Priorities of care are expressed by the person who has capacity. Their priorities may include treatments that may prolong life or treatments to achieve a balance between getting better and ensuring good quality of life or treatments aimed at symptom control and providing comfort. The ‘Plan name’ is “Emergency Care and Treatment Plan” with equivalent SNOMED CT concept recorded. In the ‘Plan contents’ field it is possible to record priorities of care, anticipatory actions and more details about emergency treatment and care. Other items ‘Plan last updated’, ‘Planned review date’ and ‘Responsibility for review’ are as described under ‘Advance Care Plan’ above. Recommended Summary Plan for Emergency Care and Treatment (ReSPECT) The ReSPECT process creates personalised recommendations for a person’s clinical care and treatment in a future emergency in which they are unable to make or express choices. These recommendations are created through conversations between a person, their families, and their health and care professionals to understand what matters to them and what is realistic in terms of their care and treatment. A ReSPECT plan is created to summarise the recommendations agreed. (resus.org.uk/respect) The ‘Plan name’ is “ReSPECT” with equivalent SNOMED CT concept recorded. If a patient has a ReSPECT plan, record its existence using the ‘Plan name’ and SNOMED CT concept and attach a copy of the document to the clinical record. Record other data items such as ‘Plan last updated’ ,‘Planned review date’ and ‘Responsibility for review’ as described under ‘Advance Care Plan’ above. |
List
|
|
Event.Record
|
|
|
End of life care plan name
|
Type of palliative care or end of life plan, e.g. Advance Care Plan, Treatment Escalation Plan, etc. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
736373009 |End of life care plan| OR 1095081000000100 |End of life advance care plan| OR 735324008 |Treatment escalation plan| OR 887701000000100 |Emergency health care plan| OR 1382601000000107 |Recommended Summary Plan for Emergency Care and Treatment form|
|
|
|
|
Plan contents
|
To record the details of a person's end of life plan. May include a person's wishes and preferences in their Advance Care Plan or a list of ceilings of treatment for Treatment Escalation Plan or priorities of care and anticipatory actions for an Emergency Care and Treatment Plan. |
R | 0…1 |
|
Text
|
|
|
|
|
Planned review date/interval
|
This is the date/interval when the end of life care plan will next be reviewed. |
R | 0…1 |
|
General Timing Specification
|
|
|
|
|
Responsibility for review
|
The professional responsible for reviewing the plan in the future. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Name
|
The name of the professional. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Role
|
The role the professional has in relation to the person e.g. GP, physiotherapist, community nurse, social worker etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Grade
|
The grade of the professional. |
R | 0…1 |
|
String
|
|
|
|
|
Speciality
|
The specialty of the professional e.g. physiotherapy, oncology, mental health etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
ACTIVITY TREATMENT FUNCTION CODE
|
|
|
|
Professional identifier
|
Professional identifier for the professional e.g. GMC number, HCPC number etc or the personal identifier used by the local organisation. |
R | 0…1 |
|
Identifier
|
NHS Data Dictionary
—
PROFESSIONAL REGISTRATION ENTRY IDENTIFIER
|
|
|
|
Organisation details
|
The details of the organisation providing the service. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Organisation name
|
The name of the organisation providing the service. |
R | 0…1 |
PRSB recommends use of Organisation Data Service (ODS) codes to retrieve organisation names, where available. |
Organisation Name
|
|
|
|
|
Organisation identifier
|
The Organisation Data Service (ODS) code (unique identifier) for the organisation providing the service. |
R | 0…1 |
Implementers are advised to review the key documents maintained and published by the ODS [ https://digital.nhs.uk/services/organisation-data-service ] including about the Data Search and Export Service [ https://digital.nhs.uk/services/organisation-data-service/data-search-and-export ] and FHIR R4 implementation guide [ https://simplifier.net/guide/organisation-data-services/Home?version=1.2.0-beta ]. |
Identifier
|
NHS Data Dictionary
—
ORGANISATION IDENTIFIER
(Recommended)
|
|
|
|
Contact details
|
Contact details of the personal contact (e.g. telephone number, address, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Cardio-pulmonary resuscitation (CPR) decision
|
Whether a decision has been made; the decision; who made the decision; the date of decision; date for review and location of documentation. |
R | 0…1 |
A DNACPR decision is an instruction to not attempt cardiopulmonary resuscitation. DNACPR decisions are designed to protect people from unnecessary suffering by receiving CPR that they don’t want, that won’t work or where the harm outweighs the benefits. In many areas decision making may be supported by recognised documentation, which may be included as part of the record. Where a CPR decision is made it is important to record who made the decision, the date of decision, date for review (if appropriate) and location of any documentation. The following information may be recorded as part of the information standard:
Patient records may have information regarding a person’s Cardio-Pulmonary (CPR) decision already recorded when implementing the standard. This information may not conform to the information model and value set defined in the standard. Migration of this data either by data mapping or manually will need to be supported prior to go live. Support for this process is out of scope for the standard. |
Label Concept
|
|
Event.Record
|
|
|
Cardio-pulmonary resuscitation (CPR) decision
|
The cardio-pulmonary resuscitation (CPR) decision. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
450475007|For attempted cardiopulmonary resuscitation| OR 450476008|Not for attempted cardiopulmonary resuscitation|
|
|
|
|
Involvement in CPR Decision
|
Details of the person's, their family's and carer's involvement in the CPR decision. |
R | 0…* |
Whenever possible the CPR decision must be made in consultation with the person. If the person cannot be involved because they are not able to make decisions for themselves, those close to them or their representatives must be involved in discussions to explore the person’s wishes, feelings, beliefs and values in order to reach a ‘best-interests’ decision. Details of the person's, family and carers involvement in the CPR decision are recorded in this section of the standard using the appropriate SNOMED CT concept or free text where no codes are available. Where more than one person is involved then more than one record is made with the appropriate SNOMED CT concepts. |
List
|
|
|
|
|
Person and personal contacts involved in the decision
|
The person, their legitimate representative, family member or carer involved in the CPR decision. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
713079002|Discussion about cardiopulmonary resuscitation| OR 713656002|Discussion about cardiopulmonary resuscitation with family member| OR 1403141000000101|Discussion about cardiopulmonary resuscitation with carer|
|
|
|
|
Name
|
Name of the person involved in the decision. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Relationship
|
The relationship the personal contact has to the person, e.g. father, grandmother, family friend etc. Includes additional roles the person performs on behalf of the other (e.g. carer, next of kin, emergency contact, dependent, etc.). |
R | 0…* |
|
Coded Element
|
FHIR
—
UKCorePersonRelationshipType
|
|
|
|
Role
|
The role of the person involved in the CPR decision. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Date for review
|
The date for review of CPR decision. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Responsibility for review
|
The professional responsible for reviewing the decision. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Name
|
The name of the professional. |
R | 0…1 |
|
Person Name
|
|
|
|
|
Grade
|
The grade of the professional. |
R | 0…1 |
|
String
|
|
|
|
|
Role
|
The role the professional has in relation to the person e.g. GP, physiotherapist, community nurse, social worker etc. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
JOB ROLE CODE
|
|
|
|
Specialty
|
The specialty e.g. physiotherapy, oncology, mental health etc |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
ACTIVITY TREATMENT FUNCTION CODE
|
|
|
|
Organisation details
|
The details of the organisation providing the service. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Organisation name
|
The name of the organisation providing the service. |
R | 0…1 |
PRSB recommends use of Organisation Data Service (ODS) codes to retrieve organisation names, where available. |
Organisation Name
|
|
|
|
|
Organisation identifier
|
The Organisation Data Service (ODS) code (unique identifier) for the organisation providing the service. |
R | 0…1 |
Implementers are advised to review the key documents maintained and published by the ODS [ https://digital.nhs.uk/services/organisation-data-service ] including about the Data Search and Export Service [ https://digital.nhs.uk/services/organisation-data-service/data-search-and-export ] and FHIR R4 implementation guide [ https://simplifier.net/guide/organisation-data-services/Home?version=1.2.0-beta ]. |
Identifier
|
NHS Data Dictionary
—
ORGANISATION IDENTIFIER
(Recommended)
|
|
|
|
Professional identifier
|
Professional identifier for the professional providing the service e.g. General Medical Council (GMC), Nursing Medical Council (NMC) number etc, or the personal identifier used by the local organisation. |
R | 0…1 |
|
Identifier
|
|
|
|
|
Contact details
|
Contact details of the personal contact (e.g. telephone number, address, email address etc.). |
R | 0…1 |
|
Text
|
|
|
|
|
Location of document
|
The location of the CPR decision document. |
R | 0…1 |
|
String
|
|
|
|
|
Estimated prognosis
|
Details of the person's estimated prognosis. |
R | 0…1 |
This allows for the recording of a person’s estimated prognosis. This is a clinical judgment indicating the anticipated period of time until death e.g., last days, last weeks, last months or year or more of life. An estimate of prognosis may support the patient e.g., application for benefits at a higher rate under ‘special rules’ through completion of a DS1500/SR1 form. From July 2025 the SR1 form has replaced the DS1500 form. |
Label Concept
|
|
Event.Record
|
|
|
Estimated prognosis
|
Where a person is terminally ill this is a clinical judgment indicating the anticipated period of time until death e.g. last days, weeks, months or year of life. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
511401000000102|Last days of life| OR 955231000000109|Last weeks of life| OR 968211000000101|Last months of life| OR 767503006|Limited life expectancy of approximately one year| OR 1413121000000106|Limited life expectancy of more than one year|
(Recommended)
SNOMED CT
—
845701000000104|Gold standards framework prognostic indicator stage A (blue) - year plus prognosis| OR 845721000000108|Gold standards framework prognostic indicator stage B (green) - months prognosis| OR 845751000000103|Gold standards framework prognostic indicator stage C (yellow) - weeks prognosis| OR 845771000000107|Gold standards framework prognostic indicator stage D (red) - days prognosis|
(Recommended)
|
|
|
|
Person is on the Palliative Care Register
|
Indicates if the person is on the palliative care register. |
R | 0…1 |
Early identification of people likely to be in their last year(s) of life provides opportunity for honest conversations about what matters to the person and facilitates care for them which is aligned to their needs and preferences. It can support an MDT approach to care that is coordinated between professionals and proactive to meet the changing need of the patient. A palliative care register, commonly used within primary care can be used to identify patients who may be in their last year(s) of life. It is recommended that (where possible) an explanation of this process is provided to the patient and their family/carer. This data item will enable the recording of a SNOMED CT concept indicating that the person is on the palliative care register and thus allow for the sharing of this information with other care providers. |
Coded Element
|
SNOMED CT
—
1403151000000103 |On palliative care register|
|
Record
|
|
|
Anticipatory medicines/equipment
|
Details of the availability or location of the person's anticipatory medicines/equipment. |
R | 0…1 |
Anticipatory prescribing for patients at the end of life is the prescription and dispensing of injectable medications to a named patient in advance of clinical need for administration by suitably trained individuals if symptoms arise in the final days of life. It is promoted to optimise symptom control in community settings to prevent crisis hospital admissions as it ensures rapid access to medications (particularly out of hours when sourcing of medication can be delayed) and enables administration to manage symptoms when needed. Information on the availability and location of the anticipatory medicines and equipment for end-of-life care can be recorded. The data items also allow for the recording of SNOMED CT concepts that indicate there has been an issue and prescription of palliative care anticipatory medicines and equipment. |
Label Concept
|
|
Event.Record
|
|
|
Statement on anticipatory medicines/equipment
|
A statement regarding the availability or location of the anticipatory medicines/equipment. |
R | 0…1 |
|
Text
|
|
|
|
|
Anticipatory medicines and equipment
|
Coded data on the issue of palliative care anticipatory medicines and equipment. |
R | 0…* |
|
Coded Element
|
SNOMED CT
—
376201000000102|Issue of palliative care anticipatory medication box| OR 871021000000106|Prescription of palliative care anticipatory medication|
|
|
|
|
Preferred place of death
|
Details of the person's preferred place of death. |
R | 0…1 |
These data items provide the opportunity to record a person’s preferred place of death. ‘The name of the place’ is a text field that can record the name of preferred place of death. ‘Type of the place’ records the SNOMED CT concept for preferred place of death e.g. home, hospice, hospital. A supporting text field can be used to record any additional information which could include alternative options if the preferred place of death was unavailable or a record of when a person may not have a preference of where they do not want to die. |
Label Concept
|
|
Event.Record
|
|
|
Preferred place of death
|
The preferences that a person has identified as their preferred place to die. |
R | 0…1 |
These data items provide the opportunity to record a person’s preferred place of death. ‘The name of the place’ is a text field that can record the name of preferred place of death. ‘Type of the place’ records the SNOMED CT concept for preferred place of death e.g. home, hospice, hospital. A supporting text field can be used to record any additional information, which could include alternative options if the preferred place of death was unavailable or a record of when a person may not have a preference of where they do not want to die. |
Label Concept
|
|
|
|
|
Name of the place
|
The name of the preferred place of death. |
R | 0…1 |
|
Text
|
|
|
|
|
Type of Place
|
The type of preferred place of death. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Palliative care financial support
|
Details of the financial support forms/claims the clinician has informed the person about or completed on behalf of the person. |
R | 0…1 |
There are special rules for people who are nearing the end of their life that provide fast-track access to certain benefits provided by the Department for Work and Pensions. These data items provide the opportunity to record (using the appropriate SNOMED CT concepts or free text when no codes are available) that the person was informed about their financial entitlements and where claims for financial support have been completed or declined. |
Label Concept
|
|
Event.Record
|
|
|
Type of financial support
|
The forms or claims discussed, completed or declined. |
R | 0…* |
|
Coded Element
|
SNOMED CT
—
871631000000101|Discussion about DS1500 report| OR 768381000000107|DS1500 Disability living allowance report declined| OR 514591000000108|Completion of DS1500 terminal illness medical report|
SNOMED CT
—
1874621000000100|Discussion about SR1 form| OR 1874631000000103|SR1 form declined| OR 1751111000000104|Completion of SR1 form|
(Recommended)
|
|
|
|
After death
|
Details of place and date of death. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Actual place of death
|
The location where the person actually died as recorded on the death certificate. If the person died somewhere other than their preferred place, record the reasons why this happened. |
R | 0…1 |
This is the actual place of death. ‘The name of the place’ is a text field that records the actual place of death. ‘Type of place’ uses SNOMED CT concepts to record the type of place of death. The ‘Type of place’ data item enables a system comparison between preferred place of death and actual place of death. |
Label Concept
|
|
Event.Record
|
|
|
Name of the place
|
The name of the actual place of death. |
R | 0…1 |
|
Text
|
|
|
|
|
Type of place
|
The type of place where the person's death took place. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Date of death
|
The date on which a person died or is officially deemed to have died, as recorded on the death certificate. |
R | 0…1 |
|
Date Time
|
|
Event.Record
|
|
|
Documents (including correspondence, audio and images)
|
Details about documents related to the person. |
R | 0…1 |
This section is currently under review to ensure alignment with EH4001: Clinical Document Indexing Standards v4.8 and the DICOM Standard. Any further additions or updates will be included in the Core Information Standard v3 major release and next minor release of the Palliative and End of Life Care Information Standard. For further information please contact support@theprsb . Implementers are advised to review the current release of EH4001: Clinical Document Indexing Standards v4.8 [ https://www.digihealthcare.scot/app/uploads/2025/04/CDI-Standard-V4.8-FINAL.pdf ] and further information in the Document Indexing Guidance Notes v3.2 [ https://www.digihealthcare.scot/app/uploads/2022/03/CDI-Guidance-v3.2-FINAL.pdf ] and the current release of the DICOM standard [ https://www.dicomstandard.org/current ]. This section includes details of palliative or end of life documents and images. It includes the metadata that is required for the document or image and a link to the actual document or image. When displayed in a record, documents and images should be organised logically in date order. Local implementations will need to determine the best logical groupings for use here. A specific cluster is included for images as these are a special case where there is a document (e.g. a KOS document) with information about the image and often produced by the machine or imaging system, and a specific set of additional information (such as event code list and format code). Note that this document is separate from the investigation report which provides the results or interpretation of the imaging. |
Label Concept
|
|
|
|
|
Documents record entry
|
This is a documents record entry. There may be 0 to many record entries under a section. Each record entry is made up of a number of elements or data items. |
R | 0…* |
|
List
|
|
Event.Record
|
|
|
Documentation location
|
The location of the document. |
R | 0…1 |
|
String
|
|
|
|
|
Confidentiality
|
The code specifying the level of confidentiality of the document. |
R | 0…1 |
|
Coded Element
|
FHIR
—
Confidentiality
|
|
|
|
Class
|
The document type e.g. report, summary, images, treatment plan, patient preferences, workflow. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
Clinical Document Indexing Standard - Document Type
(Recommended)
|
|
|
|
Document title
|
The title of the document. |
O | 0…1 |
|
Text
|
|
|
|
|
Document name
|
The name of the document. This should align to the Clinical Document Indexing standard. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
Clinical Document Indexing Standard - Document Subtype
(Recommended)
DICOM
—
ProcedureCodeSequence
(Example)
|
|
|
|
Document media type
|
Media type of the document. |
R | 0…1 |
|
String
|
IANA Media Types
—
https://www.iana.org/assignments/media-types/media-types.xhtml
|
|
|
|
Service
|
The service that created the document. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Comments
|
Comments associated with the document. |
R | 0…1 |
|
Text
|
|
|
|
|
Additional information required for images.
|
Additional information required for images. |
R | 0…1 |
Implementers are advised to review the release schedule and current release documents for the National Interim Clinical Imaging Procedure (NICIP) Code Set [ https://nhsengland.kahootz.com/t_c_home/view?objectID=45878224 ] |
Label Concept
|
|
|
|
|
Image procedure
|
The procedure used to capture the image. |
R | 0…1 |
|
Coded Element
|
NICIP
—
National Interim Clinical Imaging Procedure (NICIP) Code Set
(Mandatory)
SNOMED CT
—
NICIP to SNOMED CT mapped concepts
(Recommended)
|
|
|
|
Image procedure laterality
|
The laterality of the image procedure. |
R | 0…1 |
|
Coded Element
|
SNOMED CT
—
^999000821000000100 |Laterality simple reference set|
(Recommended)
|
|
|
|
Image procedure date
|
The date and time the image procedure was performed. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Images
|
Images details. |
R | 0…1 |
|
Label Concept
|
|
|
|
|
Image capture date
|
The date and time when the image was captured. |
R | 1…1 |
|
Date Time
|
|
|
|
|
Image ID
|
A unique image identifier generated by the system. |
R | 1…1 |
|
Identifier
|
|
|
|
|
Image location
|
The URL for the image. |
R | 1…1 |
|
String
|
|
|
|
|
Format code
|
The format code of the document that provides information on how to display the document. |
R | 0…1 |
|
String
|
|
|
|
|
Event code list
|
The type of image (acquisition modality) and the anatomical site imaged. |
R | 0…1 |
|
Coded Element
|
|
|
|
|
Comments
|
Comments associated with the imaging. |
R | 0…1 |
|
Text
|
|
|
|