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

Millions of individuals with type 1 and type 2 diabetes need insulin every day to keep their blood sugar levels in a healthy range. In recent decades, it has grown increasingly difficult for many to access this life-saving medication, as insulin prices continue to rise.

Managing the Costs of Insulin

Millions of individuals with type 1 and type 2 diabetes need insulin every day to keep their blood sugar levels in a healthy range. In recent decades, it has grown increasingly difficult for many to access this life-saving medication, as insulin prices continue to rise. Take a look at these recent statistics:

The cost of insulin increased by an average of 14% every year from 2012 to 2018.

In 2017, insulin accounted for 20% of all diabetes-related healthcare spending before rebates and discounts and 6.3% after rebates and discounts.

In a 2018 survey on insulin affordability conducted by the American Diabetes Association, 39% of the respondents reported an increase in their insulin costs between 2017 and 2018.

Rising insulin costs can significantly impact an individual’s ability to manage their health. 27% of those surveyed by the ADA said that insulin prices affected how much of the medication they could buy or use. Missed insulin doses can lead to serious health complications including diabetic ketoacidosis.

While insulin access remains a critical issue for many Americans with diabetes, lawmakers have recognized the urgency of lowering insulin costs. In November 2021, the U.S. House of Representatives passed the Build Back Better Act, which caps out-of-pocket copays for insulin at $35 per month. The legislation has yet to pass in the U.S. Senate, but President Joe Biden recently reaffirmed his commitment to lowering insulin costs — and prescription medication costs more broadly — as part of his domestic agenda.

In the meantime, there are a variety of resources to help you manage the costs of insulin, including patient assistance programs and copay savings cards from insulin manufacturers. Here’s more on eligibility for these programs.

The Lilly Cares® Foundation Patient Assistance Program

The Lilly Cares Foundation Patient Assistance Program provides free insulin and glucagon products for individuals who have Medicare Part D or no health insurance coverage and meet certain income requirements.

Learn more about program terms and conditions and the application process.

The Novo Nordisk® Patient Assistance Program

The Novo Nordisk Patient Assistance Program provides insulin and other diabetes medications at no cost to individuals who have Medicare or no health insurance coverage and whose total household income is at or below 400% of the federal poverty level.

Sanofi Patient Connection provides Sanofi medications including insulin at no cost to individuals whose total household income is at or below 400% of the federal poverty level.

The Lilly Insulin Value Program offers all Lilly insulins at $35 per month to individuals with commercial health insurance or no health insurance coverage. Download the copay card here.

Sanofi offers a copay savings card for those with insurance as well as the Valyou Savings Program for those without insurance, which offers Sanofi insulin at $99 per month. Learn more about Sanofi savings opportunities.

Novo Nordisk offers savings cards that reduce copays for a variety of insulin products. Get more details here.

Your financial well-being is our priority

At Alto, we understand how stressful it can be to navigate insurance coverage benefits and savings opportunities. We prioritize your financial wellness, working with your doctor, your insurance (if applicable), and any third party savings programs that you may qualify for to make your insulin and other medications as affordable as possible. In addition to automatically applying any coupon savings, we’ll connect you with any outside programs that require you to apply directly.

We also offer free, same-day delivery to simplify your diabetes management, and our dedicated diabetes support team is here to answer any questions you may have. Get started or learn more about Alto, 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.

For many individuals, the journey of living with type 2 diabetes starts early. Once referred to as adult-onset diabetes due to its prevalence among middle-aged and older Americans, the condition has become more common in children, adolescents, and young adults, due in part to growing childhood obesity rates. While some aspects of type 2 diabetes management, like glucose monitoring and healthy lifestyle choices, are important for all age groups, other parts of treatment may change with time. Here’s a snapshot of what type 2 diabetes may look like at each stage of life and tips for living with the condition.

Managing Type 2 Diabetes at Any Age

All type 2 diabetes treatment plans include healthy eating, frequent physical activity, and blood sugar monitoring regardless of age. Depending on a child or adult’s blood sugar levels and overall health, they may also need diabetes medication or insulin therapy to supplement these lifestyle changes. In addition to insulin, two other diabetes medications may be used to treat type 2 diabetes during childhood: metformin, an oral medication, and liraglutide, an injectable medication.

Younger children will need assistance with blood sugar monitoring, and if your child takes insulin, they will also need help with insulin administration. It’s important that teachers or other school staff are able to provide support during school days. Make sure that someone at the school is prepared to administer glucagon if your child’s blood sugar falls below a healthy range (known as hypoglycemia).

Inform your child’s teacher and/or other school staff of your child’s type 2 diagnosis before classes begin. Be sure to discuss daily treatment needs like blood sugar monitoring, insulin therapy, or other medication needs, as well as how to spot the signs and symptoms of low blood sugar. The American Diabetes Association (ADA) has resources that can help you start these conversations.

Living with type 2 diabetes as a young child can be emotionally challenging. It often helps to build connections with other children who are on the same journey. Explore programming for children with type 2 diabetes, like the ADA’s summer camps.

If your child is overweight, their doctor may recommend that you focus on slowing weight gain rather than losing weight since they are still growing. Follow your doctor’s recommendations and look for simple but impactful changes, like swapping carbohydrate-rich foods for a snackable fruit or vegetable, or trading soft drinks and fruit juices for water.

Whether you’ve had type 2 diabetes since childhood or are newly diagnosed, living with the condition as a young adult requires you to take an active role in the management of your health. It’s important to build a relationship with a care team that you trust to avoid any gaps in your treatment. Depending on your treatment plan, you may also have to learn about the logistics of filling prescriptions, ordering diabetes supplies, and coordinating with your insurance company.

Taking on additional responsibilities and navigating life more independently doesn’t mean that you’re completely on your own in managing your diabetes. If parents or another relative previously helped you with blood sugar monitoring, scheduling doctor’s appointments, or other aspects of care, use them as a resource during this transitional period as you become more confident managing your health. You may also want to expand your support system by working with a certified diabetes educator or connecting with other young adults living with type 2 diabetes.

Make sure you understand how other health issues can affect diabetes. For example, the common cold or flu can impact your calorie intake and blood sugar levels, so it’s important to be prepared to manage other illnesses. Alcohol safety is also extra important when living with type 2 diabetes, as alcohol is a factor in your blood sugar levels. For those taking insulin, be mindful of how alcohol use affects insulin therapy.

Build a diabetes care team you trust. In addition to seeing a primary care physician for general health issues, search for an endocrinologist who specializes in diabetes treatment.

Familiarize yourself with all aspects of managing type 2 diabetes, from navigating health insurance to monitoring blood sugar. Consider working with a certified diabetes educator. These are healthcare professionals with extensive knowledge of the condition who can offer individualized support. You can also search for a diabetes education program.

Find opportunities to connect with other young adults learning how to manage type 2 diabetes, like the Beyond Type 2 community.

The progression of type 2 diabetes varies significantly by individual. While many individuals are just beginning the journey of living with the condition in their 30s or 40s, diabetes management may feel like second nature for those who were diagnosed at an earlier age. It’s also possible for a person’s treatment needs to evolve at this stage of life. If lifestyle changes and other medications are effective, you may be tapering off of insulin. Conversely, you may need to begin taking additional medications, such as insulin, in order to manage your diabetes even more effectively. As always, follow your care team’s recommendations for your specific needs.

Regardless of what type 2 diabetes looks like for you, one thing’s for certain: it’s important to stay on top of your care and put your health first even when life is at its busiest. Make sure there’s plenty of room in your calendar for physical activity and doctor’s appointments. If you take insulin, find the right delivery method for your schedule and lifestyle. Many people who work long days in a physical setting find insulin pumps and pens convenient as they eliminate the need to remember the timing of injections.

If you are considering starting a family, your doctor can help you plan to have a healthy pregnancy. Get clarity on your A1C targets — your average blood sugar levels over several months — and how long to maintain them before pregnancy. Once you become pregnant, make a doctor’s appointment as soon as possible to learn about any potential changes to your treatment plan.

Revisit your fitness routine, if needed, to find the right activities for your schedule. If you find it challenging to fit enough exercise into your life — ideally 150 minutes of moderate-intensity aerobic activity per week — try to fit shorter bursts of physical activity into your day. 

