Surgical planning system and method for preoperatively evaluating rotation center data

Abstract

Disclosed are surgical planning systems and methods for planning orthopedic procedures, including creating, editing, executing, and / or reviewing surgical plans pre-operatively, intra-operatively, and / or post-operatively. The surgical planning systems and methods may be used to pre-operatively assess the center of rotation of a planned post-operative implant relative to the center of rotation of the pre-operative native anatomy. A delta distance between the center of rotation of the planned post-operative implant and the center of rotation of the pre-operative native anatomy may be utilized to optimize the center of rotation of a specific implant most appropriate for a given patient's anatomy, thereby improving surgical outcomes.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This disclosure claims priority to U.S. Provisional Patent Application No. 63 / 238,411, filed on August 30, 2021, and the entire content thereof is incorporated herein by reference.

Background Art

[0002] This disclosure is directed to the field of surgical planning, and more specifically, to surgical planning systems and methods for planning orthopedic procedures. Surgical planning may include, for example, pre - operatively evaluating both the anatomical center of rotation and the implant model center of rotation in order to select an appropriate implant type, size, position, orientation, etc.

[0003] Arthroplasty is a type of orthopedic surgical procedure performed to repair or replace a diseased joint. A surgeon may wish to establish a surgical plan for the preparation of the surgical site, the selection of an implant, and the placement of the implant at the surgical site before performing arthroplasty in order to improve the outcome. Surgical planning may include capturing an image of the surgical site and determining the position of the implant based on the image.

Summary of the Invention

[0004] This disclosure relates to improved surgical planning systems and methods.

[0005] The surgical planning systems and methods of this disclosure may be utilized in some implementations for planning orthopedic procedures, including pre - operative, intra - operative, and / or post - operative, for creating, editing, executing, and / or reviewing a surgical plan. The surgical planning systems and methods may be utilized for planning and implementing orthopedic procedures to restore the function of a joint.

[0006] A surgical planning system may include, among other things, a memory device configured to store computer-executable instructions, and a processor operably coupled to the memory device and configured to execute the computer-executable instructions. The processor may execute the computer-executable instructions to receive an input related to the position of an implant model relative to a bone model within a planning environment, and calculate a deviation between the planned postoperative center of rotation of the implant of the implant model and the preoperative native anatomical structure center of rotation of the bone model.

[0007] Another surgical planning system may include, among other things, a memory device configured to store computer-executable instructions, and a processor operably coupled to the memory device and configured to execute the computer-executable instructions. The processor may execute a planning environment including a display module, a spatial module, and a comparison module. The memory device is configured to store an implant model and a bone model. The bone model includes the identification of the preoperative native anatomical structure center of rotation. The spatial module is configured to establish the planned postoperative center of rotation of the implant of the implant model superimposed on the bone model. The comparison module is configured to determine the delta distance between the planned postoperative center of rotation of the implant and the preoperative native anatomical structure center of rotation, and the display module is configured to display the delta distance within a display window of a graphical user interface. The planned postoperative center of rotation of the implant may include anterior / posterior coordinates, superior / inferior coordinates, and medial / lateral coordinates referenced relative to the preoperative native anatomical structure center of rotation.

[0008] A computer-implemented surgical planning method may include, among other things, receiving a preoperative planning input from a user. The preoperative planning input may include, for example, the position of an implant model relative to a bone model of a target patient. The method may further include identifying a planned postoperative center of rotation of the implant of the implant model relative to the bone model and calculating a delta distance between the planned postoperative center of rotation of the implant and a preoperative native anatomical center of rotation of the bone model.

[0009] Embodiments, examples, and alternatives of the following description and drawings, including any of the preceding paragraphs, claims, or various aspects or individual features thereof, may be taken independently or in any combination. Features described in connection with one embodiment are applicable to all embodiments, provided such features are not incompatible.

[0010] The various features and advantages of the present disclosure will become apparent to those skilled in the art from the following detailed description of the invention. The drawings accompanying the detailed description may be briefly described as follows. BRIEF DESCRIPTION OF THE DRAWINGS

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

[0012] The present disclosure is directed to an improved surgical planning system and method for planning orthopedic procedures, including creating, editing, executing, and / or reviewing a surgical plan preoperatively, intraoperatively, and / or postoperatively. The surgical planning system and method may be utilized to plan and implement orthopedic procedures for restoring joint function.

[0013] In some embodiments, the surgical planning system and method may be used to preoperatively evaluate the center of rotation of a planned postoperative implant relative to the center of rotation of the preoperative native anatomical structure. The delta distance between the center of rotation of the planned postoperative implant and the center of rotation of the preoperative native anatomical structure may be utilized to optimize the center of rotation of the specific implant most appropriate for a given patient's anatomical structure, thereby improving surgical outcomes. These and other features of the present disclosure are considered in more detail in the following paragraphs of the detailed description of the invention.

[0014] A surgical planning system according to an exemplary aspect of the present disclosure may include a memory device configured to store computer-executable instructions, and a processor operably coupled to the memory device and configured to execute the computer-executable instructions. The processor may execute the computer-executable instructions to receive an input related to the position of an implant model relative to a bone model within a planning environment, and further calculate a deviation between the planned center of rotation of the implant after surgery and the center of rotation of the pre-operative native anatomical structure of the bone model.

[0015] In a further implementation, the center of rotation of the pre-operative native anatomical structure is the native center of rotation about which the joint mechanism of the joint associated with the bone model will revolve.

[0016] In a further implementation, the center of rotation of the pre-operative native anatomical structure is an interpolation of the patient's original non-degraded anatomical structure associated with the bone model.

[0017] In a further implementation, the planned center of rotation of the implant after surgery is a value associated with the implant associated with the implant model.

[0018] In a further implementation, the implant is a glenosphere implant.

[0019] In a further implementation, the implant is a humeral head implant.

[0020] In a further embodiment, the deviation is a delta distance representing the length of the vector in three-dimensional space between the planned center of rotation of the implant after surgery and the center of rotation of the pre-operative native anatomical structure.

[0021] In a further implementation, the processor is further configured to display the delta distance within a user interface of the surgical planning environment.

[0022] In a further embodiment, the delta distance is visually indicated by a line extending between the planned center of rotation of the implant after surgery and the center of rotation of the native anatomical structure before surgery.

[0023] In a further implementation, the delta distance is visually indicated by a numerical value of a graphic indicator of the user interface.

[0024] In a further implementation, the processor is further configured to query a database of the surgical planning system for records having similar center of rotation characteristics.

[0025] In a further implementation, the database is an anatomical component classification database that stores a plurality of anatomical component classifications that characterize anatomical differences and variances within the anatomical differences within a representative patient population.

