SAP PID Issue 1.1 25th Feb 2008(1)

7/30/2019 SAP PID Issue 1.1 25th Feb 2008(1)

http://slidepdf.com/reader/full/sap-pid-issue-11-25th-feb-20081 1/33

Project Initiation Document Single Assessment Process

Lancashire Care NHS Foundation Trust

Blackburn with Darwen Primary Care Trust

East Lancashire Hospitals NHS Trust

Blackburn with Darwen Single AssessmentProcess Project

Project Initiation Document

I 1 1



I 1 1


VERSION HISTORY

Version Date Issued Brief Summary of Change Owner’s Name

Draft 0.1 25/01/08 First Draft Version For Consultation Mike Brooks

Draft 0.2 07/02/08 Second Draft Following Project Team M01 Project Team

Draft 0.3 14/02/08 Third Draft Following Project Team M02 Project Team

Draft 0.4 14/02/08 Fourth Draft Following Project Team M03 Project Team

Draft 0.5 21/02/08 Fifth Draft Following Project Board M01 Project Team

Issue 1.0 21/02/08 First Issue following Project Board M02 Project Board

Issue 1.1 25/02/08 Second Issue – comments from Stephenlord & Helen Dawson

Project Board

For more information on the status of

this document, please see the covering

letter or contact:

SAP Project Manager Blackburn with Darwen Borough Council Adult Social ServicesK Floor Tower BlockKing William Street

BLACKBURN




CONTENTS

1 BACKGROUND................................................................................................................... 5

2 PROJECT DEFINITION.......................................................................................................72.1 Project Objectives.................................................................................................... 72.2 Project Scope...........................................................................................................7

2.2.1 Volumes & Sizing.....................................................................................................72.2.2 Outline Functionality.................................................................................................8

2.2.3 Integration................................................................................................................92.2.4 System Management and Security..........................................................................9

2.3 Project Approach....................................................................................................102.4 Project Deliverables............................................................................................... 102.5 Exclusions..............................................................................................................112.6 Constraints.............................................................................................................11

2.6.1 Blackburn with Darwen SAP Tools.........................................................................112.6.2 Timescales.............................................................................................................12

2.6.3 Existing Information Systems.................................................................................122.6.4 Resources..............................................................................................................122.7 Assumptions - Infrastructure...................................................................................12

2.7.1 Health.................................................................................................................... 122.7.2 Social Services......................................................................................................13

2.8 NHS - National Programme for IT...........................................................................132.9 Stakeholders.......................................................................................................... 13

2.9.1 Partner Organisations............................................................................................132.9.2 Other Key Stakeholders.........................................................................................132 9 3 Oth St k h ld 14




9.1 Introduction............................................................................................................ 26

9.2 Membership...........................................................................................................269.3 Accountability.........................................................................................................269.4 Responsibilities...................................................................................................... 269.5 MEETINGS............................................................................................................ 279.6 Project Board Memebers........................................................................................27

10 APPENDIX C : PROJECT TEAM - TERMS OF REFERENCE.......................................2910.1 Introduction..........................................................................................................2910.2 Membership......................................................................................................... 29

10.3 Accountability.......................................................................................................2910.4 Responsibilities....................................................................................................2910.5 Meetings...............................................................................................................30

11 APPENDIX D : PROJECT MANAGER JOB DESCRIPTION...........................................31

12 APPENDIX E : SAP FLOW CHART................................................................................33

13 APPENDIX F : SINGLE ASSESSMENT PROCESS PROJECT PLAN ..........................35




1 BACKGROUND

The Older Persons National Service Framework (NSF) was launched in March 2001, with theaim of ensuring that age discrimination is eradicated and that older people and their carersreceive consistently high quality services, wherever they live and whatever their circumstances. Most importantly, the NSF requires closer integration of health and socialcare, and that these agencies will work together in this pursuit. The NSF also required that aclient centred Single Assessment Process (SAP) be established within health and social carecommunities by April 2004!

