No patient information provided as no patient was involved in this concern.Field system engineer was informed by the site about a green splash screen on the mvs with an error message "could not load config file to ias" and the system wouldn't fully boot.Upon further onsite investigation, the engineer discovered that the mobile view station's configuration files were corrupted, the engineer also discovered that the ethernet port kit along with the ethernet cable were damaged.Field system engineer was able to resolve the issue by re-loading the configuration files and replacing the ethernet port kit.No further issues were reported.There was no patient present when this issue was identified.System passed all tests during system checkout and no further action is required at this time.This event was identified during a retrospective review as discussed with the (b)(6) district office on (b)(6) 2016 via medtronic navigation, inc.Response to (b)(6) 2016 (b)(4).This review was performed as a result of recent changes/improvements to the medtronic navigation, inc.Medical device report (mdr) review process and is for non-adverse event reportable malfunctions within the last two years where the reported malfunction was not previously associated with serious injuries.Similar malfunctions that had resulted in significant delays of surgery or required additional intervention had been reported as mdr serious injuries.Based on this 483 observation, the reporting determination has been revised to consider these malfunction events reportable.This process change resulted in an overall increase in the number of mdrs filed by medtronic navigation, inc., since april 2016.It should be noted that this increase is not the result of the discovery of new product problems, but rather the result of a broader interpretation and application of the regulations within our processes.
|