If you take insulin, consult with your doctor about insulin delivery options to find the best fit for your needs.

Choose a diabetes pharmacy partner that simplifies your treatment. At Alto, we consolidate all of your medications and supplies into a single monthly delivery, and our mobile app can help you manage all of your diabetes needs in one place.

Preventative care and healthy lifestyle choices take on additional importance when you’re living with diabetes, which increases your risk for other chronic conditions like heart disease, high blood pressure, high cholesterol, and dementia.

Many older adults with diabetes also have high blood pressure, which is linked to a higher risk for strokes and heart attacks as well as vision and kidney function. Stay on top of key numbers like your blood pressure and cholesterol levels, and follow your doctor’s recommendations for treatment. You may also want to ask your doctor about additional screenings related to your mental health or cognitive health, as older adults with diabetes are more likely to experience depression or cognitive impairment. (If caring for an older adult with diabetes, watch for the signs of depression and dementia.)

Stay current with vaccines, including the annual flu shot and the pneumonia vaccine. If you are unsure which vaccines you need, ask your doctor.

Ask your doctor about the recommended frequency of screenings for other health conditions, including cancer screenings and kidney function tests.

Find a loved one to help with insulin administration and recording blood sugar readings, if needed.

Managing diabetes is easier at any age with the right pharmacy partner by your side. The Alto app can help you manage all of your diabetes needs in one place, and our dedicated diabetes support team is here to offer guidance and make sure you have everything you need for your treatment.

Reach out any time through in-app secure messaging or by phone at 1-800-874-5881 to learn how we can support your diabetes care.

With more engineers contributing to Alto’s codebase than ever before, we needed to establish better boundaries: which team owns what? Here’s how we developed a tagging-based solution to code ownership and drove and measured adoption.

How We Established Better Boundaries and Clearer Code Ownership at Alto

Some problems are nice to have. Over the course of 2020 the engineering team at Alto saw explosive growth, expanding from about fifteen to more than seventy individual contributors. Growth at this pace required us to rethink our team structures and priorities more than once. This growth felt amazing: the new capacity enabled us to make progress on our backlogs like never before.

But still, there were challenges. We saw a steady rise in merge conflicts as more people contributed to the same code base. Build times increased as more and more code was contributed. A big influx of new perspectives and talent also meant new gaps in historical context and responsibility. New teams took big bites out of their new priorities — great! But what about the old ones? Who was going to fix that bug? Who needs to review this PR? Who is accountable for this performance problem?

Who, in short, owned what? By the end of 2020, it was clear to us that a good, practical, working answer to this question would be the critical first step to continuing smooth, rapid, distributed iteration on our product.

Up to this point, the large majority of product development at Alto had happened in the context of a Ruby on Rails monolith, which — over a half decade of intense development — had grown pretty large. We’d stuck more or less to the default Rails convention of organizing code by function rather than feature, which meant that our code was distributed across a few mostly flat and very broad subdirectories such as '/models' and '/controllers', making it difficult to learn much about the structure and ownership of our business domains by merely looking at how the code was laid out. We knew that this was not going to work for us over the long term.

Our long term vision started to coalesce around a notion of “better boundaries.” First, we would modularize the monolith along the lines suggested by Shopify’s packwerk utility. Then, we would carve some of those modules out into separate engines that could be built and tested separately. Finally, we’d deploy and operate some of those engines independently as their own services. Clear ownership was fundamental to this plan: on either side of an effective boundary, you need to know not just what it is but also who owns it. We lacked that clarity.

The RFC (Request for Comments) we ultimately adopted opened with four questions:

How might we produce a domain model and do something useful at the same time?

How will we avoid imposing (the wrong) prescriptive model from the top down?

How will we keep it up to date and accurate?

We considered jumping straight into moving files around into a more modular structure. Ultimately we decided against this approach as a first step for a number of reasons. The benefit of moving files around is mostly abstract — it’s not immediately clear what to do with a better module structure. It’s relatively expensive to move files around in a Rails app — doing so typically requires you to rename the contents (and update all its callers), which amounts to a lot of busy work, and it’s extra expensive to be wrong. And the in-between state is rough: which example should I follow in deciding where to put my new file? First you are obligated to create a map of the future state, and then to keep that map in sync with reality as you go.

