Reproductive Organoids for Disease Modelling
Source Kessler et al., 2015 · Max Planck Institute for Infection Biology, Berlin · 10.1038/ncomms9989
Abstract
This protocol describes the establishment and long-term maintenance of 3D organoid cultures derived from human fallopian tube epithelium. Single bipotent stem cells give rise to organoids that faithfully recapitulate the native mucosal fold architecture and can be stably expanded for over one year in culture. The organoids contain both ciliated and secretory cells and respond physiologically to Wnt, Notch, and hormonal signaling.
Protocol overview
27 steps across 7 phases
- a Tissue collection and transport
- b Tissue preparation and dissociation
- c Cell collection and resuspension
- d Primary culture in 2D
- a Cell detachment and preparation for 3D seeding
- b Matrigel polymerization
- c Expansion medium overlay
- d Initial organoid formation and assessment
- e Media exchange
- a Assessment of passaging interval
- b Matrigel dissolution
- c Mechanical fragmentation
- d Organoid replating
- e Post-passage culture establishment
- f Long-term stability assessment
- a FACS isolation of EpCAM+ cells
- b Single-cell seeding in Matrigel
- c Monoclonal organoid expansion
- a Notch inhibition with γ-secretase inhibitor DBZ
- b Assessment of differentiation phenotype
- a Hormone treatment
- b Tissue collection and RNA isolation
- c Gene expression analysis
- a Organoid fixation and processing
- b Immunofluorescent labeling
- c Confocal microscopy imaging
- d Transmission electron microscopy (optional)
Full SOP
Full SOPs need an account and a plan
Create an account, then get free Academic access (for verified academics) or choose a plan. Plans include step-by-step procedures, reagent concentrations, QC checklists and batch record templates.
Create an accountAlready registered? Log in
Attribution
This SOP was written by Organthis based on the published method in Kessler et al., 2015. Once the originating laboratory has confirmed it, the SOP is marked Verified.
Something wrong with this entry? Report an issue with this protocol