Deprecated: Since 5.0.0: Calling Table::get() with options array is deprecated. Use named arguments instead. /application/src/Controller/ParagraphsController.php, line: 67 You can disable all deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED`. Adding `src/Controller/ParagraphsController.php` to `Error.ignoredDeprecationPaths` in your `config/app.php` config will mute deprecations from that file only. in /application/vendor/cakephp/cakephp/src/Core/functions.php on line 377

Warning: Unable to emit headers. Headers sent in file=/application/vendor/cakephp/cakephp/src/Core/functions.php line=377 in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 65

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 158

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 228
Dave's PCF WIP: Paragraphs

13363

Application APPARATUS, SYSTEM, AND METHOD FOR GENERATING PATIENT-SPECIFIC IMPLANTSAND/OR INSTRUMENTATION
Matter Number PER-32 Reference Case 1 PER-32
Created 1/6/24, 9:49 PM Modified 1/6/24, 9:49 PM
Application Number
Paragraph Number

199

Content

Referring to FIG. 11E, in one embodiment, anatomical data about the patient can be used to define other structures of the resection guide 1020 or other patient specific instruments. For example, anatomical data about the patient that can be captured in the patient imaging data (e.g., due to the fidelity of the technology providing the patient imaging data) can be used to define how deep one or more resection features 1022 are. Controlling the depth of the resection features 1022 can be used to manage how deep a surgeon’s cutting instruments can reach within the resection features 1022. Managing a depth for one or more resection features may be referred to as defining a patient specific height for the resection guide 1020. In one embodiment, the patient imaging data is used to define a desired cutting depth. This depth can be used to report a depth marking that a surgeon should watch for on an edge of the cutting tool that indicates how deep the cutting tool is. The preoperative plan provided according to the present disclosure can indicate this desired cutting depth. During the surgical procedure, a surgeon can watch for this depth as the resection is being performed.

Notes

Added by DJM Jan 2024