The NSF was effectively replaced in 2006 by “A New Ambition for Old Age next steps inimplementing the NSF for Older People”.

In Blackburn with Darwen progress on developing a SAP capability has been slow. Activitieshave started but have subsequently floundered due to a lack of commitment and ownershipacross all agencies.

In place though not actively used across all care settings is a manual SAP questionnaire thatincorporates both the Contact and Overview assessments. These were agreed by all partiessome two years ago and are used within the Social Services via the Anite SWIFT system butnot within the NHS

A part of this project will be a review of a baseline manual process as well as the generationof a Business Case to support the development of an IT based solution to support the SAPdata collection and workflows.




Services and the PCT. The outcome of this Project Board was an agreement to refocus the

SAP activity by appointing a full time SAP Project Manager who would initially deliver a PIDand a Strategic Outline Business Case followed by a Full Business Case.

Whilst an Information Management and Technology (IM&T) solution for SAP is notmandatory, it has become clear through the activities to date and the experiences of other SAP implementations, that it would be difficult if not impossible to deliver a truly efficient,effective and integrated SAP without such a solution.




2 PROJECT DEFINITION

The ultimate aim of what we are delivering is the provision of an IT solution that supports thetimely, effective and legal collection and sharing of information between the NHS and SocialServices.The main deliverable of the project to satisfy the above is a Full Business Case and other relevant documentation that justifies the procurement of a computerised SAP process for theFour Partner Agencies (FPA). It does not cover the implementation of a computer system.In addition the project is also responsible for all tool based (paper forms) implementationsthroughout the lifetime of this project.

2.1 PROJECT OBJECTIVES

The specific objectives are: -

Establish effective governance arrangements to ensure that the introduction of thetools and IT system fully fits with the requirements of introducing a FPA wide SAP

Development of appropriate requirements specifications of SAP for both business and

IM&T needs.

Development of business case(s) for computerised SAP, with appropriate options,costings and recommendations.

Undertake an appropriate procurement exercise to purchase a computer system toimplement SAP within the Four Partner Agencies.

Controlled implementation of SAP tools ahead of the IM&T solution that arecommensurate with the future IM&T solution.




2.2.2 Outline Functionality

Any IT system must:

Enable the creation of contact and overview assessments to an accepted DOHstandard e.g. FACE

Enable the creation of Care Plans to an accepted DOH standard e.g. FACE

Enable data collected in contact and overview assessments to be shared (viamessaging) with other systems for use in specialist assessments

Enable specialist assessments created in other systems to be attached to thecorresponding contact and overview assessments

Enable the collection of all data as defined for SAP via DOH and Social Care datastandards

Be sufficiently flexible to enable the addition of fields as required by FPA SAPProcess and/or fields to support other processes that are not defined in DOH datastandards e.g.

Enable the collection data as defined by the Section 2 and Section 5notifications under the Community Care (Delayed Discharges etc) Act2003.

Enable the management of assessments i.e.

Editing/updates of fields by whom and when

Historical retention of all changes




Be able to be used via the Assessment Notification mechanism as defined above and

the Contact Assessment for some referrals e.g. GP to Social Care.

Enable the tagging by individual/organisation of the Assessment Notification asdefined by the Requirements Workstream e.g. for information, for action, commissiona service.

Allow patient/client alerts to be assigned for both clinical and non-clinical problems

Allow the addition of client/patients not pre-populated on the system. E.g. a personwithout a NHS number and/or who has just moved into area or is visiting

Minimise the degree of duplication of data entry between SAP and existing other systems

2.2.3 Integration

Any IT system must:

Be capable of a Data take on from existing Social Services and Health informationdatabases. The System should have the capability even though this requirement may

not be implemented.

Be capable of a real time interfacing to/from existing national and local SocialServices and Health information databases excluding at this stage GP Systems

