Any to Any

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 consumer will be approved.

3. 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.

4. A tenancy request should be raised in Jira to request a tenancy in Production Tenancy Request – Interweave – Jira Service Management. Please note: this should only be submitted once approval at Gate 2 has been granted.

5. Interweave PMO will schedule a project kick off session with key officers from Interweave and the organisation. The purpose is to agree next steps around approach, clinical safety, and the cadence of meetings.

6. Interweave PMO will notify the Service Desk of the organisation’s approval, so the organisation is added to our environment to begin assurance activities.

Assurance

1. Information Governance – It is advisable to complete these activities shortly after approval at Initiation stage as these can sometimes take time for approval. It may be that only the DPIA is requiring updating as these agreements are likely in place for the organisations other consumption project.

• a. An Information Sharing Agreement must be created and approved by the organisation Interweave Information Governance Officer.

• 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 consuming data to a shared care record.

• e. All organisations wishing to consume GP Connect will need to sign up to the National Sharing Agreement here.

2. Technical and Cyber Assurance

• a. An Onboarding Technical Assurance checklist must be submitted, though please double check as this may not be required if you are already be live with other consumption projects.

3. Testing and Data Standards

• a. The organisation must complete witness testing with the Interweave Test Team. This is to ensure everything working as expected, and patients are displayed safely. On occasion, the Service Desk will need to be involved – the Test Team will advise.

4. Business Change processes

• a. Any changes to standard operating procedures, communications plans, users guides etc. should be in place at this stage, with 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 shared care record, who we should contact if there are any problems etc.

5. Assurance approval

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

• b. Once approved at Gate 2, Interweave will notify stakeholders of this approval and outline next steps. This is when the organisation should submit a tenancy request.

Implementation

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

2. Organisation to obtain Interweave Hazard Log for review.

3. Organisation to produce a clinical safety report and hazard log.

4. Organisation to complete clinical safety testing – using their use case to test that the data is displaying as expected.

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

6. Organisation to agree ‘go live’ date and raise a Jira ticket to confirm this so project can be closed and agreed communications can be shared with end users.

Support

1. This phase is designed to support an organisation in their early use of Interweave.