Initiation

 
1. Project Initiation Document or Local Charter along with use case to support the need for this project are likely to already be in place, as this project is about sharing more resources.
 
2. 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 technical approach, data standards, clinical safety, and the cadence of meetings.
 

Assurance

 
1. Information Governance – likely to be already in place, however, a review of what was approved for the early provision project would be advisable.
 
2. Technical and Cyber Assurance – this is likely not to be required as this was approved previously, however, if technical infrastructure has changed then this may be required. This can be discussed during the project kick off session with Interweave Architect.
 
3. Testing and Data Standards
 

1. 1. a. A Test Report must be created and approved by the organisation using test patients provided by Interweave. This ensures that scenarios outlined in use case are available and working as expected, and the data is presently correctly. The report should be shared with Interweave Data Standards Team for review and approval.

 

1. 1. b. A successful sample of FHIR resources must be shared with the Interweave Data Standards Team for review and approval.

 

1. 1. c. Following sign off from the Data Standards Team, the Data Quality Report (DQR) must be submitted to the Interweave Clinical Safety Officer for approval.

 

1. 1. d. The organisation should raise a health check request via Jira, to be undertaken on their environments. Any issues will need to be resolved before progression can be granted.

 

1. e. Please note: Testing and Data Standards activities should be completed in this order.

 
4. Business Change processes
 

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

 

1. 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 your environment goes down etc.

 

5. Assurance approval

1.  
   1. 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 to the next environment.

 

1. 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 Staging environment, where they would complete further testing with data that reflects the live environment.
 
2. The organisation must update their DQR with their findings and share this with the Interweave Clinical Safety Officer and PMO for awareness.
 
3. An opportunity for the organisation to respond to any consumer issues. These will be notified to the organisation via Jira.
 
4. Once complete, the organisation should decide whether they are ready to proceed to Production. The organisation would use Interweave Console to proceed to Production.
 
5. Once in the Production environment, both the organisation’s and Interweave’s Clinical Safety Officers must complete clinical safety testing – a smoke test with live data.
 
6. Final DQR detailing results to be approved by both Clinical Safety Officers.
 
7. Organisation to complete any final preparations for go live and organise local approval.
 
8. Organisation to agree go live date by raising a ticket on Jira, so the project can be closed and the agreed communications can be shared with end users.
 

Support

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