Have a common Patient Index (NHS number) that enables the acceptance of datafeeds from national demographic databases.

Enable the use of other local numbers e.g. hospital unit number, Social Services

b




synchronised with corporate/national databases systems e.g.

All Patients Demographic details.

Acute/Community Hospitals Name National Codes, Structured Addressesincluding town/city and full post code, telephone numbers, e-mailaddresses.

PCT GP Practice and sub Practice Name, Names of GP’s, GP NationalCodes, Practice codes, Structured addresses including town/city and fullpost code,

Social Services Name, National Codes, Structured Addresses includingtown/city and full post codes, telephone numbers, e-mail addresses.

2.3 PROJECT APPROACH

This initial Project will finish following the delivery of a Full Business Case to support theInitial Requirements. This Full Business Case will identify the preferred supplier from thevendor selection process.

A second Project involving a new PID and hence revised Project Team and workstreams willthen manage the implementation of the preferred supplier’s solution.

The project will be run following the PRINCE2 project management methodology.

2.4 PROJECT DELIVERABLES

The following deliverables are expected from the project.

A P j t I iti ti D t ifi j bj ti t f th j t d




when the SAP will be used and what will be done with the information that has been

added.

SAP Governance Proposal i.e. who will administer the system, where will the systembe housed, who is responsible for the managed service

SAP Scenarios catalogue – catalogue of pathways to define the requirements

SAP Information Sharing Protocol

Should the preferred option be an external procurement then the following

deliverables will also be required:

SAP IT Vendor Selection Process

Use Case Catalogue – a detailed statement of requirements sent to thereduced list of suppliers against which a detailed assessment of compliance will be undertaken leading to the final selection of a supplier

An OJEU advert – the Official Journal of the European Union is the bodywhere our tender request will be delivered

2.5 EXCLUSIONS

The following exclusions are noted for this project: -

Project Scope - The project is concerned with the identifying the best IT solution for implementing SAP in Blackburn with Darwen, this will cover all aspects up to andincluding the procurement of a solution, if required. However this will not cover theimplementation of the IT solution, which would be considered a follow on project and

th i t j t t ld d t b t bli h d t t thi




within the Social Services Anite SWIFT system and are not being currently used by the NHS.

No equivalent SAP related tools are used within the NHS.2.6.2 Timescales

The plan provided in this PID will be to deliver a Full Business Case with a preferred supplier by the end of July 2008. This date is based upon an external procurement and is governedby the timescales as defined in OJEU. This could potentially enable an implementation of anIT solution by the end of 2008.

2.6.3 Existing Information Systems

This project is ultimately aiming to develop a computerised tool that will hopefully integratewith, and support, existing Health & Social Care computer systems within Blackburn withDarwen. Some of the major systems are: -

Blackburn with Darwen Social Services use the Anite SWIFT system.

Blackburn with Darwen PCT, where the appropriate functionality exists, such asPodiatry and SLT services, uses the LSP ISOFT iPM system. In some services, a

short term plan has been agreed to implement stand alone databases, whilst therequired level of functionality is delivered through the national CFH solution. Themedium to long term plan of the PCT is to standardise all services on the IsoftLorenzo product.

Lancashire Care use the LSP supplied ISOFT iPM system.

East Lancashire Hospitals Trust use an integrated ISOFT (TOREX) Clinicom systemacross both Burnley and Blackburn hospitals.

Th l l f i t ti ith th b t d d t hi h it b l t d ill




be included in the cost model to cover for example upgrades devices and/or

additional devices especially mobiles.

2.7.2 Social Services

WAN - It is assumed that access will be given to the N3 network for use by SocialServices staff. This will be managed by an issue on the current projects Issue Log.

LAN – as per Health above.

PC’s and Peripherals – as per Health above.

The above are initial project assumptions that may change following the Infrastructure Gap Analysis which can only be finalised once the supplier, user base and business model havebeen defined more accurately.

