> For the complete documentation index, see [llms.txt](https://docs.wellcomecollection.org/collections-information/lQ0fMyP8xr8hWWJiQkfl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wellcomecollection.org/collections-information/lQ0fMyP8xr8hWWJiQkfl/transcribe-wellcome/research/organisations/wihm.md).

# Wellcome Institute of/for the History of Medicine (WIHM)

Wellcome Institute of/for the History of Medicine (WIHM)

successor institution to Wellcome Historical Medical Museum and Wellcome Historical Medical Library

1968 - Wellcome Institute of the History of Medicine 1973 - Wellcome Institute for the History of Medicine (title change) 1976 - creation of joint Academic Unit with UCL WIHM still in existence in 1993, albeit fragmented across different buildings: Academic Unit, Bentley House, ...

see [Symons 1993](https://archive.org/details/Symons1993/mode/2up), p[46ff](https://archive.org/details/Symons1993/page/n49/mode/2up), p[57n67](https://archive.org/details/Symons1993/page/n61/mode/2up)

List of staff associated with WIHM


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wellcomecollection.org/collections-information/lQ0fMyP8xr8hWWJiQkfl/transcribe-wellcome/research/organisations/wihm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
