Curriculum vitae & project index

W. Taylor Farrington, MD

BS Biomedical Engineering / MD — Acute Care Hospitalist — Data Engineer & Steward

Philadelphia, PA Board certified, Internal Medicine (ABIM) Licensed in Texas & Pennsylvania NPI 1154940732

01

Documents

Curriculum vitae PDF · posting soon
Professional narrative PDF · posting soon

This page is a complement to the CV, not a replacement for it: the PDFs carry the full record, and everything here is the short version plus the working code behind it.

02

Professional narrative

[Paragraph one — clinical identity. Where you trained, what kind of inpatient medicine you practice, and what you are known for on the wards. Written for a division chief who will read exactly this far before deciding whether to open the CV.]

[Paragraph two — the through-line. How the questions that surfaced at the bedside turned into models, warehouses, and analyses; why you build the tooling yourself rather than commissioning it; what that combination lets you do that neither skill alone would.]

[Paragraph three — the synthesis. What engineering training changed about how you practice, what practice changed about how you build, and where the two are heading next.]

03

Curriculum vitae

Training & appointments

  1. [20XX – present]

    [Current role]

    [Institution, City]

  2. [20XX – 20XX]

    [Prior appointment]

    [Institution, City]

  3. [20XX – 20XX]

    Residency, Internal Medicine

    [Program, City]

  4. [20XX]

    Doctor of Medicine

    [Medical school, City]

  5. [20XX]

    B.S., Biomedical Engineering

    [Institution, City]

At a glance

  • Certification [ABIM Internal Medicine, 20XX – 20XX]
  • Licensure Texas & Pennsylvania, active · NPI 1154940732
  • Clinical focus [Acute care hospital medicine; e.g. perioperative co-management, transitions of care]
  • Academic focus [e.g. clinical informatics, capacity & operations modeling, health equity analytics]
  • Teaching [Roles with students, residents, fellows]
  • Selected work [Publications, abstracts, invited talks — full list in the CV]
04

Projects

Clinical and peri-clinical data work. Two repositories are public and carry their own full write-ups, methods, and provenance notes; the rest are in private development and are described here in outline.

Public repositories

hupsim

v1 shipped

A room-level capacity model of a single academic hospital campus, built entirely from cited public sources with a confidence tag on every structural fact and all dynamics explicitly simulated.

  • simulation
  • capacity modeling
  • geospatial
  • provenance

mimicwarehouse

In progress

A local EMR data warehouse over MIMIC-IV with end-to-end provenance, protocol-frozen inquiry over retrospective data, and a pre-commit leak guard — data never leaves the machine. Public while in flight; v1 is a way out.

  • MIMIC-IV
  • DuckDB
  • Polars
  • Streamlit
  • data governance

Private & in development

Described in outline while the work matures. Methods, code structure, and results are available to discuss directly, and each repository opens publicly once it reaches a defensible state.

phillysim

Private

Municipal disparity modeling for Philadelphia — linking public administrative and health data to make neighborhood-level inequity legible at the scale decisions are actually made.

  • health equity
  • public data
  • geospatial

wikemgapsim

Private

Modeling editorial coverage gaps in WikEM, the open emergency medicine reference — where the clinical knowledge commons is thin, and whom that thinness reaches.

  • knowledge commons
  • text analysis
  • gap analysis

epppsynth

Private

A structured synthesis of existential psychotherapy literature for physicians and patients — corpus work applied to the parts of clinical life that resist quantification.

  • corpus synthesis
  • physician wellbeing

chesscomhistory

Private

A decade of personal game records as a longitudinal backbone for cross-analysis — a controlled sandbox for time-series and behavioral methods before they meet clinical data.

  • time series
  • API ingestion
  • methods sandbox

Some private work involves data that cannot be redistributed; the rest is simply unfinished. Neither is listed here as a placeholder for something that does not exist — ask, and I will walk you through any of it.

05

Technical toolkit

Languages

Python, SQL, R, JavaScript

Data engineering

DuckDB, Parquet, Polars, pandas, dbt-style modeling, reproducible pipelines

Clinical data

MIMIC-IV, OMOP concepts, ICD-10 / CPT terminologies, de-identification & disclosure discipline

Analysis & delivery

Simulation & discrete-event modeling, geospatial analysis, Streamlit, Git-based provenance