Abstract

As the work load has been shifting from heavy manufacturing to office work, neck disorders are increasing. However, most of the current cervical spine biomechanical models were created to simulate crash situations. Therefore, the biomechanics of cervical spine during daily living and occupational activities remain unknown. In this effort, cervical spine biomechanical models were systematically reviewed based upon different features including approach, biomechanical properties, and validation methods.The objective of this review was to systematically categorize cervical spine models and compare the underlying logic in order to identify voids in the literature.Twenty-two models met our selection criteria and revealed several trends: 1) The multi-body dynamics modeling approach, equipped for simulating impact situations were the most common technique; 2) Straight muscle lines of action, inverse dynamic/optimization muscle force calculation, Hill-type muscle model with only active component were typically used in the majority of neck models; and 3) Several models have attempted to validate their results by comparing their approach with previous studies, but mostly were unable to provide task-specific validation.EMG-driven dynamic model for simulating occupational activities, with accurate muscle geometry and force representation, and person- or task-specific validation of the model would be necessary to improve model fidelity.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.