1 / 12

Upgrading the IT Environment for Social Outcome Reporting

Tui Futures Roadmap. Upgrading the IT Environment for Social Outcome Reporting. Tui Futures Roadmap. What is Tui? Tui within the IT context Recommendations for the future. Prerequisites for successful implementation. What is Tui.

yannis
Download Presentation

Upgrading the IT Environment for Social Outcome Reporting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tui Futures Roadmap Upgrading the IT Environment for Social Outcome Reporting

  2. Tui Futures Roadmap • What is Tui? • Tui within the IT context • Recommendations for the future. • Prerequisites for successful implementation

  3. What is Tui • TUI is a system to record and organise a picture of a person’s accumulated adversity, risks and resiliencies and how these change over time. • It is only used by ISR staff, i.e. those involved with intensive client case management . • It provides the information on which they can base their service provision decisions.

  4. Tui Context MoLi CMS Curam 4.5 Tui Tui UCV II Core client data No core client data

  5. Recommendations • Merge Tui with CMS and Model Office onto version 5.1 of the Cúram platform. • First Ensure pre-requisites are met to allow this. • In the interim move TUI in-house, attach to IAP and provide pre-population of client data from UCV II as per SAL.

  6. Business Pre-requisites for Merger • Define an MSD wide integrated business process for client assessment • Define an MSD wide standard set of hierarchies of questions and optionally predefined answers used to assess client needs Both of these are recognised business needs and preliminary work is progressing on the second.

  7. IT Pre-requisites for Merger • A security architecture that permits controlled non-MSD staff access to CMS functionality. TUI is used by non-MSD staff. Richard Parry is doing preliminary work on such an architecture. • The establishment of dynamic data replication of core client data between UCV II and Curam’s client database. Rey Non is advocating the second point as an intermediate step to full replacement of UCV II by Curam. It needs a signed off business case.

  8. Indicative Timeline

  9. Conclusion • Tui is to be phased out with ameliorative steps taken in the interim. • Key business and architectural issues need to be addressed to successfully complete the merger of Tui and Moli with CMS on Curam but these issues must be addressed to support other key MSD initiatives so we should start now.

  10. What has happened since, Tui • Consultation with vendor end of march • Code base review undertaken April • Agreement on hardware with I & S April • The business case being finalised. Degree of amendments beyond make safe yet to be agreed. • Final code handover from the supplier is imminent.

  11. What has happened since,Moli • Moli development as a separate application has ceased. • Business funding for production under review.

  12. Prerequisites for roadmap • Working group established on Social Outcome Reporting. Working group drafting paper to recommend: • Definition of high level process for capture and use of client state and outcome data (assumption is fully integrated with CMS) • Finalisation of P2P based information model.

More Related