[0026] In a further implementation, each of the plurality of anatomical component classifications is a numerical classification of the anatomical composition of a bone or joint of a representative patient population.

[0027] In a further embodiment, the processor is further configured to command to prompt the user to evaluate the probability of a favorable surgical outcome based on records having similar center of rotation characteristics.

[0028] According to another exemplary aspect of the present disclosure, a surgical planning system may include a memory device configured to store computer-executable instructions and a processor operably coupled to the memory device and configured to execute the computer-executable instructions. The processor may execute a planning environment including a display module, a spatial module, and a comparison module. The memory device is configured to store an implant model and a bone model. The bone model includes an identification of the center of rotation of the preoperative native anatomical structure. The spatial module is configured to establish a planned postoperative center of rotation of the implant of the implant model superimposed on the bone model. The comparison module is configured to determine a delta distance between the planned postoperative center of rotation of the implant and the center of rotation of the preoperative native anatomical structure, and the display module is configured to display the delta distance within a display window of the graphical user interface. The planned postoperative center of rotation of the implant may include anterior / posterior coordinates, superior / inferior coordinates, and medial / lateral coordinates referenced to the center of rotation of the preoperative native anatomical structure.

[0029] In a further implementation, the delta distance is visually indicated by a line extending between the planned postoperative center of rotation of the implant and the center of rotation of the preoperative native anatomical structure.

[0030] In a further implementation, the delta distance is visually indicated by a numerical value within the display window.

[0031] In a further implementation, the center of rotation of the preoperative native anatomical structure is an interpolation of the patient's original, non-degraded anatomical structure associated with the bone model.

[0032] In a further implementation, the planned postoperative center of rotation of the implant is a value associated with the implant, and the implant is a glenosphere implant or a humeral head implant.

[0033] Another exemplary aspect of the present disclosure, a computer-implemented surgical planning method may include receiving preoperative planning input from a user. The preoperative planning input may include, for example, the position of an implant model relative to a bone model of a target patient. The method may further include identifying a planned postoperative center of rotation of the implant of the implant model relative to the bone model, and calculating a delta distance between the planned postoperative center of rotation of the implant and the preoperative native anatomical center of rotation of the bone model.

[0034] FIG. 1 illustrates an exemplary surgical planning system 10 (hereinafter referred to as "system 10"). System 10 may be used to plan orthopedic procedures, including preoperative, intraoperative, and / or postoperative, for creating, editing, reviewing, improving, and / or executing surgical plans. System 10 may be utilized for various orthopedic and other surgical procedures, such as arthroplasty for repairing joints, for example.

[0035] Arthroplasty of the shoulder joint is regularly referred to throughout the present disclosure to illustrate or emphasize certain features of system 10. However, the teachings of the present disclosure are not intended to be limited to any particular joint of the human musculoskeletal system and should therefore be understood to be applicable to, among others, the shoulder, knee, hip, ankle, wrist, etc. Further, the teachings of the present disclosure are not intended to be limited to arthroplasty procedures and are therefore applicable to the repair of fractures and / or other deformities within the scope of the present disclosure.

[0036] System 10 may include, among other things, at least one host computer 12, one or more client computers 14, one or more imaging devices 16, a cloud-based storage system 18, and a network 20. System 10 may include a greater number or a lesser number of subsystems within the scope of the present disclosure.

[0037] The host computer 12 may be configured to execute one or more software programs. In some implementations, the host computer 12 may be two or more computers configured to cooperate to process software instructions sequentially or in parallel.

[0038] The host computer 12 may be operable to communicate with the network 20 and may itself include one or more computing devices. The network 20 may be, for example, a private local area network (LAN), a private wide area network (WAN), the Internet, or a mesh network.

[0039] The host computer 12 and each client computer 14 may include one or more of a computer processor, memory, storage means, network devices, and input and / or output devices and / or interfaces. The input device may include, for example, a keyboard, a mouse, etc. The output device may include, for example, a monitor, a speaker, a printer, etc. The memory may include, for example, UVPROM, EEPROM, FLASH, RAM, ROM, DVD, CD, a hard drive, or other computer-readable media that may store data and / or other information related to the surgical planning and implementation techniques disclosed herein. The host computer 12 and each client computer 14 may be a desktop computer, a laptop computer, a smartphone, a tablet, a virtual machine, or any other computing device. The interface may facilitate communication with other systems and / or components of the network 20.

[0040] Each client computer 14 may be configured to communicate with the host computer 12 either directly, such as via a direct client interface 22, or through the network 20. In other implementations, the client computers 14 may be configured to communicate directly with each other via a peer-to-peer interface 24.

[0041] Each client computer 14 may be operably coupled to, for example, one or more of the imaging devices 16. Each imaging device 16 may be configured to capture or acquire one or more images 26 of a patient's anatomical structure present within a scan field (e.g., a window) of the imaging device 16. The imaging device 16 may be configured to capture or acquire two-dimensional (2D) and / or three-dimensional (3D) grayscale and / or color images 26. A variety of imaging devices 16 may be utilized, including but not limited to, an x-ray device, a computed tomography (CT) device, or a magnetic resonance imaging (MRI) device that acquires one or more images 26 of a patient. The images 26 may be stored in the storage system 18.

[0042] The client computer 14 may also be configured to execute one or more software programs, such as those associated with various surgical planning tools and / or applications. Each client computer 14 may be operable to access and locally and / or remotely execute a planning environment 28 for creating, editing, executing, refining, and / or reviewing one or more surgical plans 36 during the pre-operative, intra-operative, and / or post-operative phases of a surgery. The planning environment 28 may be a stand-alone software package or may be incorporated into another surgical tool. The planning environment 28 may be configured to communicate with the host computer 12 either through the network 20 or directly through a direct client interface 22.

[0043] The planning environment 28 may be further configured to interact with one or more of the imaging devices 16 to capture or acquire an image 26 of a patient's anatomical structure. The planning environment 28 may provide a display or visualization of one or more images 26, bone models 30, implant models 32, transfer models 34, and / or surgical plans 36 via one or more graphical user interfaces (GUIs). Each image 26, bone model 30, implant model 32, transfer model 34, surgical plan 36, as well as other data and / or information, may be stored on the memory system 18 within one or more files or records according to a specified data structure.

[0044] The planning environment 28 may include various modules for performing desired planning functions. For example, as further discussed below, the planning environment 28 may include a data module for accessing, obtaining, and / or storing data regarding the surgical plan 36, a display module (e.g., within one or more GUIs) for displaying the data, a spatial module for modifying the data displayed by the display module, and a comparison module for determining one or more relationships, for example, between a selected bone model and a selected implant model. However, a greater or lesser number of modules may be utilized, and / or one or more of the modules may be combined to provide the disclosed functionality.

