Why the study?
Parameters of lumped arterial system models used in hybrid mock loops are typically derived from general cases rather than adapted to specific patients.
An iterative optimization method successfully identifies parameters of a five-element lumped arterial model in real-time using simulated data, demonstrating potential for customizing hybrid mock loops.
Supports patient-specific arterial modeling in mock loops; leaves open prospective clinical validation.
A lumped model of the arterial system has been used in constructing a hybrid mock loop due to its real-time response. However, the parameters of the model are always from a general case and not adapted to a specific patient. In this study, we focused on on-line parameter identification of the lumped model of the arterial system that could be used for a specific patient. A five-element lumped arterial model is adopted in this study, in which the five parameters are to be determined. The aortic flow rate and the venous pressure are chosen as the inputs of the model, and aortic pressure as the output. An iterative optimization based on the established state space equations of the five-element model is used to seek the best parameter values by minimizing the difference between the model prediction and the previously obtained aortic pressure. The method is validated using simulated data from a complete numerical cardiovascular model. Results show that the method can track the dynamic variation of the parameters very well. Finally, a sensitivity analysis of the model parameters is conducted to interpret the effect of parameter changes. The good performance of the identification demonstrates the potential application of this method to customize a hybrid mock loop for a specific patient or clinically monitor the arterial vessel characteristics in real time.
No takes yet. Share an insight, caveat, or question.
Huang et al. (2020) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: