Surgical performance insight system background

Abstract

Examples described herein provide a surgical performance insight system that provides summaries and analysis of surgical cases. The surgical performance insight system can provide analytics and trends associated with surgical cases along with video playback. The surgical performance insight system can also provide a utilization dashboard to observe wider-scale interactions and engagement.

Description

[0001] P612928PC00

[0002] 1

[0003] SURGICAL PERFORMANCE INSIGHT SYSTEM

[0004] BACKGROUND

[0005] The present disclosure relates in general to computing technology and relates more particularly to computing technology for a surgical performance insight system.

[0006] Many devices and systems can generate and record data separately during surgical procedures. Interpreting the captured data and determining how such data can be useful is a complex process. Data captured as log data or raw recordings may not be readily interpretable by parties interested in analyzing such data. Identifying relevant data for comparison can also be challenging due to data complexity and quantity.

[0007] SUMMARY

[0008] According to an aspect, a computer-implemented method is provided. The method includes. The method also includes identifying a plurality of surgical case data associated with a group of users and a plurality of surgical case videos associated with a user of the group of users. The method also includes outputting to a first region of a first user interface, a graphical representation of one or more metrics derived from the surgical case data, and outputting to a second region of the first user interface, one or more links associated with a subset of the surgical case videos. The method further includes modifying the graphical representation of one or more metrics based on a command received through the first user interface to filter out a portion of the surgical case data associated with the group of users while continuing to display the links associated with the subset of the surgical case videos and providing access to view one of the surgical case videos through a second user interface based on detecting selection of a corresponding one of the links through the first user interface.

[0009] According to another aspect, a system includes a memory system and one or more processors coupled to the memory system and configured to execute a plurality of instructions to perform a plurality of operations. The operations include displaying a representative frame of a surgical case video in a video viewing region of a user interface based on receiving a selection of the surgical case video from a plurality of surgical case videos and displaying a performance region in the user interface, wherein the performance region is configured to display performance data associated with one or more surgical cases. The operations also include providing a complete case control in the user interface, where the complete case control is user selectable, and filtering a source data set used to populate the performance region to remove data from incomplete P612928PC00

[0010] 2 cases of the one or more surgical cases based on detecting a selection of the complete case control and one or more complete cases tags associated with the one or more surgical cases.

[0011] According to a further aspect, a computer program product includes a memory device having computer executable instructions stored thereon, which when executed by one or more processors cause the one or more processors to perform a plurality of operations. The operations include accessing a plurality of surgical case data associated with a plurality of users who share use of one or more surgical devices and outputting a video engagement summary in a graphical format in a user interface that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data. The operations further include outputting a procedure summary that summarizes procedure types associated with the surgical case data in the user interface, outputting user summary data of interactions with the surgical case videos, receiving one or more filter parameters, and adjusting one or more of: the video engagement summary, the procedure summary, and the user summary data based on the one or more filter parameters.

[0012] The above features and advantages, and other features and advantages, of the disclosure are readily apparent from the following detailed description when taken in connection with the accompanying drawings.

[0013] BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The specifics of the exclusive rights described herein are particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the aspects of the disclosure are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

[0015] FIG. 1 depicts a computer-assisted surgery (CAS) system according to one or more aspects;

[0016] FIG. 2 depicts a surgical procedure system according to one or more aspects;

[0017] FIG. 3A depicts a user interface providing surgical case data analysis and surgical case video links according to one or more aspects;

[0018] FIG. 3B depicts a user interface providing surgical case data analysis and surgical case video links after applying a filter according to one or more aspects; P612928PC00

[0019] 3

[0020] FIG. 4A depicts a user interface providing surgical case data analysis and other information through a mobile application according to one or more aspects;

[0021] FIG. 4B depicts a user interface providing procedure volume through a mobile application according to one or more aspects;

[0022] FIG. 40 depicts a user interface providing case details and links according to one or more aspects;

[0023] FIGS. 4D-4G depict a user interface providing case timings plotted for various durations according to one or more aspects;

[0024] FIG. 5A depicts a user interface for viewing a surgical case video and performance data analytics according to one or more aspects;

[0025] FIG. 5B depicts a user interface for viewing a surgical case video, an activity summary, and performance data analytics according to one or more aspects;

[0026] FIG. 50 depicts a user interface for viewing a surgical case video, timelines, and performance data analytics according to one or more aspects;

[0027] FIG. 6A depicts performance data analytics examples according to one or more aspects;

[0028] FIG. 6B depicts an auto-phase analysis example according to one or more aspects;

[0029] FIGS. 7A and 7B depict a user interface for viewing a surgical case video and performance data trends with a first case timings interface according to one or more aspects;

[0030] FIG. 70 depicts a user interface for viewing a surgical case video and performance data trends with a second case timings interface according to one or more aspects;

[0031] FIG. 7D depicts a user interface for viewing a surgical case video and performance data trends with insufficient data according to one or more aspects;

[0032] FIGS. 8A and 8B depict performance data trends examples according to one or more aspects;

[0033] FIGS. 9A, 9B, and 90 depict a user interface of a utilization dashboard with video engagement and procedure graphs according to one or more aspects;

[0034] FIG. 9D depicts a user interface of a utilization dashboard with procedure and device summaries according to one or more aspects;

[0035] FIGS. 9E, 9F, and 9G depict a user interface of a utilization dashboard with user interaction and procedure summaries according to one or more aspects;

[0036] FIG. 9H depicts a user interface of a utilization dashboard with pending invites and procedure summaries according to one or more aspects; P612928PC00

[0037] 4

[0038] FIG. 91 depicts a user interface of a utilization dashboard with procedure and device summaries according to one or more aspects;

[0039] FIG. 9J depicts a user interface of a utilization dashboard with a filter interface according to one or more aspects;

[0040] FIG. 9K depicts a user interface of a utilization dashboard with video engagement and procedure graphs according to one or more aspects;

[0041] FIG. 9L depicts a user interface of a utilization dashboard with insufficient data according to one or more aspects;

[0042] FIGS. 10A and 10B depict a filter interface according to one or more aspects;

[0043] FIG. 11 depicts a flowchart of a method according to one or more aspects; FIG. 12 depicts a flowchart of a method according to one or more aspects; FIG. 13 depicts a flowchart of a method according to one or more aspects; and

[0044] FIG. 14 depicts a block diagram of a computer system according to one or more aspects.

[0045] The diagrams depicted herein are illustrative. There can be many variations to the diagrams and / or the operations described herein without departing from the spirit of the described aspects. For instance, the actions can be performed in a differing order, or actions can be added, deleted, or modified. Also, the term “coupled” and variations thereof describe having a communications path between two elements and do not imply a direct connection between the elements with no intervening elements / connections between them. All of these variations are considered a part of the specification.

[0046] DETAILED DESCRIPTION

[0047] Exemplary aspects of the technical solutions described herein include systems and methods for surgical performance insights. T echnical challenges of surgical data viewing can include collecting data from multiple sources, such as video data, instrument data, patient data, surgical team data, and historical data and presenting the information in a meaningful way. For example, data may be collected with a different time base and format that can be challenging to align in time to coordinate the associated information. The associated data can be partitioned into case records with index information generated to allow for various performance statistics to be computed efficiently across case types, surgical groups, specific users, geographic locations, patient groups, and other such groupings. Having the associated information available and ready for viewing as close in time to surgical procedure completion can be challenging. Controlling data collection, tag generation, and other aspects during a surgical procedure can allow the P612928PC00

