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

Alto’s launch in the Long Island market extends our industry-leading patient care model to even more of the New York metro area.

Hello, Long Island!

Alto’s launch in Long Island, New York, extends our industry-leading patient care model to even more New York-area residents.

With the addition of our latest pharmacy location in Plainview, Long Island, even more residents of the greater New York City metro area can now choose Alto’s same-day doorstep delivery for all of their pharmacy needs. Alto Long Island opens its doors today, Tuesday, April 5, 2022.

At Alto, we believe it’s our job to ensure you have your medications at the best price, on time and with the support you need. We bring the pharmacy to you - no more waiting in line, making an extra trip, or finding out your prescription isn’t ready to be picked up after you’ve already arrived. Our free doorstep delivery means your medications come directly to you on the day and time you select, and most medications are available the same-day. Stay up to date on your courier’s progress with text alerts and in our mobile app. 

Starting a new medication or doing an injection for the first time? Message a pharmacist with your questions, even in the evenings and on weekends. And we’re a full service pharmacy - we stock all major brand, generic, over-the-counter and specialty medications, meaning your entire family’s pharmacy needs can be managed in the Alto app and coordinated into one delivery.

Courier delivery windows
Monday - Friday: 

12:30 – 3:30 pm ET (1:30 – 4:30 pm ET for outlying areas)*

6:00 – 9:00 pm ET (7:00 – 10:00 pm ET for outlying areas)

2:00 –5:00 pm ET (3:00 – 6:00 pm ET for outlying areas)

Need to pick up? Our new Long Island pharmacy is located at 100 Manetto Hill Road, Suite 104, in Plainview.

Monday - Friday: 9:00 am – 7:00 pm ET
Saturday - Sunday: 8:00 am – 4:30 pm ET

New York residents interested in using Alto’s services for their medication needs can ask their doctor’s office to send all prescriptions to Alto Pharmacy (via ePrescribe or phone). Have existing prescriptions at another pharmacy? Start a transfer online or give us a call at 1 (800) 874-5881, and we’ll handle the switch. 

General customer support hours are Monday - Friday 9 am - 12 midnight ET and Saturday - Sunday 10 am - 9 pm ET. Patients can reach out to Alto via phone at 1 (800) 874-5881 or app.

*Weekday afternoon delivery is only available to residents of New York City's five boroughs at this time.

Founded in 2015, Alto is a patient-centric digital pharmacy based committed to the health and wellbeing of you and your family. We provide free same-day delivery to your door seven days a week for prescriptions, but, more importantly, offer cost transparency, personalized in-app and phone support, and real-time coordination with doctors and insurance companies to get you the care that you need. Alto is headquartered in San Francisco with offices in Denver and Dallas, and currently delivers across the greater Bay Area, Los Angeles, Orange County, San Diego, Seattle, Denver, Las Vegas, New York City, Houston, Dallas and Austin.

Vaccines — which were first developed in 1796 for smallpox and continue to evolve with new research and technology — build on your immune system’s natural function to protect you from serious diseases. Just like white blood cells and the other components of your immune system, vaccines help you develop immunity, but without the initial illness and risk of health complications. Here’s a look at how vaccines work.

The Science Behind Vaccines

Your immune system has a natural way of defending you from the viruses and bacteria that cause illness. As these germs multiply rapidly and infect your body, an army of white blood cells fights back, producing antibodies that attack the invaders.

The first time you are infected by a specific virus or bacteria, your immune system often cannot destroy the germ quickly enough to prevent you from becoming sick. After you’ve recovered, certain immune cells hold onto the memory of the infection. This allows them to mobilize quickly if they encounter the same germ again, preventing illness in the future. Immunity, your body’s resistance to certain types of infection, is the outcome of this process.

To understand how vaccines work, it’s helpful to know how your immune system naturally fights an infection. B-lymphocyte white blood cells produce blood proteins called antibodies, which attack antigens — the part of the invading germ that triggers an immune response. T-lymphocyte white blood cells attack already infected cells in the body. After the infection has ended, a few T-lymphocytes, or memory cells, remain to ensure a fast immune response should the same germ reappear.

Vaccines imitate infections, triggering the process of building immunity to a specific disease without causing illness. Your immune system responds to these imitation infections the same way it would to an actual infection. Detecting antigens from the vaccine, your immune system produces antibodies and T-lymphocyte cells. The imitation infection leaves your body with T-lymphocyte memory cells and B-lymphocytes, which will know how to quickly fight that antigen in the future. This prevents you from becoming sick if you are exposed to the virus or bacteria that cause the disease.

It typically takes several weeks for your body to produce T-lymphocyte and B-lymphocyte cells in response to a vaccine, which is why in most cases you will not immediately develop immunity. This means that you could become infected with a disease and develop symptoms shortly after vaccination, so it’s important to take necessary precautions until you become fully immune to the virus or bacteria. The healthcare professional administering your vaccine will inform you of the anticipated timeline for immunity.

Sometimes the imitation infection created by a vaccine causes mild symptoms such as a fever. These side effects are normal and indicate that your body is building immunity.

While all vaccines arrive at the end result of immunity, there are several paths for getting there. When deciding which type of vaccine to create for a disease, researchers consider a variety of factors, including the immune system’s response to the germ that causes the disease, the population likely to receive the vaccine, and the regions of the world where it will be used. These are the seven types of vaccines commonly used in the U.S.