Instead, we opted for a lightweight solution that would allow us to map our domains and their owners in the code itself — helping to ensure it’s up to date and accurate — without having to restructure it at the same time. We’d do this by tagging code in code comments, and then building tools to leverage these tags in various ways to increase visibility and enforce ownership. This has the nice effect of producing a new domain map incrementally from the bottom up, rather than prescriptively from the top down.

We called this the '@owners' tag, and it looks like this:

# @owners { team: platform, domain: orders }
class Wunderbar::OrdersController < Wunderbar::WunderbarController
  def show
		...
  end

  # @owners { team: inventory }
  def out_of_stock
    ...
  end
end

We based our tooling around extending the YARD documentation tool to recognize this as a custom tag. You can teach YARD to recognize a custom tag by passing a command line option like '--tag owners:"Owners"', which by default will cause the tag value to appear in generated documentation under the header “Owners”. The Ruby API for declaring a tag programmatically is shown in the snippet below as well.

We wanted the tag to be interpreted hierarchically to handle cases where ownership has diverged within the same class or module, such that we might want to tag one or two methods differently from the rest, as well as to ease the burden when all of the classes / modules / methods under a namespace belong to the same team and domain, since you can just tag the shared parent. We set an initial goal around getting 100% of our methods covered by at least a “team” value, at which point we would require all code to be covered in our build process.

To get a basic feel for how to work with these tags, make sure the 'yard' gem is available, tag a couple of your files, and then try running the code below in your project. It will print out the tag associated with each tagged code block.

require 'yard'
# Define the custom tag.
YARD::Tags::Library.define_tag('Owners', :owners)

# Parse your codebase. You might want to pass a more specific path here.
YARD.parse('.')

# Load all the method, class and module code blocks into memory
code_blocks = YARD::Registry.all(:method, :class, :module)

# Print the tag associated with each tagged block.
code_blocks.each do |code_block|
  tag = code_block.tag('owners')
  # automatically tag nested classes, modules and methods.
  while tag.nil? && code_block.namespace != nil && [:class, :module].include?(code_block.namespace.type)
    code_block = code_block.namespace
    tag = code_block.tag('owners')
  end
  print "Code Block: #{code_block}, tag: #{tag.text}, line: #{tag.line}" if tag
end

We ultimately developed a handful of CLI tools based on this technique that allow us to produce reports measuring the percentage of code covered by team and domain at different levels, among other things:

bin/yardowners --help
Usage: bin/yardowners [options]
        --methods                    view by methods
        --files                      view by files
        --teams                      teams report
        --domains                    domains repot
        --team=TEAM                  filter by team
        --domain=DOMAIN              filter by domain
        --codeowners                 update codeowners
        --lint                       lint owners tags
        --require-domains            lint for presence of domain in  
owners tags
    -h, --help                       display this help and exit

We use this CLI to add checks to our CI process around coverage / correctness, as well as to report progress toward our goals of 100% coverage.

To get the tagging process started across the organization, we dumped all of our class and module names (thanks again, YARD!) into a big spreadsheet, and then asked each team to get together and spend a bit of time putting their names next to the ones they owned. We adopted the attitude that it was better to have the wrong value than no value, since it would be easy to adjust later.

We covered a good 80% of the code using this spreadsheet by the time each team had taken an initial pass. From there, we filled the blanks in with “TODO”, and then wrote a little script to automatically insert the tags into the code (again based on the YARD metadata, which conveniently gives you the line numbers for the top of each class / module declaration).

At that point, we enabled a linter requiring 100% team owner coverage on all new PRs. We set a new goal to eliminate TODOs, and chipped away at it over the course of a month or so. We then repeated this process for the “domain” values, driving that to 100% as well. We found that the spreadsheet-based divide-and-conquer approach allowed us to cover a lot of ground very quickly.