[0045] Memory system 18 may be operable to store data to / from or otherwise provide data to other computing devices such as host computer 12 and / or one or more client computers 14 of system 10. Memory system 18 may be, for example, a storage area network device (SAN) configured to communicate with host computer 12 and / or client computer 14 through network 20. Although shown as a separate device of system 10, in some implementations, memory system 18 may be incorporated within host computer 12 and / or client computer 14, or may be directly coupled to host computer 12 and / or client computer 14. Memory system 18 may be configured to store one or more of computer software instructions, data, database files, configuration information, etc.

[0046] In some implementations, system 10 may be a client-server architecture configured to execute computer software on host computer 12, which may be accessible by client computer 14 using either a sinklient application or a web browser that can be executed on client computer 14. Host computer 12 may load computer software instructions from local storage or from memory system 18 into memory, and may execute the computer software using one or more computer processors.

[0047] System 10 may further include one or more databases 38. The database 38 may be stored in a central location such as on the memory system 18. In another implementation, the one or more databases 38 may be stored in the host computer 12 and / or may be a distributed database provided by one or more of the client computers 14. Each database 38 may be a relational database configured to associate one or more images 26, bone models 30, implant models 32, and / or transfer models 34 with each other and / or with their respective surgical plans 36. Each surgical plan 36 may be associated with the anatomical structure of a respective patient. Each image 26, bone model 30, implant model 32, transfer model 34, and surgical plan 36 may be assigned a unique identifier or database entry for storage on the memory system 18. Each database 38 may be configured to store data and other information corresponding to the images 26, bone models 30, implant models 32, transfer models 34, and surgical plans 36 in one or more database records or entries and / or may be configured to link or otherwise associate one or more files corresponding to each respective image 26, bone model 30, implant model 32, transfer model 34, and surgical plan 36. The various data stored in the database 38 may correspond to the anatomical structure of each respective patient from previous surgical cases and may also be arranged into one or more predetermined classifications such as gender, age, race, defect classification, type of procedure, anatomical structure classification, surgeon, facility or organization.

[0048] Each image 26 and bone model 30 may include data and other information obtained from one or more medical devices or tools such as the imaging device 16. The bone model 30 may include one or more digital images and / or coordinate information related to the anatomical structure of the patient obtained from or derived from the images 26 captured by the imaging device 16 or obtained in another way.

[0049] Each implant model 32 and transfer model 34 may include coordinate information associated with a design established or modified by a predetermined design or planning environment 28. The predetermined design may correspond to one or more components. The planning environment 28 incorporates and / or interfaces with one or more modeling packages, such as a computer-aided design (CAD) package, to render the models 30, 32, 34 as two-dimensional (2D) and / or three-dimensional (3D) volumes or constructs, which may overlay one or more of the images 26 within the display screen of one or more GUIs or the bone model 30.

[0050] The implant model 32 may correspond to implants and components of various shapes and sizes. Each implant may include one or more components that may be located at a surgical site, including prosthetics, screws, anchors, grafts. Each implant model 32 may correspond to a single component or may include two or more components configured to establish an implant assembly. Each implant and associated components may be formed of various materials, including metallic materials and / or non-metallic materials. Each bone model 30, implant model 32, and transfer model 34 may correspond to 2D and / or 3D geometric shapes and may be utilized to generate wireframes, meshes, and / or solid constructs within the GUI.

[0051] Each surgical plan 36 may be associated with, or linked to, one or more of the image 26, the bone model 30, the implant model 32, and / or the transfer model 34. The surgical plan 36 may include various parameters associated with the image 26, the bone model 30, the implant model 32, and / or the transfer model 34. For example, the surgical plan 36 may include parameters related to the anatomical implant associated with the patient's anatomical structure captured in the image 26 and the center of rotation of the planned implant. The surgical plan 36 may further include parameters including spatial information related to the relative positioning and coordinate information of the selected bone model 30, implant model 32, and / or transfer model 34.

[0052] The surgical plan 36 may define one or more corrections to the bone model 30 and information related to the positions of the implant model 32 and / or transfer model 34 relative to the original bone model 30 and / or the corrected bone model 30. The surgical plan 36 may include coordinate information related to the corrected bone model 30 and the relative positions of the implant model 32 and / or transfer model 34 in one or more predetermined data structures. The planning environment 28 may be configured to implement one or more corrections to the various models either automatically or in response to user interaction with the user interface. Corrections to each of the bone model 30, implant model 32, transfer model 34, and / or surgical plan 36 may be stored in one or more of the databases 38 either automatically and / or in response to user interaction with the system 10.

[0053] One or more surgeons and / or other staff users may be presented with the planning environment 28 via the client computer 14 and may simultaneously access each of the images 26, bone models 30, implant models 32, transfer models 34, and surgical plans 36 stored in the database 38. Each user may interact with the planning environment 28 to create, view, refine, and / or modify various aspects of the surgical plan 36. Each client computer 14 may be configured to store local instances of the images 26, bone models 30, implant models 32, transfer models 34, and / or surgical plans 36, which may be synchronized with the database 38 in real time or periodically. The planning environment 28 may be a stand-alone software package executed on the client computer 14 or may be provided, for example, as one or more web-based services executed on the host computer 12.

[0054] The system 10 described above may be configured to preoperatively plan surgical procedures. The preoperative planning provided by the system 10 may include, but is not limited to, features such as constructing a virtual model of the patient's anatomical structure, classifying the virtual model, identifying landmarks within the virtual model, selecting and orienting virtual implants within the virtual model, and specifying and evaluating rotation center information within the virtual model.

[0055] Continuing to refer to FIG. 1 and referring now to FIG. 2, the system 10 may include a computing device 40 that includes at least one processor 42 coupled to a memory 44 having the ability to store computer-executable instructions. The computing device 40 may be representative of any of the computing devices disclosed herein, including but not limited to host computer 12 and / or client computer 14. The processor 42 may be configured to execute one or more of the planning environments 28 for creating, editing, executing, refining, and / or reviewing one or more surgical plans 36 and any associated bone models 30, implant models 32, and transfer models 34 during the pre-operative, intra-operative, and / or post-operative phases of a surgical procedure.

[0056] The processor 42 can be a custom or commercially available processor, a central processing unit (CPU), or any device generally configured to execute software instructions. The memory 44 can include any one or combination of volatile memory elements and / or non-volatile memory elements. The processor 42 may be operably coupled to the memory 44 and configured to execute one or more programs stored within the memory 44 based on various inputs received from other devices or data sources associated with the system 10.

[0057] The planning environment 28 may include at least a data module 46, a display module 48, a spatial module 50, and a comparison module 52. Although four modules are shown in the very schematic depiction of FIG. 2, it will be appreciated that more or fewer modules may be utilized and / or, further, one or more of the modules may be combined to provide the disclosed functionality for executing the planning environment 28.

[0058] The data module 46 may be configured to access, retrieve, and / or store in the database 38 data and other information corresponding to one or more images 26 of a patient's anatomical structure, bone model 30, implant model 32, transfer model 34, and / or surgical plan 36. The data and other information may be stored in the one or more databases 38 as one or more records or entries 54. In some implementations, the data and other information may be stored in one or more files that are accessible by referencing one or more objects or memory locations referenced by the entry 54.

[0059] The memory 44 may be configured to access, load, edit, and / or store instances of one or more images 26, bone model 30, implant model 32, transfer model 34, and / or surgical plan 36 in response to one or more commands from the data module 46. The data module 46 may be configured to cause the memory 44 to store local instances of the image 26, bone model 30, implant model 32, transfer model 34, and / or surgical plan 36, which may be synchronized with the entry 54 stored in the database 38.

[0060] The data module 46 may be further configured to receive from various sources such as the imaging device 16 data and other information corresponding to at least one or more images 26 of the patient's anatomical structure. The data module 46 may be further configured to command the imaging device 16 to capture or acquire the image 26 automatically or in response to user interaction.

[0061] The display module 48 may be configured to display data and other information related to one or more surgical plans 36 on at least one graphical user interface (GUI) 56 that includes one or more of the image 26, bone model 30, implant model 32, and / or transfer model 34. The computing device 40 may incorporate the display device 58 or may be coupled to the display device 58. The display module 48 may be configured to cause the display device 58 to display information on the user interface 56. A surgeon, planning technician, or other user may interact with the user interface 56 within the planning environment 28 to view one or more images 26 of the patient's anatomical structure and / or one or more of any associated bone model 30, implant model 32, and transfer model 34. A surgeon, planning technician, or other user may interact with the user interface 56 via the planning environment 28 to create, edit, execute, improve, and / or review one or more surgical plans 36.

[0062] Referring still to FIG. 2 and now to FIG. 3, the user interface 56 may include one or more display windows 60 and one or more objects 62 that may be presented within the display windows 60. The display windows 60 may include any number of windows, and the objects 62 may include any number of objects within the scope of the present disclosure. In this embodiment, a user, who may be a planning technician operating on the host computer 12, may interact with the user interface 56, which includes, for example, the objects 62 and / or the display windows 60, to read out, display, edit, store, etc., various aspects of each surgical plan 36, which may include information from the selected image 26, bone model 30, implant model 32, and / or transfer model 34.

[0063] Object 62 can be accessed by user interaction and may be organized in the state of one or more menu items associated with each display window 60, and may include graphics such as menus, tabs, buttons, etc. In one embodiment, examples of object 62 include tab 62A, drop-down menu 62B, drop-down list 62C, button 62D, etc. Geometric objects including other information related to the bone model 30 and / or surgical plan 36 may be displayed in one or more of the display windows 60.

[0064] The display window 60 may include first, second, third, and fourth display windows 60-1, 60-2, 60-3, and 60-4. Although four display windows are illustrated in FIG. 3, it is of course possible to utilize more or fewer display windows 60 in accordance with the teachings disclosed herein.

[0065] The first display window 60-1 may be associated with a three-dimensional (3D) view, and the second, third, and fourth windows 60-2, 60-3, and 60-4 may be associated with two-dimensional (2D) views. In one embodiment, the second, third, and fourth windows 60-2, 60-3, and 60-4 may be associated with two-dimensional (2D) DICOM views (e.g., coronal, sagittal, and transverse directions, respectively) that can be presented to the user. The planning environment 28 may be configured such that a change in one of the display windows 60-1 to 60-4 is synchronized with each of the other display windows 60-1 to 60-4. The change may be automatically and / or manually synchronized among the display windows 60-1 to 60-4 in response to user interaction.

[0066] The display module 48 may be configured to display one of the selected ones of the bone models 30 in the first, second, third, and fourth display windows 60-1, 60-2, 60-3, 60-4. The selected bone model 30 may correspond to a bone associated with a joint, such as the humerus as illustrated in FIG. 3. In the illustrated embodiment, the selected bone model 30 has already been created from the image 26, for example, by segmenting, thresholding, and separating the bone from the joint.

[0067] The spatial module 50 may be configured to enable a user to identify various landmarks within the selected bone model 30 (such as, for example, via a desktop application executable by the processor 42). In one embodiment, the center of rotation 64 of the preoperative native anatomical structure may be identified within the anatomical structure associated with the selected bone model 30. In the present disclosure, the term "center of rotation of the preoperative native anatomical structure" may be defined as the native center of rotation about which the joint mechanism of the joint associated with the selected bone model 30 revolves. The center of rotation 64 of the preoperative native anatomical structure may be identified in a manner that ignores any bone erosions, and thus, the center of rotation 64 of the preoperative native anatomical structure may substantially mimic the center of rotation of the patient's original, non-degraded anatomical structure. Thus, the center of rotation 64 of the preoperative native anatomical structure can be an approximation or interpolation of the patient's original, non-degraded anatomical structure.

[0068] Regarding the shoulder joint, the rotational center 64 of the preoperative native anatomical structure may be defined with respect to the humeral head of the humerus. For example, the user may position a sphere 66 within the 3D rendering of the selected bone model 30 via the spatial module 50, which in this embodiment represents the native anatomical structure of the patient's humerus and which is shown in the first display window 60-1. The sphere 66 may be positioned visually using both the 3D reconstruction of the selected bone model 30 within the first display window 60-1 and the 2D views provided within the second, third, and fourth display windows 60-2, 60-3, 60-4, and may also be referenced with respect to landmarks such as the scapular plane. The sphere 66 may represent the native humeral head of the patient and may also include a specific diameter and position with respect to the scapular plane, and thus, the center of the sphere 66 may be defined as the rotational center 64 of the preoperative native anatomical structure. The rotational center 64 of the preoperative native anatomical structure may establish an X, Y, Z coordinate origin of 0,0,0 within the image data associated with the rotational center feature.

[0069] Once determined, the location of the rotational center 64 of the preoperative native anatomical structure may be saved as a landmark within the image data associated with the surgical plan 36 for the subject patient. The rotational center 64 of the preoperative native anatomical structure may then be referenced for further development and refinement of the surgical plan 36 for a particular patient.

[0070] Referring now to FIG. 4 while continuing to refer to FIGS. 2 and 3, the display module 48 of the planning environment 28 may be further configured to display additional data / information associated with the rotational center feature of the system 10 within another graphical user interface 156. In this embodiment, the user, who may be a surgeon working on one of the client computers 14, interacts with the user interface 156 to read, display, edit, store, etc., various aspects of the selected surgical plan 36.

[0071] The user interface 156 may include a first display window 160-1 and a second display window 160-2. Although two display windows are illustrated in FIG. 4, it will be appreciated that more or fewer display windows may be utilized in accordance with the teachings disclosed herein.

[0072] The user interface 156 may further include one or more objects 162 that enable a user to interact with the user interface 156, such as to identify various aspects of the surgical plan 36. The objects 162 may include graphics such as menus, tabs, buttons, etc., that are accessible by user interaction and may be organized in the form of one or more menu items associated with each display window 160-1, 160-2. In one embodiment, the objects 162 include a drop-down menu 162A, a button 162B, and an arrow 162C.

[0073] Geometric objects including the selected bone model 30 and / or other information related to the surgical plan 36 may be displayed within the display windows 160-1, 160-2. In one embodiment, the native preoperative anatomical structure associated with the selected bone model 30 may be presented within the display window 160-1, and one of the implant models 32 may be shown within the display window 160-2 superimposed over the native anatomical structure associated with the selected bone model 30. Thus, the display window 160-2 may be configured to present the planned postoperative aspect of the surgical plan 36. The display module 48 may be configured to display the selected bone model 30 within the display window 160-1 and may be further configured to display both the selected bone model 30 and the selected implant model 32 within the display window 160-2.

[0074] In the illustrated embodiment of FIG. 4, both display windows 160-1 and 160-2 are configured to illustrate a coronal view of various geometric objects. However, other views may be presented, for example, a transverse view (see FIG. 5). The user may select one of buttons 162B to switch between available views.

[0075] Display module 48 may be configured to display a 3D representation of the selected bone model 30 and the selected implant model 32 within display window 160-2. Spatial module 50 may be configured to enable the user to interact with display window 160-2 or another portion of user interface 156 to move the selected bone model 30 and / or the selected implant model 32 within the space (e.g., up, down, left, right). For example, spatial module 50 may be configured to set a virtual position and / or a virtual axis in response to the placement of the bone model 30 and each associated implant model 32 relative to the patient's anatomical structure. The virtual position and / or virtual axis may be automatically set and / or adjusted based on the position and orientation of the selected implant model 32 relative to the selected bone model 30 and / or in response to user interaction with user interface 156. The user may select the components of implant model 32 and their positions / orientations as part of a pre-operative plan that can be performed within user interface 156.

[0076] The selected implant model 32 may include one or more components. For example, the implant model 32 may include at least a first component 32A and a second component 32B coupled to the first component 32A to establish an assembly. The first component 32A may be configured to be at least partially received within the volume of the selected bone model 30. The second component 32B may have an articular connection surface sized to mate with an opposing bone or an articular surface of an implant. In the illustrated embodiment of FIG. 4, the selected implant model 32 is a reverse total shoulder arthroplasty implant assembly. However, other configurations are contemplated, including but not limited to, an anatomical total shoulder arthroplasty implant assembly (see, e.g., the implementation of FIG. 6).

[0077] The display module 48 may be configured to display a cross-sectional view of the selected implant model 32 and / or the selected bone model 30 in one or both of the display windows 160-1, 160-2. The cross-sectional view may be presented as an image of the bone associated with the selected bone model 30. The orientation of the cross-sectional view may be predefined or specified in response to a user interaction with the user interface 156, such as by pressing the arrow 162C, for example.

[0078] The display module 48 may be further configured to display, within one or both of the display windows 160-1, 160-2, the center of rotation 64 of the pre-operative native anatomical structure. Coordinates (0,0,0) associated with the center of rotation 64 of the pre-operative native anatomical structure may be displayed within the graphic indicator 70. The graphic indicator 70 may be superimposed, for example, over the display window 160-1 or disposed adjacent to the display window 160-1.

[0079] The coordinates associated with the center of rotation 64 of the preoperative native anatomical structure may be displayed during the anatomical period. For example, the first coordinate may be a location inside or outside the center of rotation value, the second coordinate may be a location in front of or behind the center of rotation value, and the third coordinate may be a location above or below the center of rotation value.

[0080] The native center of rotation 72 of another bone (e.g., glenoid fossa) of the selected bone model 30 may also be displayed for reference in the display window 160-1, with or without anatomical coordinates. These values and anatomical locations may be native values that are derived from the marking procedure performed by the planning technician on the host computer 12. In some implementations, the native centers of rotation 64, 72 are native landmarks, and thus their associated values cannot be adjusted by the surgeon user within the user interface 156.

[0081] The spatial module 50 may be configured to identify the planned postoperative implant center of rotation 74 of the first component 32A of the selected implant model 32. The planned postoperative implant center of rotation 74 may be automatically updated as the user manipulates the selected implant model 32 with respect to the bone model 30 within the display window 160-2. In implementations where the surgical procedure plan 36 is related to the procedure of reverse total shoulder arthroplasty (see, for example, FIGS. 4-5), the first component 32A of the selected implant model 32 is a glenosphere implant, and the planned postoperative implant center of rotation 74 is the center of the glenosphere implant. In other implementations where the surgical procedure plan 36 is related to the procedure of anatomical total shoulder arthroplasty (see, for example, FIG. 6), the first component 32A of the selected implant model 32 is a humeral head implant, and the planned postoperative implant center of rotation 74 is the center of the humeral head implant.

[0082] The coordinates associated with the center of rotation 74 of the planned postoperative implant may be displayed as corresponding anatomical coordinates (e.g., in millimeters) relative to the center of rotation 64 of the preoperative native anatomical structure. For example, the first coordinate may be the medial or lateral coordinate of the center of rotation value of the implant relative to the medial or lateral coordinate of the center of rotation 64 of the preoperative native anatomical structure, the second coordinate may be the anterior or posterior coordinate of the center of rotation value of the implant relative to the anterior or posterior coordinate of the center of rotation 64 of the preoperative native anatomical structure, and the third coordinate may be the superior or inferior coordinate of the center of rotation value of the implant relative to the superior or inferior coordinate of the center of rotation 64 of the preoperative native anatomical structure. The anatomical orientation for each of these coordinates may be based on resampling of the imaging dataset relative to landmarks (e.g., scapular planes) stored within the bone model 30.

[0083] The spatial module 50 may be configured to cause the display module 48 to display the coordinates associated with the center of rotation 74 of the planned postoperative implant within the graphic indicator 76. The graphic indicator 76 may be superimposed, for example, onto the display window 160-2 or may be arranged adjacent to the display window 160-2.

[0084] The comparison module 52 may be configured to generate or set one or more parameters associated with the performance of the surgical plan 36. The parameters may include, for example, one or more settings or dimensions associated with the center of rotation data resulting from the positioning of the implant model 32 relative to the bone model 30.