Live vaccines use a weakened version of the living virus or bacteria that causes a disease. They are most similar to the natural infection and produce long-lasting immunity. The weakened form of the germ does not lead to serious disease, like that caused by the wild form of the germ, for most individuals with strong immune systems. However, live vaccines aren’t safe for those who are immunocompromised, including children undergoing cancer treatment. Examples of live vaccines include the measles, mumps, and rubella (MMR) vaccine and the chickenpox vaccine.

Inactivated vaccines are produced by inactivating, or killing, the germ that causes a disease. Examples include the polio, hepatitis A, and flu vaccines. They don’t provide as strong of immunity as live vaccines, so additional doses, also referred to as booster shots, are often needed for ongoing protection.

Toxoid vaccines target a toxin, a harmful substance produced by a germ, rather than the entire germ itself. They contain a weakened version of the toxin to be targeted called a toxoid, which teaches your immune system how to fight off the natural toxin. Similar to the germs used in live vaccines, toxoids are weakened to a point where they do not cause illness. These vaccines are used to prevent diseases caused by toxin-producing bacteria such as diphtheria and tetanus.

Subunit vaccines use portions of a virus or bacteria called subunits rather than the entire germ. Vaccines for diphtheria, tetanus, and pertussis, or whooping cough, are combined into the DTaP vaccine. The pertussis component is a subunit vaccine.

Conjugate vaccines fight a specific type of bacteria whose antigens are more difficult for a child’s immune system to detect due to their outer coating. The vaccines link the coating to stronger antigens that the immune system can more easily respond to. Like subunit vaccines, these vaccines are more targeted and only use part of the germ. Examples of conjugate vaccines include the haemophilus influenzae type B (Hib) vaccine.

Viral vector vaccines produce immunity to a virus by using a modified version of a different virus to deliver instructions to your immune cells. The modified version of the other virus is referred to as a vector virus. Recent Ebola vaccines have used this technology, and the Johnson & Johnson COVID-19 vaccine is also a viral vector vaccine.

mRNA vaccines help your body produce a protein that triggers an immune response and the development of antibodies. This technology was used to create the Pfizer-BioNTech and Moderna COVID-19 vaccines.

Read ‘What the COVID-19 Vaccine Means for Those With HIV’

All vaccines in the United States require approval by the Food and Drug Administration (FDA) and are held to rigorous safety and effectiveness standards. The vaccine approval process starts with lab tests, which may take years in some cases. The FDA analyzes the results to determine if the vaccine should be tested with people. If the vaccine moves forward, the next step is clinical trials where the vaccine is tested on volunteers.

Clinical trials typically begin with a smaller group of 20 to 100 volunteers before including thousands more. The trials gather information about vaccine safety, the typical immune response, and dosing. If any safety concerns emerge during this stage, the FDA must address them before it can authorize the vaccine.

Vaccine manufacturers are required to continuously monitor vaccine safety after approval and test every batch produced to ensure effectiveness, quality, and purity. These test results are reviewed by the FDA, which also conducts an inspection of the factory where the vaccine was produced. If you experience severe side effects after vaccination, contact your healthcare provider so that they can report potential concerns to the Centers for Disease Control and Prevention (CDC)’s vaccine monitoring database.

COVID-19 mRNA vaccines were developed and approved more quickly than a typical vaccine given the urgent nature of the pandemic. This expedited timeline was made possible by significant investment from governments and companies in the vaccine development process and decades of research on mRNA vaccine technology. These vaccines were as thoroughly vetted for quality and safety as any other vaccine.

Many vaccines are received during childhood, like the polio, chickenpox, and MMR vaccines, but there are others you may need as an adult. The CDC recommends the zoster vaccine, which prevents shingles, for adults ages 50 and older and the pneumonia vaccine for those over 65. Other vaccines may be recommended based on additional factors including job or school requirements, travel, and health conditions. Check in with your doctor about which vaccines you need.

The CDC also recommends an annual flu vaccine for everyone 6 months and older. New versions of flu vaccines are developed annually in anticipation of circulating flu virus strains, so health experts recommend getting one every year to prepare for cold and flu season. It’s especially important to be proactive about flu vaccination if you are over the age of 65 or have a chronic condition such as COPD or diabetes.

For detailed vaccine recommendations by age group, reference the CDC’s recommended immunization schedules for children and adolescents and adults.

At Alto, a pharmacist is your partner in health. If you take medication, we will work with your doctor, your insurance (if applicable), and any third party savings programs that you may qualify for to make your medications as affordable as possible. And our team of pharmacists is available to chat whenever questions come up. 

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.

To automate a manual, error-prone pharmacy workflow, we turned to event streaming. Here’s what we learned from one of the first Kafka use cases at Alto.

How We Used Kafka to Build an Event-Driven Automation Pipeline and Scale Our Pharmacy

Imagine this: You're at the doctor’s office, and your doctor just wrote you a new prescription. Minutes later, before you even check out with the receptionist, you already have a notification from Alto Pharmacy on your phone that your prescription is ready. All you have to do is pick the date and time that works best for your free courier delivery.

This is the future we’re building at Alto: a future where a prescription can be transcribed, billed, and verified by a pharmacist in five minutes, flat. To get there without dramatically increasing Alto’s head count, we need to automate much of the process, starting with the first step: transcribing, or intaking, a prescription.