[0048] 5 resulting data sets to be processed more rapidly to coordinate and display the associated information without manual intervention. User interfaces of a surgical performance insight viewer can be designed for ease of navigation through large volumes of surgical data by providing a combination of summary data, detailed data, and various analytics for performance comparison. Technical solutions are described herein to address such technical challenges. Particularly, technical solutions herein provide surgical performance insight generation and display.

[0049] Turning now to FIG. 1 , an example computer-assisted system (CAS) system 100 is generally shown in accordance with one or more aspects. The CAS system 100 includes at least a computing system 102, a video recording system 104, and a surgical instrumentation system 106. As illustrated in FIG. 1 , an actor 112 can be medical personnel that uses the CAS system 100 to perform a surgical procedure on a patient 110. Medical personnel can be a surgeon, assistant, nurse, administrator, or any other actor that interacts with the CAS system 100 in a surgical environment. The surgical procedure can be any type of surgery. In other examples, actor 112 can be a technician, an administrator, an engineer, or any other such personnel that interacts with the CAS system 100. For example, actor 112 can record data from the CAS system 100, configure / update one or more attributes of the CAS system 100, review past performance of the CAS system 100, repair the CAS system 100, and / or the like including combinations and / or multiples thereof.

[0050] A surgical procedure can include multiple phases, and each phase can include one or more surgical actions. A “surgical action” can include an incision, a compression, a stapling, a clipping, a suturing, a cauterization, a sealing, or any other such actions performed to complete a phase in the surgical procedure. A “phase” represents a surgical event that is composed of a series of steps (e.g., closure). A “step” refers to the completion of a named surgical objective (e.g., hemostasis). During each step, certain surgical instruments 108 (e.g., forceps) are used to achieve a specific objective by performing one or more surgical actions. In addition, a particular anatomical structure of the patient may be the target of the surgical action(s).

[0051] The video recording system 104 includes one or more cameras 105, such as operating room cameras, endoscopic cameras, and / or the like including combinations and / or multiples thereof. The cameras 105 capture video data of the surgical procedure being performed. The video recording system 104 includes one or more video capture devices that can include cameras 105 placed in the surgical room to capture events surrounding P612928PC00

[0052] 6

[0053] (i.e. , outside) the patient being operated upon. The video recording system 104 further includes cameras 105 that are passed inside (e.g., endoscopic cameras) the patient 110 to capture endoscopic data. The endoscopic data provides video and images of the surgical procedure.

[0054] The computing system 102 includes one or more memory devices, one or more processors, a user interface device, among other components. All or a portion of the computing system 102 shown in FIG. 1 can be implemented for example, by all or a portion of computer system 1500 of FIG. 14. Computing system 102 can execute one or more computer-executable instructions. The execution of the instructions facilitates the computing system 102 to perform one or more methods, including those described herein. The computing system 102 can communicate with other computing systems via a wired and / or a wireless network.

[0055] A data collection system 150 can be employed to store the surgical data, including the video(s) captured during the surgical procedures. The data collection system 150 includes one or more storage devices 152. The data collection system 150 can be a local storage system, a cloud-based storage system, or a combination thereof. Further, the data collection system 150 can use any type of cloud-based storage architecture, for example, public cloud, private cloud, hybrid cloud, and / or the like including combinations and / or multiples thereof. In some examples, the data collection system can use a distributed storage, i.e., the storage devices 152 are located at different geographic locations. The storage devices 152 can include any type of electronic data storage media used for recording machine-readable data, such as semiconductor-based, magnetic-based, optical-based storage media, and / or the like including combinations and / or multiples thereof. For example, the data storage media can include flash-based solid-state drives (SSDs), magnetic-based hard disk drives, magnetic tape, optical discs, and / or the like including combinations and / or multiples thereof.

[0056] In one or more examples, the data collection system 150 can be part of the video recording system 104, or vice-versa. In some examples, the data collection system 150, the video recording system 104, and the computing system 102, can communicate with each other via a communication network, which can be wired, wireless, or a combination thereof. The communication between the systems can include the transfer of data (e.g., video data, instrumentation data, and / or the like including combinations and / or multiples thereof), data manipulation commands (e.g., browse, copy, paste, move, delete, create, compress, and / or the like including combinations and / or multiples thereof), data P612928PC00

[0057] 7 manipulation results, and / or the like including combinations and / or multiples thereof. In one or more examples, the computing system 102 can manipulate the data already stored / being stored in the data collection system 150. Alternatively, or in addition, the computing system 102 can manipulate the data already stored / being stored in the data collection system 150 based on information from the surgical instrumentation system 106.

[0058] In one or more examples, the video captured by the video recording system 104 is stored on the data collection system 150. In some examples, the computing system 102 curates parts of the video data being stored on the data collection system 150. In some examples, the computing system 102 filters the video captured by the video recording system 104 before it is stored on the data collection system 150. Alternatively, or in addition, the computing system 102 filters the video captured by the video recording system 104 after it is stored on the data collection system 150. Instrument data (e.g., robotic logs, electrosurgical instrument logs, etc.) can also be stored in the data collection system 150.

[0059] A surgical data management system 160 can provide access to portions of data captured in the data collection system 150, as well as data and records stored in other systems. The surgical data management system 160 can establish user access permissions to patient and surgical data. The surgical data management system 160 can also control access through an interface based on the user access permissions. Access to the surgical data management system 160 can be provided through one or more applications or secure web pages. The surgical data management system 160 can be a stand-alone application, module, and / or an extension of another system. Additional aspects of the surgical data management system 160 can include accessing artificial intelligence (Al)- powered surgical video and analytics. Further aspects of the surgical data management system 160 can include accessing simulation materials that can assist surgeons to prepare, practice, and teach surgical procedures. Further aspects of the surgical data management system 160 can include integrating aspects of equipment in an operating room, surgery planning, rating surgeon performance, and other such features. The surgical data management system 160 can also provide access to technical specifications and information relating to the use of surgical instruments, for example.

[0060] Turning now to FIG. 2, a surgical procedure system 200 is generally shown according to one or more aspects. The example of FIG. 2 depicts a surgical procedure support system 202 that can include or may be coupled to the CAS system 100 of FIG. 1. The P612928PC00

[0061] 8 surgical procedure support system 202 can acquire image or video data using one or more cameras 204. The surgical procedure support system 202 can also interface with one or more sensors 206 and / or one or more effectors 208. The sensors 206 may be associated with surgical support equipment and / or patient monitoring. The effectors 208 can be robotic components or other equipment controllable through the surgical procedure support system 202. The surgical procedure support system 202 can also interact with one or more user interfaces 210, such as various input and / or output devices. The surgical procedure support system 202 can store, access, and / or update surgical data 214 associated with a training dataset and / or live data as a surgical procedure is being performed on patient 110 of FIG. 1. The surgical procedure support system 202 can store, access, and / or update surgical objectives 216 to assist in training and guidance for one or more surgical procedures. User configurations 218 can track and store user preferences.

[0062] The surgical procedure support system 202 can also communicate with other systems through a network 230. For example, the surgical procedure support system 202 can communicate with a surgical performance insight viewer 240 and a surgical data postprocessing system 250 through the network 230. Other types of devices, such as a computing device 234 (e.g., a mobile phone, laptop, personal computer, or tablet computer), can communicate directly with the surgical procedure support system 202 or through the network 230. As one example, user interfaces 210 may be connected to or integrated with the surgical procedure support system 202 by a wired connection while the computing device 234 connects to the surgical procedure support system 202 via a wireless connection. In some aspects, the computing device 234 can execute or link to another computer system that executes the surgical data management system 160 of FIG. 1 to access various data sources through the network 230.

[0063] The surgical data post-processing system 250 can receive surgical data and associated data generated by the surgical procedure support system 202 and may be separately stored and secured through other data storage. Access to specific data or portions of data through the surgical data post-processing system 250 may be limited by associated permissions. The surgical data post-processing system 250 may include features such as video viewing, video sharing, data analytics, and selective data extraction. In some aspects, the surgical data post-processing system 250 can apply one or more machine learning models to generate case tags for surgical case videos. Tags can be metadata stored with an association to surgical case videos and need not be displayed with the surgical case videos. For example, tags can identify aspects such as timestamps within P612928PC00

[0064] 9 the surgical case video where events occur or transitions occur between steps or phases. Surgical phases, camera in / out events, instrument appearance (e.g., visible in video I not visible in video), case completion, and other such occurrences can be detected through video analysis using one or more machine learning models trained to identify such occurrences. Further, tags or annotations can be manually added, deleted, or edited as needed.

[0065] The surgical performance insight viewer 240 can provide viewing access to various data sources, such as surgical data 214, data collected in the one or more storage devices 152 of FIG. 1 , and post-processed data generated by the surgical data post-processing system 250. For example, surgical instrument data, video data, and artificial intelligence generated data can be accessed for viewing through the surgical performance insight viewer 240. The surgical data post-processing system 250 may generate surgical performance metrics and comparison data across data sets collected at multiple locations, making analytics data available to the surgical performance insight viewer 240. The surgical performance insight viewer 240 can preload case data for more than one case of a user, for example, when the user performs a login or otherwise activates the surgical performance insight viewer 240. In some aspects, the surgical performance insight viewer 240 and / or surgical data post-processing system 250 can be components of the surgical data management system 160 of FIG. 1.

[0066] One or more computing device 264 (e.g., a mobile phone, laptop, personal computer, or tablet computer), can execute the surgical data management system 160 of FIG. 1 to access various data sources through a network 260. The network 230 may be within a facility or multiple facilities maintained within a private network. The network 260 may be a wider area network, such as the internet. Accordingly, the networks 230 and 260 may have access to different files and data sets along with shared access to select files and data sets. In some aspects, networks 230 and 260 can be combined.

[0067] According to aspects, the surgical data management system 160 of FIG. 1 can provide multiple user interfaces and functions through the surgical performance insight viewer 240, such as those described with respect to FIGS. 3A-10B. Various user interfaces can be designed for specific types of devices, such as handheld mobile devices, for efficient navigation and display of content. Variations in the features and flow of transitions between user interfaces and content accessible through user interfaces can exist, for example, with respect to interactive interfaces for case summary data, case details, case tags, video viewers with supplemental information, phase analysis, insights, procedure P612928PC00

[0068] 10 volume, procedure analysis, performance metrics, instrument usage, outlier case identification, and other such aspects.

[0069] FIG. 3A depicts a user interface 300 providing surgical case data analysis and surgical case video links according to one or more aspects. The surgical performance insight viewer 240 can identify a plurality of surgical case data associated with a group of users and a plurality of surgical case videos associated with a user of the group of users. For example, the user may be presented logged in to the surgical performance insight viewer 240 and the group of users can be other users who are members of the same institution or work group. The surgical performance insight viewer 240 can output to a first region 302 of the user interface 300, a graphical representation of one or more metrics derived from surgical case data. In some aspects, the surgical case data can include tags and / or metrics identified by surgical data post-processing system 250 of FIG. 2. The surgical performance insight viewer 240 can also output to a second region 304 of the user interface 300, one or more links associated with a subset of the surgical case videos. The graphical representation of one or more metrics derived from surgical case data in the first region 302 can be interactive, through touch, click, tap, hover, or other gestures. For example, tapping on a chart segment 303 of a circular chart of the first region 302 can result in filtering data displayed in a bar chart of first region 302, as depicted in the example of FIG. 3B. Upon invoking a filtering action, a clear filter command 305 may be displayed to revert back to the full display of data as in FIG. 3A. Notably, adjusting filter criteria of the first region 302 need not impact or filter the links displayed through the second region 304. Links in the second region 304 can be separately filtered through searches or other filters, e.g., procedure type, surgeon, etc. In some aspects, filtering performed in either the first region 302 or the second region 304 can apply to both the first region 302 and the second region 304. The links in second region 304 can include a thumbnail style representative image of a video along with a title, tags, procedure type, lead surgeon name, date, and other such information. Selecting a link can result in a user interface transition to a case-based view.

[0070] FIG. 4A depicts a user interface 400 providing surgical case data analysis and other information through a mobile application according to one or more aspects, such as a mobile application aspect of surgical performance insight viewer 240. As one example, the user interface 400 may initially display a graphical representation 402 of one or more metrics derived from a plurality of surgical case data associated with a group of users. The user interface 400 can also display one or more live streaming sessions 404 and a link 406 to a recently uploaded surgical case video, and wherein the link is reachable P612928PC00

[0071] 11 through one or more of a procedure volume or a case selection interface. Scrolling, tapping, or other gestures detected through the user interface 400 can result in the surgical performance insight viewer 240 modifying content displayed on the user interface 400. As one example, scrolling or tapping on the user interface 400 (e.g., tapping on graphical representation 402) can navigate to user interface 410 of FIG. 4B. The example of FIG. 4B can further breakdown procedure volume information, for example, to illustrate a distribution of total cases across procedure types and an average time per procedure. The user interface 410 can also include a view all cases command 414 that transitions to user interface 420 of FIG. 4G. User interface 420 can display a plurality of links 422 to cases with corresponding videos. The user interface 420 can also include a search interface 424 to search / filter the list of cases and associated links 422. While a set of user interfaces 400, 410, 420 are depicted in the example of FIGS. 4A-4C, it will be understood that other interfaces described herein can be scaled to fit various sized displays, such as mobile devices, tablets, desktop computers, laptop computers, and the like.

[0072] FIGS. 4D-4G depict a user interface 430 providing case timings plotted for various durations according to one or more aspects. The user interface 430 can be sized to fit a display of a mobile device, tablet computer, or other device. Case timing data can be displayed with various levels of granularity depending on whether an all-time case duration 432 is selected as in FIG. 4D, a six-month case duration 434 is selected as in FIG. 4E, a 1 -month case duration 436 is selected as in FIG. 4F, or a 1-week case duration 438 is selected as in FIG. 4G. As the duration changes, values can be visually depicted by grouping / averaging values for each duration range. Although specific durations are depicted in the examples of FIGS. 4D-4G, other case duration time ranges are contemplated.

[0073] FIG. 5A depicts a user interface 500 for viewing a surgical case video and performance data analytics according to one or more aspects. The user interface 500 can be generated by the surgical performance insight viewer 240 and may be reached through the links of FIGS. 3A, 3B, 4A, 4C, for example. Performance data analytics can be determined by the surgical performance insight viewer 240, surgical data postprocessing system 250, and / or other components of the surgical procedure support system 202 of FIG. 2. In some aspects, the surgical performance insight viewer 240 can display a representative frame of a surgical case video in a video viewing region 502 of the user interface 500 based on receiving a selection of the surgical case video. The surgical performance insight viewer 240 can display a performance region 504 in the P612928PC00

[0074] 12 user interface 500, where the performance region 504 is configured to display performance data associated with one or more surgical cases. The performance region 504 can include a selection control 510 to toggle between workflow, analytics, and trends, for example. Further, the performance region 504 can include a complete case control 512 in the user interface 500, where the complete case control 512 is user selectable. A source data set used to populate the performance region 504 can be filtered to remove data from incomplete cases of the one or more surgical cases based on detecting a selection of the complete case control 512 and one or more complete cases tags associated with the one or more surgical cases. For example, complete case tags can be added during analysis by the surgical data post-processing system 250 for instance, using a machine learning model that identifies surgical phases, confirms that a final surgical phase is reached, and confirms that a camera out event follows the final surgical phase for a laparoscopic surgery example. In some aspects, a case completion tag can be visually indicated, such as complete recording tag 511. Various analytics can be displayed in the performance region 504, such as a case overview 506 and an autophase analysis chart 508.

[0075] The user interface 500 can also include other information and interactive controls. For example, a summary region 520 can document a procedure name, surgeons active in the case, a date, sharing, download, timelines 521 , and an activity command 522. Selecting the activity command can trigger the surgical performance insight viewer 240 to display a popup chart 530 that is selectable to display one of: the number of views chart, the number of downloads chart, or the number of shares chart in response to a user selection, as depicted in the example of FIG. 5B. The popup chart 530 can be interactive, allowing selection (e.g., hover, tap, click, etc.) of a point in time to see who watched the video, shared the video, or downloaded the video, for instance. Selecting the timelines 521 of FIG. 5A can display a plurality of timelines 524 that indicate an occurrence of an event, phase, or transition appearing at a time within a surgical case video displayed in the video viewing region 502. For example, the timelines 524 can include an auto-phase that identifies portions of the surgical case video where particular surgical phases have been identified to occur, camera in / out (e.g., a camera duration timeline), surgical tools, anatomy, and other such information. A slider 526 can be user selectable to move the current play time of the surgical case video displayed in the video viewing region 502 forward or backward in time.

[0076] FIG. 6A depicts performance data analytics examples that can be displayed, for example, in the performance region 504 of user interface 500, according to one or more P612928PC00

[0077] 13 aspects. A case overview 506 can summarize information, such as video length, case duration, endoscopic time, camera out time, camera out occurrences, and other such information for the current case, an average for the user, and a larger-scale average, such as institutional, regional, or global averages. An instrument time in-view chart 507 can indicate a percentage of time that each surgical instrument of a plurality of instruments appeared in-view for the current case, an average for the user, and a larger- scale average, such as institutional, regional, or global averages. An anatomy time inview chart 509 can depict a percentage of time the particular anatomy appeared in-view for the current case, an average for the user, and a larger-scale average, such as institutional, regional, or global averages.

[0078] FIG. 6B depicts an auto-phase analysis chart 508 example that can be displayed, for example, in the performance region 504 of user interface 500, according to one or more aspects. The auto-phase analysis chart 508 can include a circular chart portion 602 and a table portion 604. The circular chart portion 602 can visualize relative percentages of each automatically detected phase as a percentage of total case duration. The table portion 604 can include details about each of the phases, such as a phase name, a phase time for the current case, an average for the user, and a larger-scale average, such as institutional, regional, or global averages for the same surgical procedure. Further, the table portion may highlight certain aspects, such as times in the current case where the time was below or above a threshold level relative to benchmark values.

[0079] FIGS. 7A and 7B depict the user interface 500 for viewing a surgical case video and performance data trends with a first case timings interface according to one or more aspects. In the example of FIG. 7A, a portion of a case timings chart 702 and a phase timings chart 704 can be displayed by the surgical performance insight viewer 240 when the selection control 510 is set to display trends. The case timings chart 702 and a phase timings chart 704 can be user interactive and identify where the current case fits relative to other cases, along with trends, distributions, and larger-scale averages. With regard to phase timings, one or more phases can be selected through the phase timings chart 704 to show the associated trends and data. As depicted in the example of FIG. 7B, with regard to case timings, the timing source can be selected, for instance, as case duration, endoscopic time, camera out time, etc.

[0080] FIG. 70 depicts a user interface 500 for viewing a surgical case video and performance data trends with a second case timings interface according to one or more aspects. In the example of FIG. 70, a portion of a case timings chart 722 and a phase timings chart P612928PC00

[0081] 14

[0082] 724 can be displayed by the surgical performance insight viewer 240 when the selection control 510 is set to display trends. The case timings chart 722 and a phase timings chart 724 can be user interactive and identify where the current case fits relative to other cases, along with trends, distributions, and larger-scale averages. The case timings chart 722 can include a selectable timeline 723 to rescale a range of results depicted in the case timings chart 722, for instance, by using a sliding or dragging gesture to shift a left and / or right boundary of the selectable timeline 723. Alternatively, a pinching I spreading gesture can be used to adjust the active range on the selectable timeline 723 and rescale the case timings chart 722 accordingly. Further, the case timings chart 722 can support a hover operation to tap or hold on a position or proximate to a data point displayed on the case timings chart 722 and reveal underlying data. In some aspects, a popup that appears upon a hover or tap gesture on the case timings chart 722 can include an active link to navigate to a case associated with a selected data point.

[0083] FIG. 7D depicts a user interface 500 for viewing a surgical case video and performance data trends with insufficient data according to one or more aspects. Where there is insufficient data to establish a trend, such as less than 5 cases, less than 3 cases, or another threshold level, an insufficient data graphic 732 can be displayed rather than a trend chart. This may indicate an underlying data error, such as failing to locate associated videos and data, or it can indicate an early stage of data collection, where trend data may not be sufficient to be statistically meaningful.

[0084] FIGS. 8A and 8B depict performance data trends examples according to one or more aspects with respect to the case timings chart 702. For example, hovering over a datapoint can indicate an associated value 802. Clicking or tapping on a datapoint can open a case summary popup 804, as depicted in FIG. 8B, that may allow navigation to view the case associated with the datapoint. Navigation to a newly selected case may open a new window or otherwise transition load associated case data of the selected case. Similar functionality can be provided through other charts, such as the phase timings chart 704. Data used for the case timings chart 702 and a phase timings chart 704 can be filtered based on the state of the complete case control 512.

[0085] FIGS. 9A, 9B, and 9C depict a user interface 900 of a utilization dashboard with video engagement and procedure graphs according to one or more aspects. In some aspects, the surgical performance insight viewer 240 can interactively display the utilization dashboard through the user interface 900. The surgical performance insight viewer 240 can access a plurality of surgical case data associated with a plurality of users who share P612928PC00

[0086] 15 use of one or more surgical devices. The surgical performance insight viewer 240 can output a video engagement summary 902 in a graphical format that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data. The surgical performance insight viewer 240 can also output a procedure summary 904 that summarizes procedure types associated with the surgical case data and output user summary data 906 of interactions with the surgical case videos. The user interface 900 can also include a filter control 908 configured to receive one or more filter parameters. The surgical performance insight viewer 240 can adjust one or more of: the video engagement summary 902, the procedure summary 904, and the user summary data 906 based on the one or more filter parameters. The user interface 900 can also include controls 910, which may trigger actions such as downloading or printing a page (e.g., in various file formats), customizing the layout of the utilization dashboard (e.g., rearrange components), help / feedback, settings (e.g., personalize to override default values), and other such actions. In the example of FIG. 9A, the video engagement summary 902 illustrates a chart of video uploads 903 by case type and date, and the procedure summary 904 is displayed as a circular chart. In some aspects, the layout of the procedure summary 904 can be selectable between a chart, a list view, and a detailed view that includes additional information. In the example of FIG. 9B, the video engagement summary 902 illustrates a chart of video views 905 by case type and date. In the example of FIG. 9C, a user interaction, such as hovering over the procedure summary 904 provides an information popup 907 to describe a portion of the chart receiving focus.