Once we were able to parse our '@owners' tags, the first and most important thing we did with them was to automatically generate our CODEOWNERS file. We enforce that each tagged team maps to a team name in github and check that CODEOWNERS is up to date during the build process. This new process introduced some friction, as teams started getting tagged every time a file they were tagged on changed. This turned out to be great, because it sparked a number of very productive negotiations around ownership and scope that got hashed out in code review. We keep our CODEOWNERS file synced with Sentry, too, so that exceptions raised by files you tagged as yours get assigned to your team automatically. We also track and report on the performance of individual endpoints by team according to how they are tagged.

The new owners tag hasn’t fixed all our problems by any means, but it has proved fundamental to our ability to operate as a growing set of increasingly independent teams with well specified responsibilities. In subsequent posts, we’ll talk more about how we’re using our new domain map and a suite of other cool tools to build better boundaries within and ultimately escape from our monolith.

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

Many of us are spending more time on screens than ever before, as a growing number of social interactions take place online, along with work and school for many individuals. This prolonged exposure to digital devices can be hard on the eyes. Perhaps you’ve experienced achy eyes, blurred vision, headaches, or other symptoms of eye strain and screen fatigue yourself. The good news? There are steps you can take to lighten the load on your eyes and protect your vision.

Protect Your Eyes From Screen Fatigue

The causes of eye strain are twofold. First, your eyes have to work harder to see something close up, specifically the ciliary muscle, which contracts to support your focus. Hours of concentration on a single object causes that muscle to ache. This frequently occurs with screen use — which is why eye strain is often referred to as digital eye strain, screen fatigue, or computer vision syndrome — but it can also result from intense use of your eyes in other contexts. (The 20-20-20 rule, explained in more detail below, should come in handy for long reading sessions, too!)

Then there’s the effects of blue light, which is specific to screen-related eye strain. Digital devices like computers and mobile phones emit blue light to enhance the quality of images on your screen and help you stay alert. While this mimics the sun’s natural wavelengths, absorbing this high-energy light up close for an extended period of time strains your eyes. Not only does this contribute to screen fatigue, it can potentially damage your retina, the part of your eye that processes light and communicates to your brain.

Simple precautions can protect your eyes from screen fatigue, from the set-up of your home workspace to nutrition choices. Try the following to start.

The closer you are to a screen, the harder your ciliary muscle is working, so be sure there’s enough distance between your eyes and your computer screen. The American Academy of Ophthalmology recommends sitting about 25 inches from the screen, roughly an arm’s length away.

There are a variety of blue light-blocking tools that minimize its negative effects, including screen protectors for tablets, laptops, TVs, and phones. You may also want to ask your optometrist or ophthalmologist if blue light-filtering glasses would be a good fit for your needs. If you and your doctor have decided that these glasses are right for you, remember to put them on every time you use your computer, TV, or another digital device so that you can experience their full benefits.

Limiting your exposure to blue light becomes even more important later in the night, as it can affect your production of melatonin, potentially disrupting your sleep cycle. Many electronic devices give you the ability to shift your display to warmer colors more conducive to sleep, so be sure to make the switch before scrolling from bed. (Ditching screens before bedtime altogether is even better!)

Along with blue light, glare from a screen can also lead to eye strain. Be mindful of your computer or TV screen’s brightness in comparison to your surroundings, as high contrast between screen brightness and room lighting can strain your eyes. You may have to adjust these settings a couple times each day as the sun changes position. If using a laptop, tilting your screen so that your gaze is pointed downward may also help.

The less time spent staring at a screen, the better — for your eyes, your sleep, and other aspects of your overall health. But if work or school makes it difficult for you to step away from the screen for long periods of time, even short breaks help. Use the 20-20-20 rule to let your eyes rest: take a break every 20 minutes and look at an object 20 feet away for 20 seconds.

A balanced diet can combat the effects of blue light. Omega-3 fatty acids — found in nuts, seeds, and fish like tuna and salmon — and beta carotene — found in vegetables like pumpkin, carrots, and sweet potatoes — are known to boost eye health. Green, leafy vegetables like kale and spinach contain both beta carotene and Vitamin E, another nutrient that can protect your vision.

Stay current with annual vision check-ups

You may be more susceptible to eye strain when other unaddressed vision issues are present, so be sure to go in for regular eye appointments. Even if your vision is strong, it’s still important to have a full check-up every year as part of your overall preventative care.

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.

