Member Data Hub (MDH)
Authoritative membership data, roles, status, contact information and permissions.
Artificial intelligence is creating new possibilities for medical and scientific societies — not by replacing the people who lead and manage them, but by reducing repetitive work, making organisational knowledge easier to use and connecting information that is often scattered across different systems.
Membership, congresses, courses, journals, governance and finance all generate valuable information. Today, these data often sit in separate systems and are difficult to use across the organisation.
Twister is exploring a model in which these sources can be connected securely and selectively — without giving up data ownership or creating one uncontrolled central database.
The Society Data Hub is the controlled layer that connects relevant information across the organisation. It does not necessarily move all data into one database. Instead, it can provide governed access to existing systems, based on defined permissions, responsibilities and purpose.
Authoritative membership data, roles, status, contact information and permissions.
Registrations, participation, faculty, programmes, fees, CME and evaluation data.
Society-accessible publication, editorial and performance data, subject to publisher agreements and data rights.
Minutes, policies, contracts, guidelines, board decisions and organisational history.
Budgets, payments, commitments, sponsorships and management reporting where access is authorised.
One governed access model across the society’s information landscape.
AI supports work. People retain judgement, approval and accountability.
AI should not require a society to give up control of its information. Security, privacy and governance need to be designed into the workflow — not added afterwards.
The society remains in control of its source data, access rules and retention decisions.
Each workflow or agent should receive only the data and permissions required for its defined task.
Where practical, data stay in the systems designed to hold them rather than being copied into an unnecessary central pool.
Sensitive changes, external communication and high-impact actions can require explicit human review.
Access, actions and important workflow steps should be logged so activity can be reviewed and understood.
Architectures should reflect GDPR and applicable Swiss data-protection requirements, contracts and processor obligations.
For an early deployment, Twister would favour read-only or tightly limited access wherever possible. Write access can be introduced later for defined workflows, with approval rules and clear auditability.
The opportunity is not one large AI project. It is a sequence of focused improvements to the way the society works — each with a defined purpose, measurable benefit and appropriate controls.
Identify systems, information flows, data ownership and pain points.
Choose a focused use case where AI can create practical value.
Define permissions, data handling, human review and escalation rules.
Measure the result, refine the workflow and expand only where it works.
We can start with one recurring administrative problem, one information bottleneck or one workflow that has become unnecessarily complex.
Start a conversation →