Shop Alto Essentials to add pharmacy products to any delivery!

Your partner in navigating the ins and outs of prescriptions — at no extra cost.

Alto Pharmacy Technician

Alto Pharmacist

It’s official: Alto Pharmacy is a great place to work! We’re honored to join the community of Great Place to Work-Certified™ companies based on team member feedback and a rigorous assessment of our company’s culture and benefits.

Join us in delivering our industry-leading pharmacy care to millions of people across the country. As a member of the team, you’ll play an integral role in improving our customers’ quality of life and redefining what’s possible in pharmacy. 

Be Part of a Great Place to Work — Join Our Team

Hear first-hand from members of the Alto technology teams.

Read the latest Alto blog posts covering healthcare, family health, managing diseases, and other Alto highlights.

Blog | Alto Pharmacy

Last year, we set out to tackle this technical debt by splitting the User model into separate concerns and refactoring the entire system into this new paradigm.

Tackling Technical Debt and Improving Security: How Alto Untangled an Overloaded User Model

At Alto, we have three types of users: customers, healthcare providers (nurses, doctors, etc), and operations users who run the pharmacy. For each type of user, we maintain a separate application (though they share a monolithic backend for now): our customer app; our Alto Connect app for providers; and our internal pharmacy management tool called Wunderbar, which powers the pharmacy experience from prescription intake to fulfillment.

Early on, we made the pragmatic choice to represent both customers and operations users with a single User model, distinguishing them with a “roles” attribute. This required repetitive checks that, over time, slowed down our engineering teams, presented substantial privacy risk, and posed difficult scaling challenges as we evolved our monolith into different microservices. 

The challenges of relying on a single User model for different types of users

The notion of a User is core to our concept of identity from which authentication and authorization proceeds. From a security perspective, it’s difficult to build an extensible and clean authentication and authorization system when you’re overloading one model for two very different populations of users. From a privacy perspective, this muddied customer records (which are subject to more restrictions because they’re healthcare records) with workforce records, hamstringing many analytics efforts.

Authentication: Alto employees who were also Alto customers were required to use their work emails for their customer accounts. Not only was this restriction frustrating for Alto employees, but it also posed a security risk: employees should only be able to access Wunderbar via corporate SSO, not their personal account passwords. 

Authorization: Engineering new authorization capabilities required intricate knowledge of the idiosyncrasies of our user structure. This both slowed down development and created tremendous risk that any mistake could easily escalate user permissions.

Privacy: Because they existed in the same table, both customer records and Alto operations user records were classified as Protected Health Information, or PHI, which severely limited what we were able to do with them.

Attribution: Our robust audit logs were significantly less useful when a user ID in the transaction log might refer to either an ops user or a customer.

State management: Some updates pertaining to admin identity lived on the customer model, some lived on the employee model, and others lived in other various models.

Architecture: Tight coupling would have prevented us from decoupling our monolithic system into smaller services.

Our backend is primarily a monorepo Rails application that shares a tremendous amount of functionality between our customer, provider, and ops user-specific domains. Generally we use JWTs to secure customer and ops user sessions. These JWTs are issued only once valid credentials have been present.

Ops users are required to log in via Okta SSO, enforcing both valid username/password as well as a two-factor authentication (2FA) prompt. We use Devise and Omniauth to wire up the OIDC flow with our upstream identity provider, and we use CanCan to expand a set of roles per-user into a set of capabilities that restrict what resources they can access/modify.

Ops users primarily work in our internal pharmacy management app. However, the state of these users was shared between several different tables: Users, which otherwise refer to customers, and Employees, which share some ops user-specific state tied to Users.

Large change sets of code being deployed at once are harder to code review, harder to unwind if something goes wrong, and are more likely to be more disruptive. For this project, we knew that such a large architectural change had to be broken up into many more-digestible pieces if we were to be successful. The plan:

1. Create a new dedicated model for our ops users

# == Schema Information
#
# Table name: wunderbar_users
#
#  id                        :bigint(8)        not null, primary key
#  user_id                   :bigint(8)        indexed
#  email                     :string           not null, indexed
#  first_name                :string           not null
#  last_name                 :string           not null
#  token_last_invalidated_at :datetime
#  roles_mask                :integer          default(0), not null
#  title                     :string           not null
#  team                      :string           not null, indexed
#  is_active                 :boolean          default(TRUE), not null
#  slack_user_id             :string
#  pod                       :string

This was the easy part: create the database structure for a properly isolated admin user type, which we called a WunderbarUser.

We now had our admin user state split between Employees and Users, with a new table that engineers and analysts wanted to use that was not yet populated, and we had to make progress while allowing new hires and new customers alike to onboard to our platform.

2. Synchronize state between the old tables and new table

Next, we created a WunderbarUser for any User who was, or ever had been, a Wunderbar user. This required some historical digging —we had a lot of people who were onboarded, and even some offboarded, before we even had the intermediate Employee record!

Two major choices at this stage really helped the project succeed. First, we ensured that the WunderbarUser records all had IDs matching the corresponding User records. This is because a lot of our legacy audit records (that we’re required to preserve and keep useful as a Covered Entity under HIPAA) referenced an `admin_user_id` column populated with the ID of the User. If we just created all new entries for WunderbarUsers, these old logs would require at least one level of indirection (e.g. querying back to User) to make useful.

     # Create with the same ID as the user that we're creating this from.
     wunderbar_user_attributes = {
       id: user.id,
       user_id: user.id,
       email: user.email,
       roles_mask: user.roles_mask,
       date_of_birth: user.date_of_birth,
       token_last_invalidated_at: user.token_last_invalidated_at,
       first_name: user.first_name,
       last_name: user.last_name,
       preferred_first_name: user.preferred_first_name,
       is_active: false,
     }

Second, we created a new WunderbarUser any time we created a new Employee record (e.g. when we onboarded a new employee) and synchronized any changes between Users, Employees, and WunderbarUsers tables. As a side note: we knew we’d have to protect this syncing logic to ensure that we only copied each change once — otherwise, our callbacks would fire forever!

3. Migrate functionality slowly to use the new ops user model

We migrated logic to reference WunderbarUsers where previously we’d referenced Users and/or Employees. Authentication, authorization, audit logs, and pharmacist licenses were all updated here — albeit painstakingly!

We then migrated all of the foreign keys our various Postgres database tables held to either the Users or Employees tables to instead reference the WunderbarUsers. This ended up being around a hundred foreign keys, but a constraint-only migration that fortunately didn’t involve any data changes.

In short: our goal was to do this change slowly and steadily enough that nobody would notice until, one day, we could announce to the team, “Hey, we did a big security-pertinent project, and now you can change your customer email to be anything.”

Authentication: While we use the same JWT format for each, our customer and operations user authentication systems are now totally separated.

Authorization: With separate user types, we have separate capabilities and domain-specific authorization checks for each area, enforced in code.

Experience: Onboarding as a new Altoid (somebody who works here; come join us!) is totally separate from the customer experience, and you no longer need to link your accounts together.

Privacy: Our ops users who choose to be customers enjoy the full privacy afforded to our customers without tying their account to their work identity in any way.

Attribution: Legacy audit logs are still index-able and query-able with the same IDs, just in a slightly different table.

State management: Customer state lives on the User table, and ops user state lives on the new WunderbarUsers table. Our callbacks on each have been dramatically pared down, and our intermediary Employee table is entirely gone, along with a number of other now-ancillary tables.

Architecture: We have a clear path to federate RBAC checks without shipping our entire customer database between services.

Bonus: Performance and code readability generally improved by removing complex joins and join tables and isolating concerns between the customer and ops user domains.

Another Bonus: Significant refactorings and increased test coverage along the way while we cleaned up some very old, very stale code.

Large architectural changes of legacy systems with heavy use are rarely 100% smooth. Here are a few learnings to keep in mind the next time you tackle a hefty piece of technical debt. 

1. Always validate your assumptions (e.g. the data your constraints are against) when foreign keys are concerned. Multiple times we assumed, “Hey, we’ve migrated a bunch of really big tables that are really old (insurance claims, prescriptions, and more), so there’s no way we could have another admin user that we haven’t created a commensurate WunderbarUser for, right?” Wrong! Your data can always have inconsistencies, but a simple SQL query (e.g. validate that all values of the column you’re migrating the foreign key to have a matching WunderbarUser) can save a lot of time and headaches.

2. When migrating foreign key constraints on tables with active reads in Postgres, ensure you break it into two steps. Migrate your foreign key with `{ validate: false }`

 def up
   remove_foreign_key :inventory_orders, to_table: :users, column: :created_by_id
   add_foreign_key :inventory_orders, :wunderbar_users, column: :created_by_id, validate: false
 
   validate_constraint
 end

Validate the named constraint of your foreign key separately

 def validate_constraint
   validate_constraint_statement = 'ALTER TABLE "inventory_orders" VALIDATE CONSTRAINT "fk_rails_abcd1234";'
   ActiveRecord::Base.connection.execute(validate_constraint_statement)
 end

3. When working with legacy tables, be mindful of legacy systems. Our Billing service used a very outdated golang ORM that panicked if a column specified by the `struct` in source no longer existed; this caused a late-night outage that made auto billing requests back up the next day.

4. Scoping projects is hard! This was a larger project than our team had ever scoped and delivered before. Once all the dust settled, this project took several months longer than our initial scoping estimates.This project was worth doing, but better estimates allow us to prioritize better. If we’d had a great scope of this immense project upfront, would we have chosen to do it first? Also, this was a tremendously difficult project to separate into material stages; all the benefit was really backloaded.

