PATIENT-SPECIFIC ANTERIOR PLATE IMPLANTS

[0001] The present application claims priority to U.S. Provisional Patent Application No. 63/211,226, filed Jun. 16, 2021, the entirety of which is incorporated by reference herein.

[0002] The present disclosure is generally related to orthopedic implants, and more particularly to systems and methods for designing and implementing patient-specific plates.

[0003] Orthopedic implants are used to correct numerous different maladies in a variety of contexts, including spine surgery, hand surgery, shoulder and elbow surgery, total joint reconstruction (arthroplasty), skull reconstruction, pediatric orthopedics, foot and ankle surgery, musculoskeletal oncology, surgical sports medicine, and orthopedic trauma. Spine surgery itself may encompass a variety of procedures and targets, such as one or more of the cervical spine, thoracic spine, lumbar spine, or sacrum, and may be performed to treat a deformity or degeneration of the spine and/or related back pain, leg pain, or other body pain. Common spinal deformities that may be treated using an orthopedic implant include irregular spinal curvature such as scoliosis, lordosis, or kyphosis (hyper- or hypo-), and irregular spinal displacement (e.g., spondylolisthesis). Other spinal disorders that can be treated using an orthopedic implant include osteoarthritis, lumbar degenerative disc disease or cervical degenerative disc disease, lumbar spinal stenosis, and cervical spinal stenosis.

[0022] The following headings are provided for ease of readability. While embodiments of the present technology are described under the following headings, other embodiments of the technology can include elements discussed under multiple headings. Accordingly, the fact that an embodiment may be discussed under a particular heading does not necessarily limit that embodiment to only the elements discussed under that heading.

[0023] The present technology is directed to medical device implants that are designed based on a patient's anatomy. For example, in many of the embodiments disclosed herein, the present technology provides patient-specific implants designed to be implanted relative to two or more vertebral bodies. The implants can include plates having projections or wings extending in a superior, inferior, and/or lateral direction. Each of the projections can include a contact surface to interface with a surface of a vertebral body. Each of the contact surfaces can have a topography designed to mate with a topography of the surface of the vertebral body. In some embodiments, the implants can be used to fuse, stabilize, and/or reduce the motion of a first vertebral body relative to a second vertebral body. In some embodiments, using implants described herein can improve the alignment of a first vertebral body relative to a second vertebral body, e.g., to reduce or prevent vertebral bulging. In some embodiments, a patient-specific plate is configured to extend across intervertebral spaces and obstruct movement of one or more implants, such as an interbody fusion device.

[0024] In some embodiments, the implants include a patient-specific anterior plate having a first (e.g., upper, superior, etc.) projection having a first contact surface configured to interface with an anterior surface of a first (e.g., upper, superior, etc.) vertebral body, and a second (e.g., lower, inferior, etc.) projection having a second contact surface configured to interface with an anterior surface of second (e.g., lower, inferior, etc.) vertebral body. The first contact surface can have a first topography contoured to mate with the topography of the anterior surface of the first vertebral body, and the second contact surface can have a second topography contoured to mate with a topography of the anterior surface of the second vertebral body.

[0025] In some embodiments, the projections can be configured to interface with a plurality of surfaces, such as two or more adjacent surfaces, of the corresponding vertebral bodies. For example, the first projection can include a first (e.g., uppermost) portion having a first portion contact surface. The first portion contact surface can have a topography contoured to mate with a topography of a superior surface (e.g., superior endplate) of the superior vertebral body.

[0026] In some embodiments, the implants can include an intermediate (e.g., medial, center, etc.) projection or member configured to be positioned at least partially between the first and second vertebral bodies. The intermediate projection can include a first (e.g., upper) intermediate contact surface and a second (e.g., lower) intermediate contact surface. The first intermediate contact surface can have a topography contoured to mate with at least a portion of a topography of an inferior surface (e.g., inferior endplate) of the superior vertebral body, and the second intermediate contact surface can have a topography contoured to mate with at least a portion of a topography of a superior surface (e.g., superior endplate) of the inferior vertebral body.

[0027] In some embodiments, the implants can include a first plate configured to interface with first surfaces of superior and inferior vertebral bodies, and a second plate configured to interface with second surfaces of the superior and inferior vertebral bodies. The first surfaces can be the same or different than the second surfaces, e.g., the first plate can be configured to contact anterior surfaces of the superior and inferior vertebral bodies, and the second plate can be configured to contact the anterior or lateral surfaces of the superior and inferior vertebral bodies. It can be appreciated that the first and second plates can have different topographies even when configured to contact the same surface(s) the of the superior and/or inferior vertebral bodies, for example, because the topographies of those surfaces may not be uniform. In some embodiments, the first plate can be coupled or connected to the second plate, e.g., by one or more connectors or linkages.

[0028] In some embodiments, the vertebral implants can include both a patient-specific interbody device (e.g., a cage) and a patient-specific positioning feature. The interbody device can be designed to occupy a first target position between the two vertebral bodies. The positioning feature can be designed to occupy a second target position proximate at least one of the two vertebral bodies. The positioning feature can be a plate, and the plate and the interbody device can be mechanically coupled together by a connection mechanism. The connection mechanism can be designed to connect the interbody device to the plate to form a predetermined three-dimensional spatial relationship therebetween that simultaneously permits the cage to occupy the first target position and the plate to occupy the second target position. Because the plate and the interbody device are in a predetermined three-dimensional spatial relationship when coupled together, a surgeon implanting the implant need only confirm that either the plate is in the second target position or the interbody device is in the first target position. If, for example, the surgeon confirms the plate is in the second target position, the interbody device will be in the first target position by virtue of the predetermined spatial relationship between the interbody device and the plate.

[0029] The present technology further provides methods for implanting the patient-specific implants. For example, in some embodiments, the interbody device and plate can be implanted in an uncoupled state. In such embodiments, the interbody device can be delivered proximate the first target position. The plate can then be delivered to the second target position. Once the plate is in the second target position, the plate can be coupled to the interbody device. The act of coupling the plate to the interbody device can move the interbody device into the first target position. The plate can be configured to match the geometry of one or more anatomical features against which the plate rests/sits. For example, the plate can have a curved surface that is at least generally geometrically congruent to a region of an outer surface of a vertebral body. When the plate pressed against the region, the matching surfaces can engage one another to key the plate to the vertebral body. Accordingly, the patient specific configuration of the plate can be used to position and align the plate with the spine. In some embodiments, the interbody device and plate can be delivered in a coupled state. Regardless of whether the interbody device and the plate are delivered in a coupled or uncoupled state, the mechanical coupling between the interbody device and the plate can provide a desired orientation and positioning between the interbody device and the plate such that when the plate is in the second target position, the interbody device is in the first target position, and vice versa. Once implanted, the plate can also prevent and/or reduce movement (e.g., expulsion, migration, etc.) of the interbody device.

[0030] Without being bound by theory, intervertebral implants provide the most efficacy when they are implanted at the correct position. This is especially true for “patient-specific” intervertebral implants, which, as described in detail below, are designed to mate with specific anatomical targets. However, depending on the surgical approach and the type of device being implanted, it can be difficult to deliver intervertebral implants (e.g., interbody devices such as cages) to precise target locations in an intervertebral disc space. For example, because the intervertebral disc space is between two vertebral bodies, a target location in the intervertebral disc space often cannot be directly seen and/or accessed by the surgeon throughout the surgical procedure. The target location is also typically at the bottom of a narrow surgical corridor that can further reduce the ability of a surgeon to see the target site and/or reduce maneuverability of the implant once proximate the target site. The present technology thus provides systems, devices, and associated methods that direct the intervertebral implants into the target position without having to directly visualize the target site. Without being bound by theory, the present technology is therefore expected to improve the accuracy with which interbody devices can be delivered to relatively “difficult to visualize” target positions, such as intervertebral disc spaces.

[0031] The plates described herein can ensure the interbody device is positioned at the correct (and/or relatively difficult-to-visualize) target position, reduce movement of the interbody device once it is located at the target position, and/or stabilize or fuse a first vertebral body relative to at least a second vertebral body. The plates can be designed to mate with a portion of patient anatomy at a second target position that is relatively easier to visualize and/or access than the interbody target position. For example, the plates can be designed to mate with one or more surfaces of the vertebral body (e.g., an anterior surface of a vertebral body, a lateral surface of a vertebral body, etc.). The plates can also be coupled to the interbody device to form a predefined three-dimensional spatial relationship therebetween. For example, when the plate is coupled to the interbody device, the interbody device can have a predefined position, orientation, alignment, and/or geometry relative to the plate. The predefined three-dimensional orientation can thus be designed to ensure that, when the plate is positioned at the relatively easier to visualize plate target position, the interbody device is directed into the relatively harder to visualize interbody target position. Thus, the plate can be used to help guide the interbody device into position. The plate can be mechanically coupled to the spine by one or more fasteners (e.g., bone screws, anchors, etc.). The fasteners can further prevent or limit movement of the plate relative to the adjacent vertebrae.

[0032] In some embodiments, a patient-specific intervertebral implant includes an intervertebral cage configured to mate with one or more endplates of adjacent vertebral bodies, a patient-specific positioning feature configured to mate with a target region of at least one of the adjacent vertebral bodies, and a connection mechanism. The connection mechanism can couple or be configured to couple the patient-specific positioning feature to the intervertebral cage to maintain a predetermined configuration of the patient-specific intervertebral implant when the intervertebral cage is between the endplates and the patient-specific positioning feature contacts the target region. The predetermined configuration can correspond to a target spatial relationship between the cage and positioning feature.

[0033] The present technology thus provides systems and methods for designing and implanting “patient-specific” or “personalized” medical devices, that are expected to mitigate at least some of the disadvantages of conventional intervertebral implants. In particular, the present technology can provide systems and methods for designing and implanting patient-specific implants that are optimized for the patient's particular characteristics (e.g., condition, anatomy, pathology, medical history, etc.). For example, the patient-specific medical device can be designed and manufactured specifically for the particular patient, rather than being an off-the-shelf device. However, it shall be appreciated that a patient-specific or personalized medical device can include one or more components that are non-patient-specific, and/or can be used with an instrument or tool that is non-patient-specific. For example, patient-specific positioning features can be used with non-patient-specific articulating intervertebral implants, fixed intervertebral implants, cages, etc. Personalized implant designs can be used to manufacture or select patient-specific technologies, including medical devices, instruments, and/or surgical kits. For example, a personalized surgical kit can include one or more patient-specific devices, patient-specific instruments, non-patient-specific technology (e.g., standard instruments, devices, etc.), instructions for use, patient-specific treatment plan information, or a combination thereof. The implants can include positioning features selected based on the implantation site, delivery paths, or the like. Positioning features can be or include, for example, plates, plate assemblies (e.g., plates and one or more fasteners, plates with locators, etc.), arms (e.g., deployable or nondeployed arms), or combinations thereof. For example, an implant can have arms that are deployed to contact specific positions along the spinal column.

[0034] In some embodiments, the patient-specific implants described herein are designed to occupy a specific target position once implanted. As used herein, the terms “target position,” “target site,” and “target location,” refers to a predetermined optimal location for the implant to be placed during the implant procedure, and can be based on the patient's anatomy, condition, diagnosis, prognosis, activity-level, and the like. For example, the target position may be defined by one or more of the following parameters taken in relation to an anatomical landmark: an angle or degree of orientation, and angle or degree of translation, an insertion depth, an insertion angle, degree of contact between two surfaces, and the like. Suitable anatomical landmarks include, for example, specific vertebrae or other recognizable anatomical features. The target position can therefore include a three-dimensional position of the implant relative to patient anatomy (e.g., as defined by boundaries created by patient anatomy), and/or a target orientation of the implant relative to patient anatomy. In some embodiments, the target position may incorporate a desired correction to the patient's native anatomy such that, when the implant is implanted at the target position, it manipulates the patient's anatomy to achieve the desired correction. Without being bound by theory, placing the implant at the target position is expected to optimize the benefit of and/or minimize the side effects of the implant. In particular, the full benefit of the implant may only be realized when the implant is accurately placed at the target position. Various aspects of the implant (e.g., the interbody device and the plate) can have different target positions.

[0035] Embodiments of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings in which like numerals represent like elements throughout the several figures, and in which example embodiments are shown. Embodiments of the claims may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. The examples set forth herein are non-limiting examples and are merely examples among other possible examples.

[0036] The words “comprising,” “having,” “containing,” and “including,” and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items.

[0037] As used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.

[0038] Although the disclosure herein primarily describes systems and methods for treatment planning in the context of orthopedic surgery, the technology may be applied equally to medical treatment and devices in other fields (e.g., other types of surgical practice). Additionally, although many embodiments herein describe systems and methods with respect to implanted devices, the technology may be applied equally to other types of medical devices (e.g., non-implanted devices).

[0039] FIGS. 1A and 1B illustrate a patient-specific implant 100 configured in accordance with embodiments of the present technology. In particular, FIG. 1A is a side view of the implant 100 and FIG. 1B is a front view of the implant 100 of FIG. 1A. The implant 100 includes an anterior plate 120 contacting an anterior surface of the L4 and the L5 vertebral bodies (shown in dashed line). The plate 120 can include a patient-specific geometry (e.g., size, shape, curvature, contouring, morphology, topography, etc.) designed to mate with the patient's anatomy. In particular, the plate 120 includes a first (e.g., superior, upper, etc.) projection or wing 121 and a second (e.g., inferior, lower, etc.) projection or wing 126. The first projection 121 includes a first contact surface 122 that is configured to interface with an anterior surface S₃ of the L4 vertebral body. For example, the first contact surface 122 (e.g., a posterior surface) of the plate 120 can have a topography designed to mate with a topography of an anterior surface S₃ of the L4 vertebral body. As used herein, the term “mate” can refer to the engagement of two surfaces to form a generally gapless interface with reduced and/or minimized empty space therebetween such that at least 80%, 90%, 95%, 97%, 98%, 99%, or 100% of a first surface contacts a second surface in at least some patient orientations (not including any engineered gaps, such as might exist for the space between the L4 and L5 vertebral bodies).

[0040] In the illustrated embodiment, the anterior surface S₃ is partially curved. The first contact surface 122 is therefore also partially curved to mate with at least a portion of the partially curved topography of the anterior surface S₃, e.g., to form a generally gapless interface therebetween. When the patient stands and the spine is generally straight, at least 80%, 90%, 95%, 97%, 98%, 99%, or 100% of the surface area of the first contact surface 122 contacts the anterior surface S₃ (e.g., forming a “generally gapless” interface). In the illustrated embodiment, the anterior surface S₃ has a generally “wavy” or “curved” topography with several recesses and projections. The first contact surface 122 of the first projection 121 therefore has a generally “wavy” or “curved” topography with several recesses and projections that mate with the generally wavy topography of the anterior surface S₃ to form a generally gapless interface therebetween.

[0041] In some embodiments, the first projection 121 can be configured to contact a plurality of surfaces, such as two or more adjacent surfaces, of the L4 vertebral body. The first projection 121 can include a first (e.g., superior, uppermost, etc.) portion or member 140 having a first portion contact surface 141 configured to interface with a surface adjacent/proximate to the surface contacted by the first contact surface 122. For example, in the illustrated embodiment the first portion contact surface 141 is configured to interface with a superior surface S₅ (e.g., a superior endplate) of the L4 vertebral body. The first portion contact surface 141 can have a topography designed to mate with (e.g., correspond, match, resemble, etc.) at least a portion of the topography of the superior surface S₅. In the illustrated embodiment, the superior surface S₅ is partially curved. The first portion contact surface 141 is therefore also partially curved to mate with at least a portion of the partially curved topography of the superior surface S₅, e.g., to form a generally gapless interface therebetween.

[0042] In the illustrated embodiment, the first contact surface 122 and first portion contact surface 141 are shown slightly spaced apart from the respective surfaces S₃, S₅ to more clearly show the topography of both surfaces. As one skilled in the art will appreciate, however, the first contact surface 122 can contact the anterior surface S₃ and/or the first portion contact surface 141 can contact at least a portion of the superior surface S₅ when the plate 120 is implanted in the patient.

[0043] The second projection 126 includes a second contact surface 128 configured to interface with an anterior surface S₄ of the L5 vertebral body. The second contact surface 128 can have a patient-specific geometry designed to mate with the anterior surface S₄. Because the second projection 126 is configured to mate with a different surface than the first projection 121, the second projection 126 may have a different geometry than the first projection 121.

[0044] In some embodiments, the second projection 126 can be configured to contact a plurality of surfaces, such as two or more adjacent surfaces, of the L5 vertebral body. The second projection 126 can include a second (e.g., inferior, lowermost, etc.) portion or member 142 having a second portion contact surface 143 configured to interface with a surface adjacent/proximate to the surface contacted by the second contact surface 128. For example, in the illustrated embodiment the second portion contact surface 143 is configured to interface with an inferior surface S₆ (e.g., an inferior endplate) of the L5 vertebral body. The second portion contact surface 143 can also have a patient-specific geometry designed to mate with the inferior surface S₆. Because the second portion contact surface 143 is configured to mate with a different surface than the first portion contact surface 141, the second portion contact surface 143 may have a different geometry than the first portion contact surface 141.

[0045] The plate 120 can further include a registration feature configured to aid in the positioning of the plate 120 and/or one or more of the surfaces/projections thereof relative to the L4-L5 vertebral bodies. In the illustrated embodiment, the registration feature includes an intermediate (intravertebral, medial, middle, central, core, etc.) portion or projection 144 positioned (extending, positioned, implanted, etc.) at least partially between the adjacent L4-L5 vertebral bodies. The intermediate portion 144 may be generally centered between the lateral margins of the L4 and L5 vertebral bodies, although other positions are possible. In the illustrated embodiment, the plate 120 includes an intermediate portion 144 positioned at least partially between the L4 and L5 vertebral bodies, e.g., between the inferior surface S₂ of the L4 vertebra and the superior surface S₁ of the L5 vertebra. In the illustrated embodiment, the intermediate portion 144 is configured to at least partially contact an intravertebral disk (e.g., the L4-L5 intravertebral disc) when the plate 120 is implanted. In other embodiments, the intermediate portion 144 can be configured to be spaced apart from (i.e., not contact) the intravertebral disk when the plate 120 is implanted, for example, by at least 1 mm, 2 mm, 5 mm, 10 mm, or another suitable distance. In further embodiments, the intravertebral disk can be absent or at least partially removed/resected prior to or during implantation of the plate 120. In these and other embodiments, the intermediate portion 144 can be configured to occupy at least 50%, 60%, 70%, 80%, or 90% of any void space between the L4 and L5 vertebral bodies that is not otherwise occupied by the intervertebral disc or other object(s) (e.g., intervertebral device(s)) positioned in the intervertebral space between the L4 and L5 vertebral bodies.

[0046] The intermediate portion 144 can include a first (e.g., superior, upper, etc.) intermediate contact surface 145 and a second (e.g., inferior, lower, etc.) intermediate contact surface 145. The first intermediate contact surface 145 can be configured to interface with at least a portion of the inferior surface S₂ of the L4 vertebral body. The first intermediate contact surface 145 can have a topography designed to mate at least partially with a topography of the inferior surface S₂ of the L4 vertebral body. For example, in the illustrated embodiment the inferior surface S₂ is partially curved. The first intermediate contact surface 145 is therefore also partially curved to mate with at least a portion of the partially curved topography of the inferior surface S₂, e.g., to form a generally gapless interface therebetween. The second intermediate contact surface 146 can be configured to interface with at least a portion of the superior surface S₁ of the L5 vertebral body. The second intermediate contact surface 146 can have a patient-specific geometry configured to mate with the superior surface S₁. Because the second intermediate contact surface 146 is configured to mate with a different surface than the first intermediate contact surface 145, the second intermediate contact surface 146 may have a different geometry than the first intermediate contact surface 145.

[0047] FIG. 1C is an enlarged view of a portion of FIG. 1A showing the intermediate portion 144 and surrounding patient anatomy. As best shown in FIG. 1C, the first intermediate contact surface 145 has first curvature corresponding to the topology of the inferior surface S₂ and/or a second cortical rim CR₂ of the L4 vertebral body, and the second intermediate contact surface 146 has second curvature, different than the first curvature of the first intermediate contact surface 145, corresponding to the topology of the superior surface S₁ and/or a first cortical rim CR₁ of the L5 vertebral body. In the embodiment illustrated in FIG. 1C, a distal/posterior end or terminus 147 of the intermediate portion 144 is configured to contact or otherwise interface with the native L4-L5 intervertebral disk. In other embodiments, and as described above, the distal/posterior end 147 can be configured to be spaced apart from the L4-L5 intervertebral disc to create a gap therebetween. Additionally, or alternatively, the distal/posterior end 147 can be coupled to an intervertebral device configured to be positioned between the L4 and L5 vertebral bodies, such as any of the interbody implants described further with reference to FIGS. 3A-5. In these and other embodiments, at least a portion of the L4-L5 intervertebral disc can be resected or otherwise removed, for example, to create space between the L4 and L5 vertebral bodies for the intermediate portion 144 and/or the intervertebral device. The amount of the L4-L5 intervertebral disc that is resected/removed can be patient-specific and/or at least generally similar, identical, or otherwise correspond to a size of the intermediate portion and/or the intervertebral device configured to be positioned within the L4-L5 intervertebral space.

[0048] The distal/posterior end 147 of the intermediate portion can be configured to extend a distance/length in a distal/posterior from the plate 120 (e.g., the first contact surface 122 and/or the second contact surface 128 of the plate 120), as denoted by length L in FIG. 1C. The length L can be between about 1 mm and about 20 mm, such as about 1 mm, about 2 mm, about 5 mm, about 10 mm, about 15 mm, about 20 mm, or another suitable distance. In some embodiments, the length L is based at least in part on one or more patient-specific factors, such as the distance between (1) the cortical rims CR₁, CR₂ and/or the anterior vertebral surfaces S₃, S₄, and (2) the anterior edge/surface E of the intervertebral disc L4-L5. In such embodiments, and as set forth above, the intermediate portion 144 can have a length specifically designed such that the distal end 147 abuts or otherwise contacts the anterior edge/surface E of the L4/L5 disc when the plate 120 is positioned against the anterior surfaces S₃, S₄ of the L4 and L5 vertebral bodies. In such embodiments, the distal end 147 may have a topology that corresponds to a topology of the native L4/L5 disc to reduce or prevent any unwanted forces from being transferred from the intermediate projection 144 to the disc. In other embodiments, however, the intermediate projection 144 may be designed to have a length L greater than a distance between the cortical rims CR₁, CR₂ and the anterior edge/surface E of the disc. In such embodiments, a portion of the disc can be resected before implanting the plate 120, and/or the intermediate projection 144 can bias or force the disc in a posterior direction (e.g., to help hold the disc in the interbody space). In yet other embodiments, the intermediate portion 144 can have a length L less than a distance between the cortical rims CR₁, CR₂ and the anterior edge/surface E of the disc, such that, following implantation of the plate 120, there is a gap (not shown) between the distal end 147 of the intermediate projection 144 and the anterior edge/surface E of the disc. In some embodiments, the gap is between about 0.5 mm and about 10 mm, or between about 0.5 mm and about 5 mm, such as about 0.5 mm, about 1 mm, about 1.5 mm, about 2 mm, etc.

[0049] In some embodiments, the intermediate portion 144 is designed such that the distal/posterior end 147 extends a particular distance distally/posteriorly past one or both of the anterior surfaces S₃, S₄ of the vertebral bodies L4, L5, and/or distally/posteriorly past one or both cortical rims CR of the vertebral bodies L4, L5 (e.g., the first cortical rim CR₁ of the L5 vertebral body between the inferior surface S₁ and the anterior surface S₄, and/or the second cortical rim CR₂ of the L4 vertebral body between the superior surface S₂ and the anterior surface S₂). For example, the intermediate portion 144 can be designed such that the distal/posterior end 147 extends between 1 mm and 20 mm (e.g., about 1 mm, about 2 mm, about 5 mm, about 10 mm, about 15 mm, about 20 mm, or another suitable distance) past the anterior surfaces S₃, S₄ and/or the cortical rims CR₁, CR₂. In at least some embodiments, the distance can be selected based at least partially on one or more patient-specific factors, including whether the intermediate portion 144 is configured to contact the L4-L5 intervertebral disc, whether the intermediate portion 114 is configured to be coupled to an intervertebral device, one or more dimensions of the intervertebral device configured to be coupled to the intermediate portion 144, the amount of the L4-L5 intervertebral disc to be removed/resected, the topology of one or both of the patient's vertebral bodies, and/or any of the other data and/or patient-specific information described herein.

[0050] Referring again to FIGS. 1A and 1B, a fastening element such as a screw can be used to secure the plate 120 to an adjacent anatomical structure, such as the L4 and/or L5 vertebral bodies. In some embodiments, and as best shown in FIG. 1B, the first projection 121 can include one or more apertures 124 (FIG. 1B) for receiving one or more fastening elements or screws 125 (FIG. 1A) for securing the plate 120 to the L4 vertebral body. Additionally, the second projection 126 can also include one or more apertures 127 (FIG. 1B) for receiving one or more fastening elements or screws 129 (FIG. 1) for securing the plate 120 to the L5 vertebral body. Furthermore, although not shown in FIGS. 1A and 1B, in some embodiments the intermediate portion 144 can include one or more apertures for receiving one or more fastening elements or screws, e.g., for securing the first intermediate contact surface 145 to the inferior surface S₂ and/or the second intermediate contact surface 146 to the superior surface S₁. Each of the fastening elements and/or apertures 124, 127 can include patient-specific geometries configured to mate with the patient's anatomy. For example, the position(s)/location(s) of the apertures 124 in the first projection 121 can be different than the position(s)/location(s) of the apertures 127 in the second projection 126, and the dimensions (e.g., length, width, threading, etc.) and/or insertion angle of the associated fastening elements can correspond to the patient's anatomy and/or a specific aperture. Additionally, or alternatively, in some embodiments the plate 120 can be secured to the L4 and/or L5 vertebral bodies using posterior fixation processes or techniques.

[0051] In some embodiments, incorporating multiple wings/projections into the plate 120 can provide fixation between adjacent vertebral bodies, reduce post-operative motion between the vertebral bodies, and/or increase the stability provided by the plate 120. In addition to, or in lieu of, having projections extending in a superior and/or inferior direction, the plate 120 can include one or more projections that extend laterally (e.g., relative to a medial or central axis/plane of the plate 120) and are configured to interface with one or more lateral surfaces/sides of the L4 and/or L5 vertebral bodies. In such embodiments, the lateral projections can have a patient-specific geometry that is configured to mate with a lateral surface of the L4 and/or L5 vertebral bodies. The lateral projections can also be used to secure the plate 120 to the vertebral bodies.

[0052] The plate 120 can have a predetermined target position, in which the patient-specific topography of the plate 120 mates with corresponding anatomical structure(s) of the patient's anatomy. For example, in the illustrated embodiment the contact surface 122 aligns with the anterior surface S₃ of the L4 vertebral body, the second portion contact surface 143 aligns with at least a portion of the inferior surface S₆ of the L5 vertebral body, the first intermediate contact surface 145 aligns with at least a portion of the inferior surface S₂ of the L4 vertebral body, etc.

[0053] Although the plate 120 is described and illustrated with reference to the L4 and L5 vertebral bodies in FIGS. 1A and 1B, in other embodiments the plate 120 can be configured for implantation in the cervical, lower lumbar, and/or other regions of a patient's spine. In such embodiments, the plate 120, and/or one or more components thereof (e.g., first projection 121, second projection 126, etc.), can have a correspondingly curved or arcuate geometry. For example, the plate 120, and/or one or more components thereof, can include a curved or arcuate geometry along a longitudinal or cephalad-caudal axis that corresponds to the curvature or arcuate geometry at a target position in the patient's spine along a corresponding axis.

[0054] It is expected that the patient-specific topographies of the implant 100 can prevent, inhibit, limit, or reduce movement (e.g., lateral, vertical, etc.) of the implant 100 relative to one or both adjacent vertebrae. For example, placing the implant 100 in the target position can maximize the contact between the plate 120 and the L4 and/or L5 vertebral bodies. This can increase the stability of the L4 and L5 vertebral bodies and/or reduce the risk that the plate 120 is dislodged (disconnected, decoupled, etc.) from the target position. Additionally, it is expected that the patient-specific topographies can reduce the risk that the relative positions/alignments of adjacent vertebral bodies changes after the plate 120 is placed at its target position. For example, placing the implant 100 at the target spinal segment (e.g., the L4 and L5 vertebral bodies) can limit the motion of the target spinal segment relative to other portions/segments of the patient's spine. This can reduce and/or prevent bulging of a first vertebral body (e.g., L4) relative to the implant 100 and/or a second vertebral body (e.g., L5), and/or can improve the overall alignment of the vertebral bodies in the patient's spine. It is further expected that the patient-specific topographies can improve the fit of the plate 120 in the target position, e.g., such that the plate 120 improves the fusion (coupling, connection, etc.) of a first vertebral body (e.g., L4) to a second (e.g., adjacent) vertebral body (e.g., L5).

[0055] FIGS. 2A and 2B illustrate additional patient-specific implants configured in accordance with embodiments of the present technology. More specifically, FIG. 2A illustrates a side view of an implant 200 include a first plate 220 and a second plate 250, and FIG. 2B illustrates an anterior view of the implant 200 of FIG. 2A. At least some aspects of the implant 200 can be generally similar or identical in structure and/or function to one or more aspects of the implant 100 of FIGS. 1A and 1B. Accordingly, like names and/or reference numbers are used to identify generally similar or identical aspects (e.g., first plate 220 of FIGS. 2A and 2B versus plate 120 of FIGS. 1A and 1B). Additionally, any of the features of the implant 200 of FIGS. 2A and 2B can be combined with the implant 100 of FIGS. 1A and 1B.

[0056] Referring first to FIG. 2A, the implant 200 includes a first plate 220 positioned on and/or contacting a first side of a vertebral column (e.g., the L4 and L5 vertebral bodies) and a second plate 250 positioned on and/or contacting a second side of the vertebral column. For example, in the illustrated embodiment the first plate 220 is positioned anterior of the vertebral column, and the second plate 250 is position laterally (e.g., on/proximate to a lateral side) of the vertebral column.

