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.

Practical Object-Oriented Back-in-Time Debugging

Back-in-time debuggers are extremely useful tools for identifying the causes of bugs, as they allow us to inspect the past states of objects no longer present in the current execution stack. Unfortunately the "omniscient" approaches that try to remember all previous states are impractical because they either consume too much space or they are far too slow. Several approaches rely on heuristics to limit these penalties, but they ultimately end up throwing out too much relevant information. In this paper we propose a practical approach to back-in-time debugging that attempts to keep track of only the relevant past data. In contrast to other approaches, we keep object history information together with the regular objects in the application memory. Although seemingly counter-intuitive, this approach has the effect that past data that is not reachable from current application objects (and hence, no longer relevant) is automatically garbage collected. In this paper we describe the technical details of our approach, and we present benchmarks that demonstrate that memory consumption stays within practical bounds. Furthermore since our approach works at the virtual machine level, the performance penalty is significantly better than with other approaches.

What is the Relation between Human Practical Action and an Accompanying Discourse? Discussing the Status of Practical Theory

The article discusses the function of an accompanying discourse in relation to the genesis of human practical action. On the one side, theory cannot be taken as the ground for practical action; practical action is not a realisation of intentions. On the other hand, human practical action is accompanied by series of explanations, justifications, declarations of intent, pre‑ and post-rationalisations, motivations etc. These accompanying discourses seem in one way or the other to be necessary for the actual realisation of human practical action. Following Pierre Bourdieu, it is suggested that an accompanying discourse cannot in a meaningful manner be separated from the human practical action, that practical theory should be regarded not as theory but as part of practice, and that practical theory first of all provides a common language for talking about practice and hence for reproducing a fundamentally arbitrary idea of the genesis of human practical action. Parallels are drawn to the education/formal training of semi-professionals.

A practical posture for hand grip dynamometry in the clinical setting

The optimal testing position for hand grip strength, which is a useful functional measure of nutritional status, is open to debate. We therefore examined the systematic difference between different postures in order to establish a methodology that is clinically relevant, easy to perform and reproducible.