In the end, this was a very satisfying and important project to complete. We wouldn’t have been able to accomplish it without a lot of help from our colleagues on the Platform team, the Security team, and across many other functions atAlto. Very large projects that involve a lot of moving pieces and impact other teams are always scary — but we can’t let that fear prevent us from making the changes we know we need to do in order to be successful long-term.

The Engineering Team is hiring! Learn more about open positions here.

If you take insulin daily to manage type 1 or type 2 diabetes, it’s important to choose a method of insulin delivery that fits your lifestyle and diabetes management needs. Many individuals who are often on-the-go find insulin pens to be most convenient given their portable size, discrete nature, and quick administration time. 

What to Know About Insulin Pens

Read on for more information about these devices, including the different types of insulin pens and what to consider when choosing one.

An insulin pen combines insulin and a syringe into a single device, allowing for a faster and easier administration than syringes. When it is time to administer an insulin injection, all you have to do is attach a new needle and dial the correct dosage on the pen. If you take multiple types of insulin every day, many insulin pen manufacturers offer color-coded pens or different designs to help you quickly identify each pen’s type of insulin.

While insulin pens simplify insulin delivery and how you measure your doses, you will still need to self-administer injections throughout the day. This is in contrast to an insulin pump, which automatically delivers doses of insulin at specific times. If you require many insulin injections each day, you may want to ask your healthcare provider if an insulin pump would be a good fit for your diabetes management needs.

There are two main types of insulin pens: disposable and reusable.

A disposable insulin pen contains a prefilled cartridge used for multidosing. You will discard the pen once the cartridge is empty or when the insulin expires, depending on the type of insulin you are using. These devices are sometimes referred to as “flex pens” or “quick pens.” Common brands include Lantus®, Tresiba®, Humalog®, Novolog®, and Basaglar®.

A reusable pen contains cartridges of insulin that are discarded once empty or when the insulin expires. You will replace the empty or expired cartridge with a new one and reuse the pen. These are sometimes referred to as “smart pens.” Common brands include InPen® and NovoPen®.

Follow the steps below to safely administer your insulin injections with a disposable or reusable insulin pen. A diabetes educator or healthcare provider can answer any questions and help you become more comfortable using the device.

1. Verify the expiration date of your insulin and do a visual check to make sure it has no clumps — most pens have a visible insulin reservoir. If the insulin is cloudy, roll the pen for a minute. (If the insulin is clear, you do not have to roll the pen.) If you take multiple types of insulin, make sure you are using the correct type.

2. Remove the pen cover or cap and sterilize the pen tip with alcohol using a cotton swab or gauze pad.

3. Attach a new needle to the pen, and have a sharps container ready for the used equipment. (You will need to use a new needle for each injection.)

4. Prime the pen if using it for the first time. Dial the dosage knob to two units, hold the pen with the needle pointing up, and tap the pen gently to let any air bubbles rise to the top. Press and hold the knob and look for a drop of insulin. If you do not see any insulin, repeat these steps as needed until at least one drop appears. This removes air bubbles from the needle and ensures that the needle is properly functioning. 

5. Choose an injection site, typically your abdomen, thigh, or arm, and wipe it with an alcohol swab. Hold the needle at the angle instructed by your doctor, most often a 90-degree angle.

6. Insert the needle into the skin and push the button on your insulin pen to deliver the injection. Wait ten seconds to make sure all of the insulin has been absorbed into your skin.

Unused pens must be refrigerated. However, do not place them in the freezer. Once in use, you may keep your insulin pen at room temperature. It’s important to avoid extreme temperatures as much as possible, so do not leave them anywhere where they will get too hot, like a car, or too cold. In addition, check the product’s package insert for an expiration date or consult your doctor about when to discard a pen or cartridge with unused insulin.

What to consider when choosing an insulin pen

You should consult with your doctor before choosing an insulin pen. In addition, consider the following factors:

The type of insulin you take — some insulin pens are only compatible with specific types of insulin.

Your insulin dosing needs — each pen has a maximum dosage. In addition, different pens can deliver insulin in increments of a half unit, one unit, or two units.

Your insurance coverage — ask your insurance provider what coverage they offer of insulin pens, if any, and explore the costs of other insulin delivery methods to determine the best fit for your needs.

Most insurance plans have separate medical and pharmacy benefits. In most cases, professional services provided by your doctor will fall under medical benefits while prescription diabetes medications — including insulin — will fall under pharmacy benefits. 

Some diabetes supplies, including many reusable insulin pens, are covered under a third type of benefits: the Durable Medical Equipment (DME) section of your policy. There may be restrictions on the brands or suppliers that are available, and it’s important to check with your specific policy to understand what will be covered and under which sections.

