z-logo
open-access-imgOpen Access
Different role of zinc transporter 8 between type 1 diabetes mellitus and type 2 diabetes mellitus
Author(s) -
Yi Bo,
Huang Gan,
Zhou Zhiguang
Publication year - 2016
Publication title -
journal of diabetes investigation
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.089
H-Index - 50
eISSN - 2040-1124
pISSN - 2040-1116
DOI - 10.1111/jdi.12441
Subject(s) - medicine , diabetes mellitus , type 2 diabetes mellitus , type 2 diabetes , endocrinology , type 1 diabetes , insulin , pathogenesis
Diabetes can be simply classified into type 1 diabetes mellitus and type 2 diabetes mellitus. Zinc transporter 8 (ZnT8), a novel islet autoantigen, is specifically expressed in insulin‐containing secretory granules of β‐cells. Genetic studies show that the genotypes of SLC 30A8 can determine either protective or diabetogenic response depending on environmental and lifestyle factors. The ZnT8 protein expression, as well as zinc content in β‐cells, was decreased in diabetic mice. Thus, ZnT8 might participate in insulin biosynthesis and release, and subsequently involved deteriorated β‐cell function through direct or indirect mechanisms in type 1 diabetes mellitus and type 2 diabetes mellitus. From a clinical feature standpoint, the prevalence of ZnT8A is gradiently increased in type 2 diabetes mellitus, latent autoimmune diabetes in adults and type 1 diabetes mellitus. The frequency and epitopes of ZnT8‐specific T cells and cytokine release by ZnT8‐specific T cells are also different in diabetic patients and healthy controls. Additionally, the response to ZnT8 administration is also different in type 1 diabetes mellitus and type 2 diabetes mellitus. In the present review, we summarize the literature about clinical aspects of ZnT8 in the pathogenesis of diabetes, and suggest that ZnT8 might play a different role between type 1 diabetes mellitus and type 2 diabetes mellitus.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here