This course does not seek to provide answers to ethical questions. Instead, the course hopes to teach students two things. First, how do you recognize ethical or moral problems in science and medicine? When something does not feel right (whether cloning, or failing to clone) — what exactly is the nature of the discomfort? What kind of tensions and conflicts exist within biomedicine? Second, how can you think productively about ethical and moral problems? What processes create them? Why do people disagree about them? How can an understanding of philosophy or history help resolve them? By the end of the course students will hopefully have sophisticated and nuanced ideas about problems in bioethics, even if they do not have comfortable answers.

Software Carpentry lesson that teaches how to use databases and SQL In the late 1920s and early 1930s, William Dyer, Frank Pabodie, and Valentina Roerich led expeditions to the Pole of Inaccessibility in the South Pacific, and then onward to Antarctica. Two years ago, their expeditions were found in a storage locker at Miskatonic University. We have scanned and OCR the data they contain, and we now want to store that information in a way that will make search and analysis easy. Three common options for storage are text files, spreadsheets, and databases. Text files are easiest to create, and work well with version control, but then we would have to build search and analysis tools ourselves. Spreadsheets are good for doing simple analyses, but they don’t handle large or complex data sets well. Databases, however, include powerful tools for search and analysis, and can handle large, complex data sets. These lessons will show how to use a database to explore the expeditions’ data.

This course examines the growing importance of medicine in culture, economics and politics. It uses an historical approach to examine the changing patterns of disease, the causes of morbidity and mortality, the evolution of medical theory and practice, the development of hospitals and the medical profession, the rise of the biomedical research industry, and the ethics of health care in America.

This course explores recent historical and anthropological approaches to the study of medicine and biology. Topics might include interaction of disease and society; science, colonialism, and international health; impact of new technologies on medicine and the life sciences; neuroscience and psychiatry; race, biology and medicine. Specific emphasis varies from year to year.

This class provides a space for medical students and MD/PhD students, as well as HASTS (History, Anthropology, Science, Technology, and Society) PhD students to discuss social and ethical issues in the biosciences and biotechnologies as they are being developed. Discussions are with course faculty and with leading figures in developing technologies such as George Daley or George Church in stem cell or genomics research, Bruce Walker or Pardis Sabeti in setting up laboratories in Africa, Paul Farmer and Partners in Health colleagues in building local support systems and first world quality care in Haiti, Peru, and Rwanda, and Amy Farber in building patient-centered therapeutic-outcome research for critical but “orphan” diseases. Goals include stimulating students to think about applying their learning in Boston to countries around the world, including using the experiences they have had in their home countries or research experience abroad. Goals also include a mix of patient-doctor care perspectives from medical anthropology, and moving upstream in the research chain to questions of how to move discoveries from basic research through the pipelines into clinical and bedside care.

Library Carpentry lesson to learn how to use the Shell. This Library Carpentry lesson introduces librarians to the Unix Shell. At the conclusion of the lesson you will: understand the basics of the Unix shell; understand why and how to use the command line; use shell commands to work with directories and files; use shell commands to find and manipulate data.

This subject introduces the history of science from antiquity to the present. Students consider the impact of philosophy, art, magic, social structure, and folk knowledge on the development of what has come to be called “science” in the Western tradition, including those fields today designated as physics, biology, chemistry, medicine, astronomy and the mind sciences. Topics include concepts of matter, nature, motion, body, heavens, and mind as these have been shaped over the course of history. Students read original works by Aristotle, Vesalius, Newton, Lavoisier, Darwin, Freud, and Einstein, among others.

Software Carpentry lesson on how to use the shell to navigate the filesystem and write simple loops and scripts. The Unix shell has been around longer than most of its users have been alive. It has survived so long because it’s a power tool that allows people to do complex things with just a few keystrokes. More importantly, it helps them combine existing programs in new ways and automate repetitive tasks so they aren’t typing the same things over and over again. Use of the shell is fundamental to using a wide range of other powerful tools and computing resources (including “high-performance computing” supercomputers). These lessons will start you on a path towards using these resources effectively.

This lesson is part of the Software Carpentry workshops that teach how to use version control with Git. Wolfman and Dracula have been hired by Universal Missions (a space services spinoff from Euphoric State University) to investigate if it is possible to send their next planetary lander to Mars. They want to be able to work on the plans at the same time, but they have run into problems doing this in the past. If they take turns, each one will spend a lot of time waiting for the other to finish, but if they work on their own copies and email changes back and forth things will be lost, overwritten, or duplicated. A colleague suggests using version control to manage their work. Version control is better than mailing files back and forth: Nothing that is committed to version control is ever lost, unless you work really, really hard at it. Since all old versions of files are saved, it’s always possible to go back in time to see exactly who wrote what on a particular day, or what version of a program was used to generate a particular set of results. As we have this record of who made what changes when, we know who to ask if we have questions later on, and, if needed, revert to a previous version, much like the “undo” feature in an editor. When several people collaborate in the same project, it’s possible to accidentally overlook or overwrite someone’s changes. The version control system automatically notifies users whenever there’s a conflict between one person’s work and another’s. Teams are not the only ones to benefit from version control: lone researchers can benefit immensely. Keeping a record of what was changed, when, and why is extremely useful for all researchers if they ever need to come back to the project later on (e.g., a year later, when memory has faded). Version control is the lab notebook of the digital world: it’s what professionals use to keep track of what they’ve done and to collaborate with other people. Every large software development project relies on it, and most programmers use it for their small jobs as well. And it isn’t just for software: books, papers, small data sets, and anything that changes over time or needs to be shared can and should be stored in a version control system.