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

15727

Application APPARATUS, SYSTEM, AND METHOD FOR GENERATING PATIENT-SPECIFIC DEVICES
Matter Number PER-17 Reference Case 1 PER-17
Created 1/6/24, 10:05 PM Modified 1/6/24, 10:05 PM
Application Number
Paragraph Number

321

Content

In certain embodiments, the workflow 1050 may include steps that require action by both the system 1000 and the user 1002. Such steps may be referred to as “hybrid steps.” Such steps may be indicated by both a robot head icon 1308 and a person head icon 1310 on the same step. In such steps, the system 1000 or the user 1002 may perform a first set of tasks for the step and the remaining tasks of the step are performed by the other one of the system 1000 or the user 1002. For example, the system 1000 may orient a bone model 404 and may measure a structure within the bone model 404, next a user 1002 may use the measurements to define a cut face for a planned resection of the bone model 404. Thus, in such a step a user 1002 may interact with the bone model 404 to complete the step. Alternatively, or in addition, hybrid steps may be divided into new steps, one to be completed exclusively by the system 1000 and a subsequent step to be completed exclusively by the user 1002.

Notes

Added by DJM Jan 2024