Project Initiation and Governance Compliance
The integration journey begins with the Project Initiation Document (PID) or Local Charter, which outlines the objectives, scope, and justification for connecting as a data provider. This document must be submitted to the Interweave Project Management Office (PMO), accompanied by a well-defined use case that demonstrates the value of data contribution.
In addition to the PID, approval from the organisation’s Executive Sponsor is required to confirm strategic alignment and executive buy-in. Once these documents are submitted, Interweave PMO conducts an initial Gate 1 review, evaluating the proposal’s feasibility and ensuring that it aligns with data-sharing objectives. Approval at this stage allows the organisation to gain access to key resources, including Jira Service Management, the Interweave Console, and the Interweave Academy—all of which provide the necessary tools and documentation to support integration efforts.
Following approval, a project kick-off session is scheduled, involving key stakeholders from both Interweave and the organisation. This session establishes the integration approach, data standards, clinical safety measures, and governance considerations. Organisations are also added to Interweave’s sandpit environment, allowing them to begin assurance activities in a controlled setting.
Assurance Requirements: Information Governance, Technical and Cyber Security
Assurance activities are essential to maintaining the integrity, confidentiality, and security of shared healthcare data. Information governance plays a pivotal role in ensuring compliance with UK data protection regulations, including GDPR and the Data Protection Act 2018.
Organisations must enter into an Information Sharing Agreement (ISA) with Interweave, outlining data ownership, responsibilities, and legal considerations. Additionally, a Data Protection Agreement (DPA) is required to define how patient data is processed. To mitigate potential privacy risks, a Data Protection Impact Assessment (DPIA) must be completed, highlighting how risks to personal data are identified and addressed. Fair processing materials must also be updated to inform patients about data-sharing arrangements within the Interweave ecosystem.
From a technical perspective, digital health providers must complete an Onboarding Technical Assurance Checklist, which is subject to review by Interweave’s Cyber Security Manager and Technical Architect. This process evaluates the organisation’s data security policies, infrastructure resilience, and integration readiness to ensure that only authorised and secure systems contribute to the shared care record.
Data Standards and Testing: Ensuring High-Quality Contributions
Interoperability is at the heart of Interweave’s ecosystem, and organisations must adhere to FHIR (Fast Healthcare Interoperability Resources) standards to ensure consistent data formatting and exchange. As part of the testing phase, organisations must create a Test Report using sample patient data provided by Interweave. This report must validate that the submitted data aligns with predefined use case scenarios and is accurately structured and rendered within the shared care record.
Once the test report is approved, a sample set of FHIR resources must be submitted to the Interweave Data Standards Team for validation. Following their approval, organisations must complete a Data Quality Report (DQR), ensuring that data accuracy, completeness, and consistency meet clinical standards. This report is reviewed by the Interweave Clinical Safety Officer, who assesses whether the data contributes effectively to patient care without introducing safety risks.
A critical step before advancing is conducting a health check request via Jira, where the organisation’s technical environment is assessed for stability, reliability, and performance. Any issues identified during this process must be resolved before moving to the next stage of integration.
Implementation Phases: Staging to Production
Upon successful completion of the assurance phase, organisations proceed to Gate 2 approval, allowing them to move into the Staging environment. This stage simulates a live setting using realistic but anonymised patient data, ensuring that all data flows operate as expected before deployment into the production environment.
During staging, organisations must continuously update their Data Quality Reports (DQRs), reporting any anomalies, inaccuracies, or unexpected behaviour. Any concerns raised by data consumers (other Interweave users) will be flagged via Jira, allowing the organisation to respond proactively to feedback and refine data quality before going live.
Once testing in staging is complete, organisations decide whether they are ready to transition to Production. Using the Interweave Console, the organisation formally initiates the move into a live setting, where data will be accessed by front-line health and social care professionals in real-world scenarios.
Final Clinical Safety Testing and Go-Live Preparations
Before final deployment, both the organisation’s and Interweave’s Clinical Safety Officers conduct a final round of clinical safety testing. This includes a smoke test using live data, verifying that the information is correctly integrated and accessible without impacting patient care workflows.
Once all clinical safety checks are approved, the final DQR report is submitted, marking the last formal validation step. At this point, organisations must complete local go-live preparations, ensuring that support models, standard operating procedures, and user training are in place.
The final step involves agreeing on a go-live date, which is confirmed by raising a Jira ticket. Once approved, the project is considered complete, and stakeholders are notified. Agreed communications, including guidance for end-users, are then distributed to facilitate adoption and ensure a seamless transition to full integration.
Ongoing Support and Data Maturity Enhancements
Post-implementation, Interweave provides ongoing support to organisations during their early stages of data provision. Any technical or clinical issues that arise are managed through Jira Service Management, ensuring rapid resolution and continued system stability.
For organisations looking to expand their data contributions, Interweave supports further data maturity initiatives. This allows providers to progressively increase the scope of shared data, ensuring that additional resources are properly validated, governed, and optimised for maximum impact.
Considerations for TPP Non-GP Data Providers
For organisations using TPP SystmOne (in a non-GP setting), an additional step is required to enable data-sharing functionality. The organisation must contact TPP at systmonesetup@tpp-uk.com to request that its units are enabled for integration with Interweave. This request must include the Unit Name and ID, specifying that the unit’s data will be shared into the shared care record. TPP typically enables this functionality within two weeks, and any operational issues post-integration must be reported directly to them.
Final Thoughts: Why Integrate with Interweave?
For digital health innovators, integrating with Interweave as a data provider represents an opportunity to enhance patient care through real-time, interoperable data exchange. The structured onboarding process ensures compliance, security, and high data quality, but it also requires commitment, thorough testing, and governance alignment. Successfully contributing to Interweave enables organisations to improve clinical outcomes, drive efficiency, and support integrated care across Yorkshire’s health and social care ecosystem.
For those starting their Interweave integration, understanding the governance, technical requirements, and assurance processes from the outset will be key to a smooth integration.
For more information on the Interweave integration process check out the Interweave website: https://interweavedigital.com/provider/.