Discharge to Assessment


1. Project Initiation Document or Local Charter to be submitted to Interweave Project Management Office (PMO) for approval, along with use case to support the need for this project.
2. An email from the organisation’s Executive Sponsor confirming their approval for this project to proceed should also be submitted.
3. Interweave PMO reviews the documentation at Gate 1 and approves the organisations request to connect to the shared care record as a data provider.
4. Following approval, an email will be shared by Interweave PMO to all stakeholders. Access to Jira Service Management, Console and the Academy will be granted. 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. The purpose is to agree next steps around technical approach, data standards, clinical safety, and the cadence of meetings.
6. Interweave PMO will notify the Service Desk of the organisations approval, so the organisation is added to our sandpit environment to begin assurance activities.


1. Information Governance – it is advisable to complete these activities shortly after approval, at the initiation stage, as these can take time to approve.

    a. An Information Sharing Agreement must be created and approved by the organisation and the Information Governance Team at Humber Teaching Foundation Trust, who hosts Interweave. The organisation should consult with the team directly and Cc. Interweave PMO Team.
    b. Similarly, the above steps must be carried out for a Data Protection Agreement.
    c. The 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. Technical and Cyber Assurance

    a. The Onboarding Technical Assurance checklist must be completed by the organisation and shared with the Interweave Cyber Manager and Architect for their approval.

3. Testing and Data Standards

    a. A Test Report must be created and approved by the organisation, using test patients provided by Interweave. This ensures scenarios outlined in use cases are available and working as expected, and that the data is presently correctly. The report should be shared with the Interweave Data Standards Team for review and approval.
    b. A successful sample of FHIR resources must be shared with the Interweave Data Standards Team for review and approval.
    c. Following sign off from the Data Standards Team, the Data Quality Report (DQR) must be submitted to Interweave Clinical Safety Officer for approval.
    d. The organisation should raise a health check request via Jira, to be undertaken on their environments. Any issues must be resolved before progression can be granted.
    e. Please note: Testing and Data Standards activities should be completed in this order.

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

5. 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 to the next environment.
    b. Once approved at Gate 2, Interweave will notify stakeholders of this approval and outline next steps.



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 will complete clinical safety testing – a smoke test with live data.
6. Final DQR detailing results must 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 project can be closed and agreed communications can be shared with end users.


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