...
- The Match-Connect system architecture is based on privacy and security by design principles. Deviation from these principles has to be justified, documented and approved. Typically, a trade-off has to be made between privacy/security and overall system complexity.
- A Match-Connect administrator should respond to all Match-Connect-related inquiries within 24 hours (excluding weekends), regardless of the content of the inquiry.
- Inquiries that reference system problems (for example, problems with sending/receipt of messages) should be given high priority.
- Sufficient time and care should be devoted to development and testing when establishing a connection with Match-Connect. Close collaboration is often necessary between new Match-Connect partners and WMDA to ensure that business and system expectations are being adequately met on all sides, before exchanging Match-Connect messages in production environments.
If a new Match-Connect partner does not want to implement the whole set of available message types, reasonable groups of message types should be implemented together. (tbd: reasonable sets of messages, aka known as EMDIS implementation level.
- Generally faxes and emails should be avoided in an electronic communication system. If they become necessary, it’s recommended not to mix channels in message groups, for example, if the TYP_REQ was in Match-Connect, the result should be in Match-Connect as well and not by fax/email (and vice versa).
The implementation of the central part of the Match-Connect architecture (broker, central hub) is based on these principles
...