As a pharmacy, we receive prescriptions in many different forms. Some are sent electronically, in a structured format, but others are handwritten, phoned in, or even faxed. To represent all of these forms in a single table, we previously required every incoming prescription to be transcribed by an Alto team member, who would answer questions like:

Whom is this prescription for? Is this customer already in our system?

Where did this prescription come from? Who wrote it?

What is the relevant prescription information (medication to dispense, quantity, days supply, directions, etc.)?

This manual process is both time-consuming and prone to human error, which, if uncaught, could impact our ability to process the prescription downstream. Furthermore, at our busiest times, it could take up to two hours for a team member to get through the pending intake queue — unacceptable if we hope to have prescriptions ready to schedule before people even leave their doctor’s office. 

Automating intake required close collaboration between three teams:

Data Science, who built the decision-making algorithms 

Data Engineering, who served up the results of those algorithms

Product Engineering, who used those results to automatically intake prescriptions 

To allow the teams to operate in parallel without toe-stepping — and in the language most suitable for each (the Data Science and Data teams prefer Python, while product engineers work mainly in Ruby) — we separated the code into two environments: 

1. Data Prod Interface (DPI), where the code for generating automation results lives

2. Wunderbar (our proprietary pharmacy operations platform), where the code for requesting and using those automation results lives

The key question: to establish robust communication between these two environments, should we use an API-based approach, or an event-driven one? Each has its pros and cons. 

Legacy approach everyone at Alto is familiar with

Existing enforcement of strong types and data

Difficult to scale with increased data & requests

Requires ongoing authorization / authentication

Infrastructure relevant to other business areas

Automatic retries, reprocessing, and queueing

Our existing infrastructure currently utilizes a hefty API-based structure, so there was a natural tendency to go down this path, but we knew that beginning to migrate services towards an event-based architecture with Kafka at its heart would help us in the long term.

Kafka is a framework implementation developed by LinkedIn, now open-source with the Apache Software Foundation. It aims to provide a unified, high-throughput, and low-latency platform for handling real-time data feeds. 

Alto uses Amazon Web Services as our cloud provider, and luckily, they offer an out-of-the-box managed solution for Kafka, MSK. To configure Kafka with our system, our infrastructure team worked with AWS to set up managed instances to comply with our business requirements. Our Infrastructure team will share more details about this work in an upcoming blog post. 

Kafka offers many benefits. The asynchronous nature of the message system allows for retries, reprocessing, and queueing as well as easy recovery from outages. In addition, the infrastructure work done for setting up the managed cluster would be a one-off workstream. When complete, we’d be able to re-use the same setup and configurations across various business needs to streamline other projects that leverage Kafka. 

Setting up for success: defining a strict contract

One element we had to get right from the start was the data contract. As we send messages between DPI and Wunderbar, we need to ensure messages are produced with the correct schema, so that downstream consumers know what to expect.

Protocol Buffers, or Protos, is an open-source, cross-platform data format used to serialize structured data. Developed by Google, Protos allow you to define how you structure your data once and then use generated code to easily write and read the structured data in a variety of different languages. 

At Alto, we’ve been using Protos for the past few years to speed up development with auto-generated code and ensure data continuity between our Ruby on Rails backend and JavaScript / React / React Native frontend. Protos may seem antithetical to JavaScript and Ruby since they’re both dynamically typed languages, but in practice, they have saved us countless hours of debugging and back-and-forth Slack messages. 

For this project, we turned again to Protos to define the schema for messages produced by DPI and Wunderbar. We defined IntakeAutomationRequest and IntakeAutomationResult messages in Go and generated the types (Sorbet, Flow, etc.), which both DPI and Wunderbar now refer to when producing or consuming messages.

Because Wunderbar is already configured to run on AWS and houses our existing intake logic, it was easy enough to send a prescription to DPI for automation. Where we would normally create a task for an operations team member to manually transcribe the prescription, we instead produce a message to our “request automation” Kafka topic using the ruby-kafka library.

Our consumer, instantiated in an executable that runs on a dedicated worker, consumes messages from a “receive automation” Kafka topic. First, the consumer verifies that a given message corresponds to a prescription we previously sent to DPI. Then, it persists any automation results included in that message. If the automation results are sufficient, we skip intake altogether. Otherwise, we create an intake task to be handled by an operations team member.

Because this project was among our early use cases for Kafka, we wanted to be prepared for the worst-case scenario: we produce a message requesting automation results, and for whatever reason—maybe DPI is down—we don’t hear back. For us, we defined a reasonable time frame as fifteen minutes, in order to avoid building up a large backlog of work that would have to be offloaded back onto our operations team.
To this end, we store metadata about the automation lifecycle in an intake_automation_results table, which includes timestamps representing when we sent a message to DPI and when we received a response back. A cron job runs every minute to check that table for rows where received_at is blank, and sent_at was more than fifteen minutes ago. If this occurs, we flag the prescription to be manually intaken by an operations team member.

The diagram below illustrates our intake automation architecture.

Intake automation is now live at Alto. We’re seeing prescriptions fly through in just a few minutes — during which time our automation creates a user profile if one doesn’t already exist, links the new prescription to that profile, and finds and bills the user’s insurance; a pharmacist reviews the prescription for clinical accuracy; and the user receives a text message to schedule their delivery. This single flow, prior to intake automation, once took up to four hours to complete!

Going from zero to one is quite a feat, and it wouldn’t have been possible without an event-based approach. Now that intake automation has laid the groundwork, we know that Kafka will only continue to provide exponential value to Alto as we grow and migrate more of our services to this event-based architecture. 

Interested in learning more about engineering at Alto? Follow us on LinkedIn.

Residents of the Austin metro area can now choose Alto’s same-day doorstep delivery for their pharmacy needs. 

Hello Austin

Alto's new Austin-based pharmacy marks our third location in Texas.

Starting today, December 7th, residents of the Austin metro area can now choose Alto’s same-day doorstep delivery for their pharmacy needs. 

At Alto, we believe it’s our job to ensure you have your medications at the best price, on time and with the support you need. We bring pharmacy to you - no more waiting in line, making an extra trip, or finding out your prescription isn’t ready to be picked up after you’ve already arrived. Our free doorstep delivery means your medications come directly to you on the day and time you select, and most medications are available the same-day. Stay up to date on your courier’s progress with text alerts or in our mobile app. 

Courier delivery windows
Monday - Friday: 6 - 9 pm CT (7 - 10 pm CT for outlying areas)
Saturday - Sunday: 2 - 5 pm CT (3 - 6 pm CT for outlying areas)

Walk-in hours
Monday - Friday: 9 am – 7 pm CT
Saturday - Sunday: 8 am - 4:30 pm CT

Austin residents interested in using Alto’s services for their medication needs can ask their doctor’s office to send all prescriptions to Alto Pharmacy (via ePrescribe, phone or fax).

Have existing prescriptions at another pharmacy? Start a transfer online or give us a call at 1 (800) 874-5881, and we’ll handle the switch.

Need to pick up? Our pharmacy is located at 4175 Freidrich Lane, Suite 202.

General customer support hours are Monday - Friday 8 am - 11 pm CT and Saturday - Sunday 9 am - 8 pm CT. Patients can reach out to Alto via phone at 1 (800) 874-5881 or in the Alto app.

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

When engineering incidents happen, typical deployment pipelines are just too slow—especially if customers’ medications are on the line. Here’s the speedier rollback process we use at Alto Pharmacy to ship fixes in 3 minutes, flat.

How Alto Reduced Time to Resolution for Production Incidents

Production incidents caused by newly-merged code happen to us all. When they do, most engineering organizations discuss the root cause and how to prevent similar incidents in the future. At Alto, we evaluate two additional metrics:

Time to detection: How quickly did we know something was wrong?

Time to resolution: How quickly did we restore service?

Time to resolution is especially critical for us as a pharmacy, where a long-running incident could block a user from getting their medication on time.

Over 30 times a day, an engineer at Alto hits the merge button, deploying a new build to production. Our well-automated CI/CD pipeline, built by our Infrastructure team, handles the 3-step deployment process:

1. Build: install Ruby & JavaScript dependencies

The average runtime for our standard deployment pipeline is 30 minutes—reasonable for a CI/CD pipeline, but too long when shipping a fix for a production incident.

We introduced a “hotfix” workflow as a first pass at an expedited deployment pipeline for incident response. A hotfix is a commit that introduces new code to address the incident by either removing or reverting the buggy code that introduced the issue in the first place or by shipping new code that fixes the initial issue. 

The hotfix deployment pipeline reduces incident time to resolution by triggering a specific CI job that removes the test step from our standard pipeline, reducing the workflow to just the Build and Deploy steps.

Implementing a hotfix pipeline on top of our standard pipeline in CircleCI was relatively simple—in our `.circleci/config.yml`, any part of our CI workflow that should be skipped in case of a hotfix runs a job called “early_exit_if_hotfix” that will skip the current step if the last commit message of the code being built includes the keyword “[hotfix]”.

early_exit_if_hotfix:
    steps:
      - run:
          name: Early exit if hotfix
          command: |
            git_commit_message=$(git log --format=%B -n 1)
            if [[ $git_commit_message =~ "Merge pull request #" ]]; then
              echo "This is a merge commit. Checking if this is a hotfix deploy"
              git_commit_sha=$(git log --format=%H -n 1)
              git_commit_message=$(git log --format=%B $git_commit_sha^-)
            fi
            if [[ $git_commit_message =~ "[hotfix]" ]]; then
              echo "exiting early for hotfix deploy"
              circleci-agent step halt
            fi
            echo "not a hotfix deploy, continuing"

run_ruby_tests:
  steps:
early_exit_if_hotfix
run_tests

The hotfix workflow reduces time to ship a resolution, once we identify the fix, from 30 minutes to ~18 minutes. It’s faster than our standard pipeline but still requires considerable hands-on work from the engineer performing the hotfix.

To further speed up deployment and reduce manual work, we introduced a workflow that simply rolls back to a previously-built healthy deployment image. In this workflow, the entire pipeline is reduced to just the Deploy step.

To invoke a rollback, an engineer commits a message with the keyword “[rollback]”, followed by the SHA of the commit to rollback to. Similar to the hotfix approach, any build step that should be skipped during a rollback checks the commit message for the “[rollback]” keyword before running:

early_exit_if_rollback:
    steps:
      - run:
          name: Early exit if rollback
          command: |
            git_commit_message=$(git log --format=%B -n 1)
            if [[ $git_commit_message =~ "Merge pull request #" ]]; then
              echo "This is a merge commit. Checking for rollback sha..."
              git_commit_sha=$(git log --format=%H -n 1)
              git_commit_message=$(git log --format=%B $git_commit_sha^-)
            fi
            if [[ $git_commit_message =~ "[rollback]" ]]; then
              echo "exiting early for rollback deploy"
              circleci-agent step halt
            fi
            echo "not a rollback deploy, continuing"

