Introduction to Match-Connect

In hematopoietic stem cell transplantation, the ability to swiftly and efficiently match donors with patients is paramount.  Match-Connect is a platform poised to transform the landscape of stem cell transplantation by streamlining the search, match, and connect process.

At its core, Match-Connect is a collaborative endeavour spearheaded by member organisations and associated service providers. Its primary objective is to facilitate the seamless exchange of information related to the search, verification, and work-up process for suitable unrelated grafts of hematopoietic stem cells, ultimately improving patient outcomes.

Benefits of implementing Match-Connect:

• Streamlined Process: Match-Connect simplifies the matching process for stem cell donors and patients through integrated Search, Match, and Connect services.
• Comprehensive APIs: WMDA's specialised APIs (Patient, Search, and Connect) enable quick access to global donor and cord blood databases, empowering users to identify suitable matches efficiently.
• Global Communication: The Connect API facilitates secure registry-to-registry communication, reducing complexity with a central hub approach and leveraging Microsoft Azure's reliable cloud infrastructure.
• Automation and Efficiency: Integration of APIs automates manual tasks such as data entry and analysis, reducing workload for search coordinators and shortening the patient's timeline to transplantation.
• Data Security and Control: Match-Connect prioritises data security and user control, allowing organisations to integrate seamlessly with existing systems while adhering to standardised protocols and governance.
• Tailored Implementation: Organisations can customise API integration to fit local preferences, optimising the adoption process and enhancing patient care.

In essence, Match-Connect represents a paradigm shift in how stem cell transplantation is facilitated. By harnessing the power of collaboration, innovation, and technology, Match-Connect makes life-saving treatments more accessible and efficient for patients worldwide.

Overview of capabilities

• Patient API

  • Upload new patient (PAT_UPD equivalent)
  • Retrieve the list of your patients
  • Update an existing patient
  • Change patient status (PAT_STAT equivalent)
  • Retrieve individual patient data

• Search API

  • Start a search
  • Repeat a search
  • Retrieve search results for your patient (DONOR_CB equivalent)
  • Retrieve the patient's search summary (MATCH_SUM equivalent)
  • Retrieve full donor/CBU(/ADCU) report

• Connect API

  • Request donor extended HLA typing, receive results (TYP_REQ & TYP_RES equivalent)
  • Request donor VT sample (SMP_REQ, SMP_RES, SMP_INFO, SMP_ARR equivalent)
  • Request donor IDM testing, receive results (IDM_REQ & IDM_RES equivalent)
  • Request reservation of a donor (RSV_REQ & RSV_RES equivalent)
  • Request CBU full report (CBR_REQ equivalent)
  • Sending attachments (not available in EMDIS 3)
  • Administrative messages i.e.
    • message denial (MSG_DEN equivalent),
    • warning (WARNING equivalent),
    • request cancellation (REQ_CAN equivalent),
    • reminders (RES_REM equivalent),
    • text messages (TXT_MSG equivalent),
    • service can not be performed (NO_RES equivalent),
    • message acknowledgment (MSG_ACK equivalent)

Basic technical overview

The WMDA has developed a series of connectors (APIs) that allow search coordinators to search against the global database (Search & Match Service) from their local system and submit donor-related requests via the same connectors. The APIs were developed in a modular way to facilitate ease of implementation in a step-wise fashion, but when implemented in full, the three sets of API endpoints will allow comparable search, match and communication capabilities currently available through EMDIS 3.  Also read section 2.4 of the Match-Connect semantics for the technical guidelines.

• Logical implementation: the APIs need to be implemented chronologically starting with the Patient API.  The Search API can't be used without the Patient API and the Connect API cannot be used without the Search API.  A practical solution for exceptions, such as registries that get the download and Cord Blood Banks, have been taken into consideration.

• Physical implementation: the implementation of the APIs does not have set requirements for an end-user system (graphical user interface) because the API will need to be implemented at the back-end of the registry internal system.

  There are therefore two options: 

  • Deploy software that has a built-in support for the Match-Connect APIs. For more information on this, contact, for example, Steiner Ltd, Czech Republic. 
  • Integrate APIs into your internal system yourself. This requires: 
    • Ability to make changes and additions to the existing software of your internal registry system. 
    • Internet access from the back-end system.  
    • Your internal system needs to have been written in a programming language that is able to connect to a RESTful API. This is almost any language. 
    • Available processing resources on the system where integration takes place.

  
  

• API credentials: for machine-to-machine authentication can be retrieved through WMDA Support. 
• Developer requirements:
  • 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.

Security Requirements

Data and technical infrastructure security is crucial in Match-Connect to protect sensitive patient and donor information, ensuring privacy and compliance with regulations. Robust data security measures prevent unauthorized access, safeguarding the integrity and confidentiality of critical healthcare data exchanged through the platform.  The following must be in place before implementation is initiated:

• Signing the latest version of WMDA Data Transmission and Use Agreement
• Completing WMDA Benchmark Certification OR completing the Data Security Peer Review
• Signing the Match-Connect Service Level Agreement
• Requesting the API authentication keys

Operational Requirements

Setting operational requirements in Match-Connect is essential to ensure successful implementation by providing clear guidelines and expectations for implementers. These requirements help maintain consistency, efficiency, and compatibility across systems, ensuring smooth integration and functionality of the platform for end-users and stakeholders.  The following must be in place to gain and retain access to the platform: 

• Member Organisation is in good standing with WMDA, i.e. is a community member and has paid the applicable membership fees.
• To participate in the Connect API of Match Connect, Member Organisation must ensure upload of its donor inventory at minimum daily. If Member Organizations provide other cellular therapy products to the Search & Match Service, changes should be updated as soon as they appear. The inventory must be updated at minimum on a weekly basis. 
• Member Organisations and Healthcare Professionals using the Match Connect System are fully responsible for their local implementation, the technology used, its system security, maintenance and development. Specifically, they must ensure:
• State-of-the art technology and regular updates to their systems in order to ensure an adequate level of data security and data protection. 
  • 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.
  • The Member Organisation is responsible for the 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

For more detailed information, please read Match-Connect Transition Recommendation for Registries Moving Beyond EMDIS or Manual Systems.