Many disposable insulin pens are often covered with your pharmacy benefits, in which case Alto may be able to help you get started with using an insulin pen. We will work with your insurance (if applicable) and any third party savings programs so that you can get your insulin pen at the lowest possible price.

A diabetes pharmacy partner you can rely on

At Alto, we believe a pharmacy should be a partner in your diabetes care. We have a dedicated diabetes support team to ensure that you have everything you need to follow through on your individualized treatment plan. Reach out any time through in-app secure messaging or by phone at 1-800-874-5881.

This content is not intended to be a substitute for professional medical advice, diagnosis, or treatment. Always seek the advice of your physician or another qualified health provider with any questions you may have regarding a medical condition.

All third party trademarks (including logos and icons) referenced by Alto Pharmacy remain the property of their respective owners. Unless specifically identified as such, Alto’s use of third party trademarks does not indicate any relationship, sponsorship or endorsement between Alto and the owners of these trademarks.

Emphysema — which falls under the umbrella of chronic obstructive pulmonary disease (COPD), along with chronic bronchitis — is a lung disease that most often develops as the result of many years of heavy smoking. It affects more than 3 million people in the United States.

Emphysema: Causes, Symptoms and Treatments

As a progressive lung disease, symptoms of emphysema become more pronounced over time. While there is no cure, emphysema is both manageable and preventable. You can slow the progression of the disease by following the treatment plan your doctor recommends and maintaining a healthy lifestyle.

Read on to learn more about the causes and symptoms of emphysema and common treatment options.

Emphysema involves slow and gradual damage to the tiny air sacs in your lungs (alveoli). As these air sacs weaken over time, the surface area of the lungs is reduced, limiting how much oxygen can travel to your bloodstream.

Since emphysema progresses gradually, signs and symptoms may not appear until the lung tissue has already been significantly weakened. For many people, the first noticeable symptoms include shortness of breath and more frequent coughing, especially during physical activities. Other symptoms of emphysema include wheezing, exhaustion, and chest tightness, and producing greater amounts of mucus.

In some cases, the lack of oxygen can cause blue or gray lips or fingernails. If you experience this symptom, seek immediate medical attention.

The majority of emphysema cases occur as the result of cigarette smoking, with heavier smoking linked to a higher risk of developing emphysema. Additional risk factors for emphysema include the following:

Age — in many cases of smoking-related emphysema, symptoms first become noticeable between the ages of 40 and 60

Exposure to high pollution chemical fumes or lung irritants

Having a history of childhood respiratory infections

To determine if you have emphysema, your doctor will ask about your health history and the potential symptoms of emphysema that you are experiencing. They may ask you questions about your smoking history, your exposure to secondhand smoke or chemical fumes, and if you have a family history of lung health issues.

After taking your health history, they may order one or more of the following tests to confirm a diagnosis of emphysema:

Imaging tests, including chest X-rays and computerized tomography (CT) scans, which combines X-ray images taken from different angles.

An arterial blood gas test, which measures how well your lungs transfer oxygen to your bloodstream and remove carbon dioxide.

An electrocardiogram (ECG) to check your heart’s function and rule out a diagnosis of heart disease.

A pulse oximetry, which measures the oxygen level of your blood. This can show how well oxygen travels to the parts of your body furthest from your heart.

Lung function tests, which measure how much air your lungs can hold, how easy it is for them to empty air, and how well they deliver oxygen into your bloodstream.

Quitting smoking is the most important thing you can do to slow the progression of emphysema. If you are having trouble quitting, ask your doctor for smoking cessation resources like nicotine replacement therapy to help manage withdrawal symptoms and cravings. In addition, the treatment options below can slow the progression of emphysema and help you live an active lifestyle.

Several types of medications are used to manage and treat emphysema.

Bronchodilators like albuterol (Ventolin®, Proventil®, AccuNeb®), albuterol sulfate (ProAir® HFA®, ProAir RespiClick), and levalbuterol (Xopenex®) help relax your airway muscles and open your lungs to reduce discomfort. Although not common, potential side effects of bronchodilators include nervousness or shakiness, headache, throat or nasal irritation, and muscle aches. Your doctor can explain more about the risks and benefits of using a bronchodilator when building your treatment plan.

Inhaled corticosteroids reduce swelling in your lungs and open your airways so that more air can move in and out of your lungs. They may be taken via inhaler or nebulizer. Corticosteroids commonly prescribed to treat emphysema include beclomethasone dipropionate (branded options include Qvar Redihaler®), budesonide (Pulmicort®), ciclesonide (Alvesco®), flunisolide (Aerospan®), fluticasone propionate (Flovent®), and mometasone (Asmanex Twisthaler®). 

Inhaled corticosteroids typically do not cause long-term side effects, but mouth and throat irritation and oral yeast infections may occur. As a precaution, rinse your mouth with water after each dose to prevent infections.