While fertility preservation treatments like egg freezing and IVF are significant investments of time and resources, there are many ways to lower or manage the costs of treatment. As you prepare for the financial aspects of treatment, be sure to explore all of your options for financial assistance and savings, including patient assistance programs from fertility medication manufacturers.

A Guide to Ferring Pharmaceuticals’ Fertility Medication Savings Programs

If Alto is your fertility pharmacy, your fertility medication protocol may include medications manufactured by Ferring Pharmaceuticals, which has several financial assistance programs that offset the cost of fertility medications. Here’s more on eligibility for these programs and how to apply.

The OneHeart program provides a $200 rebate for out-of-pocket costs for select Ferring fertility medications. Eligibility is for those with no insurance coverage or commercial health insurance plans. In addition, you must have started your ovarian stimulation cycle between June 1, 2020 and June 30, 2022, with all medications purchased by June 30, 2022.

The HeartFelt program helps individuals whose cycles were canceled due to COVID-19 or a natural disaster resume fertility treatment. It offers medication replacement for up to 15 vials of Menopur® and up to five syringes of Fyremadel™ (ganirelix acetate) depending on the amount of medication used in the canceled cycle. Eligibility is for those with no insurance coverage or commercial insurance coverage.

To learn more about program terms and conditions and the application process, download the HeartFelt brochure on Ferring’s patient resources page.

The HeartTomorrow program provides Menopur® at $68 per vial for those undergoing an elective egg freezing cycle. To be eligible, you must be paying cash for your fertility medications and purchase a minimum of 20 vials in your first fill.

The Heart for Heroes program provides IVF medications at no cost to eligible military veterans who have experienced infertility due to a service-related injury or who do not have insurance coverage for fertility medications. To learn more about terms and conditions and the application process, call 1-800-515-3784.

The HeartBeat program provides select fertility medications at no cost for cancer patients. To be eligible, you must be a female U.S. citizen or permanent resident with a cancer diagnosis who has not received chemotherapy within the previous six months. To learn more about terms and conditions and the application process, call 1-888-347-3415. (Residents of Arkansas, Massachusetts, or New Jersey can call 1-877-252-0553.)

If your fertility medications are manufactured by EMD Serono, read our previous post for an overview of EMD Serono’s patient assistance programs. You can also read our previous posts on managing the costs of fertility treatment to learn about additional financial resources, including Alto’s financial support for fertility medications:

Managing the Costs of Fertility Treatment

A Financial Planning Guide for Egg Freezing

We’re here for you during fertility treatment

At Alto, we understand that fertility treatment is a physical, emotional, and financial investment, and we offer support with all aspects of your fertility journey.

We prioritize your financial wellness, working 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. In addition to automatically applying any coupon savings, we’ll connect you with any outside programs that require you to apply directly.

We’re here to help with the rest of the process, too, with free same-day delivery of your medications, temperature controlled packaging, and fertility resources like personalized injection guide videos and one-on-one consultations with fertility-trained pharmacists.

To get a price quote specific to your fertility medication protocol, complete our online form.

While it can be overwhelming to receive a diagnosis of type 2 diabetes, following your doctor’s treatment plan can help you manage the condition and live a healthy and active life. In some cases, lifestyle changes alone can help you keep your blood sugar levels in a healthy range. For other individuals, insulin, oral medication, or a combination of both may also be necessary. Here’s what to know about metformin, one of the most common oral medications used to treat type 2 diabetes.

What to Know About Metformin

Metformin belongs to a class of medications called biguanides, which regulate your blood sugar levels by reducing how much glucose is produced during digestion. Currently, metformin is the only biguanide approved for diabetes treatment in the U.S.

Metformin is taken one to three times a day depending on your dosage and the form of metformin your doctor has prescribed. It is available in the following formulations and strengths:

Immediate-release tablet: 500mg, 850mg, 1000mg 

Extended-release tablet: 500mg, 750mg, 1000mg

