Co-amilofruse

Co-amilofruse
Combination of
Amiloride	Potassium-sparing diuretic
Furosemide	Loop diuretic
Clinical data
AHFS/Drugs.com	International Drug Names
Routes of; administration	Oral
ATC code	C03EB01 (WHO) ;
Legal status
Legal status	UK: POM (Prescription only) ;
Identifiers
ChemSpider	none;
	(what is this?) (verify)

Co-amilofruse (BAN) is a nonproprietary name used to denote a combination of amiloride and furosemide, which are both diuretics. Co-amilofruse is a treatment for fluid retention (oedema), either in the legs (peripheral edema) or on the lungs (pulmonary oedema). Furosemide is a loop diuretic and is more effective than amiloride, but has a tendency to cause low potassium levels (hypokalaemia); the potassium-sparing effects of amiloride may balance this.

Formulation

Two strengths of co-amilofruse are available:

2.5 mg amiloride with 20 mg furosemide, BAN of Co-amilofruse 2.5/20 (brand name Frumil LS)
5 mg amiloride with 40 mg furosemide, BAN of Co-amilofruse 5/4-0 (brand name Frumil)

gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.

gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.

gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.

gollark: If I remember right Go strings are just byte sequences with no guarantee of being valid UTF-8, but all the functions working on them just assume they are.

gollark: Oh, and the strings are terrible.

References

British National Formulary 2004

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.