Antibiotics may also be used to fight infections that can lead to emphysema-related complications like acute bronchitis or pneumonia.

Pulmonary rehabilitation is an outpatient educational program that provides the skills and knowledge needed to manage your emphysema and increase your level of physical strength and fitness. The classes are led by a team of healthcare professionals, physical therapists, and dietitians and taught in a group setting, giving you the opportunity to connect with other individuals living with emphysema and other lung diseases. Pulmonary rehabilitation is often a good fit for individuals who frequently experience shortness of breath when performing daily activities despite taking medication as prescribed.

Supplemental oxygen, or oxygen therapy, can relieve shortness of breath and increase your tolerance for physical activities. There are several devices used in oxygen therapy. Your doctor can guide you in choosing the right oxygen delivery system based on your health needs, lifestyle, and insurance benefits. You may be prescribed one oxygen device to use at home and one to use when you are on the go.

Be sure to follow all of your doctor’s instructions when using your oxygen device, including the flow rate setting (how much oxygen you’ll need per minute). In addition, you may find it helpful to explore the American Lung Association's resources on oxygen therapy.

We’re here to support your emphysema treatment

Sticking to the treatment your doctor has recommended is critical to managing emphysema. At Alto, we make that as easy as possible by offering free hand-delivery, automatic savings investigations, and easy medication management tools through our website and app. And our team of pharmacists is always here to answer your questions by phone or through the Alto app. 

Reach out any time through in-app secure messaging or by phone at 1-800-874-5881 to learn how Alto can support your emphysema treatment plan.

Face and fingerprint ID login is a convenient, seamless way to gain app access on a mobile device. Instead of typing in a lengthy, hard-to-remember username and password, many apps allow you login with just a quick scan of your face or fingerprint (also known as biometrics).

Considerations and Approaches for Implementing Biometric Login: Part 1

It's a desirable feature for both our end user and the Patients Team here at Alto — we want to make it as easy as possible for users to log in while also performing more frequent authentication checks. Improve the user experience and the security of our app? Sounds like a win-win.

As an engineer, implementing biometric login might seem easy, as mobile devices already capture, manage, and encrypt biometric data and expose APIs for app developers like myself to initiate a biometric scan. All I need to do is call that API and wait to hear if the scan is successful or not. What isn't as simple, though, is figuring out what to actually do with a successful biometric scan response. What does a successful scan mean, and how does that relate to the username and password credentials that users currently use to access our app?

This post walks through the decision points we encountered while implementing biometric login and how our healthcare privacy concerns influenced the final implementation approach.

Prior to implementing biometric login, the only way for users to access the Alto app was with email (username) and password. A valid email and password generates a session, which expires at some frequency. Once the session expires, the user must re-enter their email and password to regain access to the app.

From the beginning, we knew that biometrics would need to be built with our existing email and password session management in mind. This is made clear in the Apple developer docs: "Use biometrics as a supplement to something you’re already doing. Don’t depend on biometrics as your only authentication option."

Make it easier for users to login. Nobody likes typing in an email and password — especially on a mobile app. Our goal was to reduce the number of times a user must enter their email and password.

Enhance the security of our app using more frequent authentication checks. As a healthcare app that displays Personal Health Information (PHI), conducting more frequent authorization checks decreases the likelihood of PHI becoming exposed to an unauthorized third party.

Have the ability to revoke biometric access from a particular user. Similarly, we want to be extra careful to ensure that if a device is lost or stolen, we have a fallback plan to invalidate a user's session and protect the user’s PHI. For email and password initiated sessions, this happens when a user changes their password, as any change in login credentials will invalidate all active sessions for that user. We needed a similar contingency plan for biometric login.

There are several ways to use a mobile device's biometrics to authenticate a user, with varying degrees of security.

No server-side authentication. Simply integrate with the device's biometrics as an extra layer of authentication. If the biometric scan is successful, let the user proceed into the app.

Provides an extra check and gives your app a sense of modern polish

No server-side validation means that nothing is being validated against your system, so this is not a good substitute for account authentication. Therefore, even if you add this check, the user should still be prompted to re-enter their email and password at the same frequency as before.

Given this, this approach wouldn't help us reach our goal of reducing the number of times a user must enter their email and password.

This approach is a good fit if your application already has an existing login and session management system, and you want extra authentication checks throughout the user's session without modifying any other part of the system.

Tie biometrics to our existing email and password authentication. Use the user's biometrics to unlock an encrypted version of their email and password credentials. When a user sets up biometric login, store the user's login credentials within the device's keystore — the keystore will automatically encrypt the credentials. After a successful biometric scan, retrieve those credentials from the keystore and send them to your existing login API.

Still easy to implement, no backend changes needed

Biometric scan can be used in place of entering an email and password