Unlike individuals with type 1 diabetes, who are unable to produce any insulin at all and take insulin every day, individuals with type 2 diabetes typically can produce some insulin but experience problems with insulin production. They may not produce enough insulin, or cells in their body may have become resistant to insulin. Metformin does not change the amount of insulin you produce, but it does help counter insulin resistance. If your type 2 diabetes has progressed to a later stage, you may need insulin therapy to manage your blood sugar levels. Metformin is often used alongside insulin therapy at this stage to help the body use insulin more efficiently.

Metformin is also sometimes used off-label to treat polycystic ovary syndrome (PCOS), as insulin resistance may be a symptom of the condition.

Some people experience gastrointestinal issues like nausea and diarrhea as a result of taking metformin, most often when they first begin taking the medication. Taking metformin with meals often helps prevent these side effects. Your doctor may also have you start on a lower dosage of metformin and gradually work up to a larger dosage as an additional precaution against side effects.

There are fewer gastrointestinal side effects associated with the extended-release formulation of metformin. This formulation releases the medication slowly, maintaining a consistent level of the medication in your bloodstream over a longer period of time. If you have concerns about potential side effects of metformin, you may want to ask your doctor if an extended-release formulation of metformin is a good fit for your needs.

Metformin can decrease your levels of vitamin B12, which can lead to anemia — a condition defined by low levels of red blood cells — in rare cases. Your risk for anemia is greater if your diet is low in vitamin B12 and calcium. If you experience symptoms of anemia such as fatigue, dizziness, or lightheadedness, reach out to your doctor for an evaluation of your red blood cell levels.

In rare cases, metformin may lead to lactic acidosis, an uncommon but serious condition in which an accumulation of lactic acid in the body leads to an imbalanced pH level. The chance of this side effect occurring is low, and individuals with impaired kidney function or heart failure are most at risk. To determine if metformin is a good fit for your treatment needs, your doctor will consider your overall health history and possibly order an estimated glomerular filtration rate (eGFR) test, which is a blood test that assesses your kidney function.

Hypoglycemia occurs when your blood glucose levels drop below a healthy range, most often after taking insulin. It is typically caused by not eating enough or exercising too much, and the timing of your insulin doses may also be a factor. These are some common signs of hypoglycemia to watch for:

Coordination problems, clumsiness, and confusion

When taken on its own, metformin typically does not cause hypoglycemia. However, if you take metformin with other diabetes medications including insulin, it’s important to more carefully monitor your blood sugar and be mindful of how your diet, exercise, and alcohol intake can interact with metformin.

To prevent hypoglycemia when taking metformin, be sure to take all of your diabetes medications as prescribed and on schedule, follow your doctor’s recommendations for exercise, and eat a balanced diet. In addition, make sure your doctor has a complete picture of your health history and is aware of all the medications you take.

When your diabetes treatment plan includes multiple medications, staying on top of your prescriptions can be easier said than done. The Alto app can help you manage all of your diabetes needs in one place, and our dedicated diabetes support team is here to offer guidance and make sure you have everything you need for your treatment.

Reach out any time through in-app secure messaging or by phone at 1-800-874-5881 to learn how Alto can be a partner in your diabetes care.

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. 

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. 

Inhalers and nebulizers are both effective at delivering medications for respiratory conditions like asthma and chronic obstructive pulmonary disease (COPD). A nebulizer is a device that transforms a liquid medication into a fine mist which is then inhaled into the lungs through a mouthpiece. While nebulizers take longer to deliver medications than inhalers, their accurate dosage delivery is often a good fit for children living with asthma and other lung diseases, and many adults find them helpful as well. Here’s what to know if you’re considering using a nebulizer.

What to Know About Nebulizers

Inhalers and nebulizers are both effective at delivering medications for respiratory conditions like asthma and chronic obstructive pulmonary disease (COPD).

Blog

Managing the Costs of Insulin

Managing Type 2 Diabetes at Any Age

How We Established Better Boundaries and Clearer Code Ownership at Alto

Protect Your Eyes From Screen Fatigue

A Guide to Ferring Pharmaceuticals’ Fertility Medication Savings Programs

What to Know About Metformin

The Science Behind Vaccines

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

What to Know About Nebulizers

Developing Robust Authentication Using Rails, Omniauth, and Okta

Managing Your Medications While Traveling

Coronary Artery Disease, Explained

Switch to a better pharmacy.