- Case study #1: LOL-lab
- Case study #2: Developing the iKnife
- Case study #3: The Healthy Start, Happy Start Study
- Case study #4: Research priority-setting – how feasible is a festival approach?
- Case study #5: Establishing a public panel in research
- Case study #6: Evaluating a TB awareness animation
- Case study #7: Parents with experience of preterm birth help shape Imperial research
- Case study #8: Hackathons as a method for co-developing novel research tools
- Case Study #9: Inflammatory Bowel Disease (IBD) Patient Involvement in Research Day #IBDPRD
- Case Study #10: An interactive PPIE workshop on kidney transplant rejection
- Case study #11: The ALGeBRA Steering Group for breast cancer research
- Case Study #12: Using a community organizing approach to develop a Quality Strategy
In conversation with: Thibaut Jombart, Lecturer in Genetic Analysis
Working within: HPRU (Modelling Methodology)
What did you do?
I organised a hackathon (i.e. a coding workshop) called ‘Hackout 3’, which was funded by the Medical Research Council (MRC) and Health Protection Research Unit (HPRU). The event brought together epidemiologists, stakeholders from public health institutions, and members of the public (professional computer programmers) to develop new statistical tools for disease outbreak analysis and response.
What were you trying to achieve with the hackathon?
Professional software developers were expected to raise the quality of the software produced, and ensure that cutting-edge technologies were used.
Who did you involve and how did you find the right people?
Recruitment followed two channels: via personal invitation of eminent members of their respective communities (academic, public health, programming), and by application through an online form hosted on a website. People were directed there via advertisements on various public forums and existing mailing lists and Twitter. Some people also got in touch after hearing about the hackathon by word of mouth.
Were the people you recruited given any training?
No formal training was provided for the hackathon, though people learnt new things through the contact and exchange with other people from different backgrounds.
Did you achieve what you set out to do?
The expected impact was realised: our collaborative work was drastically improved by contributions from these members of the public who were also professional developers.
What impact did it have on the people involved?
The impact this hackathon event had on members of the public varied widely across people: some seemed put off by interactions with scientists and public health officers because of a lack of common language, and some were deeply interested in these interactions and ended up shifting their career towards more collaborations with research and public health institutions.
What was the most challenging part of doing PPI and how did you overcome it?
Dialogue between people with non-overlapping backgrounds is a challenge. Making people aware of this difficulty and adjusting expectations accordingly seemed to facilitate further interactions.
What advice would you give others interested in doing something like this?
Define expectations early on: what do you expect from the public involvement, who contributes what, and how. Also try to facilitate communication between people with different backgrounds. One way could be to ensure there is a “translator” between the different types of stakeholders who effectively speaks both of their languages. Highlighting awareness of these differences early on seems essential, but could also be facilitated through social events and collaborative tasks.
So, what’s next?
This event led to the creation of the R Epidemics Consortium (http://www.repidemicsconsortium.org/), which keeps attracting members of the public as well as public health officers and epidemiologists. Further similar Hackathon events have taken place since.