Changing email and password credentials will revoke biometric access: if a user changes their credentials, their biometrics will access stale credentials and fail to login. (This is somewhat of a con as well — it provides a poor user experience, but it's an edge case that should happen infrequently.)

There is still only one way for a user to authenticate server-side, but now two ways to pass server-side authentication — essentially weakening your app's existing account security.

This approach effectively hands out internal login credentials to third party storage. While not a huge risk considering a device's secure storage is encrypted and trusted by most users, it’s not necessarily a best practice either.

This approach is a good fit if your application doesn't contain sensitive data, and your goal is to make it more convenient for a user to login by replacing email and password with a biometric scan.

Create a separate authentication mechanism for biometrics. Introduce a new authentication mechanism specifically for biometrics, resulting in two independent forms of server-side session authentication: email with password and biometrics. The implementation could look like generating a keypair or a shared secret to save and validate against the server whenever a user attempts to login with biometrics.

Biometrics is now tied to its own secure server-side authentication mechanism, which means it can be used independently of email/password (or even replace it, if you choose to).

Two layers of authentication adds security to the app. Not only does a user need a valid email/password session, they also need a valid biometric session.

It provides fine-grain control over a user's biometric session. You can invalidate a user's biometric session by invalidating the public key and can even invalidate a biometric session without impacting an email-and-password session if needed.

Requires building and maintaining a separate authentication mechanism

This approach is a good fit if your application contains sensitive data (e.g. PHI or financial information), and your goals are to make it both more convenient for a user to login by replacing email and password with a biometric scan while also strengthening the security of your account management system.

Because we are a healthcare company dealing with sensitive data, we chose this last path. It required greater engineering investment, but we agreed it was imperative that we maintain a secure system while introducing biometric login for users.

In part 2, we talk implementation details, including the library we used, code snippets, and questions to consider before you get started. Interested in learning more about engineering at Alto? Follow us on LinkedIn.

While HIV and AIDS remain urgent public health issues, the prevention and treatment landscape has transformed drastically throughout the past four decades. Breakthroughs in treatment have made it possible to stop the progression of HIV and prevent transmission of the virus to others. Read on to learn more about HIV stages, symptoms, treatment, and prevention.

All About HIV: Stages, Symptoms and Treatment

More than 40 years have passed since AIDS, the disease caused by HIV, was first identified in the United States. While HIV and AIDS remain urgent public health issues, the prevention and treatment landscape has transformed drastically throughout the past four decades. Breakthroughs in treatment have made it possible to stop the progression of HIV and prevent transmission of the virus to others. Read on to learn more about HIV stages, symptoms, treatment, and prevention.

HIV (human immunodeficiency virus) is a virus that attacks your immune system, making you more vulnerable to other illnesses. It is transmitted through contact with the blood, semen, or vaginal fluids of someone who has HIV.

If untreated, HIV can lead to AIDS (acquired immunodeficiency syndrome), which is also considered the last stage of HIV. When HIV progresses into AIDS, your immune system has been significantly weakened by the virus.

Currently, there is no cure for HIV, but taking HIV medicine called antiretroviral therapy (ART) as prescribed stops the progression of the disease. As a result, most people living with HIV in the U.S. do not develop AIDS. There are also HIV prevention medications, PrEP and PEP, which are effective at preventing the transmission of HIV through sex or intravenous drug use.

As the HIV epidemic emerged in the U.S. in the 1980s and 90s, gay and bisexual men were disproportionately affected — in part because the virus transmits more easily through anal sex than vaginal sex — and subsequently stigmatized as carriers of the virus. However, the medical community soon discovered that anyone can contract HIV regardless of gender identity or sexual orientation, as the virus can be transmitted through anal sex, vaginal sex, or the sharing intravenous drug equipment such as needles or syringes.

In recent years, there has been significant progress toward reducing the annual HIV infection rate, and new cases of HIV among gay and bisexual men ages 13-24 dropped by 33% between 2015-2019. Still, gay and bisexual men accounted for 69% of all new HIV diagnoses in the U.S. in 2019. And in recent years, Black and Latinx individuals have been disproportionately affected by HIV. Racial and ethnic discrimination and disparities in healthcare access — which can discourage people from seeking HIV prevention services and testing — factor into HIV’s outsized impact on these communities.

There are three primary stages of HIV: acute HIV infection, chronic HIV infection, and stage 3 HIV, or AIDS.

Acute HIV infection, the first stage of HIV, may develop within two to four weeks of contracting the virus. During this stage of HIV, the virus multiplies rapidly and there is a high amount of HIV in your bloodstream (also known as your viral load). While the virus replicates and spreads, it destroys your CD4 cells, a type of white blood cell that plays a role in your immune system.

Some people with acute HIV infection quickly experience flu-like symptoms including fever, chills, rash, night sweats, muscle aches, sore throat, fatigue, swollen lymph nodes, and mouth ulcers. The only way to know your HIV status is by getting tested. If you have any of these symptoms and believe you may have been exposed to HIV, seek prompt medical care and take an HIV test. Find a free and confidential HIV testing site near you..

Experiencing these symptoms does not necessarily mean that you have HIV, as they overlap with symptoms of the flu and other illnesses. And some individuals with HIV develop these symptoms later, while others never develop them at all, which is why it’s critical to get tested for HIV on a regular basis — ideally every three months. You can still transmit the virus to others even if you do not have noticeable symptoms of HIV.

During the chronic HIV infection stage, the virus replicates less rapidly than it did in the acute stage, but it continues to damage your CD4 cells and weaken your immune system.

Many people experience no symptoms or mild symptoms during this latent period, which is also sometimes referred to as asymptomatic HIV infection or clinical latency. However, just like during the acute HIV infection stage, you can still transmit the virus to others even if you are not experiencing symptoms.

Without effective treatment, your viral load will increase and your CD4 cell count will decrease as this stage of HIV progresses. You are more likely to experience symptoms of HIV when your viral load is high and your CD4 cell count is low. Taking HIV medication as prescribed can help you maintain a low or even undetectable viral load and prevent your HIV from progressing into AIDS.

AIDS is the third and most advanced stage of HIV. In this stage, your immune system is severely weakened, your viral load continues to increase, and your CD4 cell count continues to decrease. 

HIV progresses into AIDS when you have a CD4 cell count of less than 200 cells per cubic milliliter or when you develop an opportunistic infection (OI), an illness that occurs more frequently in individuals with HIV because of their weakened immune systems.

Opportunistic infections experienced by individuals with HIV include kaposi’s sarcoma, a type of cancer that develops in your blood and lymph vessels; pneumocystis pneumonia (PCP), and mycobacterium avium complex (MAC), tuberculosis-related bacteria. However, OIs continue to occur less frequently as HIV treatment becomes more effective.

There are many effective HIV treatment options that can keep you healthy and help you maintain a low viral load. The primary treatment for HIV is called antiretroviral therapy (ART), a combination of medications that lower the amount of HIV in your bloodstream.

If you take your HIV medication every day as prescribed, you can maintain an undetectable viral load. This will preserve the strength of your own immune system and prevent you from transmitting the virus to others.

Starting ART as soon as possible after you receive an HIV diagnosis is critical to lowering your risk of developing AIDS and preventing you from transmitting the virus to others. If you have tested positive for HIV, reach out to your healthcare provider right away to begin treatment.

If you have tested negative for HIV, there are important HIV prevention medications that can help you continue to protect your health: PrEP and PEP.

PrEP, or pre-exposure prophylaxis, can lower risk of sexual transmission of HIV by 99% when taken daily and reduces the risk of getting HIV from intravenous drug use by about 74%. PrEP may be right for you if you have a partner who is HIV-positive or unsure of their HIV status, or if you have multiple partners. Pharmacists in a growing number of states can now prescribe PrEP.

PEP, or post-exposure prophylaxis, is a medication taken within 72 hours of potential exposure to HIV to lower your chances of contracting the virus. It can be prescribed by a healthcare provider at emergency rooms, sexual health clinics, community-based health centers, and, in some states, pharmacies. PEP is only for emergencies and accidental exposures. If you anticipate ongoing risk of exposure to HIV, speak with your doctor about potentially taking PrEP for long-term protection.

We’re here to help you navigate HIV treatment and prevention therapies

Our pharmacists have deep expertise in HIV treatment and prevention and can help you get started with antiretroviral therapy, PrEP, or PEP. We will coordinate with your doctor and your insurance provider to ensure that you’re receiving the best option for your needs at the best price. 

Reach out any time through in-app secure messaging or by phone at 1-800-874-5881.

Editor’s Note: This post was originally published in December 2021 and has been updated for accuracy and completeness.

World AIDS Day, observed on December 1st every year, is an important reminder that progress in the global fight against AIDS requires action and awareness from each individual around the world.

Take Action for World AIDS Day 2021

World AIDS Day, observed on December 1st every year since 1988, is an important reminder that progress in the global fight against AIDS requires action and awareness from each individual around the world.

AIDS (acquired immunodeficiency syndrome) was heavily stigmatized from the beginning of the epidemic in the 1980s. Four years passed between the first cases of AIDS in the U.S. in 1981 and the Reagan administration’s first public mention of the disease. There were many misconceptions about how HIV (human immunodeficiency virus) — the virus that causes AIDS — can be transmitted and who is at risk of contracting it.

The stigma and lack of information about transmission and prevention led to many preventable cases of HIV/AIDS in the U.S. At the peak of the epidemic in 1995, complications from the disease were the leading cause of death for adults ages 25-44, and to date, more than 700,000 people in the U.S. have died from an HIV-related illness.

The HIV and AIDS landscape looks dramatically different today than it did back when World AIDS Day was first established. With greater awareness of HIV and AIDS, and more government funding of research, new HIV infections in the U.S. decreased by 73% between 1984 and 2019. Still, the fight to end AIDS isn’t over, with more than 1.2 million people living with HIV in the U.S.

In honor of World AIDS Day 2021, take a look at what has already been accomplished in the fight against AIDS and learn about what is needed next.

There were 34,800 new HIV infections in 2019

13% of those living with HIV don’t know it

57% of those living with HIV are virally suppressed (meaning they are not at risk of transmitting the virus to others)

Milestones in the history of HIV and AIDS

AIDS first emerged in the U.S. in 1981, but researchers did not learn that HIV caused AIDS until three years later in 1984. The history of HIV medication dates back to 1986, when clinical trials for azidothymidineor (AZT), the first antiretroviral HIV/AIDS medication, began. AZT was approved to treat HIV a year later.

Highly active antiretroviral therapy, often referred to as antiretroviral therapy (ART), became the frontline treatment for HIV in 1997. ART is a combination of medications that lower your viral load, which is the amount of HIV in your bloodstream. When taken every day as prescribed, these medications can help individuals with HIV maintain an undetectable viral load, virtually eliminating their risk of transmitting the virus to others.

The U.S. Food and Drug Administration (FDA) first approved a PrEP medication in 2012. PrEP, or pre-exposure prophylaxis, can lower the risk of sexual transmission of HIV by 99% when taken daily and reduces the risk of getting HIV from intravenous drug use by about 74%.

With these breakthroughs in HIV treatment and prevention therapies, the U.S. government recently announced a goal to reduce the number of new HIV infections by 75% by 2025 and at least 90% by 2030, preventing an estimated 250,000 additional cases of HIV.

Next steps in the fight against HIV and AIDS

Despite the progress that has been made in the fight against HIV and AIDS, prevention, care, and treatment remain inaccessible for many individuals at risk of contracting HIV — both in the U.S. and around the world. The theme for World AIDS Day 2021 is Ending the HIV Epidemic: Equitable Access, Everyone’s Voice, in recognition of how health inequities contribute to the epidemic.

In the U.S., racial discrimination and deeper inequities in healthcare have contributed to HIV’s disproportionate impact upon people of color. Black and Latinx individuals — particularly gay and bisexual men — are among the groups disproportionately affected by HIV. A variety of factors contribute to these disparities, including income inequality, unequal access to healthcare, and lower use of HIV prevention and treatment services. According to 2016 CDC data, white individuals accounted for 69% of PrEP use, while Latinx and Black individuals accounted for 13% and 11%, respectively.

Fortunately, HIV prevention medication continues to become more accessible, with generic medication options and expanded health insurance coverage of PrEP. And legislation in a handful of states, including California and Colorado, allows pharmacists to prescribe PrEP. There are also a number of organizations working hard to make HIV services more accessible to communities of color, like NMAC and Black AIDS Institute.

Getting an HIV test is one of the most important things you can do for World AIDS Day. Not only will learning your HIV status give you the information you need to take control of your health, it will also help combat the stigma surrounding HIV and AIDS. Each person who makes use of testing and prevention services — and each person who speaks openly about HIV and AIDS, without perpetuating fear or stigma — brings us closer to a future without AIDS.

Search for a free and confidential HIV testing site near you.

View the CDC’s HIV stigma language guide to learn the power of the words you use when discussing HIV and AIDS.

Get support navigating HIV treatment and prevention medication

At Alto, we’re committed to doing our part to make HIV treatment and prevention services as accessible as possible. Our extensive library of HIV-focused content covers the information you need to make informed decisions about your health. And if you take PrEP or ART, our team will coordinate with your doctor’s office and your insurance provider to ensure that you’re receiving the best medication option for your health needs at the lowest price.

To learn more, reach out any time through in-app secure messaging or by phone at 1-800-874-5881.

Editor’s Note: This post was originally published in November 2021 and has been updated for accuracy and completeness.

How to Take Action for World AIDS Day 2021

Blog

Tackling Technical Debt and Improving Security: How Alto Untangled an Overloaded User Model

What To Know About Insulin Pens

Emphysema: Causes, Symptoms and Treatments

Considerations and Approaches for Implementing Biometric Login: Part 1

All About HIV: Stages, Symptoms and Treatment

How to Take Action for World AIDS Day 2021

How to Keep Your Heart Healthy During the Holidays

Celebrating National ERG Day at Alto

How Alto Reduced Time to Resolution for Production Incidents

A Financial Planning Guide for Egg Freezing

Meet Ramiah Martin, VP, Operations & Supply Chain

How to Prepare for Cold and Flu Season

Switch to a better pharmacy.