2.8 NHS - NATIONAL PROGRAMME FOR IT

The National Programme for IT (NPfIT) is in to the fifth year of the contract. Delivery acrossEngland has been fragmented in terms of the number and type of applications deployed. In

the north west of England Computer Sciences Corporation (CSC) are the Local ServiceProvider (LSP) contracted to deliver administration and clinical systems into the NHS. Todate CSC have delivered the interim ISOFT iPM PAS system into many trusts across all caresettings. Lancashire Care Trust, Blackburn with Darwen PCT and East Lancashire PCThave been using this system since 2005/2006.

SAP and Social Care integration are contained within the National Programme requirementsthat have to be delivered as part of the NPfIT. In certain parts of England these requirements

h b t t d i it d SAP t h b d li d H CSC




2.9.3 Other Stakeholders

Central Lancashire PCT

North Lancashire PCT

Blackpool PCT

Blackpool Social Services

Preston Teaching Hospitals

Blackpool Fylde and Wyre Hospitals Trust

University Hospitals Morecambe Bay

2.9.4 Other Key Interfaces

Current IT infrastructure and systems

Potential Suppliers of the SAP system

National Programme for IT




3 PROJECT ORGANISATION STRUCTURE

It is clear from previous experience that the success of complex, comprehensive projects of this nature requires the engagement of senior health and social care management, to identifypotential complexities and ensure that these are resolved as the project progresses. This willbe achieved by the establishment of a high level Project Board to oversee the running of theproject, supported by a Project Manager and an active Project Team.

The Project Organisation Structure can be seen in Appendix A of this document. Details

about these roles are contained in the sections below.

3.1 PROJECT BOARD

The Project Board will be comprised of appropriate partner organisational representativeswho can make decisions, in terms of financial, business need and risk issues. For this initialProject it is envisaged that there will be 3-4 Project Board meetings sitting every couple of months. The first to establish the project as defined in this PID and the final one to sign off the Full Business Case. In between one or two meetings to review the progress may be

helpful, particularly as decisions are being made about long listing, short listing and thepreferred supplier. All other information will be disseminated electronically via emails andnewsletters.

The Terms of Reference for the Project Board is in Appendix B.

3.2 PROJECT TEAM

A Project Team will be established to direct and co-ordinate the completions of the specific

j t k




Requirements with specific responsibilities for capturing customer requirements to

deliver:

Initial paper based tools to support the SAP

A scenarios catalogue that will enable the creation of Output BasedSpecifications that will form the basis of the IT solution.

A detailed Use Case Catalogue.

IT Solution with specific responsibilities for

The Quality Assurance of all the projects deliverables

The delivery of the vendor selection process and preferred supplier selection

The development of the Business Case(s)

Ensuring that Infrastructure Requirements are adequately covered in theBusiness Case(s).

Information Governance with specific responsibilities for:

The information Sharing protocol that defines the basis of the agreedInformation Governance model

Agreeing all requirements with respect to security of data, sharing of databetween agencies, mechanisms for patient consent

Education and Training with specific responsibilities

I d t i i th t f d h th l t d




4 INITIAL PROJECT PLAN

The most significant constraint to this project is clearly the challenging timeframe. However the urgency to complete the project must be balanced with the requirement to ensure that allnecessary information is gathered and analysed to enable the appropriate and correctdecision to be made on the preferred option and the subsequent preferred solution.

The key deliverables from each of the workstreams are defined in Section 4.1 below.

4.1 KEY MILESTONESThe key milestones for this project, and their target achievement dates are: -

Workstream Deliverable Date

Project Management

SAP Key Contacts 7th Feb 08

SAP Initial Project Scope (see PID) 21st Feb 08

SAP Project Initiation Document 21st Feb 08

SAP Risk Assessment Model 13th Mar 08

SAP Benefits Realisation Model 27th Mar 08

SAP Governance Proposal 30th May 08

