Abstract
BACKGROUND Digital technologies increasingly use intraoperative data to support documentation, workflow analysis, and clinical decision support. However, the potential contribution of audio to perioperative care is often reduced to speech transcription or unrestricted operating room recording. Orthopedic surgery is a relevant setting because documentation, procedural workflow and implant-bone interaction may all generate useful audio information. OBJECTIVE This study examined the perceived clinical roles, system requirements, and implementation conditions of purpose-bound intraoperative audio across documentation, workflow reconstruction, and mechanical monitoring to inform future perioperative technology design and validation. METHODS We conducted a qualitative formative study integrating 2 exploratory interview datasets: 6 interviews on audio-assisted documentation and workflow reconstruction and 9 interviews on acoustic monitoring during cementless femoral stem implantation as an orthopedic use case. Deductive-inductive qualitative content analysis was used to map coded meaning units to 3 functional domains and cross-layer requirements. Intercoder agreement was assessed for both focus areas. RESULTS Fifteen interviews yielded n=248 coded assignments for our developed layer framework: Documentation 76 (30.6%); Workflow Reconstruction, 42 (16.9%); Mechanical Monitoring, 89 (35.9%); and Cross-layer requirements, 41 (16.5%). The most frequently coded requirement categories were Process and Event Recognition (42/248, 16.9%), Usability (30/248, 12.1%), and Structured Reporting (24/248, 9.7%). Participants favored structured and editable reports, robust recognition of events and terminology, assistive mechanical feedback, passive operation, and purpose-limited data processing. CONCLUSIONS Purpose-bound intraoperative audio may support documentary, procedural, and mechanical functions beyond simple recording or transcription. Each function requires a separate validation strategy, while usability, privacy, workflow neutrality, interpretability, and clinician oversight remain shared implementation conditions.

This publication has 22 references indexed in Scilit: