Remember our design jams last month where participants were challenged to increase student engagement in the Health OER Network? We had a bright, diverse group of U-M students, staff, librarians, and visiting scholars participate. There was a great mix of expertise too, including medicine, communication design, biomedical engineering, human computer interaction, computer science, and more. Originally we had two design jams planned but it was so difficult to wind down the discussion after the second event that participants unanimously voted for a third one. What great enthusiasm! So what did we come up with after three sessions? A proposed OER collection of clinical cases called “Diagnose This.” Here’s a short overview of the project:.
“Diagnose This” would be a website with openly licensed short and long clinical cases. The website would include a tool that allows users to easily author, view, and create derivatives of cases. This would make diagnosis an interactive, educational exercise. The intended audience for the site would be health science students and academics. We expect most of the authors would be lecturers. While anyone could author a case, in order to ensure accuracy, cases would not be posted until they have been approved by an administrator. An administrator would also review the content for any copyright or privacy concerns. A user would access cases individually or select 10 or 20 random cases within a given category or subcategory. A user could review the cases through a 5-star rating and comments system. Cases would also have multiple choice questions and answers. After a user answered a question, they would be able to view how others responded. This approach was inspired by the New England Journal of Medicine’s interactive cases and their Image Challenge. The project would fall under the umbrella of the African Health OER Network activities. It would focus on African patients and African procedures for diagnosis with participating institutions having an administrator. However, anyone worldwide could submit a case for review.
For a more detailed overview, see the 3-page summary of the project, including a list of design jam participants, project rationale, user scenarios, functionality, and next steps. If you would like to stay involved with the project going forward, let us know!