run_ruby_tests:
  steps:
early_exit_if_hotfix
early_exit_if_rollback
run_tests

The rollback workflow looks for a build matching the specified SHA and posts a confirmation message for the engineer, then deploys that build to production. The rollback approach dropped our time to resolution even further, from 30 minutes to ~3 minutes.

There are three edge cases that we’ve also baked into our rollback workflow: potentially stale images, database migrations, and blocking new merges and deployments.

Our script has a special block warning the engineer if a target image is older than an hour. The older the image, the riskier the rollback, as the delta between the image and the latest commit on main is larger.

time_rollback=$(git show -s --format=%ct ${rollback_revision})
time_now=$(date '+%s')
if [ $(($time_now - $time_rollback)) -gt 3600 ]; then
    message="${message}\n\n:warning:The rollback commit is more than an hour old."
    message="${message}\nThe [hotfix workflow](https://www.notion.so/alto/Deploying-a-Hotfix-Rolling-Forward-bb8e9cea05b44c67a64e23ae652653b6) might be a better candidate for this deployment."
fi

We also want to warn engineers if any database migrations have occurred between the current image and the target by checking the diff of the db/migrate directory. Rolling back application code without applying changes to the database can result in the database and application code becoming out of sync, resulting in further problems. Our script will warn engineers if a migration has been detected between the current and target image and provide instructions on how to rollback migrations if required.

Because a rollback deploys an image that’s older than our latest build, we also need to block continuous deployment until we’ve restored the main branch to a safe state — typically by deploying a hotfix as soon as we can identify an appropriate fix. We accomplish this using a Github issue with a specific tag that, when open, triggers a job causing any active CI job to fail. After the incident is resolved, the incident manager closes the issue, which will retrigger the blocked jobs and resume the normal build and deploy workflow.

The expedited rollback process has reduced our overall time to ship a resolution for incidents down to a speedy 3 minutes—a valuable improvement for our internal operations users, as well as for our customers and healthcare providers who rely on Alto’s service to get prescriptions filled. Branching these incident response workflows off of our existing standard deploy pipeline keeps the maintenance cost low for our infrastructure team, and robust automation reduces the risk of manual error for our product engineers when they need to invoke these workflows.

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

October 11 marks National Coming Out Day, an opportunity to celebrate all those who have come out as LGBTQ+ and recognize the courage they’ve demonstrated by choosing to be their authentic selves.

Celebrating National Coming Out Day at Alto

October 11 marks National Coming Out Day, an opportunity to celebrate all those who have come out as LGBTQ+ and recognize the courage they’ve demonstrated by choosing to be their authentic selves. In honor of this annual celebration, we sat down with two Alto team members — Ben Romero (he/they), Business Operations Manager for Health Plans and Travis White (he/him), Senior Software Engineer — who generously shared their experiences of coming out as bisexual/queer. Here are their stories, in their own words.

Ben: Like a lot of folks, I avoided coming out for most of my life. I grew up knowing that I wasn’t exactly straight and later recognized that I’m bisexual. I remember my entire experience around my sexuality being wrapped in shame. I would reluctantly conform to heteronormativity just to avoid the fear of being outed or questioned. It wasn't until college that I first felt like I could open myself up to the experience and validation that I deserved. By the time I graduated from college, I had a refreshed sense of my place in the world, but I was still hiding my sexuality from my family.

Five years after college, I was finally ready to be open with my family about being bisexual, and it was the first time I felt as if I had to “come out.” At the time I was engaged to my non-binary/queer partner. My family knew my partner as a woman, but my partner was also beginning to validate their nonbinary gender experience. All I could think about was how much of a disservice it would be to our identities as a queer couple if we started our marriage having to assume more invalidating heteronormative assumptions. I first told my closest family members — my younger brother and parents — who supported me unconditionally and showed me so much love. Not every family member was as accepting of my sexuality, which was really disappointing, but I had more than enough support from my chosen family to finally overcome the fear that I had held on to for so long. 

Travis: I realized I wasn’t completely straight at some point in high school. Growing up Catholic, I was always taught that men are attracted to women and that being gay was a sin. So when I found myself attracted to both girls and guys during high school, I wondered what was wrong with me. I brushed it off and ignored that aspect of my sexuality for a long time, which I would later come to regret since it definitely fed into ongoing anxiety and depression in college.

I first came out to my closest friends during my junior year of college. By that point, I had fully accepted that I wasn’t straight, but I had never acted on my bisexuality. I had only dated girls, so my friends saw me as completely straight. I couldn’t quite figure out how to tell them, and it ended up happening organically while hanging out on a Friday night. We were playing a game around the table that required everyone to share something no one else knew about them. Something came over me and I decided to throw caution to the wind with a, “by the way… I’m bi.”  

I came out to my parents several years later when I was working my first engineering job out of college, living in Silicon Valley and loving life. I knew that if they chose not to accept me, it was going to be their loss. After a night out (and an amazing prime rib dinner) when they were in town, I told them that there was something I wanted to tell them about myself - that I am bisexual. My dad’s first response was, “What does that mean?” I informed them that it means I am attracted to both men and women, though more recently, I’ve come to think of myself as being attracted to interesting people regardless of the gender they identify as. My parents were very supportive, but truthfully I had reached a point where I could be accepting of the worst-case scenario. 

Ben: I was most grateful for the sense of relief I experienced. Despite facing criticism and homophobia from some of my siblings after coming out, I couldn’t shake the sense of pride I felt from allowing myself to be unapologetically queer and visible. I’m finally allowing this part of me to flourish and grow. It’s liberating to be radically honest with yourself and others, regardless of what anyone else may think. I’ve now come to identify with the term queer in addition to bisexual. Part of the growth I’ve experienced involves unlearning so much of what I’ve been socialized to believe about the gender binary, and I’m just now starting to understand where I exist outside of it.  

Travis: When I came out to my friends during college, we stayed up talking until very late into the night. I left feeling a huge weight lifted off of my shoulders — and so full of love and support from some of the people I was closest to.

And later when I came out to my parents, they accepted me with open loving arms, for which I’m grateful, but I was also prepared to move forward with my life even if they did not accept me as my true authentic self.

What resources, support groups, or communities did you rely on when coming out? 

Ben: The isolation of being in the closet can sometimes lead to stories or expectations of yourself that aren’t necessarily helpful, or true. For me, as a bisexual, some of those expectations sounded like “I’m not queer enough,” “I don’t fit into the queer community,” or “people won’t believe I’m bi/queer.” I looked to my queer friends and even to LGBTQ+ advocates on social media and was relieved to find that they had many of the same fears about coming out as I did. I found that learning from other people’s experiences could help validate my own feelings, even if we had a different orientation or gender. As a queer Latinx, I also sought validation from people who shared similar intersections around my identity, which helped me navigate the concerns I had about coming out to my family.

Travis: My friends were very supportive so I was really able to lean on them. It was also helpful to just search online for other people’s coming out stories. Before I could tell my family, I knew I had to reach a point where I would be secure in my identity regardless of the outcome of that conversation. Part of the reason it’s so important to share coming out stories is because hearing other people’s experiences helps inspire you to do the same.

What advice would you give to others considering coming out? 

Ben: Above all, put your safety first. Try your best to not take on the burden of guilt for not being your authentic self — that is not a reflection of you, but a reflection of how our environment can fail to provide the validation we deserve. Take your time and build your comfort with folks who will validate your experience. There’s a whole community of people who will back you up and care for you if someone you come out to is hurtful or invalidating. 

Travis: Do it if, and when, you’re ready. You can never control how others will react, so just accept that other people’s responses have nothing to do with you. It took me years to reach that point with my family. It can be incredibly tough, and you can never know in advance how anyone will respond, but if they cannot accept you for your true authentic self, there are plenty others out there who will.

Do you have any suggestions for allies? 

Ben: I would stress the importance of familiarizing yourself with queer history and how our struggle for acceptence has evolved over the years. The LGBTQ+ community and allies have so much to be proud of today, like the repeal of “Don’t ask, don’t tell” (a former U.S. policy that directed military applicants to not disclose their sexual orientation), the legalization of gay marriage, and more queer representation on our screens — just to name a few.

At the same time, while all of those are certainly celebratory milestones, I ask that allies also recognize that our pride comes from so much more than a handful of legislative victories over the last decade. Our pride comes from the queer folks who came before us and fought for our visibility by rallying voices to speak out against injustice. Allies can research events such as the Compton’s Cafeteria riot, the Stonewall uprising, or the works of the Combahee River Collective. Understanding this historical context is important for also understanding the intersectional nature of the LGBTQ+ struggle for acceptance and restorative justice. Even though we have much to celebrate, our struggle continues as we fight for those who are still excluded or marginalized. 

Travis: Listen. The number one thing you can do is to listen and accept what someone in the LGBTQ+ community is telling you as their truth. It may change in the future — and that’s okay! Sexuality and gender are not a binary, and both can be incredibly fluid.

For parents: how you discuss sexual orientations and gender identities at home can leave a lasting impact on your children. I remember asking my mother about her thoughts on gay marriage, and she shared a more traditional view of marriage as a union between a man and a woman. That stuck with me for a long time and is a key reason I waited so long to tell them who I truly am. Read your toddler a book about a gay couple that gets married, teach your teens about prominent members of the LGBTQ+ community (and why they’re important), and if your LGBTQ+ child asks you to drive them to gay prom, treat the scenario as completely normal — because it is.

Why is it important for you to work at a company that values diversity in all forms? 

Ben: For me it’s a requirement that a company I work for prioritizes diversity and inclusion. I appreciate that Alto provides visibility into the progress that we’ve made towards building a diverse team that reflects the diversity of the patients we build solutions for. We also hold space to identify the work that still needs to be done. It’s really validating to have your background recognized at company celebrations and events or in spaces like employee resource groups (ERGs)*. It’s also important that we do all we can in our everyday actions to foster a collaborative and inclusive environment — one where people feel comfortable enough to be their authentic selves and not like they have to mask their gender, race, neurodivergence, or any other part of their identity. 

Travis: The U.S. — and the world — is made up of so many different people. There’s diversity of thought and beliefs, educational experiences, socioeconomic status, gender, race, A homogenous company that doesn’t mirror that diversity  will never be able to serve the entire population, and will miss out on a lot of opportunities. Alto’s mission is to fulfill medicine's true purpose — to improve quality of life — for everyone who needs it. The key word to me is everyone, and to truly fulfill the promise of that mission, we need a company as diverse as our customers. I personally find it rewarding to work at a company that values diversity and has strong representation of many identities, because that’s how the best ideas come to fruition and ultimately how the most positive impact is achieved.

