Abstract Objective The aim of the study is to apply a sociotechnical model to the requirements phase of implementing a machine learning algorithm-based system to support sepsis recognition in the neonatal intensive care unit. Methods We incorporated components from the sociotechnical model, Safety in Engineering for Patient Safety 2.0, in three requirements phase activities: (1) semi-structured interviews, (2) user profiles, and (3) system use cases. Results Thirty-one neonatal intensive care unit clinicians participated in semi-structured interviews (11 nurses, 10 front line ordering clinician, five fellows, and five attending physician). Interview transcripts were coded and then compiled into themes deductively based on components from the sociotechnical model (persons, environment, organization, tasks, tools and technology, collaboration, and outcomes). The interview analysis was used to create four user profiles defining responsibilities in sepsis recognition, team collaboration, and attributes relevant to sepsis recognition. Two user profiles (nurse, front line ordering clinician) included variants based on experience relevant to sepsis recognition. The interview analysis was used to develop three system use cases representing clinical sepsis scenarios. Each use case defines the precondition, actors, and high-level sequence of actions, and includes variants based on sociotechnical works system factors that can complicate sepsis recognition. The interview analysis, user profiles, and use cases serve as the foundation for supporting sociotechnical design to all subsequent human-centered design methods including subject recruitment, formative design, summative user testing, and simulation testing. Conclusion Integration of the sociotechnical model-guided requirements gathering activities, analysis, and deliverables by framing a range of sociotechnical components and the interconnectedness of these components in the broader work system. Applying the sociotechnical model resulted in discovering work system, process, and outcome requirements that would otherwise be difficult to capture, or missed entirely, using traditional requirements gathering methods or approaches to clinical decision support design.