0
Want this question answered?
Be notified when an answer is posted
Add your answer:
Earn +20 pts
What is the difference between eudragit RS PO and eudragit RL PO?
Eudragit RS PO is a cationic polymer, while Eudragit RL PO is an anionic polymer. Eudragit RS PO is typically used for sustained-release formulations due to its permeability characteristics, while Eudragit RL PO is often used for enteric coatings due to its pH-dependent solubility properties.
In eudragit rl 100 what does rl stand for?
hfkjf
Melting point of eudragit L100 and S100?
2450 C
In polymer eudragit RL100 what 100 means?
] Description: Methacrylate-based coating materials with a variety of functional properties.Functionality Trade name Anionic polymer of methacrylic acid and methacrylates with a -COOH group Eudragit® L 100-55 - powder, spray dried L 30 D-55 which can be reconstituted for targeted delivery in the duodenum Eudragit® L 30 D-55 - aqueous dispersion, pH dependent polymer soluble above pH 5.5 for targeted delivery in the duodenumEudragit® L 100 - powder, pH dependent polymer soluble above pH 6.0 for targeted delivery in the jejunumEudragit® S 100 - powder, pH dependent polymer soluble above pH 7.0 for targeted delivery in the ileum.Eudragit® FS 30 D - aqueous dispersion, pH dependent polymer soluble above pH 7.0, requires no plasticizerCationic polymer with a dimethylaminoethyl ammonium group Eudragit E 100 - granules, pH dependent, soluble in gastric fluid up to 5.0, swellable and permeable above pH 5.0. Eudragit® E PO - powder form of E-100Copolymers of acrylate and methacrylates with quarternary ammonium group. Insoluble, High PermeabilityEudragit® RL 30D - aqueous dispersion, pH independent polymer for sustained release formulationsEudragit® RL PO - powder, pH independent polymer for matrix formulationsEudragit® RL 100 - granules, pH independentInsoluble, Low PermeabilityEudragit® RS 30D - aqueous dispersion, pH independent polymer for sustained release formulationsEudragit® RS PO - powder, pH independent polymer for matrix formulationsEudragit® RS 100 - granules, pH independentCopolymers of acrylate and methacrylates with quarternary ammonium group in combination with sodium carboxymethylcellulose Eudragit RD 100 - powder, pH independent for fast disintegrating films 2) Applications:Enteric Coatings Eudragit® L 100-55 or L 30 D-55 - delivery to the duodenum (pH > 5.0). Exact pH controlled drug release can be adjusted by a combination of polymers and coating thickness. Eudragit® L 100 - delivery to the jejunum (pH > 6.0).Eudragit® S 100 - delivery to the intestine (pH 6.0 to 7.5), site specific drug delivery can be achieved by combining with Eudragit® L types.Eudragit® FS 30 D - delivery to the colon (pH >7.0).Acryl-eze® --one step dry enteric coating system, soluble at pH 5.5Sustained Release Coatings Eudragit® RL and RS - release profile determined by the ratio of RL to RS polymers, and the film thickness applied. Taste Masking Eudragit® RD 100, pH independent, fast disintegrating film Eudragit® E 100 and EPO, pH dependent cationic polymer, soluble in gastric fluid up to pH 5.0, swellable and permeable above pH 5.0Rapidly disintegrating Films Eudragit® RD 100
What has the author Mark Eisei Sugamori written?
Mark Eisei Sugamori has written: 'Viability of islets of Langerhans microencapsulated in eudragit RL 100 for a bioartificial endocrine pancreas'
What are the various principles of encapsulation?
The ability to make changes in your code without breaking the code of all others who use your code is a key benefit of encapsulation. You should always hide implementation details. To elaborate, you must always have your variables as private and then have a set of public methods that others can use to access your variables. Since the methods are public anyone can access them, but since they are in your class you can ensure that the code works the way that is best for you. So in a situation that you want to alter your code, all you have to do is modify your methods. No one gets hurt because i am just using your method names in my code and the code inside your method doesnt bother me much. If you want maintainability, flexibility, and extensibility (and I guess, you do), your design must include encapsulation. How do you do that? • Keep instance variables protected (with an access modifier, mostly private). • Make public accessor methods, and force calling code to use those methods rather than directly accessing the instance variable. • For the methods, use the JavaBeans naming convention of set and get.
