Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Use case:

Enabling easier implementation of new social care IT systems

Scenario:

  • A London council are in the process of implementing a new social care IT system.

  • They need to be confident that all potential suppliers have the same understanding of the requirements set out in the tender documentation, so that the tenders they receive are directly comparable and are fit for purpose.

  • Each subject of care record needs to capture their demographic information, alerts, care and support needs, family support network, professionals involved etc.

  • Then they need to tailor the workflow to meet the needs of their staff for accurate and efficient recording, whilst also capturing all the essential information for statutory returns and future CQC assurance requirements.

  • They also need to consider integrations like connected care health systems to ensure they are sharing data securely, in the correct format and regularly to maintain an accurate shared care record.
    To ensure they have captured all of this information, are using the most up to date datasets and terminology, they refer to the DSC Data Catalogue and MODS.

Goal:

  • Implement an effective, accurate and efficient social care IT system which meets the needs of their staff, captures all statutory information and promotes effective support and safeguarding of vulnerable adults.

  • Implementing a system with standardised datasets and terminology will lead to more effective interoperability between health, social care and care providers.

  • Having agreed a MODS, it will make it easier to switch between systems and given agreed areas that should be covered by the MODS should enable system suppliers to have more consistent processes across systems as they all need to meet the same requirements. This should reduce the training overhead for staff and will improve safeguarding as recording standards should be easier to maintain.

Assumptions:

  • The LA will have legacy data from whatever system was in use previously. It should be possible for this data to be able to be incorporated into the new system so that there is one case history for each service user. Any previous documents/attachments should be able to be transferred across so that they give the appropriate context to the service user's information.

  • It should be possible for information fields to be mapped so that the legacy data can be straightforwardly imported into the new system and will sit under the appropriate headings/sections of that system (e.g. involvements, contact numbers, hazards etc).

Process breakdown

  • Procure a social care system that meets the needs of the organisation and supports efficient recording of statutory requirements

  • Tailor the system to meet the needs of the staff using the system and the recipients of care

  • Consider which data tables are in the system and to which of the MODS do these link

  • Import legacy data into the new system and be able to access it (view, edit, update) in the correct screens/areas of that system
    Import any associated documentation or plans into the new system and be able to access them in the appropriate areas of that system

  • Work with health and care providers to ensure the systems can integrate

  • Provide training to all staff to ensure they can use the system to maintain accurate records

  • No labels