Table of Contents
Executive Summary – Reduce time to transplant
Our patients must be able to rely on searches and registry-to-registry communication being executed promptly and correctly at all times. This means a streamlined process to exchange information related to the search, verification, and work-up process for suitable unrelated grafts of hematopoietic stem cells, ultimately improving patient outcomes.
...
Registries can customise the solution to fit local preferences, optimising the adoption process and enhancing patient care.
Definitions
Search & Match Service:
- the global database of ~42 million donors and cord blood products, presenting data from 136 sources (57 countries)
- 6% of the records are updated daily, 89% of the records are updated weekly
- operating two matching algorithms (Hap-E provided by DKMS & Atlas provided by Anthony Nolan/NMDP) that operate in different data centres and have been validated by WMDA Bio-Informatics & Innovation Committee
...
- data definitions and principles to set up peer-to-peer communication that facilitates searches and requests between registries
- peer-to-peer email-based network
Why Match-Connect?
Search coordinators have different ways of connecting with international registries. This can be through EMDIS or through a manual, administrative process (fax, email). EMDIS is based on older technology and is not compliant with modern security and privacy standards. However, the non-EMDIS process requires several manual steps, which is labour intensive and prone to error.
...
- to offer better performance (search results will be available in seconds through a simplified matching process)
- to have security and reliability by design (Microsoft Azure Cloud Infrastructure)
- to be compliant with data protection laws such as the European General Data Protection Regulation
- to reduce long-term costs and to require less maintenance (maintaining one connection where approved changes are applied centrally by WMDA instead of multiple connections that need maintenance from all members)
- to offer a better and easier experience for search coordinators to conduct searches and reduce the risk of errors
- to reduce the barrier for non-EMDIS registries to join the global communication platform
- to make the entire process more streamlined and efficient by offering additional services such as Health Availability Check and Work-Up.
What is Match-Connect?
Match Connect is series of connectors (APIs) that will allow comparable search, match and communication capabilities currently available through EMDIS 3.
...
- Basic knowledge of REST APIs.
- Ability to develop a connection between your internal system and Match-Connect APIs.
- Optional: Postman or other API development environment.
- Only JSON is accepted for input and responses.
Requirements to join Match-Connect
Data security is paramount in Match-Connect to safeguard sensitive patient and donor information. The following requirements must be met:
...
- Having signed Data Transmission and Use Agreement.
- Having completed WMDA Benchmark Certification OR completed the Data Security QuestionnaireMatch-Connect Information Security Compliance Programme.
- Having signed the Match-Connect Service Level Agreement.
- Having requested the API authentication keys.
...
- Being a community member of WMDA Sector Listing Member in good standing.
- Ensure upload of its donor/cord blood inventory at minimum daily or whenever changes are made to a record.
- Being responsible for the local implementation, the technology used, its system security, maintenance and development. Ensure adequate level of data security and data protection by using current technology, regular updates and:
- Compliance with the Match-Connect Semantics and swagger documentation when interacting with the central system.
- Functionality of new API implementations using a comprehensive testing/staging environment and adequate test executions.
- Timely and adequate processing of incoming messages to ensure smooth follow-up of requests and results.
- Responsible for any implementation of business logic, monitoring systems and checks exceeding the central Match-Connect message validation.
- Availability of development resources to fix bugs impacting the correct exchange of messages with Match-Connect according to criticality.
- Availability of development resources to implement announced major changes to Match-Connect within the defined transition timeline.
...
Transition/Implementation
EMDIS registries
To ensure a smooth transition from the decentralised EMDIS communication protocol to the centralised Match-Connect, two approaches are recommended for handling individual existing EMDIS connections.
- Approach A involves switching communication per request type, allowing early benefits from the new system and connection to early adopters and non-EMDIS registries, but it poses a high technical burden and requires adequate separation between the communication layer and internal processes.
- Approach B switches communication only when all requests with a specific partner are ready, resulting in a later start but easier maintenance and control.
WMDA recommends Approach A if both partners can handle the technical burden and the transition occurs before the introduction of work-up request; otherwise, Approach B should be used.
For handling open requests and reservations, the EMDIS_ID in the embedded patient block in Match-Connect will identify patients communicated before the transition. Open requests should be completed in their initial communication platform (EMDIS or Match-Connect), and local registry systems must manage different platforms for different partners in parallel during the transition periodThe transition process requires handling open requests and patient cases carefully to avoid duplication, with the introduction of an embedded patient block for continuity. For former EMDIS users, legacy requests must be completed within EMDIS, while new ones transition to Match-Connect, requiring synchronisation of address data and registry systems to manage parallel communication channels during the transition phase.
non-EMDIS registries
To connect your local registry system to Match-Connect, ensure your registry system is compatible with the technical standards described in the Match-Connect Semantics. This includes data formats, communication protocols, and security measures. Your system should have the necessary software and hardware capabilities to handle the integration, which may involve upgrades or new installations.
...
Transplant centres with access to WMDA Search & Match Service can use the WMDA Patient API and the WMDA Search API. All donor/CBU request functionality available in the Connect API is only accessible through your affiliated national registry.
Transition/Implementation Timeline
The transition and implementation plan outlines a timeline for implementing Match-Connect and migrating away from EMDIS. Spanning from mid-2024 to early 2028, the plan involves phased API implementation and EMDIS connection transitions. Key milestones include completing Match-Connect implementation, achieving critical mass in adoption of Match-Connect, and ultimately retiring EMDIS. Early adopters aim to complete API implementation by late 2025, while others extend into mid-2026. The ultimate goal is to fully transition all organisations to Match-Connect and retire EMDIS by the end of 2027, ensuring a seamless and efficient changeover.
Initial feedback from Early Adopters
Gift of Life “We found implementing a Match-Connect interface to MatchQuest, our registry management system, to be straightforward and with no issues. Total development time for building the necessary base classes in our system was around 10 days.” – Rafi Freudenberger |
Canadian Blood Services “Implementation of the Patient and Search APIs and elimination of our local search algorithm have stream-lined the search process and simplified system infrastructure, resulting in personnel and system efficiencies, reduced chance of data entry error, faster times to identify potential matches for patients in need, and cost savings. Our upcoming implementation of the Connect API will prepare us to communicate with all other registries in an effective, efficient, and secure way using modern technology, and ensures continued electronic communications with current partners when EMDIS is obsolete. We have no doubt that the up-front efforts to implement this change will be far out-weighed by the long-term benefits.” – Janet Parks |
Matchis “At Matchis we feel a sense of urgency to implement Match Connect. Our experience as one of the early adopters, working in the test environment, has convinced us that this centralized approach significantly expands the donor selection horizon, improves efficiency and provides a firm basis to comply with donor privacy and data security regulations.” – Jaap Dijkman |
DKMS “Match-Connect allows you to see all donors at a glance and saves time for your patients while reducing errors by automatically synchronizing patient data and search results.” – Stefanie Wehner |
DATRI “WMDA is a community to help and support each other and the API project is a very good example of the same. There is documentation on what needs to be done, support offered with frequent meetings and a team ready to answer any queries and clarification the registry might require. But, the work needs to be done by each registry – hence each registry should have the required IT and technical people at their end. The API once implemented (in each stage) reduces the manual intervention of the search coordinators and makes their work more efficient and reduces chance of error. However, each registry needs to collaborate between their business rules and the technical requirements of the registry software and the API.” – Sumati Misra |
