You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

These guidelines are intended to provide a baseline set of Match-Connect administration practices for all Match-Connect participants. Due to the critical nature of business operations facilitated via Match-Connect, it is expected that these guidelines will be followed closely and consistently. This should ensure the ongoing success of message exchange between Match-Connect partners.

  • 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.



To Consider For Documentation:

6.1: Bulk Message to Singles messages ( M ) - technical guidelines(?)

6.2: Frequency of upload definitions and terms for CBU vs donor (M)

6.3: Allow for a real-time update for donors with requests (Request update in parallel to database update) - definitions and terms (M)

6.4: HT Frequency per Registry (C)

6.5: Data Quality Validation (S)

6.6: Privacy and Security by design ( M )

6.7: Data Impact Assessment

6.8: Technical and organizational measures

6.9: Master Data Management - Communication and Implementation Matrix

  • No labels