TPP Non – GP Data Provider

Home > Provider > TPP Non – GP Data Provider

Initiation

1. Project Initiation Document or Local Charter to be submitted to Interweave Project Management Office (PMO), along with use case to support the need for this project, and an email from the Organisation’s Executive Sponsor confirming their approval for this project to proceed.

2. Interweave PMO will review the documentation at Gate 1 and submit this to Interweave Senior Leadership Team (SLT) for approval. Please note that SLT meetings take place every Monday afternoon where all documentation will be reviewed and the organisations request to connect to the shared care record as a data provider will be approved.

4. Following approval, an email will be shared by Interweave PMO to all stakeholders. Access to Jira Service Management and Console will be granted (PMO will need Name, Job Title, Contact Number, and Email Address of the individual(s) within the organisation that requires this access). Stakeholders will also be signposted to support documentation on our website.

5. Interweave PMO will schedule a project kick off session with key officers from Interweave and the organisation.

6. Interweave PMO will notify the Service Desk of the organisation’s approval.

7. Organisation to contact TPP SystmOne systmonesetup@tpp-uk.com to request their units are enabled to share data into the Interweave Shared Care Record. Please include Unit Name and ID in your email and specify that the unit information will be shared to the Shared Care Record, so TPP can understand the scope of the project.

Requests can also be called through +44 (0)113 20 500 80

TPP agreed timescale for enabling units is 2 weeks.

Assurance

1. Information Governance – it is advisable to complete these activities shortly after approval. Please note, IG is only required if the organisation is not already connected to the shared care record.

a. An Information Sharing Agreement must be created and approved by the organisation and Interweave Information Governance Officer. The organisation should consult with the Information Governance Officer directly.

b. Similarly, the above steps must be carried out for a Data Protection Agreement.

c. An organisation must complete a Data Protection Impact Assessment.

d. Fair Processing Materials must be updated to reflect providing data to a shared care record.

2. Business Change processes

a. Any changes to standard operating procedures, communications plans, users guides etc. should be in place at this stage, including a firm plan of how this will be achieved before go live. Details should be shared with Interweave to provide a level of assurance.

b. Support Model – we also require firm details of how the organisation is going to support the connection, ensuring a process is in place to notify TPP of any issues.

4. Assurance approval

a. Once all assurance activities have been completed by the organisation, the Interweave Assurance Checklist should be submitted to Interweave PMO with supporting evidence, seeking approval to proceed.

b. Once approved at Gate 2, Interweave will notify stakeholders of this approval and outline next steps.

Implementation

1. Following approval at Gate 2, the organisation would proceed to our Production environment.

2. Once in Production environment, both the organisation’s and Interweave’s Clinical Safety Officers will complete clinical safety testing – a smoke test with live data.

3. Final DQR detailing results to be approved by both Clinical Safety Officers.

4. Organisation to complete any final preparations for go live and organise local approval.

5. Organisation to agree go live by raising a Jira ticket, so the project can be closed and the agreed communications can be shared with end users.