Agentes etiológicos de infecções urinárias em ambulatório

As infeções do trato urinário (ITU), depois das infeções respiratórias, são as mais comuns na comunidade, sendo a Escherichia coli o principal agente etiológico. Afeta predominantemente o sexo feminino e, anualmente, estima-se que ocorram em todo o Mundo cerca de 150 milhões de episódios de ITU, sendo responsável por 15% dos antibióticos prescritos em ambulatório. Os objetivos deste estudo foram caracterizar os agentes etiológicos das ITU e determinar o seu padrão de resistência aos antimicrobianos na região litoral norte de Portugal, de modo a contribuir para o uso racional na terapêutica empírica. Foi realizado um estudo observacional, descritivo e transversal, sendo obtidos 80 967 resultados de uroculturas de um Laboratório de Análises Clínicas de prestação de serviços à comunidade, relativos ao período entre Abril de 2007 e Março de 2015. Registaram-se 13 541 bacteriúrias positivas (16,72%). Escherichia coli foi o microrganismo mais isolado (71,62%), seguida de Klebsiella pneumoniae (12,41%), Proteus mirabilis (7,84%), Enterococcus. faecalis (3,97%) e Pseudomonas aeruginosa (1,42%), tendo-se observado diferenças estatisticamente significativas entre sexos e idades. Verificou-se uma diminuição da resistência aos antimicrobianos a partir do ano de 2012. E. coli apresentou em 2015 a menor taxa de resistência respetivamente de 4,46% e 12,37% para a fosfomicina e nitrofurantoína. A combinação de amoxicilina+ácido clavulânico registou uma taxa de resistência superior a 20% (22,03%). O baixo nível de resistência à fosfomicina permite que este antibiótico se apresente como a opção terapêutica de primeira linha no tratamento empírico de ITU não complicada na mulher em ambulatório, pelo que, estes resultados permitem corroborar as indicações de 2011 da Direção Geral de Saúde sobre a substituição de fluoroquinolonas por fosfomicina.

Multi-purpose adaptable business tier components based on Call Level Interfaces

Call Level Interfaces (CLI) play a key role in business tiers of relational and on some NoSQL database applications whenever a fine tune control between application tiers and the host databases is a key requirement. Unfortunately, in spite of this significant advantage, CLI are low level API, this way not addressing high level architectural requirements. Among the examples we emphasize two situations: a) the need to decouple or not to decouple the development process of business tiers from the development process of application tiers and b) the need to automatically adapt business tiers to new business and/or security needs at runtime. To tackle these CLI drawbacks, and simultaneously keep their advantages, this paper proposes an architecture relying on CLI from which multi-purpose business tiers components are built, herein referred to as Adaptable Business Tier Components (ABTC). Beyond the reference architecture, this paper presents a proof of concept based on Java and Java Database Connectivity (an example of CLI).

ABTC: multi-purpose adaptable business tier components based on Call Level Interfaces

Call Level Interfaces (CLI) are low level API that play a key role in database applications whenever a fine tune control between application tiers and the host databases is a key requirement. Unfortunately, in spite of this significant advantage, CLI were not designed to address organizational requirements and contextual runtime requirements. Among the examples we emphasize the need to decouple or not to decouple the development process of business tiers from the development process of application tiers and also the need to automatically adapt to new business and/or security needs at runtime. To tackle these CLI drawbacks, and simultaneously keep their advantages, this paper proposes an architecture relying on CLI from which multi-purpose business tiers components are built, herein referred to as Adaptable Business Tier Components (ABTC). This paper presents the reference architecture for those components and a proof of concept based on Java and Java Database Connectivity (an example of CLI).

Is the activity level of HD 80606 influenced by its eccentric planet?

Aims: Several studies suggest that the activity level of a planet-host star can be influenced by the presence of a close-by orbiting planet. Moreover, the interaction mechanisms that have been proposed, magnetic interaction and tidal interaction, exhibit a very different dependence on the orbital separation between the star and the planet. A detection of activity enhancement and characterization of its dependence on planetary orbital distance can, in principle, allow us to characterize the physical mechanism behind the activity enhancement. Methods: We used the HARPS-N spectrograph to measure the stellar activity level of HD 80606 during the planetary periastron passage and compared the activity measured to that close to apastron. Being characterized by an eccentricity of 0.93 and an orbital period of 111 days, the system's extreme variation in orbital separation makes it a perfect target to test our hypothesis. Results: We find no evidence for a variation in the activity level of the star as a function of planetary orbital distance, as measured by all activity indicators employed: log(R'HK), Hα, NaI, and HeI. None of the models employed, whether magnetic interaction or tidal interaction, provides a good description of the data. The photometry revealed no variation either, but it was strongly affected by poor weather conditions. Conclusions: We find no evidence for star-planet interaction in HD 80606 at the moment of the periastron passage of its very eccentric planet. The straightforward explanation for the non-detection is the absence of interaction as a result of a low magnetic field strength on either the planet or the star and of the low level of tidal interaction between the two. However, we cannot exclude two scenarios: i) the interaction can be instantaneous and of magnetic origin, being concentrated on the substellar point and its surrounding area; and ii) the interaction can lead to a delayed activity enhancement. In either scenario, a star-planet interaction would not be detectable with the dataset described in this paper.