At Alto, we believe in a world where every perspective matters. Diversity fosters creativity and creates innovation, and we welcome candidates of all backgrounds, skill sets, and experiences. To learn more, read Why We Prioritize Diversity at Alto. 

For more information on how to make your workplace safe and equitable for LGBTQ+ team members, read 11 Simple Ways You (Yes, You!) Can Make Your Workplace More LGBTQ Inclusive. 

If you or someone you know is considering coming out, we encourage you to review these resources:

Parents, Families, and Friends of Lesbians and Gays (PFLAG) Recommended Reading: Coming Out

*ERGs are meant to empower community groups within an organization by directly linking decision makers and implementing policies that support the group’s specific needs. The groups often center around a shared identity or experience and focus on building community, providing support, and contributing to its members’ personal and professional well-being. By creating an open forum for employees to come together, discuss challenges and opportunities, and foster a sense of belonging, ERGs help both individuals and organizations thrive.

There are 1.6 million Americans living with type 1 diabetes, including about 200,000 young people under 20 and 1.4 million adults aged 20 years old and older. Here is a high-level guide to living with type 1 diabetes at any age.

How to Live with Type 1 Diabetes at Any Age

There are 1.6 million Americans living with type 1 diabetes, including about 200,000 young people under 20 and 1.4 million adults aged 20 years old and older. While type 1 diabetes is typically diagnosed during childhood or adolescence (it was once referred to as juvenile diabetes), a diagnosis can come at any age 

Living with type 1 diabetes is a lifelong journey, and insulin therapy and blood glucose monitoring will remain constant. Some aspects of diabetes management, though, apply only to certain age groups, like coordinating with school staff about a child’s type 1 diabetes care plan or prioritizing heart disease prevention as you get older (more about that later).

Below, we’ve highlighted  things to be mindful of with type 1 diabetes treatment for various age groups. This is intended to be a high-level guide to living with type 1 diabetes at any age, and your diabetes care team (or your child’s) will help you develop an individualized treatment plan with recommendations for insulin dosage, blood sugar targets, and blood sugar monitoring frequency.

Type 1 diabetes and children: blood sugar monitoring at school

Individuals with type 1 diabetes are unable to produce any insulin, a hormone produced in the pancreas which helps convert sugar, or glucose, into energy. Getting started with insulin therapy is one of the first steps after a type 1 diagnosis, and is an important part of living with type 1 diabetes at any age. Daily insulin therapy, along with blood sugar monitoring and meal planning, allows people with type 1 diabetes to maintain healthy and consistent blood sugar levels.

While the goal of insulin therapy is to keep your blood sugar levels as steady as possible throughout the day, fluctuations are natural. Checking blood sugar levels several times each day allows you to stay within a healthy range. Younger children with type 1 diabetes will need help with both insulin administration and blood sugar monitoring, and during the school day you may need teachers and other school staff to provide support. It’s also important that someone at the school understands how to administer glucagon if your child’s blood sugar falls too low (known as hypoglycemia).

Here are some steps you can take to simplify your child’s treatment needs and make sure you’re prepared for an emergency.

Communicate with your child’s teacher and/or other school staff before classes begin to make sure they’re aware of your child’s type 1 diabetes diagnosis. 

Discuss daily treatment needs like blood sugar monitoring and insulin therapy as well as potential complications that may arise, like low blood sugar, and how to spot the signs and symptoms.

You may also want to consider an insulin pump. They have become increasingly common in diabetes treatment, especially with children, due to their convenience, ease of use, and automated timing of insulin injections 

The American Diabetes Association has resources that you can share with school staff to help them understand how to support your child’s diabetes care plan. And the JDRF has a back to school checklist, which includes all the information your child’s teachers should know.

Read our previous blog to learn more about managing your child’s type 1 diabetes.

Teens and young adults: managing diabetes away from home

Learning how to navigate life with greater independence and less structure as you enter your late teens and twenties often takes on additional importance if you have type 1 diabetes. You may now be responsible for aspects of your own diabetes treatment that parents or other adults previously helped with.

For many young adults living with type 1 diabetes, this transitional period requires learning about the logistical aspects of diabetes care, like filling prescriptions, ordering supplies, and scheduling appointments. And whether you’re living far from home or nearby, it may be time to find a new doctor, as many young adults switch from seeing a pediatrician to an adult healthcare provider around the ages of 18 - 21.

To avoid any gaps in your diabetes treatment, plan ahead and work with your pediatrician and your support system, including your parents or other relatives, to create a plan for finding an adult healthcare provider. Make sure that you also have the information you need to stay on track with your diabetes management, like how to navigate health insurance, or how to use diabetes supplies like a continuous glucose monitoring device (CGM)  or insulin pump. 

It’s understandable if other challenges related to your diabetes care needs arise for the first time during this stage of life. For many young adults, there’s a learning curve with handling other illnesses when you’re away from home. For example, the flu can become more complicated if you have diabetes, since it may affect your calorie intake, which in turn may affect your blood sugar levels. Once you’ve found a primary care provider, ask them about additional steps to take when you’re sick, like checking your blood sugar levels more frequently or consuming carbohydrate-rich soft food and liquids .

