Quick Heal X-Gen v7.03 serial key or number
Quick Heal X-Gen v7.03 serial key or number
The Nutanix Bible
prism - /'prizɘm/ - noun - control plane
one-click management and interface for datacenter operations.
Design Methodology and Iterations
Building a beautiful, empathetic and intuitive product is core to the Nutanix platform and something we take very seriously. This section will cover our design methodologies and how we iterate on design. More coming here soon!
In the meantime feel free to check out this great post on our design methodology and iterations by our Product Design Lead, Jeremy Sallee (who also designed this) - standardservices.com.pk
You can download the Nutanix Visio stencils here: standardservices.com.pk
Architecture
Prism is a distributed resource management platform which allows users to manage and monitor objects and services across their Nutanix environment, whether hosted locally or in the cloud.
These capabilities are broken down into two key categories:
- Interfaces
- HTML5 UI, REST API, CLI, PowerShell CMDlets, etc.
- Management Capabilities
- Platform management, VM / Container CRUD, policy definition and compliance, service design and status, analytics and monitoring
The following figure illustrates the conceptual nature of Prism as part of the Nutanix platform:
Prism is broken down into two main components:
- Prism Central (PC)
- Multi-cluster manager responsible for managing multiple Nutanix Clusters to provide a single, centralized management interface. Prism Central is an optional software appliance (VM) which can be deployed in addition to the AOS Cluster (can run on it).
- 1-to-many cluster manager
- Prism Element (PE)
- Localized cluster manager responsible for local cluster management and operations. Every Nutanix Cluster has Prism Element built-in.
- 1-to-1 cluster manager
The figure shows an image illustrating the conceptual relationship between Prism Central and Prism Element:
Note
Pro tip
For larger or distributed deployments (e.g. more than one cluster or multiple sites) it is recommended to use Prism Central to simplify operations and provide a single management UI for all clusters / sites.
Prism Services
A Prism service runs on every CVM with an elected Prism Leader which is responsible for handling HTTP requests. Similar to other components which have a Leader, if the Prism Leader fails, a new one will be elected. When a CVM which is not the Prism Leader gets a HTTP request it will permanently redirect the request to the current Prism Leader using HTTP response status code
Here we show a conceptual view of the Prism services and how HTTP request(s) are handled:
Note
Prism ports
Prism listens on ports 80 and , if HTTP traffic comes in on port 80 it is redirected to HTTPS on port
When using the cluster external IP (recommended), it will always be hosted by the current Prism Leader. In the event of a Prism Leader failure the cluster IP will be assumed by the newly elected Prism Leader and a gratuitous ARP (gARP) will be used to clean any stale ARP cache entries. In this scenario any time the cluster IP is used to access Prism, no redirection is necessary as that will already be the Prism Leader.
Note
Pro tip
You can determine the current Prism leader by running 'curl localhost/prism/leader' on any CVM.
Authentication and Access Control (RBAC)
Authentication
Prism currently supports integrations with the following authentication providers:
- Prism Element (PE)
- Local
- Active Directory
- LDAP
- Prism Central (PC)
- Local
- Active Directory
- LDAP
- SAML Authn (IDP)
Note
SAML / 2FA
SAML Authn allows Prism to integrate with external identity providers (IDP) that are SAML compliant (e.g. Okta, ADFS, etc.).
This also allows you to leverage the multi-factor authentication (MFA) / two-factor authentication (2FA) capabilities these providers support for users logging into Prism.
Access Control
Coming soon!
Navigation
Prism is fairly straight forward and simple to use, however we'll cover some of the main pages and basic usage.
Prism Central (if deployed) can be accessed using the IP address specified during configuration or corresponding DNS entry. Prism Element can be accessed via Prism Central (by clicking on a specific cluster) or by navigating to any Nutanix CVM or cluster IP (preferred).
Once the page has been loaded you will be greeted with the Login page where you will use your Prism or Active Directory credentials to login.
Upon successful login you will be sent to the dashboard page which will provide overview information for managed cluster(s) in Prism Central or the local cluster in Prism Element.
Prism Central and Prism Element will be covered in more detail in the following sections.
Prism Central
The figure shows a sample Prism Central dashboard where multiple clusters can be monitored / managed:
From here you can monitor the overall status of your environment, and dive deeper if there are any alerts or items of interest.
Prism Central contains the following main pages (NOTE: Search is the preferred / recommended method to navigation):
- Home Page
- Environment wide monitoring dashboard including detailed information on service status, capacity planning, performance, tasks, etc. To get further information on any of them you can click on the item of interest.
- Virtual Infrastructure
- Virtual entities (e.g. VMs, containers, Images, categories, etc.)
- Policies
- Policy management and creation (e.g. security (FLOW), Protection (Backup/Replication), Recovery (DR), NGT)
- Hardware
- Physical devices management (e.g. clusters, hosts, disks, GPU)
- Activity
- Environment wide alerts, events and tasks
- Operations
- Operations dashboards, reporting and actions (X-Play)
- Administration
- Environment construct management (e.g. users, groups, roles, availability zones)
- Services
- Add-on service management (e.g. Calm, Karbon)
- Settings
- Prism Central configuration
To access the menu click on the hamburger icon::
The menu expands to display the available options:
Search
Search is now the primary mechanism for Navigating the Prism Central UI (menus are still available).
To use the search bar to navigate you can use the search bar in the top left corner next to the menu icon.
Note
Search Semantics
PC Search allows for a great deal to semantics to be leveraged, some examples include:
| Rule | Example |
|---|---|
| Entity type | vms |
| Entity type + metric perspective (io, cpu, memory) | vms io |
| Entity type + alerts | vm alerts |
| Entity type + alerts + alert filters | vm alerts severity=critical |
| Entity type + events | vm events |
| Entity type + events + event filters | vm events classification=anomaly |
| Entity type + filters (both metric and attribute) | vm “power state”=on |
| Entity type + filters + metric perspective (io, cpu, memory) | vm “power state”=on io |
| Entity type + filters + alerts | vm “power state”=on alerts |
| Entity type + filters + alerts + (alert filters) | vm “power state”=on alerts severity=critical |
| Entity type + filters + events | vm “power state”=on events |
| Entity type + filters + events + event filters | vm “power state”=on events classification=anomaly |
| Entity instance (name, ip address, disk serial etc) | vm1, , BHTXSPWRM |
| Entity instance + Metric perspective (io, cpu, memory) | vm1 io |
| Entity instance + alerts | vm1 alerts |
| Entity instance + alerts + alert filters | vm1 alerts severity=critical |
| Entity instance + events | vm1 events |
| Entity instance + events + event filters | vm1 events classification=anomaly |
| Entity instance + pages | vm1 nics, c1 capacity |
| Parent instance + entity type | c1 vms |
| Alert title search | Disk bad alerts |
| Page name search | Analysis, tasks |
The prior is just a small subset of the semantics, the best way to get familiar with them is to give it a shot!
Prism Element
Prism Element contains the following main pages:
- Home Page
- Local cluster monitoring dashboard including detailed information on alerts, capacity, performance, health, tasks, etc. To get further information on any of them you can click on the item of interest.
- Health Page
- Environment, hardware and managed object health and state information. Includes NCC health check status as well.
- VM Page
- Full VM management, monitoring and CRUD (AOS)
- Storage Page
- Container management, monitoring and CRUD
- Hardware
- Server, disk and network management, monitoring and health. Includes cluster expansion as well as node and disk removal.
- Data Protection
- DR, Cloud Connect and Metro Availability configuration. Management of PD objects, snapshots, replication and restore.
- Analysis
- Detailed performance analysis for cluster and managed objects with event correlation
- Alerts
- Local cluster and environment alerts
The home page will provide detailed information on alerts, service status, capacity, performance, tasks, and much more. To get further information on any of them you can click on the item of interest.
The figure shows a sample Prism Element dashboard where local cluster details are displayed:
Note
Keyboard Shortcuts
Accessibility and ease of use is a very critical construct in Prism. To simplify things for the end-user a set of shortcuts have been added to allow users to do everything from their keyboard.
The following characterizes some of the key shortcuts:
Change view (page context aware):
- O - Overview View
- D - Diagram View
- T - Table View
Activities and Events:
Drop down and Menus (Navigate selection using arrow keys):
- M - Menu drop-down
- S - Settings (gear icon)
- F - Search bar
- U - User drop down
- H - Help
Features and Usage
In the following sections we'll cover some of the typical Prism uses as well as some common troubleshooting scenarios.
Anomaly Detection
In the world of IT operations there is a lot of noise. Traditionally systems would generate a great deal of alerts, events and notifications, often leading to the operator either a) not seeing critical alerts since they are lost in the noise or b) disregarding the alerts/events.
With Nutanix Anomaly Detection the system will monitor seasonal trends for time-series data (e.g. CPU usage, memory usage, latency, etc.) and establish a "band" of expected values. Only values that hit outside the "band" will trigger an event / alert. You can see the anomaly events / alerts from any entity or events page.
The following chart shows a lot of I/O and disk usage anomlaies as we were performing some large batch loads on these systems:
The following image shows the time-series values for a sample metric and the established "band":
This reduces unnecessary alerts as we don't want alerts for a "normal" state. For example, a database system will normally run at >95% memory utilization due to caching, etc. In the event this drops to say 10% that would be an anomaly as something may be wrong (e.g. database service down).
Another example would be how some batched workloads run on the weekend. For example, I/O bandwidth may be low during the work week, however on the weekends when some batch processes run (e.g. backups, reports, etc.) there may be a large spike in I/O. The system would detect the seasonality of this and bump up the band during the weekend.
Here you can see an anomaly event has occured as the values are outside the expected band:
Another topic of interest for anomalies is seasonality. For example, during the holiday period retailers will see higher demand than other times of the year, or during the end of month close.
Anomaly detection accounts for this seasonality and leverages the following periods to compare between micro (daily) and macro (quarterly) trends:
You can also set your own custom alerts or static thresholds:
Note
Anomaly Detection Algorithm
Nutanix leverages a method for determining the bands called 'Generalized Extreme Studentized Deviate Test'. A simple way to think about this is similar to a confidence interval where the values are between the lower and upper limits established by the algorithm.
The algorithm requires 3 x the granularity (e.g. daily, weekly, monthly, etc.) to calculate the seasonality and expected bands. For example, the following amounts of data would be required to adapt to each seasonality:
- Daily: 3 days
- Weekly: 3 weeks (21 days)
- Monthly: 3 months (90 days)
Twitter has a good resource on how they leverage this which goes into more detail on the logic: LINK
Nutanix Software Upgrade
Performing a Nutanix software upgrade is a very simple and non-disruptive process.
To begin, start by logging into Prism and clicking on the gear icon on the top right (settings) or by pressing 'S' and selecting 'Upgrade Software':
This will launch the 'Upgrade Software' dialog box and will show your current software version and if there are any upgrade versions available. It is also possible to manually upload a NOS binary file.
You can then download the upgrade version from the cloud or upload the version manually:
Note
Upload software from the CVM
In certain cases you may want to download the software and upload from the CVM itself. I use this in my environment when I want to download builds locally to the CVM.
First SSH into a CVM and find the Prism leader:
curl localhost/prism/leader && echo
SSH to the Prism leader and download the software bundle and metadata JSON
Run the following command to "upload" the software to Prism:
ncli software upload file-path=<PATH_TO_SOFTWARE> meta-file-path=<PATH_TO_METADATA_JSON> software-type=<SOFTWARE_TYPE>
The following shows an example for Prism Central:
ncli software upload file-path=/home/nutanix/tmp/leader-prism_standardservices.com.pk meta-file-path=/home/nutanix/tmp/leader-prism_standardservices.com.pk software-type=prism_central_deploy
It will then upload the upgrade software onto the Nutanix CVMs:
After the software is loaded click on 'Upgrade' to start the upgrade process:
You'll then be prompted with a confirmation box:
The upgrade will start with pre-upgrade checks then start upgrading the software in a rolling manner:
Once the upgrade is complete you'll see an updated status and have access to all of the new features:
Note
Note
Your Prism session will briefly disconnect during the upgrade when the current Prism Leader is upgraded. All VMs and services running remain unaffected.
Hypervisor Upgrade
Similar to Nutanix software upgrades, hypervisor upgrades can be fully automated in a rolling manner via Prism.
To begin follow the similar steps above to launch the 'Upgrade Software' dialogue box and select 'Hypervisor'.
You can then download the hypervisor upgrade version from the cloud or upload the version manually:
It will then load the upgrade software onto the Hypervisors. After the software is loaded click on 'Upgrade' to start the upgrade process:
You'll then be prompted with a confirmation box:
The system will then go through host pre-upgrade checks and upload the hypervisor upgrade to the cluster:
Once the pre-upgrade checks are complete the rolling hypervisor upgrade will then proceed:
Similar to the rolling nature of the Nutanix software upgrades, each host will be upgraded in a rolling manner with zero impact to running VMs. VMs will be live-migrated off the current host, the host will be upgraded, and then rebooted. This process will iterate through each host until all hosts in the cluster are upgraded.
Note
Pro tip
You can also get cluster wide upgrade status from any Nutanix CVM by running 'host_upgrade --status'. The detailed per host status is logged to ~/data/logs/host_standardservices.com.pk on each CVM.
Once the upgrade is complete you'll see an updated status and have access to all of the new features:
Cluster Expansion (add node)
The ability to dynamically scale the Nutanix cluster is core to its functionality. To scale an Nutanix cluster, rack / stack / cable the nodes and power them on. Once the nodes are powered up they will be discoverable by the current cluster using mDNS.
The figure shows an example 7 node cluster with 1 node which has been discovered:
Open Source In Cisco Products
ORIGINAL PAPERS
Intravenous azithromycin plus ceftriaxone followed by oral azithromycin for the treatment of inpatients with community-acquired pneumonia: an open-label, non-comparative multicenter trial
Fernando G. RubioI; Clóvis A. CunhaII; Fernando L.C. LundgrenIII; Maria P.J.S. LimaIV; Paulo J.Z. TeixeiraV; Julio C.A. OliveiraVI; Valdir GolinVII; Waldo L.L.D. MattosVIII; Herbert K. MählmannIX; Edson D. MoreiraX; Jose R. JardimXI; Rodney L.F. SilvaXII; Patricia H.B. SilvaXIII
IHospital de Base of FUNFARME, São José do Rio Preto, SP
IINossa Senhora das Graças Hospital, Curitiba, PR
IIIOtávio de Freitas General Hospital, Recife, PE
IVCatholic University of Campinas, Campus II, Department of Infectious Diseases, Campinas, SP
VIrmandade da Santa Casa de Misericórdia of Porto Alegre, Porto Alegre, RS
VIUniversity Hospital of Federal University of Juiz de Fora, Juiz de Fora, MG
VIIIrmandade da Santa Casa de Misericórdia of São Paulo, São Paulo, SP
VIIINossa Senhora da Conceição Hospital, Porto Alegre, RS
IXGeneral Hospital of Itapecerica da Serra OSS Seconci, Itapecerica da Serra, SP
XGeneral Hospital Roberto Santos, Salvador, BA
XIFederal University of São Paulo, São Paulo, SP
XIIClinical Hospital de Clinicas Federal University of Paraná, Curitiba, PR
XIIISanatorinhos Hospital OSS Ação Comunitária, São Paulo, SP; Brazil
Address for correspondence
ABSTRACT
Community-Acquired Pneumonia (CAP) is a major public health problem. In Brazil it has been estimated that 2,, people are affected by CAP every year. Of those, , are admitted to hospital, and 30, have death as the outcome. This is an open-label, non-comparative study with the purpose of evaluating efficacy, safety, and tolerability levels of IV azithromycin (IVA) and IV ceftriaxone (IVC), followed by oral azithromycin (OA) for the treatment of inpatients with mild to severe CAP. Eighty-six patients (mean age ± ) were administered IVA (mg/day) and IVC (1g/day) for 2 to 5 days, followed by AO (mg/day) to complete a total of 10 days. At the end of treatment (EOT) and after 30 days (End of Study - EOS) the medication was evaluated clinically, microbiologically and for tolerability levels. Out of the total 86-patient population, 62 (%) completed the study. At the end of treatment, % (CI95: % %) reported cure or clinical improvement; at the end of the study, that figure was % (CI95: % %). Out of the 86 patients enrolled in the study, 15 were microbiologically evaluable for bacteriological response. Of those, 6 reported pathogen eradication at the end of therapy (40%), and 8 reported presumed eradication (%). At end of study evaluation, 9 patients showed pathogen eradication (50%), and 7 showed presumed eradication (%). Therefore, negative cultures were obtained from % of the patients at EOT, and from % at the end of the study. One patient (% of patient population) reported presumed microbiological resistance. At study end, 2 patients (%) still reported undetermined culture. Uncontrollable vomiting and worsening pneumonia condition were reported by % of patients. Discussion and Conclusion Treatment based on the administration of IV azithromycin associated to ceftriaxone and followed by oral azithromycin proved to be efficacious and well-tolerated in the treatment of Brazilian inpatients with CAP.
Key-Words: Community acquired infections, pneumonia, anti-bacterial agents, macrolide ketolides, azithromycin.
Community-Acquired Pneumonia (CAP) is a major public health problem. The estimated yearly incidence in the United States is 4 million cases [1]. Of those, , are admitted to hospital, with death being the outcome for up to 40% [2] and with costs reaching 23 billion dollars [3,4]. In Brazil, CAP affects 2 million people annually, being the second most common cause of hospital admittance: ,, with 30, having death as the outcome. Appropriate microbiological exams identify infection-causing microorganisms in less than 50% of cases [5,6]. Therefore, the administration of antibiotics is based on results from clinical and epidemiological studies, being eminently empirical and usually administered to fight Streptococcus pneumoniae and Haemophilus influenzae: typically, the most frequently isolated microorganisms in adult patients admitted due to CAP. Pneumococcus is still the "number 1" pathogen in all age ranges, with penicillin resistance variable at different geographical locations worldwide: in Brazil, it is approximately 2%-5%, being typically presented as an invasive pneumococcic condition, which means that it is with bacteremia, empyema or concurrent meningitis.
Brandileone et al. carried out an evaluation through CLSI/NCCLS clinical and laboratory interpretation endpoints for disc diffusion susceptibility and MIC results. Approximately % of pneumococci presented "high-level resistance", and approximately 22% presented "intermediate level resistance" [7].
CAP treatment is changeable, and tries to track down microorganisms. In , the American Thoracic Society (ATS) published guidelines for the treatment of CAP. Those guidelines recommended that inpatients should receive empirical therapy based on the association of a beta-lactam and a macrolide [7], so that atypical agents (Mycoplasma, Chlamydophila pneumoniae (Chlamydia) and Legionella) could be covered. Atypical bacteria account for 15%-20% of hospital admittances due to CAP; therefore, in many cases, diagnosis is not predictable based on clinical and/or radiological conditions.
Studies have demonstrated that if that association is administered within 24 hours of admission, hospitalization time will be reduced by 50% [8,9]. Those recommendations were slightly changed in , and confirmed in , with the possibility of administering fluoroquinolones to inpatients with CAP as well as antibiotic therapy starting within 4 hours of admission at the latest [10].
In Brazil, the Brazilian Society of Pneumology and Tisiology published guidelines for the treatment of CAP in The guidelines recommend a systematic approach after the decision had been made as to whether treatment will be in hospital or through the outpatient unit. The guidelines set out that, inpatients on the ward must receive the association of a macrolide and a third generation cephalosporin or a macrolide associated to a betalactamic and to a beta-lactamase inhibitor (IV) or a fluoroquinolone [11-15]. However, the use of fluoroquinolones has been at the core of debates for the last 10 years due to its potential ability to induce resistance, as well as tolerability problems, especially among patients with comorbidities. That led the CDC to recommend use restriction for conditions requiring an empirical approach [16]. Although Brazil has never reported resistance of S. pneumoniae invasive strains to fluoroquinolones, fast-pace emergence of Gram-negative bacteria that were resistant to a number of antibiotic classes was observed at hospitals where fluoroquinolone administration was under no restriction in treating respiratory infections, which makes therapy management of infections acquired in that setting more difficult [17]. In February, Metersky et al. conducted a multivariate analysis of CAP treatment. They observed that the empirical use of fluoroquinolone may be harmful and does not impact on the mortality rate [18], as opposed to the association of a macrolide and a third generation cephalosporin, which impacts positively [19]. In Canada, S. pneumoniae resistant to quinolones was detected concurrent to increased use of fluoroquinolone to treat CAP [20]. The work mentioned earlier, by Brandileone and cols., showed that % of the 3, S. pneumoniae strains tested were erythromycin resistant. S. pneumoniae resistance to macrolides differs in the United States and in Europe. Major approaches to CAP treatment also differ. In North America macrolides are more widely used, especially due to the fact that pathogen resistance to macrolides is mediated through efflux pumps (low level), whereas in Europe the resistance process takes place through ribosomic site change (high level). The understanding of the macrolide efficacy and tolerability profile in different ethnic groups was turned into a key aspect in such complex scenarios.
A number of factors were taken into account for macrolide choice making. Azithromycin belongs to the azalide subclass in the macrolide antibiotic class, with a proven in vitro and in vivo action spectrum against major pneumonia-causing agents: S. pneumoniae, H. influenzae, C. pneumoniae, L. pneumophila, M. catarrhalis, M. pneumoniae and S. aureus (oxacillin sensitive). Since approval in the United States in , azithromycin IV formulation has been widely used for inpatients with CAP. In addition to action spectrum, azithromycin pharmacokinetics and high tissue levels allow a single daily dose regimen. When CAP patients are treated in the outpatient unit, those pharmacological properties allow the use of azithromycin as monotherapy [21]. The purpose of the present study was to evaluate the efficacy, safety and tolerability of a combined regimen azithromycin and ceftriaxone both IV, followed by oral azithromycin when treating inpatients with moderate to severe CAP.
This is the first scientific paper in Brazil to show the efficacy of ceftriaxone + azithromycin to treat CAP in the Brazilian population scenario.
Materials and Methods
Eligibility Criteria
Both male and female patients over 18 years old, with history, clinical and radiological findings consistent with CPA diagnosis and whose severity required hospitalization and initial therapy with IV antibiotics were eligible to enroll in the study. The following criteria had to be met: (1) presence of alveolar infiltrate at thoracic X-ray, and at least two of the following findings within 48 hours prior to first visit (Visit I): onset of cough or worsening of chronic cough; change in sputum characteristics; axillary temperature > 38ºC (fever) or < ºC (hypothermia) in the previous 24 hours; pulmonary auscultation compatible with consolidation (fine bubbling rale); and leukocytosis (leukocytes > 10,/mm3 or > 15% young leukocytes); (2) presence of any score in severity criteria for coexistent diseases in the Pneumonia Severity Index (PSI) or any PSI score that would classify a patient as >II [22]. Pregnant or lactating women patients were excluded, as well as women of childbearing age not using effective contraceptives. Also excluded were patients presenting the following conditions/treatment: allergies or known or suspected intolerance to penicillin, cephalosporin, or macrolides; systemic treatment with any antibiotic for any period longer than 24 hours prior to first visit, or longer than seven days in the previous month; AIDS patients, neutropenics, (leukocytes < 2,/mm3 or neutrophils <1,/mm3) or undergoing chronic immunosuppressant therapy; clinical or radiological signs of pulmonary cavitation; cystic fibrosis, primary or metastatic pulmonary neoplasia, aspiration pneumonia, pleural empyema, tuberculosis or bronchiecstasis; gastrointestinal disorders or any other condition affecting the drug under investigation; epilepsy or seizures; clinically significant renal failure - creatinine > mg/dL, or estimated creatinine clearance < 20 mL/min/ m2 of body surface area; evidence of clinically significant hepatic failure with transaminase levels three times above the normal upper limit, or total bilirubin levels twice the upper normal limit; clinically significant cardiovascular condition. Patients participating in any other study involving investigational or commercial drugs concurrently or having participated within a month before the start of the present study were also excluded, as were those who had previously participated in the present study, those with evidence of recent alcohol or illegal drug abuse; and those who presented any condition which, following investigators' discretion, could interfere in their safety, their treatment response assessment, or that could in any way preclude treatment completion or follow-up; and those who had donated blood less than four weeks before study starting date or who planned to donate blood within a time period of four weeks after study completion. Childbearing age women who had not been surgically sterilized had to undergo a pregnancy test immediately before the study started. Additionally, effective contraceptive methods were expected to be in use during treatment period and for 10 days after study close. All patients included in the study signed the informed consent form. Study protocol was pre-approved by the Research Ethics Committee at each of the 13 institutions participating in the study. The study was conducted in compliance with Good Clinical Research Practices, the ethic principles of the Declaration of Helsinki, and the Brazilian legislation with regard to clinical research.
Study Design
This was a 30-day open-label, multicenter, non-comparative study. The study drug was administered for a period of 10 days. The average number of patients per center was 7. The center with the highest number of patients had a total of 30 enrollments. CAP patients who fulfilled the eligibility criteria were enrolled in the study. All patients received a single daily dose of mg of azithromycin associated to 1g of ceftriaxone (IV) for a period of between 2 and 5 days. Treatment proceeded with a single daily dose of mg of oral azithromycin to complete 10 treatment days. For cases where S. pneumoniae resistant to a macrolide was isolated in culture, the association of cefuroxime axetil and oral azithromycin was allowed. Patients were evaluated at enrollment (Visit I), on Visit II (day 3), at the end of treatment (Visit III day 10-12), and by study completion (Visit IV day 28 to 35), as well as daily during hospitalization. Clinical and bacteriological safety assessment was carried out at Visits I, III, and IV. Patients who finished treatment were still evaluated for safety for a period of 30 days. On Visit I the following data were collected: demographics, comorbidity history, information on the use of antibiotics in the previous month, medications currently being used, and information from an objective physical exam, which included measures of vital signs (heart and respiratory rate, blood pressure and temperature). Clinical evaluation of pneumonia signs and symptoms involved sputum characteristics, cough, dyspnea, pleuritic pain, rigors and adventitious sounds at pulmonary auscultation. Two chest X-Rays were taken: frontal and lateral view. PSI determination criteria were also evaluated, which resulted in a PSI score [22]. Blood and urine samples were collected for safety laboratory analysis. Childbearing age female patients were submitted to pregnancy test (urine or blood). Whenever possible, proper sputum samples defined as a sample with > 25 polymorphonuclear leukocytes and < than 10 epithelial cells per x field after Gram's stain test - and blood samples were obtained for culture. The sputum samples were submitted to microbiological qualitative evaluation only. Those showing bacterial growth were submitted to an antibiogram and tested locally at the center's laboratory with regard to antibiotic susceptibility following the National Committee for Clinical Laboratory Standards criteria. All patients enrolled in the study had blood samples taken for hemoculture locally at the center's laboratory. During the same visit urine samples were collected to detect Streptococcus pneumoniae and Legionella. Ideally, three sputum samples and hemoculture should have been collected for evaluation.
On Visit II (day3) the need for IV antibiotic therapy was assessed. The change to oral therapy was seen as appropriate whenever all of the criteria below were present: (1) body temperature < ºC for a minimum of 8 hours; (2) cough and dyspnea condition improvement; (3) proper oral intake and absorption; (4) leukocytosis reduction as compared to baseline. All signs and symptoms identified in Visit I were reevaluated. New ones were reported. Hematological and biochemical laboratory exams were repeated. Whenever possible, a second proper sample was obtained for sputum culture. If no expectoration was present even after nebulization and physiotherapy, culture was considered negative. Hemoculture collection was repeated if Visit I collection was positive, or if the patient had been discontinued from the study due to therapeutic failure.
At the end of treatment (Visit III, day 10 to 12), global clinical response to treatment was evaluated and classified as cure, improvement or therapeutic failure. Each of them were defined as follows: (1) cure: the resolution of signs and symptoms, with clinical recovery to before the occurrence of pneumonia condition, which included leukocytosis reduction, with improvement or non-progression of infiltrates at thoracic X-Ray; (2) improvement, as resolution of fever, but incomplete resolution of other signs and symptoms, with no need for additional antibiotic therapy; (3) therapeutic failure, such as no resolution or worsening of any of pneumonia signs or symptoms, with the need for additional antibiotic therapy. Therapeutic failure might be associated to the antibiotic in the case that the patient had been administered the study drug for at least 48 hours or non-related to the antibiotic in the case that the patient had been administered the drug for less than 48 hours; (4) undetermined when patient response to treatment could not be evaluated (lost due to follow-up or study withdrawal, except when due to therapeutic failure, among other reasons). At study close (Visit IV, days 28 to 35) or at early discontinuation, the investigator conducted a final evaluation of the global clinical response to treatment. Classification was: cure, improvement, or therapeutic failure. Both, signs and symptoms that were identified at earlier visits, and new ones that might have emerged, were compared. Those signs and symptoms were all compared to Visit I. Vital signs were also evaluated, as well as concurrent use of other medications and the occurrence of adverse events. Hematological and biochemical exams were repeated only if a clinically significant adverse event occurred, or if any relevant laboratory change was detected at Visit III. A final thoracic X-ray was taken, and whenever possible, a proper sample was obtained for sputum culture. If no sample could be obtained, it was considered equivalent to a negative culture. If initial hemoculture was positive, or if the patient was discontinued due to clinical failure, a new sample was collected for blood culture.
Efficacy and Safety Evaluation
The sample from intention to treat (ITT) patients included those who received at least one dose of IV azithromycin, and who provided sufficient data for at least one efficacy parameter analysis, conducted separately from clinical and bacteriological response. Primary efficacy parameter was clinical response, defined as the percentage of cure or improvement at the end of the study. Secondary efficacy parameters were clinical response at the end of the study and bacteriological response rate at the end of treatment (Visit III) and at end of the study (Visit IV). Clinical response was determined by comparing clinical presentation global evaluation at study end and Visit I. Safety analysis was conducted in the sample of patients that received at least one dose of the study drug (safety population). All adverse events were noted throughout the study. Serious adverse events were defined as any occurrence that might have put the patient's life at risk or resulted in hospitalization, hospitalization extension, persistent or significant impairment, teratogeny, or death. Safety analysis parameters were evaluated throughout the study and were based on the adverse event rate, early discontinuation, laboratory changes, physical exam, and vital signs.
Statistical Analysis
Sample size was estimated based on cure rate at the end of the study: 75%. Two-sided 95% CI for that rate with 20% width could be obtained with a 73-patient sample. Assuming loss to follow-up or non-evaluation of up to 20% of patients, an 88-patient sample size would be required. Patient ratio for each clinical and bacteriological response category was obtained. A 95% CI, based on the normal approximation to the binomial distribution, was calculated.
Results
Study Population
A total of 88 patients were selected, of those, 86 received the proposed treatment. Forty five patients were male (%) and approximately 66% were white. Age range was ± , and average time from onset of pneumonia was days (1 to 22 days). PSI mean score was ± , ranging from to Most commonly found comorbidities were congestive heart failure (15 patients), diabetes mellitus (14 patients), chronic pulmonary obstructive disease (COPD) (13 patients) and asthma (6 patients). Data on patients enrolled in the study are summarized in Table 1.
Of the 86 patients who were treated with the study drugs 62 (%) reached study completion. A total of 24 patients (%) did not reach completion for the following reasons: adverse events (13 patients %); change in laboratory testing (1 patient %); no efficacy (1 patient %); lost to follow-up (1 patient %); sudden death (1 patient %); other reasons (7 patients %). A total of 85 patients were included in the Modified Intention to Treat (MITT) population, made up of all patients that had been treated, except those who were wrongly diagnosed or did not present clinical symptoms at evaluation 1. 24 patients reported microbiological data and were analyzed with reference to bacteriological efficacy parameters.
Treatment Efficacy Evaluation
When the study started, pneumonia signs and symptoms were presented as follows: cough %; dyspnea %; pulmonary auscultation with rale %; pleuritic pain %; snoring at pulmonary auscultation %; wheezing % and rigors %. Pneumonia signs and symptoms showed significant improvement at the end of treatment: cough %; rale %; pleuritic pain %; snoring % and dyspnea %.
The number of patients who reported a positive clinical response (cure or improvement) can be found in Table 2. The number of patients who reported a positive bacteriological response (eradication plus presumed eradication) is shown in Table 3. Twenty four patients (% of the study population) made up the population that was modified for bacteriological evaluation through hemoculture or sputum. The latter reported a % and % rate of pneumococci that were resistant to macrolides at the end of treatment and at the end of study respectively. Only 1 patient used cefuroxime axetil rather than azithromycin.
Fifteen patients were evaluated at the end of treatment. Of those, 40% reported eradication, % reported presumed eradication, and % reported presumed persistence.
At close of study out of the 18 patients that were evaluable through microorganism isolation (sputum or hemoculture) % reported eradication or presumed eradication. (Table 3)
Table 4 shows clinical response to base pathogen in the MITT population in patients whose pathogen was isolated. Evaluation of pneumonia etiological agents that were identified was as follows: at the end of the therapy, from patients infected by Streptococcus pneumoniae % reported cure (7 patients) and % reported improvement (2 patients); of those infected by Haemophilus influenza % reported improvement (2 patients); of those infected by cure (9 patients) reported cure and % reported failure. Of the 62 patients, 18 had etiological agents identified, as listed below.
Safety and Tolerability Evaluation
Of the 86 patients in the safety population, 64 patients (%) reported adverse events. Of those, the adverse events reported by 33 patients (%) were related to the study drug. A total of adverse events were observed. Of those, 55 (39%) were related to the study drug. Serious adverse events were reported by 20 patients, but only two patients had their serious adverse events pneumonia condition worsening and uncontrollable vomiting related to azithromycin/ceftriaxone. Both patients were discontinued from the study. Of the 14 patients (%) that were discontinued from the study due to adverse events, 5 (%) were discontinued due to treatment-related adverse events. Most commonly found adverse events were: no therapeutic response in 10 patients (%); pneumonia persistence in 7 patients (%); increase in transaminase levels in 6 patients (%); pain at infusion site in 5 patients (%); epigastralgia in 5 patients (%); diarrhea in 5 patients (%); vomiting in 5 patients (%) and hypertension in 5 patients (%). A more detailed description of drug-related adverse events and their severity can be found in Table 5.
Discussion
Community Acquired Pneumonia is a high prevalence condition, with a significant morbimortality rate and approximately 20% of cases resulting in hospital admittance [23].
The present study confirms that IV administration of azithromycin associated to ceftriaxone and followed by oral azithromycin has shown good clinical efficacy in treating CAP inpatients. The possibility of changing to oral administration after between 48 and 72 hours of parenteral treatment may result in shorter hospital stay time.
Current studies support the macrolide - betalactamic association. A number of studies of the treatment of CAP recommend coverage for atypical agents as well as S. pneumoniae, including Mycoplasma, Chlamydophila pneumoniae (Chlamydia) and Legionella. Many Mycoplasma or Chlamydophila pneumoniae (Chlamydia) infections are self-limiting or are considered mixed infections that may respond to betalactamics. Subgroup analysis in Legionella infected patients shows that the therapeutic failure rate is significantly lower in patients treated with antibiotics with coverage for atypical agents.
Shefet et al. have conducted an analysis of 32 recent studies involving CAP patients who were treated with amoxicillin, 2, treated with fluoroquinolone, and 2, treated with clarithromycin and azithromycin. Corresponding rates demonstrated for clinical response were: 80%, 88%, %. Clinical response rates for treatment using fluoroquinolones and macrolides were significantly higher when compared to those using amoxicillin.
That makes the present study's findings more material. The data also show that for every 12 CAP patients treated with amoxicillin 1 therapeutic failure was reported and it could have been prevented if a macrolide or a fluoroquinolone [27] had been used.
A number of studies have tried to measure the impact of treatment compliance for CAP outcome. However, none of those studies were designed to evaluate specific antibiotic therapy regimens.
The present study is not failure free. Major criticism may be raised of the qualitative rather than quantitative microbiological analysis, as well as of the fact that cultures were not presented by collection site (hemoculture or sputum), but by patient (eradication or persistence).
Some conclusions may be drawn, however, to be added to the literature currently available.
Retrospective conventional studies suggest that treatment using a macrolide combined, typically with a cephalosporin, to form an initial therapeutic scheme for patients who need hospitalization may be associated to lower mortality rate and shorter hospital stay time when compared to treatment with cephalosporin only [30,31].
Sanchez et al. conducted a prospective study in involving elderly patients with CAP. In the study, IV administration of azithromycin and clarithromycin associated to ceftriaxone was compared. Hospital stay time was ± days for the group treated with azithromycin, and ± days for the group treated with clarithromycin (p<). The mortality rate was also lower in the azithromycin group when compared to the clarithromycin group (% vs. %; p<). These data suggest the association azithromycin-ceftriaxone to be more efficacious when compared to clarithromycin [34].
The present study has shown that the combination of IV azithromycin and ceftriaxone to treat CAP inpatients agreed with previous publications, having shown % clinical response at the end of treatment, and % at the end of the study [31,35,36]. Approximately 75% of patients reported some adverse event during the study, but only % were related to azithromycin. From all serious adverse events only 2 were related to the study drug, and resulted in the withdrawal of the two patients from the study. This data is in agreement with current literature, and has demonstrated the concern with regard to pharmacosurveillance in the present study.
In conclusion: azithromycin presents a good safety and tolerability profile. Therefore, IV azithromycin associated to ceftriaxone may be an appropriate therapeutic choice to treat CAP patients who need hospitalization in Brazil. Currently, the most widely accepted concept with regard to the starting dose time frame for CAP patients who need hospitalization is "the more septic the patient, the more likely it is that as little as a 1 hour delay may impact mortality rate". The recommendation is that the first dose be administered at the Emergency Service where the patient is seen for the first time, rather than waiting for the patient to be admitted. That would mean good conduct assistance and the best option choice for the patient.
References
1. Bartlett J.G., Mundy L.M. Community-acquired pneumonia. N Engl J Med ;(24)- [Links]
2. Fine M.J., Smith M.A., Carson C.A., et al. Prognosis and outcomes of patients with community-acquired pneumonia. A meta-analysis. JAMA ;(2)- [Links]
3. Marrie T.J., Peeling R.W., Fine M.J., et al. Ambulatory patients with community-acquired pneumonia: the frequency of atypical agents and clinical course. Am J Med ;(5)- [Links]
4. Marrie T.J. Community-acquired pneumonia. Clin Infect Dis ;18(4)- [Links]
5. Bates J.H., Campbell G.D., Barron A.L., et al. Microbial etiology of acute pneumonia in hospitalized patients. Chest ;(4)- [Links]
6. Fang G.D., Fine M., Orloff J., et al. New and emerging etiologies for community-acquired pneumonia with implications for therapy. A prospective multicenter study of cases. Medicine (Baltimore) ;69(5)- [Links]
7. Brandileone M.C., et al. Increase in numbers of beta-lactam-resistant invasive Streptococcus pneumoniae in Brazil and the impact of conjugate vaccine coverage. Journal of Medical Microbiology ;- [Links]
8. ATS Statement. Guidelines for the initial management of adults with conmunity-acquired pneumonia: diagnosis assesment of severity, and initial antimicrobial therapy. Am Rev Respir Dis ;- [Links]
9. Stahl J.E., Barza M., Desjardin J., et al. Effect of macrolides as part of initial empiric therapy on length of stay in patients hospitalized with community-acquired pneumonia. Arch Intern Med ;- [Links]
Lode H. In: Azithromycin in the treatment of community-acquired pneumonia in adults. Cambridge Medical Publications, . [Links]
Sanchez F., Mensa J., Martinez J.A., et al. Is Azithromycin the First-Choice Macrolide for Treatment of Community-Acquired Pneumonia? Clin Infect Dis ;6(10)- [Links]
Plouffe J., Schwartz D.B., Kolokathis A., et al. Clinical efficacy of intravenous followed by oral azithromycin monotherapy in hospitalized patients with community-acquired pneumonia. The Azithromycin Intravenous Clinical Trials Group. Antimicrob Agents Chemother ;44(7)- [Links]
American Thoracic Society. Guidelines for the initial management of adults with community-acquired pneumonia: diagnosis, assesment of severity, and initial antimicrobial therapy. Am Respir Crit Care Med ;- [Links]
Pereira C.A.C., Rocha R.T., Silva R.F., et al. Diretrizes para Pneumonias Adquiridas na Comunidade (PAC) em Adultos Imunocompetentes. J Bras Pnem ;30(Supl)-4. [Links]
Bartlett J.G., Dowell S.F., Mandell L.A., et al. Practice guidelines for the management of community-acquired pneumonia in adults. Infectious Diseases Society of America. Clin Infect Dis ;31(2)- [Links]
Mandell L.A., Wunderink R.G., Anzueto A., et al. Infectious Diseases Society of America/American Thoracic Society Consensus Guidelines on the Management of Community-Acquired Pneumonia in Adults. Clin Infect Dis ;44 Suppl 2:S27- [Links]
Heffelfinger J.D., Dowell S.F., Jorgensen J.H., et al. Management of community-acquired pneumonia in the era of pneumococcal resistance: a report from the Drug-Resistant Streptococcus pneumoniae Therapeutic Working Group. Arch Intern Med ;(10)-8. [Links]
Rifenburg R.P., Paladino J.A., Bhavnani S.M., et al. Influence of fluoroquinolone purchasing patterns on antimicrobial expenditures and Pseudomonas aeruginosa susceptibility. Am J Health Syst Pharm ;56(21)- [Links]
Park-Wyllie L.Y., Juurlink D.N., Kopp A., et al. Outpatient gatifloxacin therapy and dysglycemia in older adults. N Engl J Med ;- [Links]
Metersky M.L., Ma A., Houck P.M., Bratzler D.W. Antibiotics for bacteremic pneumonia. Chest ;- [Links]
Chen D.K., McGeer A., de Azavedo J.C., Low D.E. Decreased susceptibility of Streptococcus pneumoniae to fluoroquinolones in Canada. Canadian Bacterial Surveillance Network. N Engl J Med ;(4)-9. [Links]
Garey K.W., Amsden G.W. Intravenous azithromycin. Ann Pharmacother ;33(2) [Links]
Fine M.J., Singer D.E., Hanusa B.H., et al. Validation of a pneumonia prognostic index using the MedisGroups Comparative Hospital Database. Am J Med ;94(2)-9. [Links]
Mandell L.A., Bartlett J.G., Dowell S.F., et al. Update of practice guidelines for the management of community-acquired pneumonia in immunocompetent adults. Clin Infect Dis ; [Links]
File T.M. Community-acquired pneumonia. Lancet ; [Links]
Mills G.D., Oehley M.R., Arrol B. Effectiveness of beta lactam antibiotics compared with antibiotics active against atypical pathogens in non-severe community acquired pneumonia: meta-analysis. BMJ ; [Links]
Shefet D., Robenshtock E., Paul M., Leibovici L. Empiric antibiotic coverage of atypical pathogens for community acquired pneumonia in hospitalized adults. Cochrane Database Syst Rev :CD [Links]
Mandell L.A., Marrie T.J., Grossman R.F., et al. Canadian guidelines for the initial management of community-acquired pneumonia: an evidence-based update by the Canadian infectious diseases society and the Canadian thoracic society. Clin Infect Dis ;- [Links]
Mortensen E.M., Restrepo M., Anzueto A., Pugh J. Effects of guideline-concordant antimicrobial therapy on mortality among patients with community-acquired pneumonia. Am J Med ; [Links]
Menendez R., Torres A., Zalacain R., et al. Guidelines for the treatment of community-acquired pneumonia: Predictors of adherence and outcome. Am J Respir Crit Care Med ; [Links]
Stahl J.E., Barza M., DesJardin J., et al. Effect of macrolides as part of initial empiric therapy on length of stay in patients hospitalized with community-acquired pneumonia. Arch Intern Med ;(21)- [Links]
Gleason P.P., Meehan T.P., Fine J.M., et al. Associations between initial antimicrobial therapy and medical outcomes for hospitalized elderly patients with pneumonia. Arch Intern Med ;(21)- [Links]
Martinez J.A., Horcajada J.P., Almela M., et al. Addition of a macrolide to a beta-lactam-based empiric antibiotic regimen is associated with lower in-hospital mortality for patients with bacteremic pneumococcal pneumonia. Clin Infect Dis ; [Links]
Waterer G.W., Somes G.W., Wunderink R.G. Monotherapy may be suboptimal for severe bacteremic pneumococcal pneumonia. Arch Intern Med ; [Links]
Sanchez F., Mensa J., Martinez J.A., et al. Is azithromycin the first-choice macrolide for treatment of community-acquired pneumonia? Clin Infect Dis ;36(10)- [Links]
Bohte R., van't Wout J.W., Lobatto S., et al. Efficacy and safety of azithromycin versus benzylpenicillin or erythromycin in community-acquired pneumonia. Eur J Clin Microbiol Infect Dis ;14(3)-7. [Links]
Paladino J.A., Gudgel L.D., Forrest A., Niederman M.S. Cost-effectiveness of IV-to-oral switch therapy: azithromycin vs. cefuroxime with or without erythromycin for the treatment of community-acquired pneumonia. Chest ;(4)-9. [Links]
Address for correspondence:
Dr. Fernando Rubio
Hospital de Base of FUNFARME. Av. Brigadeiro Faria Lima,
São José do Rio Preto SP Brazil
Zip code: -
E-mail: Financial Support: gongora@standardservices.com.pk
The present study was conducted with the financial support of Pfizer.
Received on 6 December ; revised 18 March
What’s New in the Quick Heal X-Gen v7.03 serial key or number?
Screen Shot

System Requirements for Quick Heal X-Gen v7.03 serial key or number
- First, download the Quick Heal X-Gen v7.03 serial key or number
-
You can download its setup from given links: