Summary
- Access to records
- Accessibility
- Adult
- Age
- Appointment / scheduling
- Architecture, Models and Frameworks
- Artificial intelligence
- Authentication
- British Standards Institute (BSI)
- Care
- Care records
- Child
- Clinical decision support
- Clinical safety
- Coding
- Continuity of care
- Cyber security
- Data
- Data definitions and terminologies
- Data governance
- Date and Time
- Demographics
- Design
- Digital Imaging
- Dispensing
- Electronic Health Record
- Equality
- European
- Financial management
- Form
- GS1
- Genetic and Genomic
- Good practice
- Government
- Health
- Health Level 7 (HL7)
- Holistic and Traditional
- ISO Technical Committee 215 (ISO/TC 215)
- Information Technology (IT) Infrastructure
- Information codes of practice
- Information governance
- International Standardization Organisation (ISO)
- International Standards
- Interoperability
- Interoperability - Knowledge
- Interoperability - Organisation / Service
- Interoperability - Semantic
- Interoperability - Skills
- Interoperability - Structural
- Interoperability - Syntactic
- Interoperability - Technical
- Key care information
- Learning Health Systems
- Local
- Location
- Medical devices
- Medical products
- Messaging
- Metadata
- Naming and Number
- Open
- Orchestration
- Organisation
- Patient communication
- Personalised Digital Health
- Pharmacy, Medicines and Prescribing
- Product management
- Professional
- Provider
- Public health
- Publicly Available Specification
- Race and Ethnicity
- Record
- Reference data
- Referrals
- Requests, Orders and Observation
- Security, Safety and Privacy
- Service
- Sex and Gender
- Sexual orientation
- Technical Report
- Technical Specification
- Telehealth and Virtual Care
- Tests and diagnostics
- Vaccination
- Web
- Women's health
- Workforce
- Worldwide Web Consortium (W3C)
- Care home
- Social care
Contact Point
Documentation
Document 1
Paragraph 1
Paragraph 2
- Digital Social Care Record (DSCR)
- ISO 13606
- Contsys
- Core Information Standard
- HL7 FHIR UK CORE
- SNOMED CT (UK Edition)
- NHS Data Dictionary
- ISN Approved Collections
- Open Referral
- LGA inform
- SAVVI
- OpenEHR Social Determinants of Health
- OpenEHR Social Context Project
- The Gravity Project - Gravity Project - Confluence
- SNOMED International Social Care Project
///mermaid graph TD accTitle: Classes of information about the person within the MODS will fall into one of the following categories accDescr: Imagine a giant digital folder that holds all of a person’s health information in one place. Inside this folder, information is organized a bit like a nesting doll: big folders contain individual records (like a doctor's visit note), and those notes are broken down into smaller sections and specific entries. Each entry then points to the tiny details, such as a specific test result or a single measurement. The system is designed to handle general details about who the person is alongside these specific health stories, making sure that every piece of information—from a broad summary to a single data point—stays connected and easy for healthcare staff to find. subgraph EHR_EXTRACT DEMOGRAPHIC_DATA[DEMOGRAPHIC DATA] FOLDER[FOLDER] -->|sub_folders| FOLDER FOLDER -.->|compositions| COMPOSITION[COMPOSITION] COMPOSITION -->|content| SECTION[SECTION] COMPOSITION -->|content| ENTRY[ENTRY] SECTION -->|members| SECTION SECTION -->|members| ENTRY ENTRY -->|items| CLUSTER[CLUSTER] ENTRY -->|items| ELEMENT[ELEMENT] CLUSTER -->|parts| CLUSTER CLUSTER -->|parts| ELEMENT ELEMENT -->|value| DATA_VALUE[DATA_VALUE] end
- Explain the Classes of information about the person within the MODS diagram
Imagine a giant digital folder that holds all of a person’s health information in one place. Inside this folder, information is organized a bit like a nesting doll: big folders contain individual records (like a doctor's visit note), and those notes are broken down into smaller sections and specific entries. Each entry then points to the tiny details, such as a specific test result or a single measurement. The system is designed to handle general details about who the person is alongside these specific health stories, making sure that every piece of information—from a broad summary to a single data point—stays connected and easy for healthcare staff to find.
Paragraph 3
Paragraph 4
Paragraph 5
Paragraph 6
Paragraph 7
Paragraph 8
Paragraph 9
Paragraph 10
| As a… | I need… | So that… | MODS data sources | Other data sources |
|---|---|---|---|---|
| Person receiving care | To tell people about my care and support needs (including any changes to what I need) once and once only |
(a) I don't have to keep repeating myself to all the different professionals involved in my life (b) my care and support can adapt to meet my changing needs |
About Me Observations including but not limited to Needs, Risks, Wishes, Preferences, Strengths | |
| Person receiving care | Everyone involved in my care and support to have access to comprehensive and up-to-date information about my care and support needs | I get the right level and type of care and support at the right time |
About Me Observations such as Needs, Risks, Wishes, Preferences, Strengths Problems Medication management Allergies and adverse reactions | |
| Care actor | My involvement as a carer to be included in the Digital Social Care Record | Professionals are aware of the role I play in caring for/supporting the individual, and are able to involve me appropriately throughout the individual's care journey | Carers | |
| Data SME | I need to understand the definitions, formats and processes used to collect data from various organisations and people and ensure that is consistent | I can provide aggregate data that is statistically valid, consistent over time, and fit for a wide range of purposes | ||
| Data SME | Client/person level data to align with existing data sources about individuals, eg PDS, GP Connect | To avoid duplication of records, so that aggregate data gives a more accurate picture across the whole population | MODS |
PDS GP Connect |
| Operational SME (care provider) | My records to be populated with accurate, up-to-date data about health conditions, allergies and adverse reactions, prescriptions, etc from the GP's records; and this data to be updated in real time if it changes |
(a) I can ensure the person receiving care’s day-to-day health needs are being met correctly (b) I don't need to re-create/re-enter data that is already held digitally |
About Me Observations including but not limited to Needs, Risks, Wishes, Preferences, Strengths | GP Connect |
| Operational SME (care provider) | Confidence that I have a legitimate reason to hold/access all the data held within the DSCR/MODS | I am fully compliant with the GDPR | ||
| Operational SME (care provider) | New care and support packages arriving from the local authority to contain as much detail as possible about the individual's care and support needs, health conditions (including cognitive and sensory impairments) and desired outcomes | I don't need to repeat any aspects of the needs assessment process which others have already undertaken |
Observations including but not limited to Needs, Risks, Wishes, Preferences, Strengths |
Care Act eligibility assessment LA care and support plan GP Connect |
| Operational SME (care provider) | New care and support packages arriving from the local authority to include a clear statement of the care and support being commissioned, including time and cost | I can ensure the care and support I provide is in line with the funding available for it |
LA care and support plan LA funding – time and budget | |
| Operational SME (care provider) | To locate data sources about indicators/metrics | I can incorporate data collection needs into my internal working processes as efficiently as possible |
NHS Digital CQC Skills for Care | |
| Operational SME (care provider) | Confidence that the DSCR/MODS is fully aligned with statutory/regulatory requirements | I can be certain that by adopting MODS I am meeting all these requirements | MODS |
Primary and secondary legislation CQC guidance NICE guidance |
| Operational SME (care provider) | To be consulted/informed about changes to statutory requirements, data standards, data gathering requirements, registration requirements etc | I can be fully prepared for changes which will impact on the way I provide care and support and/or capture data | ||
| Operational SME (care provider) | Access to standard national datasets and data standards | I can review/compare them against the data I capture in my own systems | ||
| Operational SME (care provider) | To be notified when someone I provide domiciliary care for is admitted to hospital | I do not have to make unnecessary visits | Hospital systems | |
| Operational SME (health) | Clear and accurate information about the care and support needs of a person with sensory or cognitive impairment, learning disabilities and/or mental health needs when they are admitted to hospital | We can communicate with them effectively and take account of their needs in the way we care for them in hospital |
About Me Observations including but not limited to Needs, Risks, Wishes, Preferences, Strengths Care and support plan Carers | About Me |
| Operational SME (health) | Clear and accurate information about the care and support arrangements available at home when someone is discharged from hospital | We know if it is safe and appropriate to discharge the individual back home |
Care and support plan Carers | |
| Operational SME (social work) | Data from care providers and TEC systems at an appropriate level of detail about the day-to-day care and support provided to an individual and the outcomes being achieved |
(a) Contribute to the annual review of the individual's care and support plan (b) Flag any significant changes in care and support needs (c) Ensure commissioning meets current and future demand |
Instructions Actions Alert Outcome |
TEC data Day-to-day care record Hospital admissions/discharges Changes in care and support needs |
|
Operational SME (social work) Operational SME (care provider) | To record data once in the system, ensure it is complete and accurate, and be confident that it will reach everyone else who needs to see it | To reduce the time pressure of constantly re-entering data and responding to requests for routine information | MODS | |
| System SME (system administrator) | To be consulted/informed about changes to statutory requirements, data standards, data gathering requirements, registration requirements etc | I can be fully prepared for changes which will impact on the way I capture data | ||
| System SME (system supplier) | To locate data sources about indicators/metrics | I can ensure that data is captured correctly to auto-populate the statutory returns required of my clients | MODS | |
| System SME (system supplier) | To locate person-specific data sources | I can create the functionality to import person-specific data from reliable and trustworthy sources to save double-entry and data quality issues |
Data Catalogue PDS GP Connect |
Paragraph 11
Paragraph 12
| As a performance manager I need... | So that... | And ultimately... |
|---|---|---|
| To be able to signpost data providers to a central repository with standardised data definitions and collection methodologies | All the people in my own organisation and external organisations who submit their data to me have consistent definitions and consistent data collection methodologies | I can provide aggregate data that is statistically valid, consistent over time, and fit for a wide range of purposes |
| Access to new data/reporting requirements | I can ensure that our data and recording practices fully reflect the requirements of statutory returns, including the design of new forms/workflow to support new reporting requirements | We can keep better, clearer and more consistent case records, supporting direct care provision, service management and forward planning. |
| Access to agreed definitions | I can provide a meaningful analytical narrative | My organisation's management team can make sense of complex data |
| Access to an agreed information governance and data security framework | I can ensure that the sensitive data I receive is being processed and shared appropriately | My organisation has a holistic and accurate picture of people's health, care and support needs |
| As a data architect I need... | So that... | And ultimately... |
|---|---|---|
| Access to past and present data standards, preferred definitions, collection methodologies and terminology hierarchies | I can understand the capabilities and limitations of existing data collections | I can develop new data standards and specifications which overcome any problems identified within existing approaches |
| A comprehensive glossary of terms used across health and adult social care | I can identify inconsistencies in the definition of terms which may lead to inconsistency in data gathering and/or its interpretation | I can provide a clear set of preferred definitions as part of new data standards and specifications |
| Access to the level of granularity of current datasets | I can identify areas where too little (or too much) detail is currently being recorded | New data specifications can strike the right balance in terms of the granularity of data capture vs the resource required to capture/analyse it and the value which that analysis will offer |
| A publishing platform to share draft and final data standards I develop | I can receive feedback from users | New standards can be widely adopted |
| An agreed conceptual data model | New data standards and specifications can draw on and build on existing standardised approaches | New standards and specifications can be readily implemented |
| Access to an agreed information governance and data security framework | I can be confident that data suppliers will contribute sensitive data to new data models | New data standards and specifications will give a holistic and accurate picture of individuals' health, care and support needs |
| As a business intelligence manager I need... | So that... | And ultimately... |
|---|---|---|
| To be able to signpost data providers to a central repository with standardised data definitions and collection methodologies | All the people/organisations who submit their data to me have consistent definitions and consistent data collection methodologies | I can provide aggregate data that is statistically valid, consistent over time, and fit for a wide range of purposes |
| Visibility of data standards and their relationship to statutory/regulatory requirements (eg Care Act, Equality Act, Mental Health Act, Mental Capacity Act, CASSG, CQC registration requirements, NICE/SCIE/RCOT guidance, etc) | I have confidence that DSCR/MODS data is fully aligned with statutory and regulatory requirements | I can be confident that the data I receive gives evidence that organisations are compliant with their statutory obligations |
| To see details of the data standards in use by providers, local authorities and NHS bodies | I can understand whether data is being provided in a standardised digital format, and if not, what the different data formats comprise | I can quickly and efficiently import data from multiple sources into my modelling tools without the need for extensive manual processing |
| To see details of the personal identifiers used in different data standards/systems | Client/person level data can be aligned with existing data sources about individuals, eg PDS, GP Connect | To avoid duplication of records, so that aggregate data gives a more accurate picture across the whole population |
| Access to an agreed information governance and data security framework | I can be confident that data suppliers will contribute sensitive data to inform integrated reports | My reports will give a holistic and accurate picture of people’s health, care and support needs at both an individual and an aggregated level |
| As a software developer I need... | So that... | And ultimately... |
|---|---|---|
| To be consulted/informed about changes to statutory requirements, data standards, data gathering requirements, registration requirements etc | I can be fully prepared for changes which will impact on the way our system captures and analyses data | We are able to maintain and deliver an efficient roadmap for our product |
| To locate data sources about indicators/metrics | I can ensure that data is captured correctly to auto-populate the indicators and metrics our customers need | Our system provides better business value to our customers |
| To locate person-specific data sources and the data structures they utilise | I can create the functionality to import person-specific data from reliable and trustworthy sources | System users can avoid double-entry and the data quality issues it causes |
| To access the data standards used across the health and adult social care sectors | Our system can be designed for maximum interoperability | Our system can be an effective tool to support a shared care record |
| Access to an agreed information governance and data security framework | I can be confident that our system will handle sensitive data appropriately | Our system will give a holistic and accurate picture of people's health, care and support needs |
| As a business analyst I need... | So that... | And ultimately... |
|---|---|---|
| To identify all the potential functional and non-functional requirements of the new system | The information collected in and generated from the system will be unambiguous, consistent and comprehensive | The system will meet business needs |
| To be aware of all statutory and mandatory data standards, both current and forthcoming | The system can be implemented to meet current and future reporting needs as far as possible | Future development and implementation costs can be reduced and/or delayed |
| To access good practice in data management as evidenced by the data catalogue | The new system can incorporate non-mandatory elements which reflect good practice across the health and adult social care sectors | Ensure there is flexibility for the system to meet specific local information needs |
| To access existing data standards | I can ensure that the new system will be interoperable with others | Reducing the need for manual intervention, double-entry and potential data quality issues |
| Access to an agreed information governance and data security framework | I can ensure that the new system specification will reflect the need to handle sensitive data appropriately | The new system will give a holistic and accurate picture of people's health, care and support needs |
| As a procurement officer I need... | So that... | And ultimately... |
|---|---|---|
| Standardised terminology which I can reference when writing our system specification | I can ensure that both my organisation and all system suppliers have the same understanding of terms used in our procurement documentation | My organisation is exposed to reduced risk in respect of procuring a system that is fully fit for purpose |
| To verify which standards are mandated | I can ensure the systems I am procuring meet statutory reporting requirements | The organisation is exposed to reduced risk in respect of meeting its statutory and regulatory requirements |
| To identify existing data collections and data sources, and the structures/data standards to which they operate | I can identify opportunities for system integration and interoperability | My organisation can secure value for money through streamlined and integrated systems and processes |
| Access to an agreed information governance and data security framework | I can ensure that the new system specification will reflect the need to handle sensitive data appropriately | My organisation is exposed to reduced risk in respect of information governance and data security |
| As a systems integrator I need... | So that... | And ultimately... |
|---|---|---|
| To understand the content and format of different data sources | I can extract the required information from the most appropriate source | I can create a standardised master record |
| To transform data extracted from different sources into a consistent format | Heterogeneous data can be shared across multiple systems | Front line professionals can have a single view of all the information held about an individual |
| Design a target data model into which to load different data sources | I can provide data analysts/data scientists with a common data model | To allow them to interrogate multiple sources |
| To understand the quality and provenance of all my data sources | I can offer data analysts/data scientist, within the common data model, the context of the source data as well as the data itself | Users of the common data model can be clear about the limitations of the data they are accessing |
| Access to an agreed information governance and data security framework | I can ensure that the new system specification reflects the need to handle sensitive data appropriately | The new system will give a holistic and accurate picture of people's health, care and support needs |
Paragraph 13
| Category | Use case | Priority (derived from stakeholder survey) | LA ASC | Care recipients | Carers | Care providers | NHS | PH | C&F | DHSC | Software suppliers |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Individual | Multiple clinicians/professionals/carers involved in an individual's day-to-day life (GP, District Nurse, social worker, care provider, care worker, social prescriber, local authority call handler, others), not operating as part of a multi-disciplinary team, but needing to access clear and accurate records - in a language that bridges the gap between clinical and everyday terminology - and capture/share information to inform ongoing care delivery and to help the person live the life they want to. | 3.97 | Y | Y | Y | Y | Y | ||||
| Individual | Communicating an individual's care needs between local authority and care provider at the point of commissioning | 3.86 | Y | Y | Y | ||||||
| Individual | Hospital admissions/discharge teams understand the care plan already in place and are able to provide the necessary care information to care providers on discharge | 3.86 | Y | Y | Y | Y | Y | ||||
| Individual | Consistency of care to an individual when a temporary worker needs to step in | 3.79 | Y | Y | Y | ||||||
| Individual | Care Home sending information to GP system | 3.21 | Y | Y | Y | ||||||
| Service | Enabling easier implementation of new social care IT systems | 4.00 | Y | Y | Y | ||||||
| Service | Sharing elements of care planning information across many systems – componentisation of care plan | 3.90 | Y | Y | Y | Y | |||||
| Service | As care providers move to digital systems (by 2024?), enable easier transfer of routine info to local authorities | 3.79 | Y | Y | Y | ||||||
| Service | DHSC able to receive management information from all local authorities and care providers which uses agreed, understood and shared terminology | 3.76 | Y | Y | Y | ||||||
| Service | Population Health Management – greater ability to share health and care datasets to gain insights across a place | 3.41 | Y | Y | Y | Y | Y | ||||
| Service | Care providers can interrogate the data they are capturing, rather than just recording it | 3.41 | Y | ||||||||
| Service | Local authorities receiving information from care providers that enables activity (review of needs etc) to be stratified through artificial intelligence | 3.17 | Y | Y |
Paragraph 14
Paragraph 15
Paragraph 16
Paragraph 17
///mermaid
graph TD
accTitle: A visualisation of a conceptual data model for adult social care based on the International Standard EN ISO 13940:2016 and Contsys:2019
accDescr: This diagram shows how different people and groups work together to support someone who needs care. At the heart of it all is the person being looked after, surrounded by the important details that keep them safe, such as their legal rights and their permission for care. A team of professionals—which could be an individual, a small team, or a large organization—uses this information to provide support and make decisions on the person's behalf. By carefully watching and recording what they see (observations), these helpers can figure out the best way to plan the person's care and daily activities. These observations act as a guide: they tell the team what is happening right now and help them decide which actions or plans are needed to help the person live their best life.
subgraph AuditCol [" "]
Audit[Audit
Info.]
end
subgraph Main Model [" "]
subgraph TopActors [" "]
Org[Organisation]
Team[Team]
Person[Person]
end
CareActors[Care Actors]
Subject[Subject of Care]
Obs[Observations]
subgraph LeftInfo [" "]
Legal[Legal Information]
Admin[Administrative Information]
Consent[Consent Information]
end
subgraph RightActions [" "]
Assessments[Assessments]
Plans[Care Plans]
Actions[Instructions
Actions
Activities]
end
Org & Team & Person --> CareActors
CareActors --> |"Supports
Provides Care for
Takes Decisions on Behalf of"| Subject
Subject --> |Refers to| Obs
Legal & Admin & Consent --> |Concerns| Subject
Subject --> |Performed for| Assessments & Plans & Actions
Obs --> |Recorded| Assessments & Plans & Actions
Obs --> |Influences| Assessments & Plans & Actions
end
- Explain the visualisation of a conceptual data model for adult social care based on the International Standard EN ISO 13940:2016 and Contsys:2019
This diagram shows how different people and groups work together to support someone who needs care. At the heart of it all is the person being looked after, surrounded by the important details that keep them safe, such as their legal rights and their permission for care. A team of professionals—which could be an individual, a small team, or a large organization—uses this information to provide support and make decisions on the person's behalf. By carefully watching and recording what they see (observations), these helpers can figure out the best way to plan the person's care and daily activities. These observations act as a guide: they tell the team what is happening right now and help them decide which actions or plans are needed to help the person live their best life.
Care actors include People, Teams and Organisations who can have multiple roles where they Support, Provide Care for and/or Take decisions on behalf of the Subject of Care
Assessments & Care plans are performed for the Subject of Care and can be influenced by Observations about the Subject of Care. These result in Instruction, activity & actions which may result in further Observations being recorded which in turn may trigger ReAssessments & Care plan reviews.
Consent and legal information concerning the subject of care must be captured to inform the provision of care, as well as Administrative Information that will inform operational delivery of care.
All adult social care records must include Audit Information.
Paragraph 18
///mermaid graph TD accTitle: Visualisation of a conceptual data model for Care Actor - Organisation, team or person participating in health and adult social care. accDescr: When someone needs support with their health or daily life, they are the "Subject of Care" at the heart of a big team. This team includes family and friends (like personal contacts or unpaid carers) and professional care workers who all work together to provide the right help. To make sure everything runs smoothly, organizations like the NHS or local councils (the commissioners and service providers) organize and fund the care, while voluntary groups offer extra support to the person and their family. Most importantly, the person receiving care is involved in every step, but if they ever need help making a choice, a trusted "proxy" can step in to make decisions on their behalf to ensure they always get the best possible support. subgraph Taxonomy ["Left Diagram: Taxonomy & Inheritance Structure"] direction TB CareTeam_T[Care Team] -->|part of| Person_T[Person] Organisation_T[Organisation] -->|is a| CareActor_T[Care Actor] Person_T -->|is a| CareActor_T CareActor_T -->|has role 1..*| Role_T[Role] subgraph Providers [" "] direction LR LocalAuthority_T[Local Authority] --> Commissioner_T[Commissioner] HealthcareProvider_T[Healthcare Provider] --> ServiceProvider_T[Service Provider] SocialCareProvider_T[Social Care Provider] --> ServiceProvider_T VoluntaryOrganisation_T[Voluntary Organisation] --> ServiceProvider_T end subgraph GeneralRoles [" "] direction LR UnpaidCarer_T[Unpaid Carer] PersonalContact_T[Personal Contact] SubjectOfCare_T[Subject of Care] Proxy_T[Proxy for Subject of Care] end subgraph CareWorkers [" "] direction LR LocalAuthorityProfessional_T[Local Authority Professional] --> CareWorker_T[Care Worker] Volunteer_T[Volunteer] --> CareWorker_T CareProfessional_T[Care Professional] --> CareWorker_T HealthProfessional_T[Health Professional] --> CareWorker_T end Commissioner_T -->|is a| Role_T ServiceProvider_T -->|is a| Role_T UnpaidCarer_T -->|is a| Role_T PersonalContact_T -->|is a| Role_T SubjectOfCare_T -->|is a| Role_T Proxy_T -->|is a| Role_T CareWorker_T -->|is a| Role_T end subgraph ER_Model ["Right Diagram: Functional Relationship Model"] direction TB ServiceProvider_R[Service Provider] --- Commissioner_R[Commissioner] CareTeam_R[Care Team] CareWorker_R[Care Worker] --- SubjectOfCare_R[Subject of Care] --- UnpaidCarer_R[Unpaid Carer] VoluntaryOrganisation_R[Voluntary Organisation] Proxy_R[Proxy for Subject of Care] PersonalContact_R[Personal Contact] ServiceProvider_R -->|0..1| Commissioner_R ServiceProvider_R -->|0..* supports| SubjectOfCare_R Commissioner_R -->|0..1 supports| SubjectOfCare_R CareWorker_R -->|1..* part of| CareTeam_R CareTeam_R -->|0..* provides care for 1..*| SubjectOfCare_R UnpaidCarer_R -->|1..* part of| CareTeam_R CareWorker_R -->|* employed by 0..1| ServiceProvider_R CareWorker_R -->|0..* provides care for 1..*| SubjectOfCare_R UnpaidCarer_R -->|0..* provides care for 1..*| SubjectOfCare_R CareWorker_R -->|* employed by 0..1| VoluntaryOrganisation_R VoluntaryOrganisation_R -->|0..* supports| SubjectOfCare_R VoluntaryOrganisation_R -->|0..* supports| UnpaidCarer_R Proxy_R -->|0..* takes decisions on behalf of 1| SubjectOfCare_R SubjectOfCare_R -->|1 has 0..*| PersonalContact_R SubjectOfCare_R -->|1..* ordinarily resident in 0..1| Commissioner_R SubjectOfCare_R -->|1..* ordinarily resident in 0..1| ServiceProvider_R end
- Explain the visualisation of a conceptual data model for Care Actor
When someone needs support with their health or daily life, they are the "Subject of Care" at the heart of a big team. This team includes family and friends (like personal contacts or unpaid carers) and professional care workers who all work together to provide the right help. To make sure everything runs smoothly, organizations like the NHS or local councils (the commissioners and service providers) organize and fund the care, while voluntary groups offer extra support to the person and their family. Most importantly, the person receiving care is involved in every step, but if they ever need help making a choice, a trusted "proxy" can step in to make decisions on their behalf to ensure they always get the best possible support.
A [Person](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=584770), [Organisation](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=464197) or **Care Team** can be a [Care Actor](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=""&elementId=58691). Each [Care Actor](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=""&elementId=58691) will have a **Role** in a particular context. For example the same [Person](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=584770) may have one or more roles in various different contexts: [Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685) [Unpaid carer](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463690) [Personal contact](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463950) [Care worker](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463617) [Proxy for subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463949) **Service Providers** are all [Organisations](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=464197&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods) that provide a [type of service](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=""&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&elementId=463710) and include: [Social Care Providers](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&elementId=464567) **Healthcare providers including** [General practices](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&elementId=464566) **Voluntary Organisations** and in some cases **Local Authorities**. Service Providers are [Organisations](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=464197&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods) that *support* the **[Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685)** and employ **[Care workers](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=463617&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods)** who *[provide care for](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=""&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&elementId=465636)* the **[Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685)**, sometimes as *part of* a **[Care Team](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=""&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&q=care+team&search=true&elementId=463701)**. Unpaid carers *[provide care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=""&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&q=provide+care&search=true&elementId=465636)* for the **[Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685)** and can be *part of* the **[Care Team](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=""&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&q=care+team&search=true&elementId=463701)**. **[Personal contacts](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463950)** and their *relationship* with the **[Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685)** is captured as part the record. If the **[Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685)** does not have capacity, a **[Proxy for subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463949)** may be appointed to take *decisions* on their behalf and the *relationship* between them and the **[Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685)**, alongside **[Legal information](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=463609&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods)** is recorded. **[Care Actors](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=584644)** can also be a *Commissioner* of services i.e the [source of care funding](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=""&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&elementId=465036). This may be determined by the **Local Authority** that the **[Subject of care](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463685)** and/or **[Unpaid carer](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&classId=463690)** is *[ordinarily resident in](/adult-social-care/published-standards/adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods/data-specification/data-browser?classId=""&id=adult-social-care-digital-social-care-record-minimum-operational-data-standard-mods&elementId=463700)*.
Paragraph 19
///mermaid graph TD accTitle: Visualisation of a conceptual data model for Assessment - the process of evaluating a person’s needs, wishes, strengths and preferences, as well as identifying any relevant risks associated with them. accDescr: When a person needs support, their care team carries out a formal check, called an assessment, to understand their unique situation and how best to help them. This process involves looking at the person’s strengths, what they are good at, and what they want for their own life, while also identifying any risks or specific needs they have. Professional care workers lead these checks, but they always listen to the person or a trusted friend acting on their behalf to make sure the final plan reflects their true wishes and preferences. Because lives change, these assessments are regularly reviewed and updated to ensure the support stays right for the person, making sure they stay safe, healthy, and in control of their future. subgraph ContextLayer [" "] direction LR Observation[Observation] Review[Review] end subgraph PrimaryActors [" "] direction LR CareActor[Care Actor] Proxy[Subject of Care Proxy] SubjectOfCare[Subject of Care] end subgraph CoreHub [" "] Assessment[Assessment] end Observation -->|1 influences| Assessment Review -->|0..* reviews 1| Assessment CareActor -->|1..* performs| Assessment CareActor -->|1..* completes| Assessment CareActor -->|1 authorises| Assessment Proxy -->|1 expressed by 1| Assessment SubjectOfCare -->|1 performed for 0..*| Assessment subgraph Subtypes [" "] direction LR NeedsAssessment[Needs Assessment] MentalCapacityAssessment[Mental Capacity Assessment] FinancialAssessment[Financial Assessment] RiskAssessment[Risk Assessment] end Assessment -->|is a| NeedsAssessment Assessment -->|is a| MentalCapacityAssessment Assessment -->|is a| FinancialAssessment Assessment -->|is a| RiskAssessment MentalCapacityAssessment --- DoLS[DoLS] FinancialCircumstance[Financial circumstance] FinancialAssessment -->|1| FinancialCircumstance SubjectOfCare -->|1 ... 0..*| FinancialCircumstance subgraph RiskDetails [" "] direction LR SafeguardingConcern[Safeguarding Concern] Risk[Risk] end RiskAssessment -->|1 identifies 0..*| SafeguardingConcern RiskAssessment -->|1 identifies 0..*| Risk SubjectOfCare -->|1 has 0..*| SafeguardingConcern SubjectOfCare -->|1 has 0..*| Risk subgraph NeedsDetails [" "] direction LR Need[Need] Wishes[Wishes] Strength[Strength] Preferences[Preferences] end NeedsAssessment -->|1 evaluates 0..*| Need NeedsAssessment -->|1 evaluates 0..*| Wishes NeedsAssessment -->|1 evaluates| Strength NeedsAssessment -->|1 evaluates 0..*| Preferences SubjectOfCare -->|1 has| Need SubjectOfCare -->|1 expresses 0..*| Wishes
- Explain the visualisation of a conceptual data model for Assessment
When a person needs support, their care team carries out a formal check, called an assessment, to understand their unique situation and how best to help them. This process involves looking at the person’s strengths, what they are good at, and what they want for their own life, while also identifying any risks or specific needs they have. Professional care workers lead these checks, but they always listen to the person or a trusted friend acting on their behalf to make sure the final plan reflects their true wishes and preferences. Because lives change, these assessments are regularly reviewed and updated to ensure the support stays right for the person, making sure they stay safe, healthy, and in control of their future.
Paragraph 20
///mermaid graph TD accTitle: Visualisation of a conceptual data model for Care plan - a written plan typically recorded after an assessment, addressing the needs and risks associated with the person receiving care and setting out goals and instructions for the care they will receive. accDescr: A care plan is like a helpful roadmap designed specifically for you to ensure you get the right support. It is built by listening to your personal wishes and preferences, looking at what you are already good at, and identifying the areas where you might need a hand to stay safe. For any of these plans to start, you—or someone you trust to speak for you—must understand the plan and agree to it, which is known as giving consent. Professional care workers then use this agreement to set clear goals and write down simple instructions for the team to follow. This process makes sure that every action taken is centered on what matters most to you, helping you stay in control of your life while receiving the help you need. subgraph UpperContext [" "] direction LR Consent[Consent] CareActor[Care Actor] end subgraph CoreActors [" "] direction LR Proxy[Subject of Care Proxy] SubjectOfCare[Subject of Care] end subgraph Hub [" "] CarePlan[Care Plan] end subgraph ExternalInfluences [" "] direction LR Observation[Observation] Wishes[Wishes] Preferences[Preferences] end subgraph PlanComponents [" "] direction LR Need[Need] Risk[Risk] Strength[Strength] Goal[Goal] Instruction[Instruction] end CareActor -->|1..* performs| CarePlan CareActor -->|1..* completes| CarePlan CareActor -->|1 authorises| CarePlan Proxy -->|1 expressed by| CarePlan SubjectOfCare -->|1 performed for 0..*| CarePlan CarePlan -->|1 requires 1| Consent SubjectOfCare -->|1 gives 1| Consent Proxy -->|1 states 1| Consent Observation -->|0..* influences 1| CarePlan Wishes -->|0..* influences 1| CarePlan Preferences -->|0..* influences 1| CarePlan CarePlan -->|1 addresses 0..*| Need CarePlan -->|1 addresses 0..*| Risk CarePlan -->|1 evaluates 0..*| Strength CarePlan -->|1 targets 1..*| Goal CarePlan -->|1 determines 0..*| Instruction Instruction -->|0..* targets 0..*| Goal Instruction -->|0..* is performed for 1| SubjectOfCare SubjectOfCare -->|1 has 0..*| Need SubjectOfCare -->|1 has 0..*| Risk
- Explain the visualisation of a conceptual data model for Care plan - a written plan typically recorded after an assessment, addressing the needs and risks associated with the person receiving care and setting out goals and instructions for the care they will receive.
A care plan is like a helpful roadmap designed specifically for you to ensure you get the right support. It is built by listening to your personal wishes and preferences, looking at what you are already good at, and identifying the areas where you might need a hand to stay safe. For any of these plans to start, you—or someone you trust to speak for you—must understand the plan and agree to it, which is known as giving consent. Professional care workers then use this agreement to set clear goals and write down simple instructions for the team to follow. This process makes sure that every action taken is centered on what matters most to you, helping you stay in control of your life while receiving the help you need.
Paragraph 21
///mermaid graph TD accTitle: Visualisation of a conceptual data model for Instruction, activity action accDescr: When you have a health goal, your care team writes down clear instructions on exactly what needs to happen to help you reach it. These instructions are turned into specific activities, like a nurse giving a vaccination, a doctor performing a check-up, or a care worker helping with daily tasks. Every time one of these tasks is finished, it is recorded as an "action" so there is a clear history of what was done, who did it, and when it happened. This careful tracking makes sure everyone on your team knows exactly how you are being supported and ensures that every step taken is helping you stay healthy and safe %% Top Level Activity Grid subgraph Activities ["Types of Activity"] direction LR Vaccination ~~~ Device ~~~ ToC[Transfer of Care] ~~~ Comm[Communication] Medication ~~~ Procedure ~~~ Task ~~~ Referral ~~~ Service end %% Main Logic Flow with Cardinality Goal -- "0..* targets 0..1" --> Instruction Instruction -- "1 determines 0..*" --> Activity Activity -- "0..* performed in 0..1" --> Location %% Connecting Subtypes to Parent Activity --- Activities %% Operational Links Activity -- "0..* performed for 1" --> SubjectOfCare Activity -- "0..* responsible for 0..*" --> CareActor Action -- "0..* recorded 0..*" --> Activity Action -- "0..* performed by 1..*" --> CareActor Action -- "0..* during 0..1" --> Visit Action -- "1..* recorded 0..1" --> Observation Action -- "0..* performed for 1" --> SubjectOfCare Location -- "1 contains 0..*" --> Visit
- Explain the visualisation of a conceptual data model for Instruction, activity & action
When you have a health goal, your care team writes down clear instructions on exactly what needs to happen to help you reach it. These instructions are turned into specific activities, like a nurse giving a vaccination, a doctor performing a check-up, or a care worker helping with daily tasks. Every time one of these tasks is finished, it is recorded as an "action" so there is a clear history of what was done, who did it, and when it happened. This careful tracking makes sure everyone on your team knows exactly how you are being supported and ensures that every step taken is helping you stay healthy and safe.
///mermaid graph LR Instruction --- Activity1[ACTIVITY] Instruction --- Activity2[ACTIVITY] Instruction --- Activity3[ACTIVITY] Activity1 --- Action1_1["ACTION 2aug2008 12:00"] Activity1 --- Action1_2["ACTION 6aug2008 15:45"] Activity2 --- Action2_1["ACTION 4aug2008 10:30"] Activity3 --- Action3_1["ACTION 1aug2008 10:30"] Activity3 --- Action3_2["ACTION 3sep2008 10:40"] Activity3 --- Action3_3["ACTION 1oct2008 10:30"] StandaloneAction["ACTION 13sep2008 11:23"]
Paragraph 22
///mermaid graph TD accTitle: Visualisation of a conceptual data model for Observation accDescr: An "observation" is simply a way for your care team to write down important information about your health and daily life, covering everything from your personal wishes and strengths to medical facts like allergies or test results. When a professional notices something or you share how you are feeling, they record it to create a clear picture of your situation, noting where it happened and who was involved. These gathered details are vital because they help your team make the right decisions about your future support. By looking at these observations, your team can update your care plan, check your progress in reviews, and give specific instructions to make sure the help you receive always matches what matters most to you. %% Top Level Observation Types (Inheritance) subgraph ObservationTypes [Types of Observation] direction LR Problem ~~~ Allergies ~~~ Alert ~~~ InvRes[Investigation Result] ~~~ Outcome Incident ~~~ SafCon[Safeguarding Concern] ~~~ Need ~~~ Strength ~~~ Risk Circumstance ~~~ DailyLiving[Daily Living] ~~~ Preferences ~~~ Wishes ~~~ Environment end %% Core Entity Observation((Observation)) %% Central Relationships with Cardinality Observation -- "is a" --> ObservationTypes SubjectOfCare -- "1 refers to 0..*" --> Observation CareActor -- "1 records 0..*" --> Observation Observation -- "0..* involves 0..*" --> CareActor Observation -- "1..* performed in 1" --> Location %% Downstream Influences Observation -- "influences 0..*" --> Review Observation -- "influences 0..*" --> CarePlan[Care Plan] Observation -- "influences 0..*" --> Assessment Observation -- "influences 0..*" --> Instruction
- Explain the visualisation of a conceptual data model for Observation
An "observation" is simply a way for your care team to write down important information about your health and daily life, covering everything from your personal wishes and strengths to medical facts like allergies or test results. When a professional notices something or you share how you are feeling, they record it to create a clear picture of your situation, noting where it happened and who was involved. These gathered details are vital because they help your team make the right decisions about your future support. By looking at these observations, your team can update your care plan, check your progress in reviews, and give specific instructions to make sure the help you receive always matches what matters most to you.
Paragraph 23
///mermaid graph TD accTitle: Visualisation of a conceptual data model for Administrative Information accDescr: To help your care run smoothly, there is a lot of behind-the-scenes work focused on keeping everyone connected through clear communication and organized records. This includes sharing documents and important details about when you start or finish using a care service. Your care worker will regularly schedule a "review" to check in on how things are going. This review is the main place where big decisions happen; your team looks at your assessments, daily activities, and specific instructions to decide if your overall care plan needs to be updated. This process ensures that the support you receive is always current and based on what is actually happening in your life. %% Main People and Entities Sub[Subject of Care] CA[Care Actor] SP[Service Provider] %% Central Administrative Items Comm[Communication] Doc[Document] Adm[Admission details] Dis[Discharge Details] Occ[Occupancy] Rev[Review] %% Supporting Concepts (Side boxes) subgraph Context Location Address Event end %% Administrative Flow Comm -- sends/receives --> CA Comm -- concerns --> Sub Doc -- records/concerns --> CA Doc -- concerns --> Sub Adm -- provides/concerns --> SP Adm -- concerns --> Sub Dis -- provides/concerns --> SP Dis -- concerns --> Sub Occ -- concerns --> SP CA -- Schedules --> Rev %% Review Fan-out Rev -- concerns --> Assessment Rev -- concerns --> Instruction Rev -- concerns --> Action Rev -- concerns --> Activity Rev -- concerns --> CarePlan
- Explain the visualisation of a conceptual data model for Administrative information
To help your care run smoothly, there is a lot of behind-the-scenes work focused on keeping everyone connected through clear communication and organized records. This includes sharing documents and important details about when you start or finish using a care service. Your care worker will regularly schedule a "review" to check in on how things are going. This review is the main place where big decisions happen; your team looks at your assessments, daily activities, and specific instructions to decide if your overall care plan needs to be updated. This process ensures that the support you receive is always current and based on what is actually happening in your life.
Paragraph 24
///mermaid graph TD accTitle: visualisation of a conceptual data model for Consent and legal information accDescr: Everything in your care starts with your permission, which is often called giving informed consent. You are at the heart of every decision, but you can also have a trusted person—like a legal proxy or someone with power of attorney—help make choices for you if you are ever unable to do so yourself. There are also special documents used to record your specific wishes ahead of time, such as how you want to be treated in an emergency or if you want to refuse certain medical treatments. The most important rule shown here is that your clear agreement is required before your care team can start a new care plan, carry out health tests, or follow specific instructions. This process ensures you stay in control of your health and that your personal choices are always respected. %% Top Level Legal/Professional Entities CA[Care Actor] Sub[Subject of Care] Proxy[Subject of Care Proxy] LPA[Lasting Power of Attorney] IC[Informed Consent] %% Legal Documents (Left and Right) DoLS[DoLS] ADRT[Advanced Decision to Refuse Treatment] CPR[CPR Decision] AS[Advanced Statement] MHA[Mental Health Act or Equivalent] %% Organizational Logic CA -- "1 assigns 0..*" --> LPA LPA -- "0..* is assigned to 1" --> Sub LPA --- Proxy Sub -- "1 has 0..*" --> DoLS Sub -- "1 concerns 0..*" --> ADRT Sub -- "1 concerns 0..*" --> CPR Sub -- "1 concerns 0..*" --> AS Sub -- "1 concerns 0..*" --> MHA Sub -- "1 states 0..*" --> IC Proxy -- "1 states 0..*" --> IC %% Consented Processes subgraph Processes [Processes Requiring Consent] direction LR Ass[Assessment] ~~~ Inst[Instruction] ~~~ Actn[Action] ~~~ Actv[Activity] ~~~ CP[Care Plan] end IC -- "0..1 requires 0..*" --> Ass IC -- "0..1 requires 0..*" --> Inst IC -- "0..1 requires 0..*" --> Actn IC -- "0..1 requires 0..*" --> Actv IC -- "0..1 requires 0..*" --> CP
- Explain the visualisation of a conceptual data model for Consent and legal information
Everything in your care starts with your permission, which is often called giving "informed consent". You are at the heart of every decision, but you can also have a trusted person—like a legal proxy or someone with power of attorney—help make choices for you if you are ever unable to do so yourself. There are also special documents used to record your specific wishes ahead of time, such as how you want to be treated in an emergency or if you want to refuse certain medical treatments. The most important rule shown here is that your clear agreement is required before your care team can start a new care plan, carry out health tests, or follow specific instructions. This process ensures you stay in control of your health and that your personal choices are always respected.
Paragraph 25
///mermaid graph TD accTitle: Visualisation of a conceptual data model for Audit Information accDescr: To make sure your information is always handled safely, every time a professional—like a doctor or social worker—looks at or updates your records, a digital "diary" called a change log automatically takes a note of it. Whether they are writing a new document, changing an old one, or even deleting something, the system keeps track of exactly what happened, who did it, and when. This creates a permanent history of your information that acts as proof to show that everything is being done correctly and fairly. By having this clear record of every change made by a care worker, your team can always look back at previous versions of your files to see how your support has evolved, ensuring your details are accurate and your privacy is protected. %% Main Entities Doc[Document] Sys[System] CL[Change Log] VR[Versioned Record] CA[Care Actor] %% Relationships with Cardinality Doc -- "0..1 proves 1" --> CL Sys -- "1 recorded in 1" --> CL CL -- "1 relates to 1" --- VR CA -- "1 Creates, Modifies, Amends, Attests, Deletes 1" --> CL
- Explain the visualisation of a conceptual data model for Audit Information
To make sure your information is always handled safely, every time a professional—like a doctor or social worker—looks at or updates your records, a digital "diary" called a change log automatically takes a note of it. Whether they are writing a new document, changing an old one, or even deleting something, the system keeps track of exactly what happened, who did it, and when. This creates a permanent history of your information that acts as proof to show that everything is being done correctly and fairly. By having this clear record of every change made by a care worker, your team can always look back at previous versions of your files to see how your support has evolved, ensuring your details are accurate and your privacy is protected.
Paragraph 26
Paragraph 27
Review & Status
- William Hemingway
- Alison Taylor
- Andrew Chiu
- Andrew Fenton
- Adam Milward
- Gavin Start
- Charlotte Reynolds
- Mervyn Olver
- Paul Marsden
- Natasha Neads