107
Views
0
CrossRef citations to date
0
Altmetric
Original Articles

Expression and characterization of g protein‐activated inward rectifier k+ channels in xenopus oocytes

, &
Pages 471-476 | Received 03 Aug 1998, Accepted 28 Aug 1998, Published online: 22 Nov 2010
 

Abstract

The G protein‐activated inwardly rectifying K+ channel (GIRK1) was coex‐pressed in Xenopus oocytes along with the 5‐HTia receptor, a 7‐helix receptor known to be coupled to K+ channels in many neural tissues. Thus, the activation of the 5‐HT1A receptor by its agonist leads to the opening of GIRK1. The GIRK1 current was measured using the two electrode voltage clamp technique with bath application of 5‐HT in the presence of various external potassium concentrations [K+]o. GIRK1 showed a strong inward rectification since only hyperpolarizing voltages evoked inward currents. K+ was the major ion carrier as evidenced by about 44 mV voltage shift corresponding to a 10‐fold external [K+] change. 5‐HT induced a concentration‐dependent inward K+ current (EC 50=10.7nM) which was blocked by Ba2+ Pertussis toxin (PTX) pre‐treatment reduced the K+ current by as much as about 70%, suggesting that PTX‐sensitive G protein (Gi or Go type) are involved in the 5‐HT1A receptor‐GIRK1 coupling in Xenopus oocytes

Notes

To whom correspondence should be addressed. Tel: 82–331–219–2621, Fax: 82–331–219–1615 E‐mail: [email protected]

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.