Page History

Match-Connect is an API-based platform designed to streamline and modernise donor-patient communication across registries.

Match-Connect replaces the older EMDIS system with a more secure, standardised, and future-proof solution for international collaboration.

• Patient API (must be implemented first): Manages patient data and updates.
• Search API (requires Patient API): Initiates and retrieves donor search results.
• Connect API (requires Search API): The third API service that WMDA provides in the secure registry-to-registry communication system. Connect API provides a modern message-based architecture enabling registries to communicate donor exchange requests and responses efficiently, rapidly, and securely.

APIs work behind the scenes and will not change your system’s graphical interface (GUI). You have two options:

1. Use software that already supports Match-Connect APIs (e.g., contact Steiner Ltd, Czech Republic).
2. Integrate the APIs into your own system. This will require:
   • Knowledge of REST APIs.
   • Ability to build connections to Match-Connect.
   • Familiarity with JSON data format.
   • (Optional) Use of Postman or similar tools.

Match-Connect does not currently provide automatic delivery receipts. However:

• Endpoint messageResponseRequest is intended as an automated response to every user-generated message. It serves three purposes: message acknowledgment, warning, message denial. This is a purely machine-tomachine type of message, as compared to EMDIS where such responses can be user-generated.
• You can use the messageRetrieve endpoint to confirm that a message has been received.
• For critical messages, registries may implement manual confirmation or use the textMessageRequest endpoint for follow-up communication.
• Messages with responseType “success” and “warning” are sent to the receiving registry. Messages with responseType “failed” will not be sent. Appropriate responses are provided by the API:
  • 200 OK for responseType “success” and “warning”;
  • 400 Bad request for responseType “failed”