[0087] FIG. 9D depicts user interface 900 of the utilization dashboard with procedure and device summaries according to one or more aspects. Procedure summary 912 can expand the procedure summary 904 to list procedure types, a total uploaded, a monthly average, users, and other such information. Device summary 914 can display a shared device usage table of devices (e.g., surgical recording devices) used at various locations, total uploaded videos, total procedures, total active days used, users, and other such information. The device information can be used to identify over or under utilized equipment, which may also be indicative of a future need to adjust resources, modify capacity, plan maintenance, and other such actions. As a further example, other information that can be displayed may include videos stored on a device as a percentage of memory capacity, a capacity alert if available storage is below an alert threshold, and / or software version information. P612928PC00

[0088] 16

[0089] FIGS. 9E, 9F, and 9G depict user interface 900 of the utilization dashboard with user interaction and procedure summaries according to one or more aspects. The user summary data 906 can indicate details, such as an active surgeons table, a pending surgeons table, a deactivated surgeons table. For example, the active surgeons table can indicate a number of surgeons actively performing video uploads and video viewing, which may include tracking and displaying total uploaded videos, average monthly uploaded videos, total procedures, total views, an a graphical breakdown of video uploads (e.g., graphic of case duration per procedure). The user summary data 906 can be interactive, such as displaying underlying details in a popup 915 upon detecting hovering over a summarized value, as depicted in the example of FIG. 9F. Similarly, hovering over graphical content, such as the graphic of case duration per procedure, can trigger displaying a popup 917 to provide further details, such as procedure type, number of cases, percentages, and other such information.

[0090] FIG. 9H depicts a user interface 900 of a utilization dashboard with pending invites and procedure summaries according to one or more aspects. The user summary data 906 can include a list of pending invites 919, which may indicate users who have been invited to view or upload videos but have not accepted and become active users yet.

[0091] FIG. 9I depicts user interface 900 of a utilization dashboard with procedure and device summaries according to one or more aspects. The procedure summary 912 can list procedures including a graphical indication that may be scaled based on total uploaded videos or other relevant information (e.g., total case duration, etc.). The procedure summary 912 can also include a complete case control 913 that is user selectable to filter the data displayed in the procedure summary 912 to include or exclude incomplete cases based on inclusion of a complete recording tag with the underlying data.

[0092] FIG. 9J depicts user interface 900 of a utilization dashboard with a filter interface 918 according to one or more aspects. The filter interface 918 can support filtering a variety of parameters, such as one or more of: an upload date range, a surgical approach, a surgeon, a procedure type, a device, and engagement metrics.

[0093] FIG. 9K depicts a user interface 900 of a utilization dashboard with video engagement and procedure graphs according to one or more aspects. The surgical performance insight viewer 240 of FIG. 2 can output a video engagement summary 922 in a graphical format that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case P612928PC00

[0094] 17 data, for example, as a bar chart arranged by date and color coded by procedure type. The surgical performance insight viewer 240 can also output a procedure summary 924 that summarizes procedure types associated with the surgical case data, for instance, as a circle chart, and output user summary data 926 of interactions with the surgical case videos. The user summary data 926 can include various groupings of information, such as for active users, pending invites, and off-boarded users. Further, the user summary data 926 can include data about users, total uploads, average uploads per unit of time, average views per unit of time, average shares per unit of time, average downloads per unit of time, procedure types, procedure breakdown, and / or other such information. The procedure breakdown can be graphically depicted as bars scaled based on a number of videos for each procedure type relative to the total number of videos.

[0095] In the example of FIG. 9K, a user interaction, such as hovering over the procedure summary 924 provides an information popup 927 to describe a portion of the chart receiving focus. Hovering, tapping, or clicking over other portions of the user interface 900 can result in other information popups appearing.

[0096] FIG. 9L depicts a user interface 900 of a utilization dashboard with insufficient data according to one or more aspects. Where there is insufficient data to generate a graph, such as less than 2 cases, less than 1 case, or another threshold level, an insufficient data graphic 932 can be displayed rather than a circle chart and / or bar chart. This may indicate an underlying data error, such as failing to locate associated videos and data, or it can indicate an early stage of data collection where trend data may not be sufficient to be statistically meaningful. In such an instance, user summary data 936 may also display a message indicating that no user data is available.

[0097] FIGS. 10A and 10B depict filter interface 918 according to one or more aspects with different filter parameters set. For example, in FIG. 10A, an upload date range filter 1002 can support selections of date ranges in terms of fiscal years, year, quarters, months, weeks, or days. As a further example, as illustrated in FIG. 10B, a surgeon filter 1004 can allow all surgeons with data to be selected or any individual or sub-combination to be selected for analysis as source data. Similarly, each filter type can be separately selected to provide flexibility in data source selection for visualization through the utilization dashboard.

[0098] Turning now to FIG. 11 , a flowchart of a method 1100 for surgical performance insight generation and display is generally shown in accordance with one or more aspects. All P612928PC00

[0099] 18 or a portion of method 1100 can be implemented, for example, by all or a portion of CAS system 100 of FIG. 1 , the system 200 of FIG. 2, and / or computer system 1500 of FIG. 14, for instance through execution of the surgical data management system 160. For purposes of explanation, the method 1100 is described with respect to the surgical performance insight viewer 240.

[0100] At block 1102, the surgical performance insight viewer 240 can identify a plurality of surgical case data associated with a group of users and a plurality of surgical case videos associated with a user of the group of users. At block 1104, the surgical performance insight viewer 240 can output to a first region 302 of a first user interface 300, a graphical representation of one or more metrics derived from the surgical case data. At block 1106, the surgical performance insight viewer 240 can output to a second region 304 of the first user interface 300, one or more links associated with a subset of the surgical case videos. At block 1108, the surgical performance insight viewer 240 can modify the graphical representation of one or more metrics based on a command received through the first user interface 300 to filter out a portion of the surgical case data associated with the group of users while continuing to display the links associated with the subset of the surgical case videos. For example, the filter command can be based on detecting a tap or click on a chart segment 303 of the first region 302. At block 1110, the surgical performance insight viewer 240 can provide access to view one of the surgical case videos through a second user interface 500 based on detecting selection of a corresponding one of the links through the first user interface 300.

[0101] In some aspects, the surgical performance insight viewer 240 can modify the graphical representation 402 in user interface 400 in a mobile application aspect in block 1110. Further, in a mobile application aspect, link selection can be performed through user interface 400 or user interface 420 in block 1112.

[0102] According to some aspects, the graphical representation of one or more metrics derived from the surgical case data can be configured to display one or more of a procedure breakdown chart, a number of uploads and downloads over time chart, and an average procedure time.

[0103] According to an aspect, the surgical performance insight viewer 240 can display a representative frame of a surgical case video in a video viewing region 502 of the second user interface 500 based on receiving a selection of the surgical case video from the subset of the surgical case videos and display a performance region 504 in the second P612928PC00

[0104] 19 user interface 500, where the performance region 504 is configured to display performance data associated with one or more surgical cases.