[0057] The second plate 250 can include a patient-specific geometry (e.g., size, shape, curvature, contouring, morphology, topography, etc.) configured to mate with the patient's anatomy. In particular, the second plate 250 includes a first (e.g., superior, upper, etc.) projection or wing 252 and a second (e.g., inferior, lower, etc.) projection or wing 254. The first projection 252 includes a first contact surface 256 (FIG. 2B) that is configured to interface with a lateral surface S₇ of the L4 vertebral body. The first contact surface 256 (e.g., a posterior surface) of the second plate 250 can have a topography designed to mate with a topography of the lateral surface S₇ of the L4 vertebral body. In the illustrated embodiment, the lateral surface S₇ is partially curved. The first contact surface 256 is therefore also partially curved to mate with at least a portion of the partially curved topography of the lateral surface S₇, e.g., to form a generally gapless interface therebetween. In the illustrated embodiment, the anterior surface S₇ has a generally “wavy” or “curved” topography. The first contact surface 256 of the first projection 252 therefore has a generally “wavy” or “curved” topography that mates with the generally wavy topography of the lateral surface S₇ to form a generally gapless interface therebetween. In the illustrated embodiment, the first contact surface 256 is shown slightly spaced apart from the lateral surface S₇ to more clearly show the topography of the various surfaces. However, as one skilled in the art will appreciate, the first contact surface 256 can contact the lateral surface S₇ when the second plate 250 is implanted in the patient.

[0058] In some embodiments, the first projection 252 can be configured to contact a plurality of surfaces, such as two or more adjacent surfaces, of the L4 vertebral body. The first projection 252 can further include a first (e.g., superior, uppermost, etc.) portion or member 253 having a first portion contact surface 255 configured to interface with a superior surface S₅ (e.g., a superior endplate) of the L4 vertebral body. The first portion contact surface 255 can have a topography designed to mate with (e.g., correspond, match, resemble, etc.) the topography of the superior surface S₅. In the illustrated embodiment, the superior surface S₅ is partially curved. The first portion contact surface 255 is therefore also partially curved to mate with at least a portion of the partially curved topography of the superior surface S₅, e.g., to form a generally gapless interface therebetween.

[0059] The second projection 254 includes a second contact surface 258 configured to interface with a lateral surface S₈ of the L5 vertebral body. The second contact surface 258 can also have a patient-specific geometry designed to mate with the lateral surface S₈. Notably, because the second projection 254 is configured to mate with a different surface than the first projection 252, the second projection 254 may have a different geometry than the first projection 252.

[0060] In some embodiments, the second projection 254 can be configured to contact a plurality of surfaces, such as two or more adjacent surfaces, of the L5 vertebral body. The second projection 254 can further include a second (e.g., inferior, lowermost, etc.) portion or member 257 having a second portion contact surface 259 configured to interface with an inferior surface S₆ (e.g., an inferior endplate) of the L5 vertebral body. The second portion contact surface 259 can have a patient-specific geometry designed to mate with at least a portion of the inferior surface S₆. Because the second portion contact surface 259 is configured to mate with a different surface than the first portion contact surface 255, the second portion contact surface 259 may have a different geometry than the first portion contact surface 255.

[0061] The second plate 250 can further include an intermediate (intravertebral, medial, middle, central, core, etc.) portion or projection 260 positioned (extending, positioned, implanted, etc.) at least partially between the adjacent L4-L5 vertebral bodies. The intermediate portion 260 can be configured generally similar or the same as the intermediate portion 144 of FIGS. 1A-1C. The intermediate portion 260 can include a first (e.g., superior, upper, etc.) intermediate contact surface 262 and a second (e.g., inferior, lower, etc.) intermediate contact surface 264. The first intermediate contact surface 262 can be configured generally similar or the same as the first intermediate contact surface 145 of FIGS. 1A and 1B. The second intermediate contact surface 264 can be configured generally similar or the same as the second intermediate contact surface 146 of FIGS. 1A and 1B.

[0062] The implant 200 can further include one or more linkages or connectors 266 (individually identified as a first connector 266a and a second connector 266b in FIGS. 2A and 2B) configured to couple or connect the first plate 220 and the second plate 250. For example, in the illustrated embodiment the first projection 252 of the second plate 250 is coupled to the first projection 221 of the first plate 220 by the first connectors 266a, and the second projection 254 of the second plate 250 is coupled to the second projection 226 of the first plate 220 by the second connector 266b. In other embodiments, the implant 200 can include more or fewer connectors 266, and the connectors 266 can be configured to couple any part, region, or location of the first plate 220 to any part, region, or location of the second plate 250. For example, in some embodiments, the first projection 221 of the first plate 220 can be coupled to the second projection 254 of the second plate 250. Each of the connectors 266 can include a patient-specific geometry (e.g., size, shape, curvature, contouring, morphology, topography, etc.) configured to mate with the patient's anatomy. In some embodiments, each of the connectors 266 can be at least partially flexible or deformable, e.g., to conform to a lateral topography of the patient's vertebral bodies. Each of the connectors 266 can be coupled to the first and/or second plates 220, 250 before and/or after implantation or insertion into the patient. In some embodiments, each of the connectors 266, the first plate 220, and/or the second plate 250 can be a one-piece component or assembly. In some embodiments, the first and second plates 220, 250 can be coupled to each other (e.g., via the connectors 266) in a predetermined three-dimensional orientation such that positioning the first plate 220 at a first target position positions (e.g., automatically positions) the second plate at a second target position. Accordingly, positioning the first plate to mate with one or more first anatomical structures can cause the second plate to mate (e.g., automatically mate) with one or more second anatomical structures.

[0063] As described previously regarding FIGS. 1A and 1B, one or more fastening elements such as screws (not shown in FIGS. 2A and 2B for the purpose of clarity) can be used to secure the first and/or second plates 220, 250 to an adjacent anatomical structure, such as the L4 and/or L5 vertebral bodies. For example, the first projection 252 of the second plate 250 can include one or more apertures 268 configured to receive the fastening elements to secure the first projection to the L4 vertebral body, and the second projection 254 of the second plate 250 can include one or more apertures 270 configured to receive the fastening elements to secure the second projection 254 to the L5 vertebral body. Additionally, one or more of the connectors 266 can include one or more apertures configured to receive fastening elements.

[0064] Although described in the context of having two plates in FIGS. 2A and 2B, in other embodiments the implant 200 can include more plates. For example, the implant 200 can include at least three, four, five, six, seven, eight, or any suitable number of plates. Additionally, in some embodiments the sides/surfaces of each of the adjacent vertebral bodies can each include two or more plates. For example, two or more plates can be positioned anterior to the patient's vertebral column, two or more plates can be positioned on a first lateral side of the patient's vertebral column, and/or two or more plates can be positioned on a second (e.g., opposite) lateral side of the patient's vertebral column, etc. Although the implant 200 is described and illustrated with reference to the L4 and L5 vertebral bodies in the embodiment illustrated in FIGS. 2A and 2B, in other embodiments the plate 120 can be configured for implantation in the cervical, lower lumbar, and/or other regions of a patient's spine.

[0065] It is expected that implants including multiple plates, each having patient-specific topography, can prevent, inhibit, limit, or reduce movement (e.g., lateral, vertical, etc.) of the plate relative to one or both adjacent vertebrae. For example, implants including multiple plates can increase the stability of adjacent vertebral bodies and/or reduce the risk that the one or more of the plates are dislodged (disconnected, decoupled, etc.) from the target position. Additionally, it is expected that the implants including multiple plates can reduce the risk that the relative positions/alignment of adjacent vertebral bodies changes after the plates are placed at their target positions, e.g., to reduce and/or limit bulging of a first vertebral body (e.g., L4) relative to one of the one or more plates and/or a second vertebral body (e.g., L5). It is further expected that implants including multiple plates can improve the fit of the pates in their target positions, e.g., such that the plate 120 improves the fusion (coupling, connection, etc.) of a first vertebral body to a second (e.g., adjacent) vertebral body.

[0066] FIGS. 3A and 3B illustrate another patient-specific implant 300 configured in accordance with embodiments of the present technology. At least some aspects of the implant 300 can be generally similar or identical in structure and/or function to one or more aspects of the implant 100 of FIGS. 1A and 1B and/or the implant 200 of FIGS. 2A and 2B. Accordingly, like names and/or reference numbers are used to identify generally similar or identical aspects (e.g., plate 320 versus plate 120 of FIGS. 1A and 1B, first plate 220 of FIGS. 2A and 2B). Additionally, any of the features of the implant 300 of FIGS. 3A and 3B can be combined with the implant 100 of FIGS. 1A and 1B and/or the implant 200 of FIGS. 2A and 2B.

[0067] FIG. 3A is a side view of the implant 300 implanted proximate the L4 and L5 vertebral bodies (shown in dashed line). FIG. 3B is front view of the implant 200 of FIG. 3A. The implant 300 can include a patient-specific interbody element or cage 310, a patient-specific positioning element or plate 320, and a connection element or mechanism 330 coupling the cage 310 to the plate 320. The cage 310 is positioned in the disc space between the L4 and L5 vertebral bodies and interfaces with a superior aspect of the L5 vertebral body and an inferior aspect of the L4 vertebral body. The plate 320 is positioned anterior to the vertebral column and can include features generally similar or the same as the plate 120 of FIGS. 1A and 1B and/or the first plate 220 of FIGS. 2A and 2B.

[0068] The cage 310 can include a first (e.g., upper) surface 312 having a topography designed to mate with a topography of an inferior (e.g., an inferior endplate) surface S₂ of the L4 vertebral body, and a second (e.g., lower) surface 314 having a topography designed to mate with a topography of a superior (e.g., a superior endplate) surface S₁ of the L5 vertebral body. In some embodiments, the cage 310 includes a patient-specific geometry (e.g., size, shape, curvature, contouring, morphology, topography, etc.) designed to mate with the patient's anatomy. For example, in the illustrated embodiment, a first (e.g., upper) surface 312 of the cage 310 can have a topography designed to mate with a topography of an inferior surface S₂ of the L4 vertebral body. When the patient stands and the spine is generally straight, at least 80%, 90%, 95%, 97%, 98%, 99%, or 100% of the surface area of the first surface 312 contacts the inferior surface S₂ (e.g., forming a “generally gapless” interface) such that loads are applied generally evenly across the cage 310. In the illustrated embodiment, the inferior surface S₂ has a generally “wavy” topography with several recesses and projections. The first surface 312 of the cage 310 therefore has a generally “wavy” topography with several recesses and projections that mate with the generally wavy topography of the inferior surface S₂ to form a generally gapless interface therebetween. A second (e.g., lower) surface 314 of the cage 310 can have a topography designed to mate with a topography of a superior surface S₁ of the L5 vertebral body. When the patient stands and the spine is generally straight, at least 80%, 90%, 95%, 97%, 98%, 99%, or 100% of the surface area of the second surface 314 can contact the inferior surface S₁ (e.g., forming a “generally gapless” interface) such that loads are applied generally evenly across the cage 310. In the illustrated embodiment, the superior surface S₁ is generally flat. The second surface 314 of the cage 310 therefore has a generally flat topography to mate with the generally flat topography of the superior surface S₁ to form a generally gapless interface therebetween. In the illustrated embodiment, the first surface 312 is shown slightly spaced apart from the inferior surface S₂, and the second surface 314 is shown slightly spaced apart from the superior surface S₁, to more clearly show the topography of the various surfaces. However, as one skilled in the art will appreciate, the first surface 312 can contact the inferior surface S₂ and/or the second surface 314 can contact the superior surface S₁ when the cage 310 is implanted in the patient. In addition to improving the fit of the cage 310, the matching topographies can prevent, inhibit, or limit lateral movement of the cage 310 relative to one or both of the L4 and L5 vertebrae. For example, the topographies can be designed to keep movement of the cage 310 less than 5%, 2%, or 1% of the maximum length of the inferior surface S₂. In these and other embodiments, the intermediate portion 344 can be configured to support one or both the L4 and L5 vertebral bodies, in addition to or in lieu of the cage 310. The intermediate portion 344 can be configured to support a first portion of the load less than, equal to, or greater than a second portion of the load supported by the cage 310. For example, the intermediate portion 344 can be configured to support at least 5%, 10%, 20%, 50%, 60% a percentage therebetween, or another suitable percentage of the load applied by one or both of the L4 and L5 vertebral bodies to the implant 300.

[0069] Both the cage 310 and the plate 320 can have a predetermined target position, in which the patient-specific topographies of the cage 310 and the plate 320 are configured to mate with their corresponding anatomical structures. For example, the cage 310 is shown in a first target position in which its patient-specific topography aligns with the anatomical structure having the corresponding topography (e.g., the first surface 312 and the second surface 314 align with the inferior surface S₂ and the superior surface S₁, respectively). In some embodiments, the first target position may be generally centered between the lateral margins of the L4 and L5 vertebral bodies, although other positions are possible. The plate 320 is shown in a second target position in which the patient-specific topography of the plate 320 and/or one or more of the surfaces thereof aligns with the portions/surfaces of the patient's anatomy having the corresponding topography (e.g., the first contact surface 322 aligns with the anterior surface S₃, the second intermediate contact surface 346 aligns at least partially with the inferior surface S₁, etc.).

[0070] Placing the cage 310 and the plate 320 at their respective target positions is expected to optimize the benefit of, and/or reduce the side effects associated with, the implant 300, e.g., as described previously. It is additionally expected that placing the cage 310 in the first target position maximizes the contact between the cage 310 and the L4 and L5 vertebral bodies, which can reduce the risk that the cage is ejected from the disc space between the L4 and L5 vertebral bodies.

[0071] The cage 310 can be coupled to the plate 320 via a connection mechanism 330. In the illustrated embodiment, the connection mechanism 330 is coupled to the intermediate portion 344 of the plate 320. Although illustrated as having a gap between the intermediate portion and the cage 310 in FIGS. 3A and 3B, in other embodiments the intermediate portion can contact the cage 310 when the cage 310 is coupled to the plate 320 via the connection mechanism 330. In such embodiments, the intermediate portion 344 can be dimensioned to have a length such that the intermediate portion 344 abuts or contacts the cage 310 when the cage 310 and the plate 320 are placed at their respective target positions. Additionally, in some embodiments the intermediate portion 344 can have a height corresponding to the height of the cage 310 and/or the height of an intervertebral space (e.g., between the L4 and L5 vertebral bodies). When the intermediate portion 344 contacts the cage 310, it can at least partially prevent or inhibit motion (e.g., anterior motion) of the cage 310.

[0072] The connection mechanism 330 can include a rigid or semi rigid interface. The connection mechanism 330 is described in PCT App. No. PCT/US21/59837 titled “PATIENT-SPECIFIC VERTEBRAL IMPLANTS WITH POSITIONING FEATURES,” filed Nov. 18, 2021, the entirety of which is incorporated by reference herein. For example, and as described in greater detail below with respect to FIGS. 4 and 5, the connection mechanism 330 can include a rigid connection including, for example, one or more screws (e.g., bone screws), bolts (e.g., a lag blot, a carriage bolt, a hex bolt, a machine screw, a wood screw, etc.), a rigid metal arm, etc. Semi-rigid connections can include a semi-rigid metal arm (e.g., a slotted arm, a flexible arm, etc.), arm with cut-out or bend points, etc. In some embodiments, the connection mechanism 330 can be a key and slot mechanism, a magnet, a rivet, a tether, or other suitable fastening element(s). In some embodiment, and as best shown in FIG. 3B, the plate 320 can include an aperture 336 or other feature to facilitate connection of the plate 320 to the cage 310. As described in greater detail below with respect to FIG. 6, the cage 310 and the plate 320 are coupled via the connection mechanism 330 before being delivered to the intervertebral disc space. In other embodiments, and as described in greater detail below with respect to FIG. 7, the cage 310 and the plate 320 can be delivered to the intervertebral disc space in an uncoupled state, and the connection mechanism 330 can be used to mechanically couple the cage 310 and the plate 320 once both are implanted.

[0073] The spatial relationship (e.g., a one-dimensional relationship, a two-dimensional relationship, or the three-dimension relationship) of the cage 310 relative to the plate 320 depends at least in part on the connection mechanism 330. As will be described in greater detail below, the desired spatial relationship between the cage 310 and the plate 320 following implantation depends on the relative location of the first target position (e.g., the target position of the cage 310) and the second target position (e.g., the target position of the plate 320). The connection mechanism 330 can therefore be designed to connect the cage 310 to the plate 320 to form the specific dimensional spatial relationship that simultaneously permits the cage 310 to occupy the first target position and the plate 320 to occupy the second target position. For example, the connection mechanism 330 can be in the form of a flexible tether that maintains a one-dimensional spatial relationship (e.g., a maximum distance from the cage to the plate 320). By way of another example, the connection mechanism 330 can be a semi-rigid arm capable of flexing in the inferior and superior direction to allow a desired level of flexion of the spine. The semi-rigid arm can maintain a two-dimensional relationship between the cage 310 and plate 320 to limit or prevent lateral movement of the cage 310.

[0074] Although the plate 320 is illustrated in FIG. 3B as having a width or lateral dimensions less than a width of the cage 310, in other embodiments the plate can have a width equal to and/or greater than the width of the cage 310. For example, in at least some embodiments the plate 320 can extend across an entire width of the if the cage and/or the adjacent vertebra. In such embodiments, the connection mechanism 330 and/or the intermediate portion 344 can have a width equal to or less than the width of the plate 320, e.g., such that the connection mechanism 330 and/or the intermediate portion 344 can contact an entire side (e.g., an entire anterior side) of the cage 310. This can reduce or prevent the cage 310 from moving in an anterior direction when implanted in the target position.

[0075] In some embodiments, the implant 300 can include a plurality of plates at least generally similar or identical in structure and/or function to the plate 320, and each of the plurality of plates can be coupled to the cage 310 by a connection mechanism. In some embodiments, the implant 300 can include a plurality of plates and a plurality of corresponding cages at least generally similar or identical in structure and/or function to the cage 310, and each of the plates can be coupled to the corresponding cage by a connection mechanism.

[0076] Although the implants in FIGS. 1A-3B are shown as implanted relative to specific vertebral bodies (e.g., the implant 100 is shown relative to the L4 and L5 vertebral bodies), the implants described herein can be designed to be implanted relative to and/or between other vertebral bodies, including those in the cervical, thoracic, and lumbar regions (e.g., S1-L4, L2-T12, C3-C4, etc.). Moreover, although the implants shown in FIGS. 2A and 2B include a “cage” and a “plate”, the present technology is not limited to such embodiments. Rather, the present technology can include other types of interbody devices and orthopedic implants. Additionally, because the implants described herein are designed to match individual patient anatomy, the size, shape, and geometry of the implants will vary according to individual patient anatomy. The present technology is thus not limited to any particular implant design or configuration, and can therefore include other implants beyond those expressly illustrated or described herein.

[0077] FIG. 4 is a partially schematic top view of a patient-specific implant 400 configured in accordance with embodiments of the present technology. The implant 400 can be at least generally similar or identical in structure and/or function to any of the patient-specific implants 100, 200, 300 previously described herein. For example, the implant 400 can include an interbody element or cage 410, a positioning element or plate 420, and a connection mechanism 430 configured to couple the cage 410 to the plate 420. The cage 410, the plate 420, and/or the connection mechanism 430 can have patient-specific features (e.g., geometry, topography, etc.), such as any of the patient-specific features previously described herein. The plate 420 can have one or more apertures 424 that extend between a first (e.g., outer) surface 423 and a second (e.g., inner) surface 422. Once the implant 400 is implanted in a patient, one or more screws (not shown) can be inserted through the apertures 424 and secured to an anatomical structure (e.g., screwed into one or more vertebral bodies).

[0078] As illustrated, certain aspects of the connection mechanism 430 can be integral with the plate 420. For example, the plate 420 can be connected to or include an integral projection 432 (e.g., arm, extension, lever, etc.) that extends transversely from the plate 420. In some embodiments, the integral projection 432 can be at least generally similar or identical in structure and/or function to the intermediate projection 144 of FIGS. 1A-1C. The projection 432 can have a hollow interior defining a lumen or other opening 434 (shown using dashed line in FIG. 4) that is aligned with an aperture 436 extending through the plate 420. As described below, a screw or other fastening element (e.g., a lag blot, a carriage bolt, a hex bolt, a machine screw, a wood screw, etc.) can be inserted into the lumen 434 via the aperture 436. A distal end portion of the projection 432 can fit within a corresponding recess or receiving feature 416 in the cage 410. The recess 416 may include a receiver 417, which in some embodiments defines a threaded female connector for receiving a corresponding threaded male connector inserted through the projection 432 via the lumen 434. For example, the receiver 417 can align with the lumen 434 when the projection 432 is advanced into the recess 416, such that a screw or other fastening element can be inserted through the aperture 436 of the plate 420, advanced through the lumen 434 of the projection 432, and secured (e.g., threadably secured) to the receiver 417, thereby securing the plate 420 to the cage 410.

[0079] Additionally, or alternatively, the connection mechanism 430 can couple the plate 420 to the cage 410 using other suitable mechanisms. For example, in some embodiments the receiver 417 may comprise one or more magnets that adhere to the distal end portion of the projection 432 when it is inserted into the recess 416 to magnetically couple the plate 420 to the cage 410. As another example, the connection mechanism 430 can utilize a key and slot mechanism, in which the projection can include one or more key features configured to releasably engage one or more slot features in the recess 416 to releasably couple the plate 420 to the cage 410. In yet other embodiments, the plate 420 can be coupled to the cage 410 using a rivet, a tether, or another suitable connection mechanism.

[0080] In some embodiments, the connection mechanism 430 can form a rigid (e.g., inelastic) interface between the plate 420 and the cage 410 that minimizes and/or reduces strain in response to external stresses. For example, the connection mechanism 430 may be rigid so as to retain a predetermined three-dimensional orientation between the cage 410 and the plate 420 even if one or both of the cage 410 or the plate 420 is subjected to mechanical stress. In embodiments in which the connection mechanism 430 is rigid, the connection mechanism 430 may include one or more metal screws or bolts extending substantially the entire length of the projection 432.

[0081] In some embodiments, the connection mechanism 430 can form a semi-rigid interface between the plate 420 and the cage 410 to minimize strain in response to external stresses while permitting some degree of relative motion between the plate 420 and the cage 410 to account for changes in patient anatomy during patient motion. For example, in some embodiments the connection mechanism 430 may permit motion of up to 5 degrees, 10 degrees, 15 degrees, etc. in at least one plane of motion. In embodiments in which the connection mechanism 430 is semi-rigid, one or more aspects of the connection mechanism 430 (e.g., the projection 432) can be composed of an at least partially elastic or flexible material (e.g., nitinol, silicone, rubber, etc.) and/or include one or more motion segments or joints.

[0082] Regardless of its composition, the connection mechanism 430 provides a specific (e.g., patient-specific) three-dimensional spatial relationship/orientation between the plate 420 and the cage 410 when the plate 420 is coupled to the cage 410 via the connection mechanism 430. Accordingly, the projection 432, the recess 416, and other associated features can be designed such that, when the plate 420 is secured to the cage 410, the plate 420 and the cage 410 assume a predetermined orientation and/or position relative to each other. For example, because the cage 410 is designed to be implanted at a first target position and the plate 420 is designed to be implanted at a second target position, coupling the plate 420 to the cage 410 causes the plate 420 and the cage 410 to assume an orientation that enables the cage 410 to be in the first target position and simultaneously allows the plate 420 to be in the first target position. As a result, and as described in more detail later, coupling the plate 420 to the cage 410 when the plate 420 is at the second target position can automatically position the plate 420 and the cage 410 at their predetermined orientations/positions, which can move the cage 410 to occupy the first target position.

[0083] FIG. 5 is a partially schematic top view of a patient-specific implant 500 configured in accordance with embodiments of the present technology. The implant 500 can be generally similar to any of the patient-specific implants previously described. For example, the implant 500 can include an interbody element or cage 510, a positioning element or plate 520, and a connection mechanism 530 configured to couple the cage 510 to the plate 520. The cage 510, the plate 520, and/or the connection mechanism 530 can have patient-specific features (e.g., geometry, topography, etc.), such as any of the patient-specific features previously described herein. The plate 520 can have one or more apertures 524 that extend between a first (e.g., outer) surface 523 and a second (e.g., inner) surface 522. Once the implant 500 is implanted in a patient, one or more screws can be inserted through the apertures 524 and secured to an anatomical structure (e.g., screwed into one or more vertebral bodies).

[0084] As with the connection mechanism 430 of the implant 400, certain aspects of the connection mechanism 430 can be integral with the plate 420. For example, the plate 520 can be connected to or include an integrated projection 532 (e.g., arm, extension, lever, etc.) that extends transversely from the plate 520. The projection 532 can be generally similar or the same as the intermediate projection 144 of FIGS. 1A-1C. The projection 532 can have a hollow interior defining a lumen or other opening 534 that is aligned with an aperture 536 in the plate 520. Unlike the connection mechanism 430 of the implant 400, the cage 510 does not include a recess for slidable receiving a distal end portion of the projection 532. Rather, the cage 510 includes a threaded receiver 517 defining a threaded female connector for receiving a corresponding threaded male connector. The threaded receiver 517 extends inwardly from an outer surface of the cage 510 (as opposed to extending inwardly from a recess, such as the recess 416 shown in FIG. 4). Once the projection 532 is generally aligned with the threaded receiver 517, a screw or other fastening element (not shown) can be inserted through the aperture 536 of the plate 520, advanced through the lumen 534 of the projection 532, and threadably secured to the threaded receiver 517 to secure the plate 520 to the cage 510.

[0085] In some embodiments, the connection mechanism 530 can form a rigid (e.g., inelastic) and/or semi-rigid connection interface between the plate 520 and the cage 510 that minimizes and/or reduces strain in response to external stresses. For example, the connection mechanism 530 may retain a predetermined three-dimensional orientation between the cage 510 and the plate 520 even if one or both of the cage 510 or the plate 520 is subjected to mechanical stress.

[0086] Similar to the connection mechanism 430, the connection mechanism 530 provides a specific (e.g., patient-specific) three-dimensional spatial relationship/orientation between the plate 520 and the cage 510. Accordingly, the projection 532, the threaded receiver 517, and other associated features can be designed with an orientation such that, when the plate 520 is secured to the cage 510, the plate 520 and the cage 510 assume a predetermined orientation and position relative to each other. In particular, because the cage 510 is designed to be implanted at a first target position and the plate 520 is designed to be implanted at a second target position, coupling the plate 520 to the cage 510 causes the plate 520 and the cage 510 to assume an orientation that enables the cage 510 to be in the first target position and simultaneously allows the plate 520 to be in the first target position. As a result, and as described in more detail below, coupling the plate 520 to the cage 510 when the plate 520 is at the second target position forces the plate 520 and the cage 510 into the predetermined orientation, which can direct the cage 510 to occupy the first target position.

[0087] The present technology also provides methods for implanting patient-specific vertebral devices at a target region or proximate to a patient's spine. FIG. 6 is a flowchart of a method 600 for implanting a patient-specific vertebral implant having a cage and a plate assembled ex vivo. The method 600 can include any of the implants, plates, and/or cages described herein.

[0088] The method 600 can include, in step 602, coupling a plate to a cage, e.g., to form a patient-specific implant. The plate can be coupled to the cage via any of the connection mechanisms described herein. Step 604 is performed before the implant is implanted into the patient, and can be performed by a surgeon, a surgical robotic platform, and/or a surgeon assisted by a surgical robotic platform. In some embodiments, for example, the plate and cage are manufactured as separate components and are coupled together in the operating room as part of the pre-operative procedure, or any other ex vivo procedure. In other embodiments, the plate and the cage can be manufactured in a coupled state (e.g., the plate and the cage can be a unitary or integral component). In such embodiments, the step 602 can be omitted. Regardless, once coupled, the cage and plate can assume a predetermined three-dimensional orientation that enables the cage to occupy a cage target position at least partially contact a first anatomical structure(s), and the plate to simultaneously occupy a plate target position at least partially contacting a second anatomical structure(s).

[0089] The method 600 continues in step 604 by delivering the implant to the implant target region at or proximate the patient's spine. In some embodiments, the implant target region can be proximate to the cage target position and/or the plate target position. Accordingly, once the implant is delivered to the implant target region, the plate can be moved to the plate target position, and/or the cage can be moved to the cage target position. Step 604 can be performed by a surgeon, a surgical robotic platform, and/or a surgeon assisted by a surgical robotic platform.

[0090] At step 606, the plate can be moved to the plate target position. This can be done by a surgeon, a surgical robotic platform, and/or a surgeon assisted by a surgical robotic platform. In some embodiments, a surgeon performing or otherwise assisting with the surgery can directly visualize the plate target position, enabling the surgeon to accurately position the plate at the plate target position. In some embodiments, because the plate has a patient-specific topography/geometry configured to mate with the second anatomical structure(s) at the plate target position, the surgeon will be able to tell when the plate is at the plate target position based on the physical interaction between the plate and the second anatomical structure(s) (e.g., the plate “fits” with the second anatomical structure(s) when placed at the plate target position). In some embodiments, the plate can be secured at the plate target position by inserting a screw or other fastening element through one or more apertures in the plate and into the second anatomical structure(s).

[0091] Because the plate is coupled to the cage in a predetermined three-dimensional orientation, positioning the plate at the plate target position automatically positions the cage at the cage target position. Accordingly, positioning the plate at the plate target position also positions (e.g., automatically positions) the cage at the first target position. Without being bound by theory, placing the cage and plate at their respective target positions is expected to optimize the benefit of and/or minimize the side effects of the implant. In particular, the full benefit of the implant may only be realized when the implant is accurately placed at the target position. The method 600 can optionally continue in step 608 by confirming that the cage is in the cage target position. The position of the cage can be confirmed using one or more conventional imaging technologies known in the art (e.g., X-Ray, MRI, CT-scan, etc.).

[0092] FIG. 7 is a flowchart of a method 700 for implanting a patient-specific vertebral implant having a plate and a cage assembled at least partially in vivo. The method 700 can include a patient-specific implant having a cage and a plate, such as any of the implants, plate, and/or cages described previously.

[0093] In step 702, the cage is delivered to a location proximate a cage target position, and in step 704, the plate is delivered to a location proximate a plate target position. The cage can be configured to mate with a first anatomical structure(s) in the cage target position, and the plate can be configured to mate with a second anatomical structure(s) at the second target position. However, unlike described above with respect to method 600, the cage and the plate are not coupled together before delivering the cage to the target position in the method 700. Without being bound by theory, delivering the cage and the plate in an uncoupled state is expected to increase the maneuverability of these components and/or reduce the size of the surgical corridor needed to deliver these components to the spinal cord region.

[0094] The method 700 can continue in step 706 by positioning the plate at the plate target position. This can also be performed by a surgeon, a surgical robotic platform, and/or a surgeon assisted by a surgical robotic platform. In some embodiments, a surgeon performing or otherwise assisting with the surgery can directly visualize the second target position, enabling the surgeon to accurately position the plate at the second target position. In some embodiments, because the plate has a patient-specific topography/geometry configured to mate with the second anatomical structure(s) at the plate target position, the surgeon will be able to tell when the plate is at the plate target position based on the physical interaction between the plate and the second anatomical structure(s) (e.g., the plate “fits” with the second anatomical structure(s) when placed at the plate target position). In some embodiments, the plate can be secured at the plate target position by inserting a screw or other fastening element through one or more apertures in the plate and into the second anatomical structure(s).

[0095] Once the plate is in the plate target position, the method 700 continues in step 708 by coupling (e.g., mechanically coupling) the plate to the cage. The plate can be coupled to the cage using any of the connection mechanisms previously described herein. Because the plate and cage assume a predetermined three-dimensional orientation when coupled, coupling the plate to the cage when the plate is positioned at the plate target position directs the cage to occupy the cage target position. Accordingly, coupling the plate to the cage positions (e.g., automatically positions) the cage at the cage target position. In some embodiments, the steps 706 and 708 can be reversed such that the plate is coupled to the cage before positioning the plate at the plate target position. In such embodiments, once the cage and plate are coupled, positioning the plate at the plate target position directs the cage to occupy the cage target position. As previously described, positioning the cage and plate at their respective target positions is expected to optimize the benefit of and/or minimize the side effects of the implant. In particular, the full benefit of the implant may only be realized when the implant is accurately placed at the target position. The method 700 can optionally continue in step 710 by confirming that the cage is in the cage target position, and/or confirming that the plate is in the plate target position. The position of the cage and/or plate can be confirmed using one or more conventional imaging technologies known in the art (e.g., X-Ray, MRI, CT-scan, etc.).

[0096] As one skilled in the art will appreciate from the foregoing description, the present technology can utilize the patient-specific nature of the implant components (e.g., the plate and the cage) to make it easier to position the cage at a cage target position. For example, because the cage and the plate are coupled together in a predetermined three-dimensional orientation, positioning the plate at a plate target position directs the cage toward and/or to the cage target position. Thus, positioning the plate at the plate target position also positions the cage at the cage target position. It may be generally easier for a surgeon to position the plate at the plate target position than it is to position the cage at the cage target position. For example, plates are typically positioned along an anterior surface of the vertebral column and/or at an anterior margin of the disc space that is generally visible to the surgeon, whereas cages are typically positioned at a location in the disc space out of view of the surgeon. Therefore, by mechanically coupling the plate and cage in a predetermined three-dimensional orientation, the surgeon can simply position the plate at the easier-to-visualize plate target position, simplifying the implant procedure. The patient-specific nature of the implants provides additional benefits, such as improved fit, improved outcomes, and/or reduced side effects, as previously described.

[0097] The present technology also provides system and methods for designing and manufacturing patient-specific implants, such as any of the patient-specific vertebral implants described herein. FIG. 8 is a network connection diagram illustrating a computing system 800 for providing patient-specific medical care and configured in accordance with select embodiments of the present technology. The system 800 is configured to design a patient-specific implant and/or generate a patient-specific surgical plan for a patient. For example, the system 800 can generate an implant and/or generate a surgical plan for a patient suffering from an orthopedic or spinal disease or disorder, such as trauma (e.g., fractures), cancer, deformity, degeneration, pain (e.g., back pain, leg pain), irregular spinal curvature (e.g., scoliosis, lordosis, kyphosis), irregular spinal displacement (e.g., spondylolisthesis, lateral displacement axial displacement), osteoarthritis, lumbar degenerative disc disease, cervical degenerative disc disease, lumbar spinal stenosis, or cervical spinal stenosis, or a combination thereof. The surgical plan can include surgical information, surgical plans (e.g., surgical implant procedure, target implant location and/or orientation, etc.), technology recommendations (e.g., device and/or instrument recommendations), and/or medical device designs. For example, the surgical plan can include at least one treatment procedure (e.g., a surgical procedure or intervention) and/or at least one medical device (e.g., an implanted medical device (also referred to herein as an “implant” or “implanted device”) or implant delivery instrument).

[0098] The system 800 includes a computing device 802, which can be a user device, such as a smart phone, mobile device, laptop, desktop, personal computer, tablet, phablet, or other such devices known in the art. As discussed in greater detail with reference to FIG. 9, the computing device 802 can include one or more processors, and memory storing instructions executable by the one or more processors to perform select methods described herein. The computing device 802 can be associated with a healthcare provider that is treating the patient. Although FIG. 8 illustrates a single computing device 802, in alternative embodiments, the computing device 802 can instead be implemented as a computing system encompassing a plurality of computing devices, such that the operations described herein with respect to the computing device 802 can instead be performed by the computing system and/or the plurality of computing devices.

[0099] The computing device 802 is configured to receive a patient data set 808 associated with a patient to be treated. The patient data set 808 can include data representative of the patient's condition, anatomy, pathology, symptoms, medical history, preferences, and/or any other information or parameters relevant to the patient. For example, the patient data set 808 can include surgical intervention data, treatment outcome data, progress data (e.g., physician notes), patient feedback (e.g., feedback acquired using quality of life questionnaires, surveys), clinical data, patient information (e.g., demographics, sex, age, height, weight, type of pathology, occupation, activity level, tissue information, health rating, comorbidities, health related quality of life (HRQL)), vital signs, diagnostic results, medication information, allergies, image data (e.g., camera images, Magnetic Resonance Imaging (MRI) images, ultrasound images, Computerized Aided Tomography (CAT) scan images, Positron Emission Tomography (PET) images, X-Ray images), diagnostic equipment information (e.g., manufacturer, model number, specifications, user-selected settings/configurations, etc.), or the like. In some embodiments, the patient data set 808 includes data representing one or more of patient identification number (ID), age, gender, body mass index (BMI), lumbar lordosis, Cobb angle(s), pelvic incidence, disc height, segment flexibility, bone quality, rotational displacement, and/or treatment level of the spine.

[0100] In some embodiments, the computing device 802 can also be configured to receive a surgical team data set 810. The surgical team data set 810 can include data representative of the surgical team that will perform the surgery on the patient. For example, the surgical team data set 810 can include preferences of the surgical team (e.g., preferred implant techniques, preferred implant instruments/tools, etc.), experience of the surgical team (e.g., past procedures performed by the surgical team), scored outcomes of past procedures performed by the surgical team, or the like. As used herein, the term “surgical team” can refer to a group of healthcare practitioners that work together in an operating room during an implant procedure, or to one or more individual surgeons.

[0101] In some embodiments, the computing device 802 can also be configured to receive a facility or provider data set 812. The facility data set 812 can include data representative of the facility at which the patient's surgery will occur. For example, the facility data set 812 can include preferences of the facility (e.g., preferred implant techniques, preferred implant instruments/tools, etc.), experience of the facility (e.g., past procedures performed at the facility), scored outcomes of past procedures performed at the facility, infrastructure available to assist/perform the surgery (e.g., availability of robotic surgical platforms, as well as the type of “input” required to control the “output” of the robotic surgical platforms), or the like. As used herein, the term “facility” can refer to a single operating room facility, a hospital having multiple operating rooms, and/or a network of hospitals.

[0102] The computing device 802 is operably connected via a communication network 804 to a server 806, thus allowing for data transfer between the computing device 802 and the server 806. The communication network 804 may be a wired and/or a wireless network. The communication network 804, if wireless, may be implemented using communication techniques such as Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), Long term evolution (LTE), Wireless local area network (WLAN), Infrared (IR) communication, Public Switched Telephone Network (PSTN), Radio waves, and/or other communication techniques known in the art.

[0103] The server 806, which may also be referred to as a “treatment assistance network” or “prescriptive analytics network,” can include one or more computing devices and/or systems. As discussed further herein, the server 806 can include one or more processors, and memory storing instructions executable by the one or more processors to perform the methods described herein. In some embodiments, the server 806 is implemented as a distributed “cloud” computing system or facility across any suitable combination of hardware and/or virtual computing resources.

[0104] The computing device 802 and/or the server 806 can design a patient-specific implant (“implant”) based at least in part on the patient data set 808, the surgical team data set 810, and/or the facility data set 812. For example, the server 806 may include a treatment planning module 818 that can design, based at least partially on any of the foregoing data inputs, the implant. In some embodiments, designing the implant includes designing a vertebral implant including a plate and/or a cage, such as any of the implants described with respect to FIGS. 1A-5, that are configured to mate with one or more corresponding target anatomical structures. The computing device 802 and/or the server 806 can design an interbody device (e.g., a cage), a positioning feature (e.g., a plate), a connection mechanism, and/or one or more fastening elements (e.g., a screw). For example, to design the connection mechanism, the target position of the cage can be determined by analyzing images of the patient. The patient's spine can be analyzed to identify a suitable target site for the plate. For example, individual vertebral bodies of the patient's spine can be analyzed to identify regions with suitable geometry and mechanical properties to interface with the plate. The computing device 802 and/or the server 806 can design the implant (e.g., the plate) based on a level of movement (e.g., a maximum level of relative movement) between the plate, the vertebral bodies, and/or the cage. The target spatial relationship between the components of the implant can be determined based on the patient data and targeted outcome.

[0105] Additional implants include, but are not limited to, screws (e.g., bone screws, spinal screws, pedicle screws, facet screws), other interbody implant devices, rods, discs, fusion devices, spacers, rods, expandable devices, stents, brackets, ties, scaffolds, fixation device, anchors, nuts, bolts, rivets, connectors, tethers, fasteners, joint replacements (e.g., artificial discs), hip implants, or the like. A patient-specific implant design can include data representing one or more of physical properties (e.g., size, shape, volume, material, mass, weight), mechanical properties (e.g., stiffness, strength, modulus, hardness), and/or biological properties (e.g., osteo-integration, cellular adhesion, anti-bacterial properties, anti-viral properties) of the implant. For example, a design for an orthopedic implant can include implant shape, size, material, and/or effective stiffness (e.g., lattice density, number of struts, location of struts, etc.).

[0106] The implant can be designed to match the patient's existing anatomy. For example, the implant can be designed such that various surfaces of the implant mate with corresponding surfaces of patient anatomy, as previously described. In some embodiments, the implant can be designed to provide a correction to the patient's existing anatomy in addition to mating with one or more surfaces of the patient anatomy. For example, the treatment planning module 818 may analyze image data of the patient's native anatomy to determine whether an anatomical correction is needed. The image data may show the patient's native anatomical configuration (e.g., pre-operative anatomy), such as the geometry, orientation, and topography of various anatomical features. In some embodiments, for example, the image data may show (and/or be used to determine) various anatomical characteristics, including, but not limited to, vertebral spacing, vertebral orientation, vertebral translation, abnormal bony growth, abnormal joint growth, joint inflammation, joint degeneration, tissue degeneration, stenosis, scar tissue, lumbar lordosis, Cobb angle(s), pelvic incidence, disc height, segment flexibility, rotational displacement, and other spinal tissue characteristics. If an anatomical correction is not required, the treatment planning module 818 can design the implant to fit the patient's native anatomy. If an anatomical correction is required, the treatment planning module 818 can design the implant such that, when the implant is implanted in the patient, it provides the anatomical correction. Additional details for designing patient-specific implants to provide one or more desired anatomical corrections can be found in U.S. application Ser. No. 16/987,113, filed Aug. 6, 2020, the disclosure of which is incorporated by reference herein in its entirety.

[0107] In some embodiments, the generated implant design is a design for an entire device. Alternatively, the generated design can be for one or more components of a device (e.g., a plate or a cage), rather than the entire device. In some embodiments, the implant design is for one or more patient-specific device components that can be used with standard, off-the-shelf components. For example, in a spinal surgery, a pedicle screw kit can include both standard components and patient-specific customized components. In some embodiments, the generated design is for a patient-specific medical device that can be used with a standard, off-the-shelf delivery instrument. For example, the implants (e.g., screws, screw holders, rods) can be designed and manufactured for the patient, while the instruments for delivering the implants can be standard instruments. This approach allows the components that are implanted to be designed and manufactured based on the patient's anatomy and/or surgeon's preferences to enhance treatment. The implants described herein are expected to improve delivery into the patient's body, placement at the treatment site, and/or interaction with the patient's anatomy.

[0108] The computing system 802 and/or the server 806 can also design a patient-specific surgical plan (“surgical plan”) based on the patient data set 808, the surgical team data set 810, and/or the facility data set 812. The surgical plan can include a detailed procedure for implanting the implant to a specific target position within the patient. For example, the surgical plan can include aspects of a pre-operative plan (e.g., detection and measurement of patient's anatomy, preparation of patient for a surgical procedure, etc.), a surgical procedure, a surgical approach (e.g., implant technique), one or more surgical steps (preparing tissue for an incision, making an incision, making a resection, removing tissue, manipulating tissue, performing a corrective maneuver, delivering the implant to a target site, deploying the implant at the target site, adjusting the implant at the target site, manipulating the implant once it is implanted, securing the implant at the target site, explanting the implant, suturing tissue, etc.) a target position, site, or location of the implant (e.g., a location, orientation, etc.), and other aspects related to pre-operative, operative, or post-operative plans.

[0109] In some embodiments, the surgical plan includes an orthopedic surgical procedure such as spinal surgery, hip surgery, knee surgery, jaw surgery, hand surgery, shoulder surgery, elbow surgery, total joint reconstruction (arthroplasty), skull reconstruction, foot surgery, or ankle surgery. Spinal surgery can include spinal fusion surgery, such as posterior lumbar interbody fusion (PLIF), anterior lumbar interbody fusion (ALIF), transverse or transforaminal lumbar interbody fusion (TLIF), lateral lumbar interbody fusion (LLIF), direct lateral lumbar interbody fusion (DLIF), extreme lateral lumbar interbody fusion (XLIF), and/or sacroiliac joint fusion (SLIF). Spinal surgery can also include non-fusion surgeries, such as artificial disc replacements. In some embodiments, the surgical procedure includes descriptions of and/or instructions for performing one or more aspects of a patient-specific surgical procedure. For example, the surgical procedure can include one or more of a surgical approach, a corrective maneuver, or a bony resection.

[0110] In some embodiments, the surgical plan includes a target position of the implant. In some embodiments, the surgical plan optionally includes a recommendation to remove tissue to clear space for the implant at the target position. For example, the surgical plan may include instructions to perform an osteotomy, muscular resection, soft tissue detachment, soft tissue retraction, discectomy, or the like to prepare the patient to receive the patient-specific implant. In some embodiments, the surgical plan includes a manipulation of tissue to prepare the patient to receive the implant. For example, the surgical plan may include instructions to adjust a relative position of two vertebrae, increase a distance between two vertebrae, and/or the like.

[0111] In some embodiments, the surgical plan includes machine-readable instructions for carrying out various steps of the surgical plan. The machine-readable instructions can be configured such that, when executed by a surgical robotic platform, the machine-readable instructions cause the surgical robotic platform to execute various aspects of an operative procedure associated with implanting the implant. For example, the surgical platform may prepare tissue for an incision, make an incision, make a resection, remove tissue, manipulate tissue, perform a corrective maneuver, deliver the implant to a target site, deploy the implant at the target site; adjust a configuration of the implant at the target site, manipulate the implant once it is implanted, secure the implant at the target site, explant the implant, suture tissue, and the like. The instructions may therefore include particular instructions for articulating robotic arms, instruments, and/or tools to perform or otherwise aid in the delivery of the patient-specific implant.

[0112] In some embodiments, the surgical plan includes step-by-step written, verbal, and/or graphic instructions that show a surgeon how to perform the patient-specific surgical plan. The patient-specific surgical plan can be displayed to the surgeon before and/or during the operative procedure (e.g., via display 822). In some embodiments, the written, verbal, and/or graphic instructions can be encoded in computer-readable instructions. The encoded instructions can be decoded and displayed to the surgeon before and/or during the operative procedure. In some embodiments, the patient-specific surgical plan includes both machine-readable instructions and written, verbal, and/or graphic illustrations.

[0113] In some embodiments, the system 800 may consider one or more reference data sets when designing the patient-specific implant and/or the patient-specific surgical plan. For example, in some embodiments the server 806 includes at least one database 820 configured to store reference data useful for the treatment planning methods described herein. The reference data can include historical and/or clinical data from the same or other patients, data collected from prior surgeries and/or other treatments of patients by the same or other healthcare providers, data relating to medical device designs, data collected from study groups or research groups, data from practice databases, data from academic institutions, data from implant manufacturers or other medical device manufacturers, data from imaging studies, data from simulations, clinical trials, demographic data, treatment data, outcome data, mortality rates, or the like.

[0114] In some embodiments, the database 820 includes a plurality of reference patient data sets, each patient reference data set associated with a corresponding reference patient. For example, the reference patient can be a patient that previously received treatment or is currently receiving treatment. Each reference patient data set can include data representative of the corresponding reference patient's condition, anatomy, pathology, medical history, preferences, and/or any other information or parameters relevant to the reference patient, such as any of the data described herein with respect to the patient data set 808. In some embodiments, the reference patient data set includes pre-operative data, intra-operative data, and/or post-operative data. For example, a reference patient data set can include data representing one or more of patient ID, age, gender, BMI, lumbar lordosis, Cobb angle(s), pelvic incidence, disc height, segment flexibility, bone quality, rotational displacement, and/or treatment level of the spine. As another example, a reference patient data set can include treatment data regarding at least one treatment procedure performed on the reference patient, such as descriptions of surgical procedures or interventions (e.g., surgical approaches, bony resections, surgical maneuvers, corrective maneuvers, placement of implants or other devices). In some embodiments, the treatment data includes medical device design data for at least one medical device used to treat the reference patient, such as physical properties (e.g., size, shape, volume, material, mass, weight), mechanical properties (e.g., stiffness, strength, modulus, hardness), and/or biological properties (e.g., osteo-integration, cellular adhesion, anti-bacterial properties, anti-viral properties). In yet another example, a reference patient data set can include outcome data representing an outcome of the treatment of the reference patient, such as corrected anatomical metrics, presence of fusion, HRQL, activity level, return to work, complications, recovery times, efficacy, mortality, and/or follow-up surgeries.

[0115] In some embodiments, the server 806 receives at least some of the reference patient data sets from a plurality of healthcare provider computing systems. Each healthcare provider computing system can include at least one reference patient data set (e.g., reference patient data sets) associated with reference patients treated by the corresponding healthcare provider. The reference patient data sets can include, for example, kinematic records, electronic medical records, electronic health records, biomedical data sets, etc.

[0116] In embodiments in which the implant and/or the surgical plan is designed based on the reference data, the data analysis module 816 can include one or more algorithms for identifying a subset of reference data from the database 820 that is likely to be useful in developing a treatment plan. For example, the data analysis module 816 can compare patient-specific data (e.g., the patient data set 808 received from the computing device 802) to the reference data from the database 820 (e.g., the reference patient data sets) to identify similar data (e.g., one or more similar patient data sets in the reference patient data sets). The comparison can be based on one or more parameters, such as age, gender, BMI, pathology, kinematics, lumbar lordosis, pelvic incidence, and/or treatment levels. The parameter(s) can be used to calculate a similarity score for each reference patient. The similarity score can represent a statistical correlation between the patient data set 808 and the reference patient data set. Accordingly, similar patients can be identified based on whether the similarity score is above, below, or at a specified threshold value. For example, as described in greater detail below, the comparison can be performed by assigning values to each parameter and determining the aggregate difference between the subject patient and each reference patient. Reference patients whose aggregate difference is below a threshold can be considered to be similar patients. In some embodiments, the data analysis module 816 includes one or more algorithms that select a set or subset of the reference patient data based on criteria other than patient parameters, such as the surgical team data set 810 (e.g., based on surgeon expertise, outcomes of particular types of procedures performed by the surgeon, etc.) and/or the facility data set 812 (e.g., surgical equipment such as surgical robots).

[0117] The data analysis module 816 can further be configured with one or more algorithms to select a subset of the reference patient data sets, e.g., based on similarity to the patient data set 808 and/or treatment outcome of the corresponding reference patient. For example, the data analysis module 816 can identify one or more similar patient data sets in the reference patient data sets, and then select a subset of the similar patient data sets based on whether the similar patient data set includes data indicative of a favorable or desired treatment outcome. The outcome data can include data representing one or more outcome parameters, such as corrected anatomical metrics, range of motion, kinematic data, HRQL, activity level, complications, recovery times, efficacy, mortality, or follow-up surgeries. As described in further detail below, in some embodiments, the data analysis module 816 calculates an outcome score by assigning values to each outcome parameter. A patient can be considered to have a favorable outcome if the outcome score is above, below, or at a specified threshold value.

[0118] In some embodiments, the data analysis module 816 selects a subset of the reference patient data sets based at least in part on user input (e.g., from a clinician, surgeon, physician, healthcare provider). For example, the user input can be used in identifying similar patient data sets. In some embodiments, weighting of similarity and/or outcome parameters can be selected by a healthcare provider or physician to adjust the similarity and/or outcome score based on clinician input. In further embodiments, the healthcare provider or physician can select the set of similarity and/or outcome parameters (or define new similarity and/or outcome parameters) used to generate the similarity and/or outcome score, respectively.

[0119] In some embodiments, the data analysis module 816 includes one or more algorithms used to select a set or subset of the reference patient data sets based on criteria other than patient parameters. For example, the one or more algorithms can be used to select the subset based on healthcare provider parameters (e.g., based on healthcare provider ranking/scores such as hospital/physician expertise, number of procedures performed, hospital ranking, etc.) and/or healthcare resource parameters (e.g., diagnostic equipment, facilities, surgical equipment such as surgical robots), or other non-patient related information that can be used to predict outcomes and risk profiles for procedures for the present healthcare provider. For example, reference patient data sets with images captured from similar diagnostic equipment can be aggregated to reduce or limit irregularities due to variation between diagnostic equipment. Additionally, patient-specific treatment plans can be developed for a particular health-care provider using data from similar healthcare providers (e.g., healthcare providers with traditionally similar outcomes, physician expertise, surgical teams, etc.). In some embodiments, reference healthcare provider data sets, hospital data sets, physician data sets, surgical team data sets, post-treatment data set, and other data sets can be utilized. By way of example, a patient-specific treatment plan to perform a battlefield surgery can be based on reference patient data from similar battlefield surgeries and/or datasets associated with battlefield surgeries. In another example, the patient-specific treatment plan can be generated based on available robotic surgical systems. The reference patient data sets can be selected based on patients that have been operated on using comparable robotic surgical systems under similar conditions (e.g., size and capabilities of surgical teams, hospital resources, etc.).

[0120] In embodiments in which the implant and/or the surgical plan is designed based on the reference data, the treatment planning module 818 can include one or more algorithms that generate the implant and/or the surgical plan based on the reference data. In some embodiments, the treatment planning module 818 is configured to develop and/or implement at least one predictive model for generating the treatment plan, also known as a “prescriptive model.” The predictive model(s) can be developed using clinical knowledge, statistics, machine learning, AI, neural networks, or the like. In some embodiments, the output from the data analysis module 816 is analyzed (e.g., using statistics, machine learning, neural networks, AI, etc.) to identify correlations between data sets, patient parameters, healthcare provider parameters, healthcare resource parameters, treatment procedures, medical device designs, and/or treatment outcomes. These correlations can be used to develop at least one predictive model that predicts the likelihood that a treatment plan will produce a favorable outcome for the particular patient. The predictive model(s) can be validated, e.g., by inputting data into the model(s) and comparing the output of the model to the expected output.

[0121] In some embodiments, the treatment planning module 818 is configured to generate the implant design based on previous treatment data from reference patients. For example, the treatment planning module 818 can receive a selected subset of reference patient data sets and/or similar patient data sets from the data analysis module 816, and determine or identify treatment data from the selected subset. The treatment data can include, for example, range of motion and/or other kinematic data, treatment procedure data (e.g., surgical procedure or intervention data) and/or medical device design data (e.g. implant design data) that are associated with favorable or desired treatment outcomes for the corresponding patient. The treatment planning module 818 can analyze the treatment procedure data and/or medical device design data to determine an optimal treatment protocol for the patient to be treated. For example, the treatment procedures and/or medical device designs can be assigned values and aggregated to produce a treatment score. The patient-specific treatment plan can be determined by selecting treatment plan(s) based on the score (e.g., higher or highest score; lower or lowest score; score that is above, below, or at a specified threshold value). The personalized treatment plan can be based on, at least in part, the patient-specific technologies or patient-specific selected technology.

[0122] Alternatively or in combination, the treatment planning module 818 can generate the implant designs based on correlations between data sets. For example, the treatment planning module 818 can correlate implant designs and medical device design data from implant designs for similar patients with favorable outcomes (e.g., as identified by the data analysis module 816). Correlation analysis can include transforming correlation coefficient values to values or scores. The values/scores can be aggregated, filtered, or otherwise analyzed to determine one or more statistical significances. These correlations can be used to determine treatment procedure(s) and/or medical device design(s) that are optimal or likely to produce a favorable outcome for the patient to be treated.

[0123] Alternatively or in combination, the treatment planning module 818 can generate designs using one or more AI techniques. AI techniques can be used to develop computing systems capable of simulating aspects of human intelligence, e.g., learning, reasoning, planning, problem solving, decision making, etc. AI techniques can include, but are not limited to, case-based reasoning, rule-based systems, artificial neural networks, decision trees, support vector machines, regression analysis, Bayesian networks (e.g., naïve Bayes classifiers), genetic algorithms, cellular automata, fuzzy logic systems, multi-agent systems, swarm intelligence, data mining, machine learning (e.g., supervised learning, unsupervised learning, reinforcement learning), and hybrid systems.

[0124] In some embodiments, the treatment planning module 818 generates the treatment plan using one or more trained machine learning models. Various types of machine learning models, algorithms, and techniques are suitable for use with the present technology. In some embodiments, the machine learning model is initially trained on a training data set, which is a set of examples used to fit the parameters (e.g., weights of connections between “neurons” in artificial neural networks) of the model. For example, the training data set can include any of the reference data stored in database 820, such as a plurality of reference patient data sets or a selected subset thereof (e.g., a plurality of similar patient data sets).

[0125] In some embodiments, the machine learning model (e.g., a neural network or a naïve Bayes classifier) may be trained on the training data set using a supervised learning method (e.g., gradient descent or stochastic gradient descent). The training dataset can include pairs of generated “input vectors” with the associated corresponding “answer vector” (commonly denoted as the target). The current model is run with the training data set and produces a result, which is then compared with the target, for each input vector in the training data set. Based on the result of the comparison and the specific learning algorithm being used, the parameters of the model are adjusted. The model fitting can include both variable selection and parameter estimation. The fitted model can be used to predict the responses for the observations in a second data set called the validation data set. The validation data set can provide an unbiased evaluation of a model fit on the training data set while tuning the model parameters. Validation data sets can be used for regularization by early stopping, e.g., by stopping training when the error on the validation data set increases, as this may be a sign of overfitting to the training data set. In some embodiments, the error of the validation data set error can fluctuate during training, such that ad-hoc rules may be used to decide when overfitting has truly begun. Finally, a test data set can be used to provide an unbiased evaluation of a final model fit on the training data set.

[0126] To generate the treatment plan, the patient data set 808, the surgical team data set 810, and/or the facility data set 812 can be input into the trained machine learning model(s). Additional data, such as the selected subset of reference patient data sets and/or similar patient data sets, and/or treatment data from the selected subset, can also be input into the trained machine learning model(s). The trained machine learning model(s) can then calculate whether various candidate treatment procedures and/or medical device designs are likely to produce a favorable outcome for the patient. Based on these calculations, the trained machine learning model(s) can select at least one treatment plan for the patient. In embodiments where multiple trained machine learning models are used, the models can be run sequentially or concurrently to compare outcomes and can be periodically updated using training data sets. The treatment planning module 818 can use one or more of the machine learning models based the model's predicted accuracy score.

[0127] The implant design and/or the surgical plan generated by the treatment planning module 818 can be transmitted via the communication network 804 to the computing device 802 for output to a user (e.g., clinician, surgeon, healthcare provider, patient). In some embodiments, the computing device 802 includes or is operably coupled to a display 822. The display 822 can show various aspects of a surgical procedure to be performed on the patient, such as the surgical approach, treatment levels, corrective maneuvers, tissue resection, and/or implant placement. To facilitate visualization, a virtual model of the surgical procedure can be displayed. The display can also show a virtual model of the patient's spine in a native and/or corrected anatomical configuration. Virtual models of the patient's spine in a native and/or corrected anatomical configuration are discussed in greater detail in PCT/US21/12065 (Docket No. 127398-8009.WO00), titled “PATIENT-SPECIFIC MEDICAL PROCEDURES AND DEVICES, AND ASSOCIATED SYSTEMS AND METHODS,” filed Jan. 4, 2021, the entirety of which is incorporated by reference herein.

[0128] Additionally, or alternatively, the display 822 can show a design for the implant, such as a two- or three-dimensional model of the device design. The display 822 can also show patient information, such as two- or three-dimensional images or models of the patient's anatomy where the surgical procedure is to be performed and/or where the device is to be implanted. The display 822 can also display structural features of the implant suitable for contacting anatomical features to improve treatment, reduce implant movement, etc. The structural features can be rigid surfaces (e.g., outer surfaces of an implant body), anchors, fixation features, etc. Images of the implantation site can be analyzed to identify such anatomical features identified by the treatment planning module 818. The computing device 802 can further include one or more user input devices (not shown) allowing the user to modify, select, approve, and/or reject the displayed treatment plan(s).

[0129] In some embodiments, the patient-specific implant design generated by the treatment planning module 818 can be transmitted from the computing device 802 and/or the server 806 to a manufacturing system 824 for manufacturing a corresponding medical device. The manufacturing system 824 can be located on site or off site. On-site manufacturing can reduce the number of sessions with a patient and/or the time to be able to perform the surgery whereas off-site manufacturing can be useful make the complex devices. Off-site manufacturing facilities can have specialized manufacturing equipment. In some embodiments, more complicated device components can be manufactured off site, while simpler device components can be manufactured on site.

[0130] Various types of manufacturing systems are suitable for use in accordance with the embodiments herein. For example, the manufacturing system 824 can be configured for additive manufacturing, such as three-dimensional (3D) printing, stereolithography (SLA), digital light processing (DLP), fused deposition modeling (FDM), selective laser sintering (SLS), selective laser melting (SLM), selective heat sintering (SHM), electronic beam melting (EBM), laminated object manufacturing (LOM), powder bed printing (PP), thermoplastic printing, direct material deposition (DMD), inkjet photo resin printing, or like technologies, or combination thereof. Alternatively or in combination, the manufacturing system 824 can be configured for subtractive (traditional) manufacturing, such as CNC machining, electrical discharge machining (EDM), grinding, laser cutting, water jet machining, manual machining (e.g., milling, lathe/turning), or like technologies, or combinations thereof. The manufacturing system 824 can manufacture one or more patient-specific medical devices based on fabrication instructions or data (e.g., CAD data, 3D data, digital blueprints, stereolithography data, or other data suitable for the various manufacturing technologies described herein). In some embodiments, the patient-specific medical device can include features, materials, and designs shared across designs to simplify manufacturing. For example, deployable patient-specific medical devices for different patients can have similar internal deployment mechanisms but have different deployed configurations. In some embodiments, the components of the patient-specific medical devices are selected from a set of available pre-fabricated components and the selected pre-fabricated components can be modified based on the fabrication instructions or data.

[0131] The treatment plans described herein can be performed by a surgeon, a surgical robot, or a combination thereof, thus allowing for treatment flexibility. In some embodiments, the surgical procedure can be performed entirely by a surgeon, entirely by a surgical robot, or a combination thereof. For example, one step of a surgical procedure can be manually performed by a surgeon and another step of the procedure can be performed by a surgical robot. In some embodiments the treatment planning module 818 generates control instructions configured to cause a surgical robot (e.g., robotic surgery systems, navigation systems, etc.) to partially or fully perform a surgical procedure. The control instructions can be transmitted to the robotic apparatus by the computing device 802 and/or the server 806.

[0132] Following the treatment of the patient in accordance with the treatment plan, treatment progress can be monitored over one or more time periods to update the data analysis module 816 and/or treatment planning module 818. Post-treatment data can be added to the reference data stored in the database 820. The post-treatment data can be used to train machine learning models for developing patient-specific treatment plans, patient-specific medical devices, or combinations thereof.

[0133] It shall be appreciated that the components of the system 800 can be configured in many different ways. For example, in alternative embodiments, the database 820, the data analysis module 816 and/or the treatment planning module 818 can be components of the computing device 802, rather than the server 806. As another example, the database 820, the data analysis module 816, and/or the treatment planning module 818 can be located across a plurality of different servers, computing systems, or other types of cloud-computing resources, rather than at a single server 806 or computing device 802.

[0134] Additionally, in some embodiments, the system 800 can be operational with numerous other computing system environments or configurations. Examples of computing systems, environments, and/or configurations that may be suitable for use with the technology include, but are not limited to, personal computers, server computers, handheld or laptop devices, cellular telephones, wearable electronics, tablet devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, or the like. In some embodiments, the system 800 may include additional features and/or capabilities, such as any of those described in U.S. application Ser. No. 16/735,222, filed Jan. 6, 2020, the disclosure of which is incorporated by reference herein in its entirety.

[0135] FIG. 9 illustrates a computing device 900 suitable for use in connection with the system 800 of FIG. 8, according to an embodiment. The computing device 900 can be incorporated in various components of the system 800 of FIG. 8, such as the computing device 802 or the server 806. The computing device 900 includes one or more processors 910 (e.g., CPU(s), GPU(s), HPU(s), etc.). The processor(s) 910 can be a single processing unit or multiple processing units in a device or distributed across multiple devices. The processor(s) 910 can be coupled to other hardware devices, for example, with the use of a bus, such as a PCI bus or SCSI bus. The processor(s) 910 can be configured to execute one more computer-readable program instructions, such as program instructions to carry out of any of the methods described herein.

[0136] The computing device 900 can include one or more input devices 920 that provide input to the processor(s) 910, e.g., to notify it of actions from a user of the computing device 900. The actions can be mediated by a hardware controller that interprets the signals received from the input device and communicates the information to the processor(s) 910 using a communication protocol. Input device(s) 920 can include, for example, a mouse, a keyboard, a touchscreen, an infrared sensor, a touchpad, a wearable input device, a camera- or image-based input device, a microphone, or other user input devices.

[0137] The computing device 900 can include a display 930 used to display various types of output, such as text, models, virtual procedures, surgical plans, implants, graphics, and/or images (e.g., images with voxels indicating radiodensity units or Hounsfield units representing the density of the tissue at a location). In some embodiments, the display 930 provides graphical and textual visual feedback to a user. The processor(s) 910 can communicate with the display 930 via a hardware controller for devices. In some embodiments, the display 930 includes the input device(s) 920 as part of the display 930, such as when the input device(s) 920 include a touchscreen or is equipped with an eye direction monitoring system. In alternative embodiments, the display 930 is separate from the input device(s) 920. Examples of display devices include an LCD display screen, an LED display screen, a projected, holographic, or augmented reality display (e.g., a heads-up display device or a head-mounted device), and so on.

[0138] Optionally, other I/O devices 940 can also be coupled to the processor(s) 910, such as a network card, video card, audio card, USB, firewire or other external device, camera, printer, speakers, CD-ROM drive, DVD drive, disk drive, or Blu-Ray device. Other I/O devices 940 can also include input ports for information from directly connected medical equipment such as imaging apparatuses, including MRI machines, X-Ray machines, CT machines, etc. Other I/O devices 940 can further include input ports for receiving data from these types of machine from other sources, such as across a network or from previously captured data, for example, stored in a database.

[0139] In some embodiments, the computing device 900 also includes a communication device (not shown) capable of communicating wirelessly or wire-based with a network node. The communication device can communicate with another device or a server through a network using, for example, TCP/IP protocols. The computing device 900 can utilize the communication device to distribute operations across multiple network devices, including imaging equipment, manufacturing equipment, etc.

[0140] The computing device 900 can include memory 950, which can be in a single device or distributed across multiple devices. Memory 950 includes one or more of various hardware devices for volatile and non-volatile storage, and can include both read-only and writable memory. For example, a memory can comprise random access memory (RAM), various caches, CPU registers, read-only memory (ROM), and writable non-volatile memory, such as flash memory, hard drives, floppy disks, CDs, DVDs, magnetic storage devices, tape drives, device buffers, and so forth. A memory is not a propagating signal divorced from underlying hardware; a memory is thus non-transitory. In some embodiments, the memory 950 is a non-transitory computer-readable storage medium that stores, for example, programs, software, data, or the like. In some embodiments, memory 950 can include program memory 960 that stores programs and software, such as an operating system 962, one or more treatment assistance modules 964, and other application programs 966. The treatment assistance module(s) 964 can include one or more modules configured to perform the various methods described herein (e.g., the data analysis module 816 and/or treatment planning module 818 described with respect to FIG. 8). Memory 950 can also include data memory 970 that can include, e.g., reference data, configuration data, settings, user options or preferences, etc., which can be provided to the program memory 960 or any other element of the computing device 900.

[0141] FIG. 10 illustrates various aspects of an operative setup configured in accordance with the present technology. As shown, the operative setup can be used to implant a patient-specific artificial implant 1000 (which can be the same or generally similar to the implants described with respect to FIGS. 1A-5) into a patient P using a robotic surgical platform 1050 (hereinafter referred to as the “platform 1050”). The platform 1050 can be configured to perform or otherwise assist with one or more aspects of the operative procedure, including, for example, preparing tissue for an incision, making an incision, making a resection, removing tissue, manipulating tissue, performing a corrective maneuver, delivering the implant to a target site, deploying the implant at the target site, adjusting the implant at the target site, manipulating the implant once it is implanted, securing the implant at the target site, explanting the implant, suturing tissue, etc. For example, the platform 1050 can include one or more arms 1055 and end effectors for holding various surgical tools (e.g., graspers, clips, needles, needle drivers, irrigation tools, suction tools, staplers, screw driver assemblies, etc.), imaging instruments (e.g., cameras, sensors, etc.), and/or medical devices (e.g., the implant 1000) and that enable the platform 1050 to perform the one or more aspects of the surgical plan (e.g., positioning cages, forming mechanical connections, installing positioning features, implanting plates, etc.). Although shown as having one arm 1055, one skilled in the art will appreciate that the platform 1050 can have a plurality of arms (e.g., two, three, four, or more) and any number of joints, linkages, motors, and degrees of freedom. In some embodiments, the platform 1050 may have a first arm dedicated to holding one or more imaging instruments, while the remainder of the arms hold various surgical tools. In some embodiments, the tools can be releasably secured to the arms such that they can be selectively interchanged before, during, or after an operative procedure. The arms can be moveable through a variety of ranges of motion (e.g., degrees of freedom) to provide adequate dexterity for performing various aspects of the operative procedure.

[0142] The platform 1050 can include a control module 1060 for controlling operation of the arm(s) 1055. In some embodiments, the control module 1060 includes a user input device (not shown) for controlling operation of the arm(s) 1055. The user input device can be a joystick, a mouse, a keyboard, a touchscreen, an infrared sensor, a touchpad, a wearable input device, a camera- or image-based input device, a microphone, or other user input devices. A user (e.g., a surgeon) can interact with the user input device to control movement of the arm(s) 1055. In some embodiments, the control module 1060 includes one or more processors for executing machine-readable instructions that, when executed, automatically control operation of the arm 1055. In such embodiments, the control module 1060 may receive machine-readable instructions specifying one or more steps of a surgical procedure that, when executed by the control module 1060, cause the platform 1050 to perform the one or more steps of the surgical procedure. For example, the machine-readable instructions may direct the platform 1050 to prepare tissue for an incision, make an incision, make a resection, remove tissue, manipulate tissue, perform a corrective maneuver, deliver the implant 1000 to a target site, deploy the implant 1000 at the target site, adjust a configuration of the implant 1000 at the target site, manipulate the implant 1000 once it is implanted, secure the implant 1000 at the target site, explant the implant 1000, suture tissue, and/or the like. The instructions may therefore include particular instructions for articulating the arm 1055 to perform or otherwise aid in the delivery of the patient-specific implant.

[0143] If the surgical plan includes executable instructions, the platform 1050 can execute instructions to perform at least a portion of the surgical procedure. In some embodiments, the platform 1050 can generate executable instructions based on the surgical plan generated by the system 800 of FIG. 8. For example, the surgical plan can include information about the delivery path, tools, and implantation site. The platform 1050 can analyze the surgical plan and develop executable instructions for performing the patient-specific procedure based on the capabilities (e.g., configuration and number of robotic arms, functionality of and effectors, guidance systems, visualization systems, etc.) of the robotic system. This enables the system 800 to be compatible with a wide range of different types of robotic surgery systems.

[0144] The platform 1050 can include one or more communication devices (e.g., components having VLC, WiMAX, LTE, WLAN, IR communication, PSTN, Radio waves, Bluetooth, and/or Wi-Fi operability) for establishing a connection with a network 1006 (which can be the same as the server 806 shown in FIG. 8) and/or a computing device 1040 (which can be the same as the computing device 900 shown in FIG. 9) for accessing and/or downloading the patient-specific plan. For example, the network 1006 can receive a request for a particular surgical plan from the platform 1050 and send the plan to the platform 1050. Once identified, the network 1006 can transmit the surgical plan directly to the platform 1050 for execution. In some embodiments, the network 1006 can transmit the surgical plan to one or more intermediate networked devices, rather than transmitting the surgical plan directly to the platform 1050. For example, the network 1006 may transmit the surgical plan to the computing device 1040 and/or the computing device 900, described previously with respect to FIG. 9. A user can review the surgical plan using the computing device before transmitting the surgical plan to the platform 1050 for execution. Additional details for identifying, storing, downloading, and accessing patient-specific surgical plans are described in U.S. application Ser. No. 16/990,810, filed Aug. 11, 2020, the disclosure of which is incorporated by reference herein in its entirety.

[0145] The platform 1050 can include additional components not expressly shown in FIG. 10. For example, in various embodiments the platform 1050 may include one or more displays (e.g., an LCD display screen, an LED display screen, a projected, holographic, or augmented reality display (e.g., a heads-up display device or a head-mounted device), one or more I/O devices (e.g., a network card, video card, audio card, USB, firewire or other external device, camera, printer, speakers, CD-ROM drive, DVD drive, disk drive, or Blu-Ray device), and/or a memory (e.g., random access memory (RAM), various caches, CPU registers, read-only memory (ROM), and writable non-volatile memory, such as flash memory, hard drives, floppy disks, CDs, DVDs, magnetic storage devices, tape drives, device buffers, and so forth). In some embodiments, the foregoing components can be generally similar to the like components described in detail with respect to computing device 900 in FIG. 9.

[0146] Without being bound by theory, using a robotic surgical platform to perform various aspects of the surgical plans described herein is expected to provide several advantages over conventional operative techniques. For example, use of robotic surgical platforms may improve surgical outcomes and/or shorten recovery times by, for example, decreasing incision size, decreasing blood loss, decreasing a length of time of the operative procedure, increasing the accuracy and precision of the surgery (e.g., the placement of the implant at the target location), and the like. The platform 1050 can also avoid or reduce user input errors, e.g., by including one or more scanners for obtaining information from instruments (e.g., instruments with retrieval features), tools, the patient specific implant 1000 (e.g., after the implant 1000 has been gripped by the arm 1055), etc. The platform 1050 can confirm use of proper instruments prior and during the surgical procedure. If the platform 1050 identifies an incorrect instrument or tool, an alert can be sent to a user that another instrument or tool should be installed. The user can scan the new instrument to confirm that the instrument is appropriate for the surgical plan. In some embodiments, the surgical plan includes instructions for use, a list of instruments, instrument specifications, replacement instruments, and the like. The platform 1050 can perform pre- and post-surgical checking routines based on information from the scanners.

[0147] FIG. 11 is a flowchart of a method 1100 for implanting a patient-specific implant. The method 1100 can include a patient-specific implant having a first plate and a second plate, such as any of the plates described previously herein. The first plate and the second plate are generally designed with patient-specific features (e.g., geometry, topography, etc.) configured to mate with respective first and second identified anatomical structures at respective first and second target positions. For example, the first and/or second plates can each be configured to mate with an anterior, superior, inferior, or lateral surface of a vertebral body. In some embodiments, the first and/or second plates can be configured to mate with one or more surfaces of the vertebral body. For example, the first and/or second plate can be configured to mate with an anterior, superior, inferior, and/or lateral surface of the vertebral body. In some embodiments, the first and second patient-specific implants can be designed to contact identical (e.g., the same) surfaces of the vertebral body, but may have different contact surface topography based on the positions of the first and second plates relative to the surfaces of the vertebral body.

[0148] At step 1102, the method 1100 can include delivering the first plate to the first target position. Step 1102 can be generally similar or the same as steps 604 and/or 606 of the method 600 of FIG. 6, and/or steps 704 and/or 706 of the method 700 of FIG. 7.

[0149] The method 1100 can include, in step 1104, delivering the second plate to the second target position. Step 1104 can be generally similar to or the same as step 1102. Step 1102 and/or step 1104 can be performed by a surgeon, a surgical robotic platform, and/or a surgeon assisted by a surgical robotic platform.

[0150] The method 1100 can continue in step 1106 by coupling (e.g., mechanically coupling) the first plate to the second plate. The first plate can be coupled to the second plate using any of the linkages, connectors, and/or connection mechanisms previously described herein. In some embodiments, the steps 1106 and 1102-1104 can be reversed such that the first plate is coupled to the second plate before positioning the first and/or second plates at their respective target positions (e.g., the first and second plate can coupled in vivo and/or ex vivo). In some embodiments, coupling the first and second plates can cause the first and/or second plates to mate (e.g., automatically mate) with the corresponding anatomical structures at the respective first and second target positions.

[0151] The method 1100 can optionally continue in step 1108 by confirming that the first and/or second plates are in the respective first and/or second target positions. The position of the first and/or second plates can be confirmed using one or more conventional imaging technologies known in the art (e.g., X-Ray, MRI, CT-scan, etc.). Step 1108 can be generally similar to or the same as step 608 of the method 600 of FIG. 6 and/or step 710 of the method 700 of FIG. 7.

[0152] FIG. 12A is a flowchart of a method 1200 for providing patient-specific medical care. The method 1200 can be a computer-implemented method, such that one or more steps of the 1200 can be performed by a computer or computing device, such as the computing device 802 of FIG. 8, the server 806 of FIG. 8, the computing device 900 of FIG. 9, and/or any other computer described herein.

[0153] In step 1202, the method 1200 can include receiving a patient data set for a patient. The patient data can be the generally similar or the same as the patient data set 808 of FIG. 8. The patient data set can include one or more images of at least a portion of the patient's spine and can show the patient's native anatomical configuration. In some embodiments, the one or more images can be used to create a virtual model of the patient's native anatomical configuration. Virtual models are discussed in greater detail in PCT/US21/12065, titled “PATIENT-SPECIFIC MEDICAL PROCEDURES AND DEVICES, AND ASSOCIATED SYSTEMS AND METHODS,” filed Jan. 4, 2021, the entirety of which is incorporated by reference herein.

[0154] In step 1204, the method 1200 can include determining a corrected anatomical configuration for the patient. The corrected anatomical configuration can be different that the native anatomical configuration in step 1202. The corrected anatomical configuration can be based at least partially on one or more reference patient data sets, such as the reference patient data sets stored in the database 802 of FIG. 8. In some embodiments, the corrected anatomical configuration can be determined by using a computing system, as described previously. In some embodiments, the computing system can include a module, such as the data analysis module 816 of FIG. 8, and the module can be configured to analyze reference patient data and determine the corrected anatomical configuration. In some embodiments, a virtual model of the corrected anatomical configuration can be generated, e.g., by modifying the one or more images and/or the virtual model of the patient's native anatomical configuration of step 1202 based on reference patient data. Modifying virtual models of the patient's native anatomical configuration is discussed in greater detail in PCT/US21/12065, titled “PATIENT-SPECIFIC MEDICAL PROCEDURES AND DEVICES, AND ASSOCIATED SYSTEMS AND METHODS,” filed Jan. 4, 2021, the entirety of which is incorporated by reference herein.

[0155] In step 1206, the method 1200 can include designing one or more patient-specific anterior plates. Individual ones of the one or more patient-specific anterior plates can be the same or generally similar as the plate 120 of FIGS. 1A and 1B, the first plate 220 of FIGS. 2A and 2B, the second plate 250 of FIGS. 2A and 2B, and/or the plate 320 of FIGS. 3A and 3B. The design for the one or more patient-specific anterior plates can be based at least partially on the corrected anatomical configuration of step 1204. For example, the one or more patient-specific anterior plates can be designed to have geometry corresponding to a geometry of a target location at a patient's spine, such that implanting the one or more patient-specific implants at the corresponding target location(s) can cause the patient's spine to assume the corrected anatomical configuration. In some embodiments, a computer or computing system can design the one or more patient-specific anterior plates, as described previously. For example, the computer can analyze the patient data in step 1202 to determine the curvature, anatomy, and/or geometry of the patient's spine, and can design one or more patient-specific anterior plates having geometry or curvature that corresponds to the geometry or curvature of the patient's spine and/or that include one or more contact surface having topography that matches a topography of the patient's spine.

[0156] In some embodiments, the one or more patient-specific anterior plate implants of step 1206 can include at least a first patient-specific anterior plate configured to be implanted at a first vertebral level and a second patient-specific anterior plate configured to be implanted at a second vertebral level. The first patient-specific anterior plate can have a different geometry than the second patient-specific implant.

[0157] In some embodiments, at least one of the patient-specific anterior plates of step 1206 can include seating features configured to hold the at least one of the patient-specific anterior plates at a specific location along the patient's spine. The seating features can include wings, projections, contact surfaces, and/or any other suitable seating feature described previously herein. For example, the seating features can the same or generally similar to the first projection 121 of FIGS. 1A and 1B, the first contact surface 122 of FIGS. 1A and 1B, the second projection 126 of FIGS. 1A and 1B, the second contact surface 128 of FIGS. 1A and 1B, and/or any other suitable element or feature of FIGS. 1A-3B.

[0158] In some embodiments, the method 1200 can further include identifying one or more target positions along the patient's spine, and each of the patient specific anterior plates of step 1206 can be designed to correspond with one or more anatomical structures at a corresponding target position. The one or more target positions can include one or more of the anterior surfaces, lateral surfaces, superior surfaces, and/or inferior surfaces of individual vertebral bodies of the patient's spine, and/or one or more vertebral levels of the patient's spine. In some embodiments, the one or more target positions can correspond to the corrected anatomical configuration of step 1204, such that implanting each of the patient-specific anterior plates at the corresponding target position can cause the patient's spine to assume (adjust, transition toward, realign, etc.) the corrected anatomical configuration.

[0159] FIGS. 12B-12F illustrate various additional methods that can be included as part of the method 1200 of FIG. 12A. Accordingly, each of the methods of FIGS. 12B-12F, and/or one or more steps thereof, can be combined with the method 1200 of FIG. 12A and/or each other.

[0160] Referring first to FIG. 12B, in some embodiments the method 1200 can further include the method 1210. At step 1212, the method 1210 includes determining a target implant location proximate to or along a virtual model of the patient's spine. The virtual model of the patient's spine can be a virtual model of the patient's spine in a corrected anatomical configuration, such as the corrected anatomical configuration described previously with reference to step 1204 of FIG. 12A. The method 1210 can further include, at step 1214, constructing a virtual model of at least one of the patient-specific anterior plates of step 1206 to seat against the target implant location.

[0161] Referring next to FIG. 12C, in some embodiments the method 1200 can further include the method 1220. At step 1222, the method 1220 can include designing a virtual model of an intervertebral implant for implantation between a first vertebra and a second vertebra. The intervertebral implant can include any of the implants, devices, plates, or cages described previously.

[0162] At step 1224, the method 1220 can further include designing at least one of the patient-specific anterior plates of step 1206 to couple to the first and second vertebrae to obstruct movement of the intervertebral implant. This can include, for example, designed a plate that includes contacts surfaces having patient-specific topographies, and/or any other aspect or feature of the patient-specific implants described herein.

[0163] Referring next to FIG. 12D, in some embodiments, the method 1200 can further include the method 1230. In step 1232, the method 1230 can include identifying features along the patient's spine for engaging at least one of the patient-specific anterior plates. The features can include, for example, one or more vertebral bodies, such as one or more adjacent vertebral bodies. Additionally, or alternatively, the features can include one or more anterior, lateral, superior, and/or inferior surfaces of individual ones of the vertebral bodies. In some embodiments, the features can further include any of the features or aspects of a patient's anatomy described herein.

[0164] At 1234, the method 1230 can further include designing one or more regions of at least one of the one or more patient-specific anterior plates to contact one or more of the identified features. In such embodiments, the at least one patient-specific anterior plate can inhibit movement of a spinal segment of the patient's spine when contacting the identified features. For example, as described previously with reference to FIGS. 1A-2B, the patient-specific topographies of the at least one of the one or more patient-specific anterior plates can prevent, inhibit, limit, or reduce movement (e.g., lateral, vertical, etc.) of the plate relative to one or both adjacent vertebrae, and can maintain the position and/or aligning of a first vertebral body relative to a second vertebral body.

[0165] Referring next to FIG. 12E, in some embodiments, the method 1200 can further include the method 1240. At step 1242, the method 1240 can include generating a virtual model of the patient's spine in the corrected anatomical configuration, e.g., the corrected anatomical configuration of step 1204. Virtual models are described in PCT/US21/12065 (Docket No. 127398-8021.US00), titled “PATIENT-SPECIFIC MEDICAL PROCEDURES AND DEVICES, AND ASSOCIATED SYSTEMS AND METHODS,” filed Jan. 4, 2021, the entirety of which is incorporated by reference herein.

[0166] At step 1244, the method 1240 can include, in response to modifying or updating the virtual model of the patient's spine, dynamically adjusting a first virtual model of one of the patient-specific anterior plates and/or a second virtual model of a spinal implant. The virtual model of the patient's spine can be modified automatically, e.g., by a computer or computing system, or by a user (e.g., a practitioner). The modifications to the virtual model of the patient's spine can be based on the patient-specific data of step 1202, and can reflect an updated or revised corrected anatomical configuration. The modifications can include changes to the dimensions, shapes, contours, spacing, positions, orientations, and/or alignments of one or more vertebral bodies of the patient's spine. The virtual model can include a one or more virtual models of patient-specific anterior plates and/or one or more virtual models of spinal implants. Modifying or updating the virtual model of the patient's spine can dynamically adjust the virtual models of the patient-specific anterior plates and/or spinal implants, e.g., so that the adjusted virtual models match the modified or updated dimensions, shapes, contours, spacing, positions, orientations, and/or alignments of the corresponding vertebral bodies. Additional aspects of adjusting virtual models are described in PCT App. No. PCT/US21/12065, titled “PATIENT-SPECIFIC MEDICAL PROCEDURES AND DEVICES, AND ASSOCIATED SYSTEMS AND METHODS,” filed Jan. 4, 2021, the entirety of which is incorporated by reference herein.

[0167] Referring next to FIG. 12F, in some embodiments the method 1200 can further include the method 1250. At step 1252, the method 1250 can include generating a virtual model of the patient's spine in the corrected anatomical configuration. This can be the same as or generally similar to step 1242 of the method 1240.

[0168] At step 1254, the method 1250 can include modifying the virtual model of the patient's spine to generate a modified virtual model. This can be the same as or generally similar to the step 1244 of the method 1240.

[0169] At step 1256, the method 1250 can include designing at least one of the patient-specific anterior plates based on the modified virtual model. The corrected anatomical configuration can be the corrected anatomical configuration of step 1204. As described previously, the virtual model of the patient's spine can include changes to the dimensions, shapes, contours, spacing, positions, orientations, and/or alignments of one or more vertebral bodies of the patient's spine. The plates based on the modified virtual model can include a change that corresponds to the modification in step 1254. For example, in some embodiments the virtual model can be modified in step 1254 to change a height of an intervertebral space between adjacent vertebra, and the plate based on the modified virtual model can include an intermediate portion and/or connection mechanism dimensioned to corresponds to the height of the intervertebral space.

[0170] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In some embodiments, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0171] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system generally includes one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

[0172] The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable” to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0173] The embodiments, features, systems, devices, materials, methods and techniques described herein may, in some embodiments, be similar to any one or more of the embodiments, features, systems, devices, materials, methods and techniques described in the following:

• • [0174] U.S. application Ser. No. 16/048,167, filed on Jul. 27, 2017, titled “SYSTEMS AND METHODS FOR ASSISTING AND AUGMENTING SURGICAL PROCEDURES”;
  • [0175] U.S. application Ser. No. 16/242,877, filed on Jan. 8, 2019, titled “SYSTEMS AND METHODS OF ASSISTING A SURGEON WITH SCREW PLACEMENT DURING SPINAL SURGERY”;
  • [0176] U.S. application Ser. No. 16/207,116, filed on Dec. 1, 2018, titled “SYSTEMS AND METHODS FOR MULTI-PLANAR ORTHOPEDIC ALIGNMENT”;
  • [0177] U.S. application Ser. No. 16/352,699, filed on Mar. 13, 2019, titled “SYSTEMS AND METHODS FOR ORTHOPEDIC IMPLANT FIXATION”;
  • [0178] U.S. application Ser. No. 16/383,215, filed on Apr. 12, 2019, titled “SYSTEMS AND METHODS FOR ORTHOPEDIC IMPLANT FIXATION”;
  • [0179] U.S. application Ser. No. 16/569,494, filed on Sep. 12, 2019, titled “SYSTEMS AND METHODS FOR ORTHOPEDIC IMPLANTS”;
  • [0180] U.S. Application No. 62/773,127, filed on Nov. 29, 2018, titled “SYSTEMS AND METHODS FOR ORTHOPEDIC IMPLANTS”;
  • [0181] U.S. Application No. 62/928,909, filed on Oct. 31, 2019, titled “SYSTEMS AND METHODS FOR DESIGNING ORTHOPEDIC IMPLANTS BASED ON TISSUE CHARACTERISTICS”;
  • [0182] U.S. application Ser. No. 16/735,222, filed Jan. 6, 2020, titled “PATIENT-SPECIFIC MEDICAL PROCEDURES AND DEVICES, AND ASSOCIATED SYSTEMS AND METHODS”;
  • [0183] U.S. application Ser. No. 16/987,113, filed Aug. 6, 2020, titled “PATIENT-SPECIFIC ARTIFICIAL DISCS, IMPLANTS AND ASSOCIATED SYSTEMS AND METHODS”;
  • [0184] U.S. application Ser. No. 16/990,810, filed Aug. 11, 2020, titled “LINKING PATIENT-SPECIFIC MEDICAL DEVICES WITH PATIENT-SPECIFIC DATA, AND ASSOCIATED SYSTEMS, DEVICES, AND METHODS”;
  • [0185] U.S. application Ser. No. 17/463,054, filed Aug. 31, 2021, titled “BLOCKCHAIN MANAGED MEDICAL IMPLANTS;”
  • [0186] U.S. application Ser. No. 17/085,564, filed Oct. 30, 2020, titled “SYSTEMS AND METHODS FOR DESIGNING ORTHOPEDIC IMPLANTS BASED ON TISSUE CHARACTERISTICS”; and
  • [0187] U.S. application Ser. No. 17/100,396, filed Nov. 20, 2020, titled “PATIENT-SPECIFIC VERTEBRAL IMPLANTS WITH POSITIONING FEATURES.”

[0188] All of the above-identified patents and applications are incorporated by reference in their entireties. In addition, the embodiments, features, systems, devices, materials, methods, and techniques described herein may, in certain embodiments, be applied to or used in connection with any one or more of the embodiments, features, systems, devices, or other matter. To the extent any materials incorporated herein by reference conflict with the present disclosure, the present disclosure controls.