TEDMED
annual conference
TEDMED is an annual conference focusing on health and medicine, with a year-round web-based community. TEDMED is an independent event operating under license from the nonprofit TED conference.
Background
As of 2014, TEDMED staff operates from Stamford, Connecticut.
Talks given at TEDMED combine "the nexus of health, information and technology" with "compelling personal stories" and "a glimpse into the future of healthcare."
The intent of the conference has been described as "a gathering of geniuses" that brings together "some of the most innovative, thoughtful pioneers of healthcare technology, media, and entertainment into one big four-day 'dinner party' to learn from one another and mix people up from different disciplines and industries to solve big problems in healthcare."
History
TEDMED was founded in 1998 by TED's founder Richard Wurman. TEDMED was inactive for a number of years, and in 2008 Wurman sold the rights to TEDMED to entrepreneur Marc Hodosh. Hodosh recreated TEDMED and launched its first conference under his guidance in San Diego in October 2009.
In January 2010, TED.com began including videos of TEDMED talks on the TED website. In October 2010, TEDMED was held in San Diego again and sold out for a second year, attracting notable healthcare leaders and Hollywood celebrities.
In 2011, Jay Walker and a group of executives and investors purchased TEDMED from Hodosh for $16 million with future additional payments of as much as $9 million. The conference was then moved to Washington, DC.
In November 2016, TEDMED was held in Palm Springs, California.
“TEDMED” enters the record as annual conference. Crown Archives preserves that source wording while asking what TEDMED, annual and conference can confirm, complicate or overturn.
Why this record matters
“TEDMED” is worth following because a concise public description often conceals a longer documentary argument. Here, TEDMED, annual and conference provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jun 15, 2026. The linked authority identifier is Q7669953. 1 of 2 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 2014, 1998, 2008 and 2009.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “TEDMED”, its source revision and the description used here.
- Expand the search: follow TEDMED primary sources, TEDMED archive and TEDMED research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “TEDMED”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “TEDMED” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.