Is SEN Virus a Major Concern in Hemodialysis and Liver Transplantation?


Seyed Mohammad mehdi Hossini Moghaddam 1 , * , Seyedeh Hamideh Mousavi 2 , Seyed Moayed Alavian 2

1 Urology and Nephrology Research Center, Shahid Beheshti University, M.C.,, IR-Iran

2 Urology and Nephrology Research Center, Shahid Beheshti University, M.C., I.R.Iran

How to Cite: Moghaddam S, Mousavi S, Alavian S. Is SEN Virus a Major Concern in Hemodialysis and Liver Transplantation?, Hepat Mon. Online ahead of Print ; 9(1):50-59.


Hepatitis Monthly: 9 (1); 50-59
Article Type: Review Article
Received: September 8, 2008
Accepted: January 13, 2009




Although hepatotropic viruses such as hepatitis B virus (HBV) and hepatitis C virus (HCV) are well-identified viral agents for the development of hepatitis, infection with some other viruses may lead to varying degrees of liver injury. Moreover, the hepatic pathogenicity of a few viral agents still remains to be determined. In recent years, viral agents such as TTV and SEN virus with possible hepatic pathogenicity have been introduced. SEN virus has been reported with different rates of prevalence in high-risk groups such as dialysis patients, and low-risk groups such as blood donors. Identification of the SEN virus as a possible etiological agent of parenteral transmission hepatitis led to a major concern about the possibility of its role in liver diseases in hemodialysis patients as well as in renal transplant patients. This manuscript provides an updated integrative review on SEN virus from virological aspect as well as epidemiologic and diagnostic medicine. Moreover, its role in liver diseases considering the co-infection with other hepatotropic viruses has also been reviewed.


SEN Virus Hepatitis Renal Dialysis Liver Transplantation

© 0, Author(s). This is an open-access article distributed under the terms of the Creative Commons Attribution-NonCommercial 4.0 International License ( which permits copy and redistribute the material just in noncommercial usages, provided the original work is properly cited.

Full Text

Full text is available in PDF