SAP OJEU Advert 10th Apr 08

SAP Implementation Project - Project Brief 31st Jul 08

Requirements

SAP Scenarios Catalogue 13th Mar 08

SAP Output Based Specification 27th Mar 08

SAP Use Case Catalogue 30th May 08

SAP Strategic Outline Business Case 27th Mar 08th




4.2 RESOURCE REQUIREMENTS

4.2.1 Staff Resources

This is a significant project that will need the investment of multi-disciplinary resources fromall partner organisations, in order to be successful.

The skills required to complete this Project up until selection of an IT tool to support the SAPare identified in terms of full time equivalents (FTE’s) as follows:

Workstream Skill Org Jan Feb Mar Apr May Jun Aug Sep

ProjectManagement

ProjectManager

SS 0.25 0.5 0.5 0.5 0.5 0.5 0.5 0.5

PCT 0.25 0.5 0.5 0.5 0.5 0.5 0.5 0.5

Project Support SS 0.25 0.5 0.5 1 1 1 1 1

BusinessManager

SS 0.1 0.1 0.2 0.2 0.2 0.2 0.2

PCT 0.1 0.1 0.2 0.2 0.2 0.2 0.2

AC/LC 0.1 0.1 0.2 0.2 0.2 0.2 0.2

RequirementsBusiness Analyst

SS 0.1 0.2 0.2 0.2 0.2

PCT 0.1 0.2 0.2 0.2 0.2 AC/LC 0.1 0.2 0.2 0.2 0.2

IT Solution(inc IG)

Quality Assurance

SS 0.1 0.2 0.2 0.2 0.2

PCT 0.1 0.2 0.2 0.2 0.2

AC/LC 0.1 0.2 0.2 0.2 0.2

Technical Architect

SS 0.2 0.2

PCT 0.2 0.2

AC/LC 0.2 0.2

T i i N d SS 0 1




infrastructure, interfaces. Internally funded from partner organisations.

Training Needs Analyst – to produce the partner organisations input into theunderstanding of the future user base and types of users within that user base.Internally funded from partner organisations.

N.B. the outline plan in Appendix F is reliant on the above level of resource. Shouldthis resource not be made available the plan would not be achievable.




5 PROJECT CONTROLS

The following PRINCE2 controls will be used within this project to monitor progress, compareachievement with plan and take any corrective action required: -

Project Initiation Document – to ensure all the partners confirm acceptance of participation within the project and agree to fulfil their elements of it.

Project Highlight Reports - prepared by the Project Manager, and circulated to the

Project Board and Project Team, giving an overview of progress, plus any highlightsor issues than need to be escalated.

Project Plan – A Microsoft Office Project Plan of the full project.

Risk Log – a log based on agreed Risk model. The risks will have a potential trigger date, impact, likelihood, a mitigation plan, costs associated with the risk and costsrequired to mitigate the risk. The mitigation costs will be included in the BusinessCase(s).

Issue Log – a log of all issues that require resolution during the project. The log willinclude description of the issue, impact of the issue, severity of the issue, owner andresolution date.

Project Closure – An overall summary of the project, confirmation from partners thatthe project has produced all deliverables and any further follow on work that isrecommended.

Project Change Control – see Section 6 for a description of the Project ChangeC




6 CHANGE CONTROL

6.1 PRINCIPLES

Where any of the Partners as identified above see the need for change to

the current user base or

the client population or

requirements or any Issued Project Deliverable

they may request such a change in accordance with the formal Change Control Procedure("CCP") as set out below.

6.2 INITIATION

The Project Team will discuss the proposed Change Control with the originator of the requestand as such that discussion will result in:

Agreement not to proceed further; or

Rejection of the request by the non-requesting party; or

Agreement to proceed in principle

6.3 PROCEEDING

The originator of the request will be asked to submit a formal Change Control request via a

Ch C t l N t (CCN)




6.4 SUBMISSION OF PARTIALLY COMPLETE CCN:

In the event that, having received a written request for a change and the requested change isfor a variation that does not enable completion of a full CCN without additional informationfrom further investigations, the originator may submit a partially complete CCN.

A partially complete CCN shall contain, as far as possible, the information specified inparagraph 6.3 and, in addition, the IT Project Manager shall submit details of suchinvestigations as may be required to obtain information necessary to complete the CCN withthe costs.

For each partially complete CCN submitted to it, the Project Team shall, within a periodagreed at the time:

Allocate a sequential number to the CCN; and

Evaluate the CCN and as appropriate either:

1. Request further information or modification of details of the CCN or any other information submitted; or

2. Give approval for the completion of the CCN by undertaking the investigationand/or testing specified in relation to it; or

3. Notify the originator of the rejection of the CCN




7 PROJECT RISKS AND ISSUES

Risk and Issues Logs will be maintained throughout the project, identifying the key risksand issues that could impact on the achievement of the project objectives. Each risk andissue will need to be managed to the satisfaction of the Project Board and the Project Team.The Project Team via Project Support should ensure that the Risk and Issue Logs arereviewed and updated on a regular basis. The Project Board should review the high severityrisks and issues at each Project Board meeting.

7.1 RISKSThe following risks are currently identified: -

Mitigation

No Description Sev Cost Plan

1

Resources not suppliedas per the requirement

identified in Section 4.2of the PID

2

Review requirements with all partner organisations and if needed escalate.Investigate getting a backfill budget.

Or PM produces the deliverables for project team review.

2Failure to getcommitment to providefunding following OBC

1Strong Project Board accountability.Seek early commitment at the firstProject Board

3Geographical scope of

j i

1Geographical options pros and consto be provided to the Project Board

i h d i




appropriate information governance

standards4




8 APPENDIX A : PROJECT ORGANISATION

PROJECT BOARD

PROJECT TEAM

ProjectManagementWorkstream

Project Manager and Project Assistant Support

RequirementsWorkstream

InformationGovernanceWorkstream

Education &Training

Workstream

SAPREFERENCE

GROUP

ITSolution

Workstream




9 APPENDIX B : PROJECT BOARD TERMS OF REFERENCE

9.1 INTRODUCTION

The Single Assessment IM&T Project Board has been appointed to provide the overalldirection and management of the project looking to identify the best IM&T solution toimplementing SAP within Blackburn with Darwen.

The Project Board is ultimately responsible for ensuring that the project remains on course,

and the delivery of the desired outcomes defined in the Project Initiation Document.

9.2 MEMBERSHIP

The membership of the Project Board will comprise of :-

Executive nominations from Blackburn with Darwen PCT, East Lancashire HospitalsTrust, Blackburn with Darwen Social Services and Lancashire Care Mental HealthTrust.

IT leads from the four Partner Agencies

Other interested bodies e.g. Lancashire County Council

Strategic Health Authority SAP Lead

Chair of The SAP Project Team

9.3 ACCOUNTABILITY




delegated to the Project Manager

Authorise any tools based implementations

Review Risk Log and ensure that all key risks are identified, appropriately assessedand strategies are in place to manage the risk to acceptable levels

Review Issues Log and ensure that all key issues have been assessed, and theoutcome of the assessment enacted upon.

At the end of the project

Approve that the overall objectives of the project have been met

Approve Follow On Recommendations Report

Approve the closure of the project

9.5 MEETINGS

The meetings will be held every two months for the duration of the project.

The Chair of the Project Board may call ad-hoc meetings to deal with critical issues arisingbetween meetings.

9.6 PROJECT BOARD MEMEBERS

Name Title Org. PB Role




John Fletcher Head of IM&T Development ELHT Quality Assurance

Declan Hadley Director IM&T LCMHT Quality Assurance

Chris Anderton Project Manager NCRS LCMHT Quality Assurance

