Practical handling of AIO admixtures - Guidelines on Parenteral Nutrition, Chapter 10

All-in-one admixtures (AIO-admixtures) provide safe, effective and low-risk PN (parenteral nutrition) for practically all indications and applications. Water, energy (carbohydrates and lipids), amino acids, vitamins and trace elements are infused together with PN either as industrially-manufactured AIO admixtures provided as two- or three-chamber bags (shelf life usually more than 12 months) completed with electrolytes and micronutrients where appropriate or as individually compounded ready-to-use AIO admixtures (compounding, usually prepared by a pharmacy on either a daily or weekly basis and stored at 2-8 degrees C). Physico-chemical and microbial stability of an AIO admixture is essential for the safety and effectiveness of patient-specific PN, and its assurance requires specialist pharmaceutical knowledge. The stability should be documented for an application period of 24 (-48) hours. It is advisable to offer a limited selection of different PN regimes in each hospital. For reasons of drug and medication safety, PN admixtures prepared for individual patients must be correctly labelled and specifications for storage conditions must also be followed during transport. Monitoring is required where applicable. Micronutrients are usually administered separately to AIO admixtures. In case compatibility and stability have been well documented trace elements and/or combination preparations including water-soluble or water-soluble/fat soluble vitamin supplements can be added to PN admixtures under strict aseptic conditions. AIO admixtures are usually not used as vehicles for drugs (incompatibilities).

Alternate, Easy and practical synthesis of allyl amines from acetyl derivatives of Baylis-Hillman adducts using Methanolic Ammonia

A methanolic ammonia-mediated alternate, easy and practical stereoselective synthesis of allyl amines from the acetyl derivatives of Baylis-Hillman adducts is described.

Practical, Pluggable Types for a Dynamic Language

Most languages fall into one of two camps: either they adopt a unique, static type system, or they abandon static type-checks for run-time checks. Pluggable types blur this division by (i) making static type systems optional, and (ii) supporting a choice of type systems for reasoning about different kinds of static properties. Dynamic languages can then benefit from static-checking without sacrificing dynamic features or committing to a unique, static type system. But the overhead of adopting pluggable types can be very high, especially if all existing code must be decorated with type annotations before any type-checking can be performed. We propose a practical and pragmatic approach to introduce pluggable type systems to dynamic languages. First of all, only annotated code is type-checked. Second, limited type inference is performed on unannotated code to reduce the number of reported errors. Finally, external annotations can be used to type third-party code. We present Typeplug, a Smalltalk implementation of our framework, and report on experience applying the framework to three different pluggable type systems.