[0105] According to an aspect, the surgical performance insight viewer 240 can provide a complete case control 512 in the second user interface 500, where the complete case control 512 is user selectable and filter a source data set used to populate the performance region 504 to remove data from incomplete cases of the one or more surgical cases based on detecting a selection of the complete case control 512 and one or more complete cases tags associated with the one or more surgical cases.

[0106] According to an aspect, the second user interface 500 can be configured to display one or more of: a number of views chart, a number of downloads chart, a number of shares chart, a camera duration timeline, one or more benchmark comparisons, and one or more trend charts.

[0107] According to an aspect, the surgical performance insight viewer 240 can display a popup chart 530 that is selectable to display one of: the number of views chart, the number of downloads chart, or the number of shares chart in response to a user selection.

[0108] According to an aspect, the surgical performance insight viewer 240 can display the camera duration timeline in a summary region 520 of the second user interface 500, where the camera duration timeline includes a slider 526 that controls playback of the surgical case video in the video viewing region 502.

[0109] According to an aspect, the performance region 504 can display one or more of the benchmark comparisons and one or more trend charts based on detecting a user input.

[0110] According to an aspect, the one or more of the benchmark comparisons can include one or more of a case overview, an auto-phase analysis, an instrument time in-view, and an anatomy time in-view.

[0111] According to an aspect, the one or more trend charts can include one or more of phase timings and case timings with a selectable interface to identify and view cases from the one or more trend charts.

[0112] According to an aspect, the surgical performance insight viewer 240 can access a plurality of surgical case data associated with a plurality of users who share use of one P612928PC00

[0113] 20 or more surgical devices and output a video engagement summary in a graphical format in a third user interface 900 that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data. Further, the surgical performance insight viewer 240 can output a procedure summary that summarizes procedure types associated with the surgical case data in the third user interface 900 and output user summary data of interactions with the surgical case videos.

[0114] According to an aspect, the surgical performance insight viewer 240 can receive one or more filter parameters and adjust one or more of: the video engagement summary, the procedure summary, and the user summary data based on the one or more filter parameters.

[0115] According to an aspect, the third user interface 900 can be configured to display one or more of: a videos uploaded chart, a procedure type chart, an active surgeons table, a pending surgeons table, a deactivated surgeons table, and shared device usage table.

[0116] The processing shown in FIG. 11 is not intended to indicate that the operations are to be executed in any particular order or that all of the operations shown in FIG. 11 are to be included in every case. Additionally, the processing shown in FIG. 11 can include any suitable number of additional operations.

[0117] Turning now to FIG. 12, a flowchart of a method 1200 for surgical performance insight generation and display is generally shown in accordance with one or more aspects. All or a portion of method 1200 can be implemented, for example, by all or a portion of CAS system 100 of FIG. 1 , the system 200 of FIG. 2, and / or computer system 1500 of FIG. 14, for instance through execution of the surgical data management system 160. For purposes of explanation, the method 1200 is described with respect to the surgical performance insight viewer 240.

[0118] At block 1202, the surgical performance insight viewer 240 can display a representative frame of a surgical case video in a video viewing region 502 of a user interface 500 based on receiving a selection of the surgical case video from a plurality of surgical case videos.

[0119] At block 1204, the surgical performance insight viewer 240 can display a performance region 504 in the user interface 500, where the performance region 504 is configured to display performance data associated with one or more surgical cases. P612928PC00

[0120] 21

[0121] In some aspects, at block 1206, the surgical performance insight viewer 240 can provide a complete case control 512 in the user interface 500, where the complete case control 512 is user selectable.

[0122] In some aspects, at block 1208, the surgical performance insight viewer 240 can filter a source data set used to populate the performance region 504 to remove data from incomplete cases of the one or more surgical cases based on detecting a selection of the complete case control 512 and one or more complete cases tags associated with the one or more surgical cases.

[0123] In some aspects, the user interface 500 can be displayed in response to a selection of a link made through an application configured to display a graphical representation of one or more metrics derived from a plurality of surgical case data associated with a group of users.

[0124] In some aspects, the application can be a mobile application configured to display one or more live streaming sessions and a link to a recently uploaded surgical case video, and the link can be reachable through one or more of a procedure volume or a case selection interface.

[0125] In some aspects, the surgical performance insight viewer 240 can access a plurality of surgical case data associated with a plurality of users who share use of one or more surgical devices and output a video engagement summary in a graphical format that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data. The surgical performance insight viewer 240 can output a procedure summary that summarizes procedure types associated with the surgical case data and output user summary data of interactions with the surgical case videos.

[0126] The processing shown in FIG. 12 is not intended to indicate that the operations are to be executed in any particular order or that all of the operations shown in FIG. 12 are to be included in every case. Additionally, the processing shown in FIG. 12 can include any suitable number of additional operations.

[0127] Turning now to FIG. 13, a flowchart of a method 1300 for surgical performance insight generation and display is generally shown in accordance with one or more aspects. All P612928PC00

[0128] 22 or a portion of method 1300 can be implemented, for example, by all or a portion of CAS system 100 of FIG. 1 , the system 200 of FIG. 2, and / or computer system 1500 of FIG. 14, for instance through execution of the surgical data management system 160. For purposes of explanation, the method 1300 is described with respect to the surgical performance insight viewer 240.

[0129] At block 1302, the surgical performance insight viewer 240 can access a plurality of surgical case data associated with a plurality of users who share use of one or more surgical devices.

[0130] At block 1304, the surgical performance insight viewer 240 can output a video engagement summary in a graphical format in a user interface 900 that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data.

[0131] At block 1306, the surgical performance insight viewer 240 can output a procedure summary that summarizes procedure types associated with the surgical case data in the user interface 900.

[0132] At block 1308, the surgical performance insight viewer 240 can output user summary data of interactions with the surgical case videos.

[0133] In some aspects, at block 1310, the surgical performance insight viewer 240 can receive one or more filter parameters.

[0134] In some aspects, at block 1312, the surgical performance insight viewer 240 can adjust one or more of: the video engagement summary, the procedure summary, and the user summary data based on the one or more filter parameters.

[0135] In some aspects, the one or more filter parameters can include one or more of: an upload date range, a surgical approach, a surgeon, a procedure type, a device, and engagement metrics.

[0136] In some aspects, the surgical performance insight viewer 240 can provide a complete case control 913 in the user interface 900, where the complete case control 913 is user selectable and a source data set used to populate the procedure summary to remove data from incomplete cases of the one or more surgical cases is filtered based on P612928PC00

[0137] 23 detecting a selection of the complete case control 913 and one or more complete cases tags associated with the one or more surgical cases.

[0138] The processing shown in FIG. 13 is not intended to indicate that the operations are to be executed in any particular order or that all of the operations shown in FIG. 13 are to be included in every case. Additionally, the processing shown in FIG. 13 can include any suitable number of additional operations.

[0139] The methods of FIGS. 11 , 12, and 13 can be embodied in various forms. For example, a system can include a memory system and one or more processors coupled to the memory system and configured to execute a plurality of instructions to perform a plurality of operations. The operations can include any number of steps of method 1100, 1200, and / or 1300.

[0140] As a further example, a computer program product can include a memory device having computer executable instructions stored thereon, which when executed by one or more processors cause the one or more processors to perform a plurality of operations. The operations can include any number of steps of method 1100, 1200, and / or 1300.

