translation missing: ko.activerecord.attributes.event.titles.recall_field_safety_notice

Recall / Field Safety Notice

mdprc 075 08 14 001

2014-08-19

Saudi Arabia

SFDA

https://ncmdr.sfda.gov.sa/Secure/CA/CaViewRecall.aspx?caid=4&rid=6318

Problem 1: when reopening a bookmark generated from processing a muga (multi-gated acquisition) scan within the nm cardiac application, the ejection fraction (ef) displayed should be the same as the ejection fraction (ef) originally displayed when the bookmark was first created. in some instances, the ejection fraction (ef) may be different. problem 2: when processing using one of the following nm clinical applications: autoquant, emory cardiac toolbox, corridor4dm, or neuroq, the patient study presented to the reviewing physician within the application may be for a different patient than the one selected from the patient directory. note: the data presented to the reviewing physician is the data for the patient presented by the application labeling. problem 3: while using the nm viewer application, an arrow annotation added to a display moves away from its original position if the viewer is subsequently maximized or if the image within the viewer is subsequently zoomed in or out. problem 4: while displaying pet images within ct viewer, the suv results displayed may be calculated with an suv method different from the one specified in system preferences. this issue affects the ct viewer and multi- modality tumor tracking applications. the expected behavior in such a case is that the application displays a warning that suv cannot be calculated due to missing information, and the images are displayed with the original acquisition units (bq/ml). instead, in affected systems, if the patient height has not been entered and the selected suv calculation method requires height data (i.E., suv-bsa), the system may display an suv calculated using a different method (suv-bw) without providing any warning that required data had not been entered or informing the user of the change.