BMIN 5200-001 · Fall 2026

Foundations of Artificial Intelligence in Health

Thursdays, 3:30–6:30pm · 3600 Civic Center Blvd, Room 6E 031
August 27 – December 3, 2026
Joseph D. Romano, PhD · joseph.romano@pennmedicine.upenn.edu

Course information

Artificial intelligence is often used interchangeably with machine learning — but ML is a subfield of AI concerned with inductive reasoning, and a great deal of what biomedical informatics actually deploys rests on deductive reasoning instead. This course covers those founding principles: knowledge representation, logic, ontologies, search, rule-based expert systems, and probabilistic inference. Machine learning shows up in the last few weeks, for contrast.

The course is about how biomedical data can be organized, represented, interpreted, searched, and applied in order to derive knowledge, make decisions, and ultimately make predictions while mitigating bias. BMIN 5200 is the first of three AI courses in a sequence: it is followed by BMIN 5210 (Machine Learning) and BMIN 5220 (Natural Language Processing).

Objectives

  • Describe the challenges of representing human knowledge in silico
  • Explain the difference between deduction and induction, and the role of both in AI
  • Discuss past and current obstacles to implementing AI in biomedical domains
  • Show how common AI approaches address real biomedical problems
  • Implement core AI methods in Python — not only describe them

Prerequisites

Familiarity with basic biomedical concepts and terminology, statistics, and computer programming. BMIN 5010, BMIN 5030, and a programming course are suggested but not required. All programming is in Python. No previous exposure to AI is assumed.

As described in the prerequisites above, all students must have the ability to write and understand Python code. If you have experience in similar programming languages and know fundamental programming concepts, you should be able to pick up Python quickly and will likely succeed in this course.

Example lecture itinerary

0–30 min
Homework review
~60 min
Lecture
~25 min
In-class coding exercise
10 min
Break
~25 min
Journal club

Grading

Assignments (four, weighted equally)40%
Final project40%
Proposal5%
Implementation and code10%
Written report17%
Recorded presentation8%
Class participation20%
Journal club presentation10%
Journal club discussion4%
In-class exercises and preparation6%

1.0 cu. Everything is due 11:59pm on a Wednesday, the night before the class that reviews it. Late work receives a zero — answers are worked through in class the next afternoon, so a late submission cannot be accepted. Attendance is expected rather than credited: there are no points for showing up, but each unexcused absence deducts 5% from the final grade, separately from the table above. An absence is excused if you email Joe about it — what makes one unexcused is not getting in touch, so email as soon as something comes up.

Bring a laptop to every class. The weekly coding exercise runs in Google Colab — click the link on the schedule below and it works, with nothing to install. If you would rather work locally, the course repository includes a requirements.txt.

Recording and attendance

Class sessions are recorded over Zoom and posted to Canvas, so you can review a lecture later or catch up on one you missed. Recordings are for enrolled students only — do not redistribute them. There is no option to attend virtually. The recordings are for review, not a substitute for being in the room: the course runs on discussion, journal club, and in-class work, none of which happen watching a video afterward.

Journal club

From Week 3 onward we spend roughly 25 minutes on one paper per week. A pair of students presents each paper — one covers background and methods, the other results and critique, and both lead the discussion. With eleven papers, everyone presents once. Presenters must also run the paper past an LLM chatbot and report which of its criticisms hold up and which are wrong.

The presentation is worth 10% of the final grade — the same as one homework assignment. Discussion on the other ten weeks is worth a further 4%: everyone is expected to have read the paper and to take part, not only the pair presenting it.

Final project

A research project (doctoral students) or an implementation project (master's and professional students), addressing a biomedical problem of your choice. Deductive inference must be central — a project built primarily on machine learning is not acceptable. Both paths produce an 8–10 page report typeset in the AAAI LaTeX template, plus a 10-minute recorded presentation. Full specification in the final project instructions.

A one-page proposal is due Wed Oct 28, stating the problem, the deductive component, the data or resources you will use, and which of the two project types you are doing. It is graded, and it is how your topic gets cleared before you build anything. It falls the week after CLIPS is taught, so implementation students propose a tool having already used it.

Generative AI policy

Although this is a course on AI, the four homework assignments and the final project — proposal, code, report, and presentation — must be completed without generative AI assistance. Violations are treated as plagiarism under Penn's Code of Academic Integrity. Two exceptions: the LLM-driven critique in journal club, where its use is required, and the in-class exercises, which earn credit for engagement rather than correctness.

Reusing course material

Everything in the public course repository — the notebooks, this site, and the structure of the course — is released under CC BY-NC-SA 4.0. Share and adapt it with attribution, non-commercially, under the same licence. Instructors elsewhere are welcome to it — the full terms are in NOTICE.md.

Anything behind a PennKey login is a different matter. Slides, journal club papers, assignment files, and class recordings on Canvas or Box are for enrolled students only and must not be redistributed — much of that material is copyrighted by publishers, and the course does not hold a licence to pass it on. Rule of thumb: if PennKey was required to get it, it is not yours to share.

Disability accommodations

Penn provides reasonable accommodations to students with disabilities approved by Student Disabilities Services. Please make an appointment with Joe as early as possible to discuss your accommodations. SDS services are free and confidential; appointments can be made at (215) 573-9235.

Office hours

Office hours will be held on Mondays, from 3:00-4:00 PM, in 3600 Civic Center Blvd., Room 05-011A. This is the same building as where class is held, but one floor down. If you cannot make that time, email Anh or Joe to set up an appointment.

Resources

Documents are hosted on Penn Box and require PennKey sign-in. Canvas is used for submitting assignments, viewing grades, and watching the class recordings.

Course documents

  • Syllabus (PDF) The authoritative version. Everything on this page, in full. Served from this site, not Box — no PennKey needed.
  • Software setup Colab, and the optional local Python environment. On GitHub — no PennKey needed.
  • Canvas course site Assignment submission, grades, and class recordings.
  • Course repository on GitHub All in-class notebooks, with Colab links.

Homework

Final project files

  • Project instructions Both project types, report sections, grading.
  • Proposal instructions One page. Due Wed Oct 28, 11:59pm.
  • AAAI LaTeX template On Overleaf — choose "Open as Template".
  • Presentation video upload Name the file bmin5200_presentation_[PENNKEY].mp4

Reference material

  • CLIPS and clipspy examples The .clp files worked through in Week 7.
  • All journal club papers Single archive of the semester's PDFs.
  • Cawsey A. The Essence of Artificial Intelligence. Pearson, 2nd ed., 2010. Recommended, not required.
  • Russell S & Norvig P. Artificial Intelligence: A Modern Approach. Pearson, 4th ed., 2020. Recommended, not required.

Schedule

Twelve meetings. Lecture slides and journal club papers are on Box (PennKey required); the in-class notebooks open directly in Colab. Each journal club paper covers the previous week's lecture topic, not that day's — so the material has always been taught before anyone has to present on it. A due item is listed on the class meeting it is due for; the deadline itself is 11:59pm the night before, on the Wednesday (submitted through Canvas).

# Date Topic Materials
1 Aug 27 Course introduction; history of AI
2 Sep 3 Knowledge representation & logic
3 Sep 10 Semantic networks, frames, ontologies Journal club: McCarthy (1959)
4 Sep 17 Heuristic, local & population-based search Journal club: Ashburner et al. (2000)
— Sep 24 No class — instructor away
— Oct 1 No class — Fall Break
5 Oct 8 Biologically-inspired search Journal club: Wolpert & Macready (1997)
6 Oct 15 Rules & knowledge-based systems Journal club: Kennedy & Eberhart (1995)
7 Oct 22 Building an expert system: CLIPS / clipspy Journal club: Shortliffe et al. (1973)
8 Oct 29 Bayesian networks; state machines Journal club: Miller et al. (1982)
9 Nov 5 Information theory & machine learning Journal club: de Dombal et al. (1972)
10 Nov 12 Deep learning & large language models Journal club: Quinlan (1986)
11 Nov 19 Explainable AI Journal club: Vaswani et al. (2017)
— Nov 26 No class — Thanksgiving
12 Dec 3 Bias & fairness in AI Journal club: Caruana et al. (2015)
— Dec 11 Final project due