[0141] Turning now to FIG. 14, a computer system 1500 is generally shown in accordance with an aspect. The computer system 1500 can be an electronic computer framework comprising and / or employing any number and combination of computing devices and networks utilizing various communication technologies, as described herein. The computer system 1500 can be easily scalable, extensible, and modular, with the ability to change to different services or reconfigure some features independently of others. The computer system 1500 may be, for example, a server, desktop computer, laptop computer, tablet computer, or smartphone. In some examples, computer system 1500 may be a cloud computing node. Computer system 1500 may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system 1500 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media, including memory storage devices. P612928PC00

[0142] 24

[0143] As shown in FIG. 14, the computer system 1500 has one or more central processing units (CPll(s)) 1501a, 1501b, 1501c, etc. (collectively or generically referred to as processor(s) 1501). The processors 1501 can be a single-core processor, multi-core processor, computing cluster, or any number of other configurations. The processors 1501 can be any type of circuitry capable of executing instructions. The processors 1501 , also referred to as processing circuits, are coupled via a system bus 1502 to a system memory 1503 and various other components. The system memory 1503 can include one or more memory devices, such as read-only memory (ROM) 1504 and a random-access memory (RAM) 1505. The ROM 1504 is coupled to the system bus 1502 and may include a basic input / output system (BIOS), which controls certain basic functions of the computer system 1500. The RAM is read-write memory coupled to the system bus 1502 for use by the processors 1501. The system memory 1503 provides temporary memory space for operations of said instructions during operation. The system memory 1503 can include random access memory (RAM), read-only memory, flash memory, or any other suitable memory systems.

[0144] The computer system 1500 comprises an input / output (I / O) adapter 1506 and a communications adapter 1507 coupled to the system bus 1502. The I / O adapter 1506 may be a small computer system interface (SCSI) adapter that communicates with a hard disk 1508 and / or any other similar component. The I / O adapter 1506 and the hard disk 1508 are collectively referred to herein as a mass storage 1510.

[0145] Software 1511 for execution on the computer system 1500 may be stored in the mass storage 1510. The mass storage 1510 is an example of a tangible storage medium readable by the processors 1501 , where the software 1511 is stored as instructions for execution by the processors 1501 to cause the computer system 1500 to operate, such as is described hereinbelow with respect to the various Figures. Examples of computer program product and the execution of such instruction is discussed herein in more detail. The communications adapter 1507 interconnects the system bus 1502 with a network 1512, which may be an outside network, enabling the computer system 1500 to communicate with other such systems. In one aspect, a portion of the system memory 1503 and the mass storage 1510 collectively store an operating system, which may be any appropriate operating system to coordinate the functions of the various components shown in FIG. 14.

[0146] Additional input / output devices are shown as connected to the system bus 1502 via a display adapter 1515 and an interface adapter 1516 and. In one aspect, the adapters P612928PC00

[0147] 25

[0148] 1506, 1507, 1515, and 1516 may be connected to one or more I / O buses that are connected to the system bus 1502 via an intermediate bus bridge (not shown). A display 1519 (e.g., a screen or a display monitor) is connected to the system bus 1502 by a display adapter 1515, which may include a graphics controller to improve the performance of graphics-intensive applications and a video controller. A keyboard, a mouse, a touchscreen, one or more buttons, a speaker, etc., can be interconnected to the system bus 1502 via the interface adapter 1516, which may include, for example, a Super I / O chip integrating multiple device adapters into a single integrated circuit. Suitable I / O buses for connecting peripheral devices such as hard disk controllers, network adapters, and graphics adapters typically include common protocols, such as the Peripheral Component Interconnect (PCI). Thus, as configured in FIG. 14, the computer system 1500 includes processing capability in the form of the processors 1501 , and storage capability including the system memory 1503 and the mass storage 1510, input means such as the buttons, touchscreen, and output capability including the speaker 823 and the display 1519.

[0149] In some aspects, the communications adapter 1507 can transmit data using any suitable interface or protocol, such as the internet small computer system interface, among others. The network 1512 may be a cellular network, a radio network, a wide area network (WAN), a local area network (LAN), or the Internet, among others. An external computing device may connect to the computer system 1500 through the network 1512. In some examples, an external computing device may be an external web server or a cloud computing node.

[0150] It is to be understood that the block diagram of FIG. 14 is not intended to indicate that the computer system 1500 is to include all of the components shown in FIG. 14. Rather, the computer system 1500 can include any appropriate fewer or additional components not illustrated in FIG. 14 (e.g., additional memory components, embedded controllers, modules, additional network interfaces, etc.). Further, the aspects described herein with respect to computer system 1500 may be implemented with any appropriate logic, wherein the logic, as referred to herein, can include any suitable hardware (e.g., a processor, an embedded controller, or an application-specific integrated circuit, among others), software (e.g., an application, among others), firmware, or any suitable combination of hardware, software, and firmware, in various aspects. Various aspects can be combined to include two or more of the aspects described herein. P612928PC00

[0151] 26

[0152] Aspects disclosed herein may be a system, a method, and / or a computer program product at any possible technical detail level of integration. The computer program product may include a computer-readable storage medium (or media) having computer- readable program instructions thereon for causing a processor to carry out various aspects.

[0153] The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non- exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device, such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

[0154] Computer-readable program instructions described herein can be downloaded to respective computing / processing devices from a computer-readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network, and / or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer-readable program instructions from the network and forwards the computer- readable program instructions for storage in a computer-readable storage medium within the respective computing / processing device.

[0155] Computer-readable program instructions for carrying out operations of the present disclosure may be assembler instructions, instruction-set-architecture (ISA) instructions, P612928PC00

[0156] 27 machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source-code or object code written in any combination of one or more programming languages, including an object-oriented programming language, such as Smalltalk, C++, high-level languages such as Python, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user’s computer, partly on the user’s computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user’s computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some aspects, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instruction by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.

[0157] Aspects are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to aspects of the disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0158] These computer-readable program instructions may be provided to a processor of a computer system, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function / act specified in the flowchart and / or block diagram block or blocks. P612928PC00

[0159] 28

[0160] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0161] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various aspects. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustration, and combinations of blocks in the block diagrams and / or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[0162] The descriptions of the various aspects have been presented for purposes of illustration but are not intended to be exhaustive or limited to the aspects disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described aspects. The terminology used herein was chosen to best explain the principles of the aspects, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the aspects described herein.

[0163] Various aspects are described herein with reference to the related drawings. Alternative aspects can be devised without departing from the scope of this disclosure. Various connections and positional relationships (e.g., over, below, adjacent, etc.) are set forth between elements in the following description and in the drawings. These connections and / or positional relationships, unless specified otherwise, can be direct or indirect, and the present disclosure is not intended to be limiting in this respect. Accordingly, a P612928PC00

[0164] 29 coupling of entities can refer to either a direct or an indirect coupling, and a positional relationship between entities can be a direct or indirect positional relationship. Moreover, the various tasks and process steps described herein can be incorporated into a more comprehensive procedure or process having additional steps or functionality not described in detail herein.

[0165] The following definitions and abbreviations are to be used for the interpretation of the claims and the specification. As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” “contains,” or “containing,” or any other variation thereof are intended to cover a non-exclusive inclusion. For example, a composition, a mixture, process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but can include other elements not expressly listed or inherent to such composition, mixture, process, method, article, or apparatus.

[0166] Additionally, the term “exemplary” is used herein to mean “serving as an example, instance or illustration.” Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. The terms “at least one” and “one or more” may be understood to include any integer number greater than or equal to one, i.e., one, two, three, four, etc. The terms “a plurality” may be understood to include any integer number greater than or equal to two, i.e., two, three, four, five, etc. The term “connection” may include both an indirect “connection” and a direct “connection.”

[0167] The terms “about,” “substantially,” “approximately,” and variations thereof are intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example, “about” can include a range of ± 8% or 5%, or 2% of a given value.

[0168] For the sake of brevity, conventional techniques related to making and using aspects may or may not be described in detail herein. In particular, various aspects of computing systems and specific computer programs to implement the various technical features described herein are well known. Accordingly, in the interest of brevity, many conventional implementation details are only mentioned briefly herein or are omitted entirely without providing the well-known system and / or process details.

[0169] It should be understood that various aspects disclosed herein may be combined in different combinations than the combinations specifically presented in the description P612928PC00

[0170] 30 and accompanying drawings. It should also be understood that, depending on the example, certain acts or events of any of the processes or methods described herein may be performed in a different sequence, may be added, merged, or left out altogether (e.g., all described acts or events may not be necessary to carry out the techniques). In addition, while certain aspects of this disclosure are described as being performed by a single module or unit for purposes of clarity, it should be understood that the techniques of this disclosure may be performed by a combination of units or modules associated with, for example, a medical device.

[0171] In one or more examples, the described techniques may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include non-transitory computer-readable media, which corresponds to a tangible medium, such as data storage media (e.g., RAM, ROM, EEPROM, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer).

[0172] Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), graphics processing units (GPUs), microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor” as used herein may refer to any of the foregoing structure or any other physical structure suitable for implementation of the described techniques. Also, the techniques could be fully implemented in one or more circuits or logic elements.

Claims

P612928PC0031CLAIMSWhat is claimed is:1 . A computer-implemented method comprising: identifying a plurality of surgical case data associated with a group of users and a plurality of surgical case videos associated with a user of the group of users; outputting to a first region (302) of a first user interface (300), a graphical representation of one or more metrics derived from the surgical case data; outputting to a second region (304) of the first user interface (300), one or more links associated with a subset of the surgical case videos; modifying the graphical representation of one or more metrics based on a command received through the first user interface (300) to filter out a portion of the surgical case data associated with the group of users while continuing to display the links associated with the subset of the surgical case videos; and providing access to view one of the surgical case videos through a second user interface (500) based on detecting selection of a corresponding one of the links through the first user interface (300).

2. The computer-implemented method of claim 1 , wherein the graphical representation of one or more metrics derived from the surgical case data is configured to display one or more of a procedure breakdown chart, a number of uploads and downloads over time chart, and an average procedure time.

3. The computer-implemented method of claims 1 or 2, further comprising: displaying a representative frame of a surgical case video in a video viewing region (502) of the second user interface (500) based on receiving a selection of the surgical case video from the subset of the surgical case videos; and displaying a performance region in the second user interface (500), wherein the performance region (504) is configured to display performance data associated with one or more surgical cases.

4. The computer-implemented method of claim 3, further comprising: providing a complete case control in the second user interface (500), wherein the complete case control is user selectable; and filtering a source data set used to populate the performance region (504) to remove data from incomplete cases of the one or more surgical cases based on detecting a selection of the complete case control and one or more complete cases tagsP612928PC0032 associated with the one or more surgical cases.

5. The computer-implemented method of any of claims 1 to 4, wherein the second user interface (500) is configured to display one or more of: a number of views chart, a number of downloads chart, a number of shares chart, a camera duration timeline, one or more benchmark comparisons, and one or more trend charts.

6. The computer-implemented method of claim 5, further comprising displaying a popup chart (530) that is selectable to display one of: the number of views chart, the number of downloads chart, or the number of shares chart in response to a user selection.

7. The computer-implemented method of claims 5 or 6, further comprising displaying the camera duration timeline in a summary region (520) of the second user interface (500), wherein the camera duration timeline includes a slider (526) that controls playback of the surgical case video in the video viewing region (502).

8. The computer-implemented method of any of claims 5 to 7, wherein the performance region (504) displays one or more of the benchmark comparisons and one or more trend charts based on detecting a user input, wherein the one or more of the benchmark comparisons comprise one or more of a case overview, an auto-phase analysis, an instrument time in-view, and an anatomy time in-view, and optionally wherein the one or more trend charts comprise one or more of phase timings and case timings with a selectable interface to identify and view cases from the one or more trend charts.

9. The computer-implemented method of any of claims 1 to 8, further comprising: accessing a plurality of surgical case data associated with a plurality of users who share use of one or more surgical devices; outputting a video engagement summary (902) in a graphical format in a third user interface (900) that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data; outputting a procedure summary that summarizes procedure types associated with the surgical case data in the third user interface (900); and outputting user summary data of interactions with the surgical case videos.P612928PC003310. The computer-implemented method of claim 9, further comprising: receiving one or more filter parameters; and adjusting one or more of: the video engagement summary (902), the procedure summary, and the user summary data based on the one or more filter parameters, and optionally wherein the third user interface (900) is configured to display one or more of: a videos uploaded chart, a procedure type chart, an active surgeons table, a pending surgeons table, a deactivated surgeons table, and shared device usage table.

11. A system comprising: a memory system; and one or more processors coupled to the memory system and configured to execute a plurality of instructions to perform a plurality of operations comprising: displaying a representative frame of a surgical case video in a video viewing region (502) of a user interface (500) based on receiving a selection of the surgical case video from a plurality of surgical case videos; displaying a performance region (504) in the user interface (500), wherein the performance region (504) is configured to display performance data associated with one or more surgical cases; providing a complete case control in the user interface (500), wherein the complete case control is user selectable; and filtering a source data set used to populate the performance region (504) to remove data from incomplete cases of the one or more surgical cases based on detecting a selection of the complete case control and one or more complete cases tags associated with the one or more surgical cases.

12. The system of claim 11 , wherein the user interface (500) is displayed in response to a selection of a link made through an application configured to display a graphical representation of one or more metrics derived from a plurality of surgical case data associated with a group of users, and wherein the application is a mobile application configured to display one or more live streaming sessions and a link to a recently uploaded surgical case video, and wherein the link is reachable through one or more of a procedure volume or a case selection interface.

13. The system of claim 11 or 12, the operations further comprise: accessing a plurality of surgical case data associated with a plurality of usersP612928PC0034 who share use of one or more surgical devices; outputting a video engagement summary (902) in a graphical format that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data; outputting a procedure summary that summarizes procedure types associated with the surgical case data; and outputting user summary data of interactions with the surgical case videos.

14. A computer program product comprising a memory device having computer executable instructions stored thereon, which when executed by one or more processors cause the one or more processors to perform a plurality of operations comprising: accessing a plurality of surgical case data associated with a plurality of users who share use of one or more surgical devices; outputting a video engagement summary in a graphical format in a user interface that summarizes one or more of: video uploads, video views, video share, and video downloads of a plurality of surgical case videos associated with the surgical case data; outputting a procedure summary that summarizes procedure types associated with the surgical case data in the user interface; outputting user summary data of interactions with the surgical case videos; receiving one or more filter parameters; and adjusting one or more of: the video engagement summary, the procedure summary, and the user summary data based on the one or more filter parameters.

15. The computer program product of claim 14, wherein the one or more filter parameters comprise one or more of: an upload date range, a surgical approach, a surgeon, a procedure type, a device, and engagement metrics, and wherein the operations comprise: providing a complete case control in the user interface, wherein the complete case control is user selectable; and filtering a source data set used to populate the procedure summary to remove data from incomplete cases of the one or more surgical cases based on detecting a selection of the complete case control and one or more complete cases tags associated with the one or more surgical cases.

Images