Stewart Cooper IT Programme Manager BWD PCT Quality Assurance

Mike Brooks SAP Project Manager Project Manager




10 APPENDIX C : PROJECT TEAM - TERMS OF REFERENCE

10.1 INTRODUCTION

The Single Assessment Project Board has been appointed to provide the overall directionand management of the project looking to identify the best tools and IM&T solutions toimplementing SAP within Blackburn with Darwen.The Project Team will support the Project Board in ensuring that resources are madeavailable to carry out the work required to make the project a success, and to ensure that the

work is completed to an acceptable standard of quality within the deadlines set for theproject.

10.2 MEMBERSHIP

The membership of the Project Team will comprise of :-

SAP Business Managers

SAP Project Manager

Business Analysts

Quality Assurance nominees

In addition relevant expertise (e.g. IM&T) within key areas will be required from both healthand social care at various points during the project, including Process, Networking,Integration, Systems Management, Database, etc

10.3 ACCOUNTABILITY




Ensure that project issues are being identified, recorded and reviewed, including

developed actions plans where required Keeping the project focussed on the agreed scope, and not allowing it to creep

beyond the defined business need

Ensuring all applicable standards are being met

Approve all Change Control requests before seeking Project Board authorisation

Approve all requests for local implementation of the tools based SAP before seeking

Project Board authorisation

10.5 MEETINGS

The meetings will be held initially weekly and fortnightly thereafter for the duration of theproject.

The Chair of the Project team or the Project Manager may call ad-hoc meetings to deal withcritical issues arising between meetings.

Name Title Org. PT Role

Anne Barnish Strategic Manager Adults & Older Peoples Services BWD PCT Business Manager

Karin Major Sensory Impairment Manager BWD BC Business Manager

Lindsey Darley Service Development Manager Integrated TherapyServices

BWD PCT Business Manager

Chris Brunning Community Care Manager BWD BC Business Manager




11 APPENDIX D : PROJECT MANAGER JOB DESCRIPTION

POST TITLE: SAP PROJECT MANAGER

Reporting to: Business Lead

Job Purpose:To project manage the development of a Full Business Case assessment of the optimalsolution for a Single Assessment Process IT system for Blackburn with Darwen which meets

the business requirements of the SAP users within Blackburn with Darwen.

Key Responsibilities:

To develop and keep under constant review, a project plan for the SAP Project,obtaining the approval of the Project Board for the same and for any significantplanned changes during the process of implementation.

To manage and coordinate all the workstreams with the SAP Business Managers, to

ensure that the project deliverables are produced within the set deadlines, and are of a suitable quality.

To develop a Strategic Outline Case for the computerised SAP process withinBlackburn with Darwen.

Production of an OJEU advert for the Single Assessment Process IM&T Solution (if appropriate)

Production of an OBS 1 to issue to suppliers with the support of the Infrastructure




12 APPENDIX E : SAP FLOW CHART

Yes

No

NoYes

Background & ContactAssessmentPersonal DemographicsDetails of needs/problems,screens for risksCompleted by Health/ Social Careworker with assessmentresponsibilitiesComplete only sections that arerelevant to the person

Contact with Health or Social Care services

Does the SAP need to betriggered?

Problem solved, adviceinformation given.

Signposted to appropriate service

Are there further needs/ risks to

address?

AssessmentOutcomes actioned

Is there evidence of significant needs and

risks?

Is the situation unpredictable/unstable

?

Specialist/In-Depth

Is an assessment by aHealth/Social Care

worker with a specificskill required?

Overview Assessment Assesses needs and risks as




13 APPENDIX F : SINGLE ASSESSMENT PROCESS PROJECT PLAN

Issue No: 1.0 35 Date: 25th February 2008Author: Mike Brooks Ref.: SAP/DEL/006

SAP PID Issue 1.1 25th Feb 2008(1)

Documents

Transcript of SAP PID Issue 1.1 25th Feb 2008(1)