[0085] In one embodiment, the comparison module 52 may be configured to derive a delta distance 78 between a planned postoperative center of rotation 74 of the implant and a preoperative native anatomical center of rotation 64. The delta distance 78 is essentially the length of a vector in three-dimensional space between the planned postoperative center of rotation 74 of the implant and the preoperative native anatomical center of rotation 64, and can thus be calculated using three anatomical coordinates associated with the planned postoperative center of rotation 74 of the implant. More specifically, the delta distance 78 may be calculated by computing the square root of the sum of the squared values of each of the medial / lateral coordinate, anterior / posterior coordinate, and superior / inferior coordinate of the planned postoperative center of rotation 74 of the implant. This calculation may be represented by the following equation. Δ = √(M / L 2 +A / P 2 +S / I 2 )

[0086] The comparison module 52 may be further configured to cause the display module 48 to display the delta distance 78 within the user interface 156. In one embodiment, the delta distance 78 may be visually indicated by a line 80 drawn between the center of rotation 74 of the implant and the center of rotation 64 of the preoperative native anatomical structure. In another embodiment, the actual value of the delta distance 78 (e.g., in millimeters) may be displayed within one or more graphic indicators 82. The graphic indicator 82 may be, for example, overlaid onto the display window 160-2 or disposed adjacent to the display window 160-2.

[0087] Using the user interface 156, the user may select implant components of the implant model 32 and their positions / orientations with respect to the bone model 30 during preoperative planning. These selections may be utilized to derive the location of the center of rotation 74 of the planned postoperative implant and the value of the delta distance 78. These values may then be evaluated by the user to adjust the planned implant type, size, position, orientation, etc. to achieve a specific postoperative center of rotation or delta distance that is most appropriate for the patient's anatomical structure. Generally, a smaller delta distance is thought to be more likely to provide an improved surgical outcome for an anatomical procedure compared to a larger delta distance.

[0088] The display module 48 may be further configured to provide a display of the subluxation rate to the user within the user interface 156 or another user interface. For example, the display module 48 may provide, as a 2D circle, the volume ratio of the humeral head sphere 66 positioned posterior to the scapular plane and, as a line, superimposed on the imaging data, the scapular plane.

[0089] Once a satisfactory delta distance 78 is achieved, the user may save the surgical plan 36. The surgical plan 36 may be saved to an appropriate database 38 of the memory system 18 and may also be approved by pressing one or more of the buttons 162B (e.g., the save button and / or the approval button). The saved and approved surgical plan 36 may include various parameters associated with the target patient, including both the value of the center of rotation 74 of the planned postoperative implant and the delta distance 78. As further discussed below, these parameters may be used for tracking / comparing patient outcome data and anatomical configuration information.

[0090] Referring now to FIG. 7 while continuing to refer to FIGS. 2-6, computing device 40 of system 10 may interface with memory system 18 through network 20 to access various databases 38 stored thereon for establishing and implementing surgical plan 36. Databases 38 of memory system 18 may include patient profile database 84, surgeon profile database 86, surgical outcome database 88, range of motion database 90, and anatomical component classification database 92. Within the scope of the present disclosure, additional databases may be stored on and accessed from memory system 18. Further, although shown as separate databases, one or more of the databases may be combined or linked together. For example, anatomical component classification database 92 may be combined or linked with one or more of patient profile database 84, surgical outcome database 88, and range of motion database 90.

[0091] Patient profile database 84 may include information that is part of an indexed and stored record or entry related to one or more current patients associated with system 10. Information stored on patient profile database 84 may include, for each patient, current surgical plan information such as gender, age, race, height, weight, defect category, type of procedure, surgeon, facility or organization, major joint, activities of daily living / lifestyle goal profile (e.g., abduction, adduction, external rotation, internal rotation, extension, flexion, external rotation combined with 60° of abduction, internal rotation with 60° of abduction, desired postoperative range of motion, etc.), saved planned postoperative implant center of rotation 74 and delta distance 78. Patient profile database 84 may further store or link to image 26 for a given patient, including landmark identifiers for preoperative native anatomical structure center of rotation 64 and planned postoperative implant center of rotation 74.

[0092] The surgeon profile database 86 may include information that is part of an indexed and stored record or entry related to one or more surgeon users associated with the system 10. Information stored on the surgeon profile database 86 may include the name of the surgeon, the facility or organization, historical data regarding the types of previous surgical procedures planned by the surgeon using the system 10, data regarding the types of implants included in the surgeon's preoperative surgical plan, data regarding the actual implants utilized in the surgeon's previous surgical procedures, data regarding the delta distance between the center of rotation of the preoperative native anatomical structure and the planned center of rotation of the postoperative implant in the surgeon's previous surgical procedures, and the like. In some implementations, the surgeon profile database 86 may interface with the patient profile database 84 to link each surgeon from the surgeon profile database 86 to the surgeon's patients enumerated in the patient profile database 84.

[0093] The surgical outcome database 88 may include information that is part of an indexed and stored record or entry related to one or more previous patients associated with the system 10. The surgical outcome database 88 may be created based on information logged by surgeons and / or other staff users after each surgical procedure and at each follow-up visit to indicate the progress of previous patients. The information stored on the surgical outcome database 88 may include, for each patient, surgical planning information such as gender, age, race, height, weight, defect category, type of procedure, specific implant used, surgeon, facility or organization, major joint, visual analog pain score, ASES score, achieved activities of daily living / lifestyle profile (e.g., abduction, adduction, external rotation, internal rotation, extension, flexion, external rotation combined with 60° abduction, internal rotation with 60° abduction, desired achieved postoperative range of motion, etc.), planned postoperative implant center of rotation, and delta distance between the center of rotation of the preoperative native anatomical structure and the planned postoperative implant center of rotation. The surgical outcome database 88 may additionally store or link preoperative and postoperative images 26 for each previous patient.

[0094] The range of motion database 90 may include information that is part of an indexed and stored record or entry related to one or more current and previous patients associated with the system 10. The range of motion database 90 may store the range of motion data resulting from range of motion simulations performed by the computing device 40 for each surgical plan 36. The range of motion data may include information related to simulated joint movements (e.g., abduction / adduction, flexion / extension, internal rotation / external rotation, etc.), identified contact or collision points for various implant positions, angular arcs and collision modes for various implant positions (e.g., between implant and implant, between implant and bone, between bone and bone, etc.), adjusted centers of rotation of the implant in a plurality of increments and offset directions for various implant positions, etc. The range of motion database 90 may additionally store, for each of the adjusted centers of rotation, the delta distance between the center of rotation of the preoperative native anatomical structure and the center of rotation of the planned postoperative implant.

[0095] The anatomical component classification database 92 may store a plurality of anatomical component classifications that characterize anatomical differences within a representative patient population and anatomical variances within the anatomical differences for one or more intended surgical procedures (e.g., anatomic total shoulder, reverse total shoulder arthroplasty, etc.). In some implementations, the representative patient population may be derived by analyzing image data such as surgical outcome database 88 and / or images from previous patients stored in any other imaging source associated with a plurality of previous patients who have already undergone the intended surgical procedure. Each of the plurality of anatomical component classifications is a numerical classification of the anatomical makeup of the bone or joint of the representative patient population.

[0096] Referring now to FIG. 8, an anatomical component classification database 92 may be created using a statistical shape modeler 94. The statistical shape modeler 94 may be a software package stored in the memory 44 of the computing device 40 or the storage system 18 and executed by the processor 42. The statistical shape modeler 94 may receive a plurality of sets of image data 96 associated with a target bone or joint. In some implementations, the set of image data 96 may be composed of tens of thousands of sets of image data. Each set of image data 96 may be specific to a previous patient in a representative patient population for the target bone or joint and may include 2D and / or 3D anatomical images related to a given type of surgery. The statistical shape modeler 94 may analyze the plurality of sets of image data 96 to construct a statistical shape model 95.

[0097] As input, the statistical shape modeler 94 may receive a plurality of predefined modes 98 used to analyze the plurality of sets of image data 96. Each of the modes 98 is a descriptor configured to characterize anatomical differences within the bone or joint associated with the statistical shape model 95. Exemplary modes 98 that may be provided to the statistical shape modeler 94 include the size of the glenoid fossa, the size of the scapula, the amount of tilt, the version number, the predicted amount of the length of the glenoid fossa and the sagittal neck, the angle of the glenoid fossa relative to the scapular neck, the critical shoulder angle, the prediction of the acromion and / or coracoid process, the size of the humeral head, the varus / valgus of the humeral head, the varus / valgus of the femur and / or tibia, the internal rotation / external rotation of the femur and / or tibia, the integrity of the subscapularis, deltoid, and / or supraspinatus muscles, the ML width and AP width, the intercondylar notch depth, the tibial slope, the Q angle of the knee, the ACL / PCL stability, the MCL / LCL stability, the amount of flexion, the amount of extension, the quality and amount of soft tissue surrounding the joint, the patellar tracking angle, bone density, the rate of osteopenia, anatomical landmarks, the joint cavity, the preoperative range of motion, the delta distance between the center of rotation of the native anatomical structure preoperatively and the planned center of rotation of the postoperative implant, any combination of the foregoing, and the like, but are not limited thereto.

[0098] In some implementations, at least seven different modes may be utilized by the statistical shape model 94 to characterize the statistical shape model 95. However, within the scope of the present disclosure, a larger or smaller number of modes may be provided.

[0099] In some implementations, the mode 98 may not be predefined. Rather, the statistical shape modeler 94 may be programmed to utilize artificial intelligence (e.g., neural networks) or machine learning to estimate the mode that is most highly correlated with the bone or joint being modeled within the statistical shape model 95.

[0100] As another input, the statistical shape modeler 94 may receive a plurality of predefined standard deviations 100 that are used to analyze a plurality of sets 96 of image data. Each standard deviation 100 may represent the anatomical variance (e.g., distance between features, orientation of features, relative features, etc.) contained within each of the plurality of predefined modes 98. The standard deviations 100 may be used to verify the percentile coverage of the representative patient population represented within the statistical shape model 95. In some implementations, at least seven different standard deviations (e.g., -3, -2, -1, 0, 1, 2, and 3) may be utilized by the statistical shape model 94 to further characterize all of the anatomical variances contained within the anatomical structures described within the statistical shape model 95. However, within the scope of the present disclosure, it is possible to utilize a larger or smaller number of standard deviations.

[0101] In response to commands from the processor 42, the statistical shape modeler 94 combines a plurality of standard deviations 100 with a plurality of predefined modes 98 to assign a plurality of anatomical component classifications 99 to the bones or joints associated with the statistical shape model 95 in order to classify the anatomical makeup of the entire patient population represented within the statistical shape model 95 N where N is any number. Each anatomical component classification 99 Nmay be stored in the anatomical component classification database 92 of the memory system 18.

[0102] FIG. 9 schematically depicts an exemplary anatomical component classification 99 assigned to a particular bone model 102 derived from a statistical shape model 95. In one embodiment, the bone model 102 is a 3D model of the scapula of the shoulder joint. However, other bones and joints can also be classified in a similar manner.

[0103] The statistical shape modeler 94 of FIG. 8 may analyze the bone model 102 for each of a plurality of modes 981-987 to characterize any anatomical differences in the bone model 102 compared to other similar bones / joints associated with the statistical shape model 95. Of course, a larger or smaller number of modes are possible.

[0104] The statistical shape modeler 94 may further characterize any anatomical variance contained within each of the plurality of predefined modes 981-987 by analyzing each mode against a plurality of standard deviations 1001-1007. Of course, a larger or smaller number of standard deviations are possible.

[0105] In the implementation shown in FIG. 9, the bone model 102 has the numerical value 0213120 assigned to it as its anatomical component classification 99. This numerical value represents a standard deviation of 0 within the first mode 981, a standard deviation of 2 within the second mode 982, a standard deviation of 1 within the third mode 983, a standard deviation of 3 within the fourth mode 984, a standard deviation of 1 within the fifth mode 985, a standard deviation of 2 within the sixth mode 986, and a standard deviation of 0 within the seventh mode 987. Thus, the anatomical component classification 99 is a unique numerical identifier for describing the anatomical structure associated with the bone model 102.

[0106] With continued reference to FIGS. 1-9, FIG. 10 schematically illustrates a method 110 for planning orthopedic procedures for each patient using the system 10. The method 110 may be performed by a user (e.g., a surgeon) as part of a surgical planning procedure for preparing a surgical plan for a patient. Fewer or additional steps may be listed below and are possible within the scope of the present disclosure, and the order of the listed steps is not intended to limit the present disclosure.

[0107] The system 10 may be configured to perform each of the steps of the method 110 via any of its associated computing devices and modules. In an exemplary implementation, one or more computing devices 40 of the client computer 14 may be programmed to perform the method 110. Thus, assume that a planning technician has already created a bone model 30 of the patient's anatomical structure and identified the center of rotation 64 of the preoperative native anatomical structure within the bone model 30. However, other implementations are further contemplated within the scope of the present disclosure.

[0108] Preoperative planning inputs may be received from the user in step 112. The preoperative planning inputs may include implant type selection, implant size selection, implant location, implant orientation, implant offset, and the like.

[0109] Based on the preoperative planning inputs, the center of rotation 74 of the planned postoperative implant may be identified in step 114. Then, the delta distance 78 between the center of rotation 74 of the planned postoperative implant and the center of rotation 64 of the preoperative native anatomical structure may be identified in step 116.

[0110] In process 118, the user may be prompted to indicate whether the specified rotational center delta distance 78 is acceptable. If not, method 110 may return to process 112 to receive additional user corrections to inputs such as implant type, size, location, orientation, etc.

[0111] If the delta distance 78 is acceptable to the user, method 110 may proceed to process 120. In this process, system 10 may receive approval of the preoperative surgical plan from the user. Next, the rotational center 74 of the planned postoperative implant and the delta distance 78 associated with the approved surgical plan are stored in an appropriate database of memory system 18 in process 122.

[0112] Next, in process 124, computing device 40 may query anatomical component classification database 92 and / or surgical outcome database 88 to find records stored therein that have similar anatomical component classifications and similar rotational center characteristics (e.g., rotational center of the preoperative native anatomical structure, rotational center of the planned implant, delta distance, etc.). The record with the closest rotational center characteristics may be displayed on the user interface of computing device 40 in process 126.

[0113] The user may be prompted in block 128 to evaluate the probability of a favorable surgical outcome based on the center or rotational data. Next, method 110 may return to process 118 by querying the user again to indicate whether the rotational center delta distance 78 is acceptable. Next, method 110 may continue in a loop fashion until the user no longer makes any further corrections to the implant type, size, location, orientation, etc.

[0114] The proposed surgical planning system and method of the present disclosure may be utilized to create and implement a surgical plan tailored to an individual patient, which may improve healing. The disclosed system and method may analyze preoperative data of centers or rotations, including the delta distance between a planned implant center of rotation and a preoperative native anatomical structure center of rotation, in order to better evaluate the probability of obtaining a favorable surgical outcome. Thus, the proposed system and method provide improved functionality compared to prior planning systems.

[0115] Although different non-limiting embodiments are illustrated as having certain components or steps, embodiments of the present disclosure are not limited to those specific combinations. Some of the components or features from any of the non-limiting embodiments may be used in combination with features or components from any of the other non-limiting embodiments.

[0116] Of course, like reference numerals identify corresponding or like elements throughout several views. Further, of course, in these exemplary embodiments, the arrangement of certain components is disclosed and illustrated, but other arrangements may also benefit from the teachings of the present disclosure.

[0117] The foregoing description should be construed as illustrative and not in any limiting sense. Those skilled in the art will understand that certain modifications may fall within the scope of the present disclosure. For these reasons, the following claims should be considered to determine the true scope and content of the present disclosure.

Claims

1. A surgical planning system comprising: a memory device configured to store computer-executable instructions; a processor operably coupled to the memory device and executing the computer-executable instructions to: receive an input related to the position of an implant model relative to a bone model within a surgical planning environment; calculate a deviation between a planned postoperative center of rotation of the implant of the implant model and a preoperative native anatomical structure center of rotation of the bone model.

2. The surgical planning system according to claim 1, wherein the preoperative native anatomical structure center of rotation is the native center of rotation about which the joint mechanism of the joint associated with the bone model revolves.

3. The surgical planning system according to claim 2, wherein the preoperative native anatomical structure center of rotation is an interpolation of the patient's original, non-degraded anatomical structure associated with the bone model.

4. The surgical planning system according to claim 1, wherein the planned postoperative center of rotation of the implant is a value associated with the implant associated with the implant model.

5. The surgical planning system according to claim 4, wherein the implant is a glenosphere implant.

6. The surgical planning system according to claim 4, wherein the implant is a humeral head implant.

7. The surgical planning system according to claim 1, wherein the deviation is a delta distance representative of the length of a vector between the planned postoperative center of rotation of the implant and the preoperative native anatomical structure center of rotation in three-dimensional space.

8. The surgical planning system according to claim 7, wherein the processor is further configured to display the delta distance within a user interface of the surgical planning environment.

9. The surgical planning system according to claim 8, wherein the delta distance is visually indicated by a line extending between the planned postoperative center of rotation of the implant and the preoperative native anatomical structure center of rotation.

10. The surgical planning system according to claim 8, wherein the delta distance is visually represented by a numerical value of a graphic indicator of the user interface.

11. The surgical planning system according to claim 1, wherein the processor is further configured to query a database of the surgical planning system for records having similar center of rotation characteristics.

12. The surgical planning system according to claim 11, wherein the database is an anatomical component classification database that stores a plurality of anatomical component classifications characterizing anatomical differences and variances within anatomical differences in a representative patient population.

13. The surgical planning system according to claim 12, wherein each of the plurality of anatomical component classifications is a numerical classification of the anatomical composition of a bone or joint of the representative patient population.

14. The surgical planning system according to claim 11, wherein the processor is further configured to issue a command that prompts a user to evaluate the probability of a favorable surgical outcome based on the record having the similar center of rotation characteristics.

15. A surgical planning system, a memory device configured to store computer-executable instructions, and a processor operably coupled to the memory device and configured to execute the computer-executable instructions to execute a surgical planning environment including a display module, a spatial module, and a comparison module. The memory device is configured to store an implant model and a bone model, the bone model includes identification of a center of rotation of a pre-operative native anatomical structure, the spatial module is configured to establish a planned post-operative center of rotation of an implant of the implant model superimposed on the bone model, the comparison module is configured to determine a delta distance between the planned post-operative center of rotation of the implant and the center of rotation of the pre-operative native anatomical structure, the display module is configured to display the delta distance within a display window of a graphical user interface.

16. The surgical planning system according to claim 15, wherein the delta distance is visually indicated by a line extending between the planned post-operative center of rotation of the implant and the center of rotation of the pre-operative native anatomical structure.

17. The surgical planning system according to claim 15, wherein the delta distance is visually indicated numerically within the display window.

18. The surgical planning system according to claim 15, wherein the center of rotation of the pre-operative native anatomical structure is an interpolation of the original, un-deteriorated anatomical structure of the patient associated with the bone model. **Claim 19** The surgical planning system according to claim 15, wherein the center of rotation of the planned post-operative implant is a value associated with the implant, and further wherein the implant is a glenosphere implant or a humeral head implant. **Claim 20** A computer-implemented surgical planning method, comprising: receiving a pre-operative plan input from a user, wherein the pre-operative plan input includes the position of an implant model relative to a bone model of a target patient; identifying a center of rotation of a planned post-operative implant of the implant model relative to the bone model; and calculating a delta distance between the center of rotation of the planned post-operative implant of the bone model and the center of rotation of the pre-operative native anatomical structure of the bone.

Images