|Other Names||Chloride channel protein ClC-Kb, Chloride channel Kb, ClC-K2, CLCNKB|
|Target/Specificity||The synthetic peptide sequence used to generate the antibody AP6358a was selected from the C-term region of human CLCNKB. A 10 to 100 fold molar excess to antibody is recommended. Precise conditions should be optimized for a particular assay.|
|Format||The synthetic peptide was lyophilized with 100% acetonitrile and is supplied as a powder. Reconstitute with 0.1 ml deionized water for a final concentration of 1 mg/ml.|
|Storage||Maintain refrigerated at 2-8°C for up to 6 months. For long term storage store at -20°C.|
|Precautions||This product is for research use only. Not for use in diagnostic or therapeutic procedures.|
|Function||Voltage-gated chloride channel. Chloride channels have several functions including the regulation of cell volume; membrane potential stabilization, signal transduction and transepithelial transport. May be important in urinary concentrating mechanisms.|
|Cellular Location||Cell membrane; Multi-pass membrane protein.|
|Tissue Location||Expressed predominantly in the kidney.|
firstname.lastname@example.org, and receive a free "I Love Antibodies" mug.
Provided below are standard protocols that you may find useful for product applications.
Chloride channel Kb (CLCNKB) is a member of the CLC family of voltage-gated chloride channels, which comprises at least 9 mammalian chloride channels. Each is believed to have 12 transmembrane domains and intracellular N and C termini. Mutations in CLCNKB result in the autosomal recessive Type III Bartter Syndrome. CLCNKA and CLCNKB are closely related (94% sequence identity), tightly linked (separated by 11 kb of genomic sequence) and are both expressed in mammalian kidney.
Schlingmann, K.P., et al., N. Engl. J. Med. 350(13):1314-1319 (2004).Jeck, N., et al., Kidney Int. 65(1):190-197 (2004).Maehara, H., et al., Neuroreport 14(12):1571-1573 (2003).Zelikovic, I., et al., Kidney Int. 63(1):24-32 (2003).Colussi, G., et al., Nephrol. Dial. Transplant. 17(3):521-523 (2002).
If you have any additional inquiries please email technical services at email@example.com.