It’s also important to understand how alcohol use can interact with insulin therapy and affect your blood sugar levels. Ask your doctor for recommendations about drinking safely when living with type 1 diabetes, and be honest with them about your alcohol consumption so that they can best address your individual health needs.

You may also benefit from working with a certified diabetes educator during the transition from your teens to adulthood. A diabetes educator is a healthcare professional with extensive knowledge of diabetes who has been certified to coach individuals living with the condition. They can make sure you have all the necessary information to successfully manage your diabetes.

Maintaining a balanced life with type 1 diabetes

It may feel like life has only gotten faster during your late twenties and into your thirties and forties. However, staying on track with your diabetes management is as important as ever — and for some individuals, you may be first learning of your type 1 diabetes diagnosis during this busy time.

A common challenge of living with type 1 diabetes in adulthood is fitting daily treatment needs into a busy schedule. If you work long days in a physical setting, it may feel inconvenient to take insulin and check your blood sugar while on the job. You may find that an insulin pump is a good option for you since you won’t have to worry about remembering the timing of your injections.

Ultimately, deciding how much of your health situation to share with an employer is a personal choice, but at least one person should be prepared to offer support in the event of an emergency if you work on site. Make sure they know the signs of low blood sugar, how to administer emergency glucagon, and where you keep your supplies.

If you are a woman living with type 1 diabetes and considering starting a family, sharing your family planning goals with your primary care physician can help you have a healthy pregnancy. Your A1C levels — your average blood sugar levels over a period of two to three months, which your doctor will check periodically during your regular visits — are even more important in the months before pregnancy. This is because your blood sugar levels can impact the development of your baby’s organs during the first 8 to 12 weeks of your pregnancy.

Ask your doctor to clarify your A1C goals and how long to maintain them before pregnancy. And once you find out you are pregnant, contact your healthcare provider as soon as possible to find out if you need to make any changes to your treatment.

Your risk for many conditions like heart disease, high blood pressure, high cholesterol, and dementia all increase as you age. When living with type 1 diabetes, preventative care and healthy lifestyle choices are even more important, as many aging-related health risks intersect with potential diabetes-related complications.

Men and women living with type 1 diabetes have a higher risk of developing heart disease than those without the condition. High blood pressure is common in older adults with diabetes, which can lead to a greater risk for strokes and heart attacks and may also affect your vision and kidney function.

It’s important to keep track of your blood pressure and cholesterol levels and follow your doctor’s recommendations for treatment, which may include lifestyle changes and medications. And depending on your overall health, you may need a loved one’s support with managing certain aspects of your diabetes care, like administering insulin and recording blood sugar readings.

Living with diabetes at any age is easier with a reliable pharmacy partner. At Alto, we’re committed to making it as simple as possible to manage your diabetes, with free same-day delivery and medication management tools like reminders and auto refills in our app. And our dedicated diabetes support team is here to ensure that you have all the information you need to follow through on your individualized treatment plan.

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

Heart-healthy living is a lifelong practice. To help you get started, we’ve compiled a list of the top heart disease prevention actions to tackle during each decade of life.

How to Prevent Heart Disease at Any Age

You may associate heart disease with aging, and for good reason — individuals age 65 and older face a higher risk for the condition. This stems in part from how aging-related changes in your body overlap with risk factors for heart disease. For example, your arteries and heart muscle stiffen with age, making it more difficult to pump blood well during exercise.

Still, it’s never too early to prioritize a heart-healthy lifestyle. As heart disease-linked conditions like diabetes and high blood pressure grow increasingly common among young adults, many people are now becoming at risk for heart disease at an earlier age. 

And even if you are young and in good overall health, the choices you make today can affect your heart health for years to come. Cardiovascular health issues like heart attacks, strokes, and heart failure often stem from a lifetime’s worth of health choices, including many you have control over.

Since heart-healthy living is a lifelong practice, it may feel more manageable if you set specific goals and priorities impactful for your age group. To help you get started, we’ve compiled a list of the top heart disease prevention actions to tackle during each decade of life. This is intended to be a high-level guide to prevention, so consult with your healthcare provider about more targeted priorities based on your individual health needs.

2. Search for a primary care provider if you don’t have one

3. Find your favorite physical activity and develop a fitness routine

You’re out in the real world, exploring what you want your life to look like. It’s normal to experience some anxiety during this exciting but nerve-racking time. Your cardiovascular health may not be top of mind as you navigate a stressful job search, adjust to the pressure of beginning a career, or start a family, but taking several heart healthy actions during this decade of life will put you on the right track early on.

Focus on building a foundation for a healthy lifestyle. That means quitting smoking if you currently smoke, figuring out which physical activities work for you, and getting in the practice of staying up to date with yearly doctor’s appointments. If you don’t already have a primary care provider, now’s the time to search for one.

1. Create a weekly routine that makes time for exercise

Blog

Hello, Long Island!

The Science Behind Vaccines

How We Used Kafka to Build an Event-Driven Automation Pipeline and Scale Our Pharmacy

Hello Austin, We're Alto Pharmacy!

How Alto Reduced Time to Resolution for Production Incidents

Celebrating National Coming Out Day at Alto

How to Live with Type 1 Diabetes at Any Age

How to Prevent Heart Disease at Any Age

Hello, San Diego!

Pulmonary Fibrosis: What to Know About Symptoms and Treatment

Hello, Dallas!

What You Should Know About the A1C Test and Diabetes

Switch to a better pharmacy.