-
Notifications
You must be signed in to change notification settings - Fork 19
Home
The Matchmaker Exchange (MME) is a federated network of databases containing patient profiles. These databases connect to each other using the MME API and share de-identified phenotype/genotype information for the purposes of finding cohorts and discovering disease genes.
The MME is overseen by a steering committee with core members from IRDiRC and GA4GH and a representative from each connected databases. While databases can join the mailing lists and being involved in API development at any time, a representative can only join the steering committee once they meet the service requirements. These are informally enforced right now. Basically, at least two existing member databases must vet a new service and connect to it before the service can officially join the MME.
- Join the mailing lists
- Follow the GitHub repos
- Implement the MME API
- Choose at least two existing members of the MME to connect with, and start testing your implementation with them using test data
- Establish live connections using real data with at least two existing members of the MME
- the implementation should be tested with sample data and should behave in a way that is consistent with the API specification and acceptable to existing MME members
There are two mailing lists:
- A general mailing list for the entire MME: https://groups.google.com/forum/#!forum/matchmaker-exchange
- A technical mailing list for API developers: https://groups.google.com/forum/#!forum/matchmaker-exchange-technical
There are three GitHub repos that may be of interest:
- The API: https://github.com/ga4gh/mme-apis
- The reference server: https://github.com/MatchmakerExchange/reference-server
- The website: https://github.com/MatchmakerExchange/matchmakerexchange.github.io
Please ensure you follow the data use guidelines outlined in the service requirements.
Version 1.0 (latest release):
- API specification: blob/v1.0a/search-api.md
- Publication in Human Mutation: doi:10.1002/humu.22850
Development version (master branch):
- API specification: search-api.md
Have a question? Send us an email at [email protected] or create a GitHub issue.
- clarify versioning
- clarify headers
- Clarify that Ensembl IDs MUST be supported
- Clarify ID and how we treat it
- Clarify API change/release policy
- Automatic testing, configure your site, passing/not
- 1.2.3... guide, even if it describes the informal process
- To query most MME services, you need to request an authentication token from that service. You can find a more detailed description here: join-protocol.md.
- To help securely share authentication tokens, the KEYS file contains GPG keys for at least one member of each MME team.