The best Hacker News stories from Show from the past day
Latest posts:
Launch HN: Axle Health (YC W21) – In-Home Healthcare as a Service
Hey everyone,<p>We’re Connor and Adam and we’re working on Axle Health (<a href="https://www.axlehealth.com" rel="nofollow">https://www.axlehealth.com</a>).<p>We provide an API for sending health professionals to people’s homes to deliver medical services. For example, a telehealth company can use our service to request an in-home blood draw for their patient.<p>Healthcare has traditionally been delivered in an office or hospital. In recent years, telehealth - providing healthcare remotely, without the need for people to come to a healthcare facility - has taken off as technology has improved, but physical tests are still often needed to make
diagnoses, and physical contact is needed to administer treatment. Without physical interaction, telehealth physicians can only handle a subset of common visit reasons. In all other cases they’re required to refer patients to a lab or in-person doctor. As a result of this lack of continuity in the patient’s care journey, most use telehealth platforms for one-off needs like getting a prescription filled. The goal of our platform is to be an extension of the physician in the patient’s home, working on the doctor’s orders to administer physical services that would normally require a visit to a lab or office.<p>I ran across this problem when I moved from New York to Los Angeles. I had received the first dose of a vaccine (not the COVID vaccine, unfortunately) before moving and needed the second on arrival. My only option was to find a new doctor who required me to do a full physical exam before I could receive the second dose. I did it, but needed to take a couple hours off of work. I thought “why can’t I just get this done at home”. It’s not just me, studies show that completion of multi-dose vaccine courses is as low as 33%. Life just gets in the way.<p>After I had my experience, I called up my friend from college, Adam, who worked at UberEats and we started thinking about the economics of bringing care to patients’ homes. The wealthy already have access to in-home healthcare. The question was, could we drive enough operational efficiency and optimization to make this available to everyone while only charging a small per visit fee for companies to use the platform. Solving this problem would have far reaching implications by expanding access to treatment in healthcare deserts, enabling decentralized clinical trials, improving uptake of basic preventive services, and leading to better health outcomes.<p>The operational and technical challenge of sending a health professional to a patient’s home is complex. There are a couple of old line national phlebotomy companies that go in-home, but phlebotomy (drawing blood) is the easy part. When you start moving up the licensure ladder from phlebotomist to medical assistant to licensed practical nurse to registered nurse, their scope of practice expands. Each state has its own laws governing the scope of practice of each of those professionals. For example, our appointment assignment algorithm needs to account for the fact that in Florida a medical assistant can start an IV line, but in California they can’t. We need to ensure each professional has the right mix of supplies for their daily appointments to drive maximum efficiency - a nurse might go from administering an immunotherapy IV at one home to a vaccine at another. Luckily Adam is crazy enough to like these logistical headaches :P<p>But, Adam won’t need to solve these problems manually. We’ve built a good bit of software around matching patients with in-home professionals. The process is fully programmatic meaning partners can use our API to find available services in a zip code, pull time slot availability and pricing by geography, indicate special instructions from the doctor, book visits, and receive visit updates via webhooks. Health professionals from our network use the Axle app to get shift assignments, indicate to patients that they’re en route, and write up any visit notes. Patients can even see their health professional on a map in real time just like an Uber. We want to make the process of getting in-home care as seamless as possible for patients and health professionals.<p>Our API documentation (<a href="https://developers.axlehealth.com" rel="nofollow">https://developers.axlehealth.com</a>) is publicly available. We’re hoping to enable the next generation of healthcare startups by offering them the ability to physically interact with patients, through us. We wanted to make the API as straightforward as possible, so we welcome any feedback on the documentation or our product at large!<p>Thanks for reading!
Launch HN: Axle Health (YC W21) – In-Home Healthcare as a Service
Hey everyone,<p>We’re Connor and Adam and we’re working on Axle Health (<a href="https://www.axlehealth.com" rel="nofollow">https://www.axlehealth.com</a>).<p>We provide an API for sending health professionals to people’s homes to deliver medical services. For example, a telehealth company can use our service to request an in-home blood draw for their patient.<p>Healthcare has traditionally been delivered in an office or hospital. In recent years, telehealth - providing healthcare remotely, without the need for people to come to a healthcare facility - has taken off as technology has improved, but physical tests are still often needed to make
diagnoses, and physical contact is needed to administer treatment. Without physical interaction, telehealth physicians can only handle a subset of common visit reasons. In all other cases they’re required to refer patients to a lab or in-person doctor. As a result of this lack of continuity in the patient’s care journey, most use telehealth platforms for one-off needs like getting a prescription filled. The goal of our platform is to be an extension of the physician in the patient’s home, working on the doctor’s orders to administer physical services that would normally require a visit to a lab or office.<p>I ran across this problem when I moved from New York to Los Angeles. I had received the first dose of a vaccine (not the COVID vaccine, unfortunately) before moving and needed the second on arrival. My only option was to find a new doctor who required me to do a full physical exam before I could receive the second dose. I did it, but needed to take a couple hours off of work. I thought “why can’t I just get this done at home”. It’s not just me, studies show that completion of multi-dose vaccine courses is as low as 33%. Life just gets in the way.<p>After I had my experience, I called up my friend from college, Adam, who worked at UberEats and we started thinking about the economics of bringing care to patients’ homes. The wealthy already have access to in-home healthcare. The question was, could we drive enough operational efficiency and optimization to make this available to everyone while only charging a small per visit fee for companies to use the platform. Solving this problem would have far reaching implications by expanding access to treatment in healthcare deserts, enabling decentralized clinical trials, improving uptake of basic preventive services, and leading to better health outcomes.<p>The operational and technical challenge of sending a health professional to a patient’s home is complex. There are a couple of old line national phlebotomy companies that go in-home, but phlebotomy (drawing blood) is the easy part. When you start moving up the licensure ladder from phlebotomist to medical assistant to licensed practical nurse to registered nurse, their scope of practice expands. Each state has its own laws governing the scope of practice of each of those professionals. For example, our appointment assignment algorithm needs to account for the fact that in Florida a medical assistant can start an IV line, but in California they can’t. We need to ensure each professional has the right mix of supplies for their daily appointments to drive maximum efficiency - a nurse might go from administering an immunotherapy IV at one home to a vaccine at another. Luckily Adam is crazy enough to like these logistical headaches :P<p>But, Adam won’t need to solve these problems manually. We’ve built a good bit of software around matching patients with in-home professionals. The process is fully programmatic meaning partners can use our API to find available services in a zip code, pull time slot availability and pricing by geography, indicate special instructions from the doctor, book visits, and receive visit updates via webhooks. Health professionals from our network use the Axle app to get shift assignments, indicate to patients that they’re en route, and write up any visit notes. Patients can even see their health professional on a map in real time just like an Uber. We want to make the process of getting in-home care as seamless as possible for patients and health professionals.<p>Our API documentation (<a href="https://developers.axlehealth.com" rel="nofollow">https://developers.axlehealth.com</a>) is publicly available. We’re hoping to enable the next generation of healthcare startups by offering them the ability to physically interact with patients, through us. We wanted to make the API as straightforward as possible, so we welcome any feedback on the documentation or our product at large!<p>Thanks for reading!
Launch HN: Axle Health (YC W21) – In-Home Healthcare as a Service
Hey everyone,<p>We’re Connor and Adam and we’re working on Axle Health (<a href="https://www.axlehealth.com" rel="nofollow">https://www.axlehealth.com</a>).<p>We provide an API for sending health professionals to people’s homes to deliver medical services. For example, a telehealth company can use our service to request an in-home blood draw for their patient.<p>Healthcare has traditionally been delivered in an office or hospital. In recent years, telehealth - providing healthcare remotely, without the need for people to come to a healthcare facility - has taken off as technology has improved, but physical tests are still often needed to make
diagnoses, and physical contact is needed to administer treatment. Without physical interaction, telehealth physicians can only handle a subset of common visit reasons. In all other cases they’re required to refer patients to a lab or in-person doctor. As a result of this lack of continuity in the patient’s care journey, most use telehealth platforms for one-off needs like getting a prescription filled. The goal of our platform is to be an extension of the physician in the patient’s home, working on the doctor’s orders to administer physical services that would normally require a visit to a lab or office.<p>I ran across this problem when I moved from New York to Los Angeles. I had received the first dose of a vaccine (not the COVID vaccine, unfortunately) before moving and needed the second on arrival. My only option was to find a new doctor who required me to do a full physical exam before I could receive the second dose. I did it, but needed to take a couple hours off of work. I thought “why can’t I just get this done at home”. It’s not just me, studies show that completion of multi-dose vaccine courses is as low as 33%. Life just gets in the way.<p>After I had my experience, I called up my friend from college, Adam, who worked at UberEats and we started thinking about the economics of bringing care to patients’ homes. The wealthy already have access to in-home healthcare. The question was, could we drive enough operational efficiency and optimization to make this available to everyone while only charging a small per visit fee for companies to use the platform. Solving this problem would have far reaching implications by expanding access to treatment in healthcare deserts, enabling decentralized clinical trials, improving uptake of basic preventive services, and leading to better health outcomes.<p>The operational and technical challenge of sending a health professional to a patient’s home is complex. There are a couple of old line national phlebotomy companies that go in-home, but phlebotomy (drawing blood) is the easy part. When you start moving up the licensure ladder from phlebotomist to medical assistant to licensed practical nurse to registered nurse, their scope of practice expands. Each state has its own laws governing the scope of practice of each of those professionals. For example, our appointment assignment algorithm needs to account for the fact that in Florida a medical assistant can start an IV line, but in California they can’t. We need to ensure each professional has the right mix of supplies for their daily appointments to drive maximum efficiency - a nurse might go from administering an immunotherapy IV at one home to a vaccine at another. Luckily Adam is crazy enough to like these logistical headaches :P<p>But, Adam won’t need to solve these problems manually. We’ve built a good bit of software around matching patients with in-home professionals. The process is fully programmatic meaning partners can use our API to find available services in a zip code, pull time slot availability and pricing by geography, indicate special instructions from the doctor, book visits, and receive visit updates via webhooks. Health professionals from our network use the Axle app to get shift assignments, indicate to patients that they’re en route, and write up any visit notes. Patients can even see their health professional on a map in real time just like an Uber. We want to make the process of getting in-home care as seamless as possible for patients and health professionals.<p>Our API documentation (<a href="https://developers.axlehealth.com" rel="nofollow">https://developers.axlehealth.com</a>) is publicly available. We’re hoping to enable the next generation of healthcare startups by offering them the ability to physically interact with patients, through us. We wanted to make the API as straightforward as possible, so we welcome any feedback on the documentation or our product at large!<p>Thanks for reading!
Launch HN: Axle Health (YC W21) – In-Home Healthcare as a Service
Hey everyone,<p>We’re Connor and Adam and we’re working on Axle Health (<a href="https://www.axlehealth.com" rel="nofollow">https://www.axlehealth.com</a>).<p>We provide an API for sending health professionals to people’s homes to deliver medical services. For example, a telehealth company can use our service to request an in-home blood draw for their patient.<p>Healthcare has traditionally been delivered in an office or hospital. In recent years, telehealth - providing healthcare remotely, without the need for people to come to a healthcare facility - has taken off as technology has improved, but physical tests are still often needed to make
diagnoses, and physical contact is needed to administer treatment. Without physical interaction, telehealth physicians can only handle a subset of common visit reasons. In all other cases they’re required to refer patients to a lab or in-person doctor. As a result of this lack of continuity in the patient’s care journey, most use telehealth platforms for one-off needs like getting a prescription filled. The goal of our platform is to be an extension of the physician in the patient’s home, working on the doctor’s orders to administer physical services that would normally require a visit to a lab or office.<p>I ran across this problem when I moved from New York to Los Angeles. I had received the first dose of a vaccine (not the COVID vaccine, unfortunately) before moving and needed the second on arrival. My only option was to find a new doctor who required me to do a full physical exam before I could receive the second dose. I did it, but needed to take a couple hours off of work. I thought “why can’t I just get this done at home”. It’s not just me, studies show that completion of multi-dose vaccine courses is as low as 33%. Life just gets in the way.<p>After I had my experience, I called up my friend from college, Adam, who worked at UberEats and we started thinking about the economics of bringing care to patients’ homes. The wealthy already have access to in-home healthcare. The question was, could we drive enough operational efficiency and optimization to make this available to everyone while only charging a small per visit fee for companies to use the platform. Solving this problem would have far reaching implications by expanding access to treatment in healthcare deserts, enabling decentralized clinical trials, improving uptake of basic preventive services, and leading to better health outcomes.<p>The operational and technical challenge of sending a health professional to a patient’s home is complex. There are a couple of old line national phlebotomy companies that go in-home, but phlebotomy (drawing blood) is the easy part. When you start moving up the licensure ladder from phlebotomist to medical assistant to licensed practical nurse to registered nurse, their scope of practice expands. Each state has its own laws governing the scope of practice of each of those professionals. For example, our appointment assignment algorithm needs to account for the fact that in Florida a medical assistant can start an IV line, but in California they can’t. We need to ensure each professional has the right mix of supplies for their daily appointments to drive maximum efficiency - a nurse might go from administering an immunotherapy IV at one home to a vaccine at another. Luckily Adam is crazy enough to like these logistical headaches :P<p>But, Adam won’t need to solve these problems manually. We’ve built a good bit of software around matching patients with in-home professionals. The process is fully programmatic meaning partners can use our API to find available services in a zip code, pull time slot availability and pricing by geography, indicate special instructions from the doctor, book visits, and receive visit updates via webhooks. Health professionals from our network use the Axle app to get shift assignments, indicate to patients that they’re en route, and write up any visit notes. Patients can even see their health professional on a map in real time just like an Uber. We want to make the process of getting in-home care as seamless as possible for patients and health professionals.<p>Our API documentation (<a href="https://developers.axlehealth.com" rel="nofollow">https://developers.axlehealth.com</a>) is publicly available. We’re hoping to enable the next generation of healthcare startups by offering them the ability to physically interact with patients, through us. We wanted to make the API as straightforward as possible, so we welcome any feedback on the documentation or our product at large!<p>Thanks for reading!
Show HN: Bunklist – Collect and discover useful websites through lists
Show HN: Bunklist – Collect and discover useful websites through lists
Show HN: My multiplayer custom-engine game that loads in less than a second
Show HN: My multiplayer custom-engine game that loads in less than a second
Show HN: My multiplayer custom-engine game that loads in less than a second
Show HN: My multiplayer custom-engine game that loads in less than a second
Berty: Peer-to-peer messaging app that works with or without internet access
Show HN: Pdoc, a lightweight Python API documentation generator
Show HN: Micro – A platform for cloud native development in Go
Show HN: Get started modding Factorio in TypeScript
Show HN: Get started modding Factorio in TypeScript
Show HN: Are you playing your violin (viola, guitar, etc.) in tune?
Show HN: Are you playing your violin (viola, guitar, etc.) in tune?
A worker owned (co-op) store for sustainable products
Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Hi HN!<p>Michel here with John, Shrif, Jared, Charles, and Chris. We are building an open-source ELT platform that replicates data from any applications, APIs, databases, etc. into your data warehouses, data lakes or databases: <a href="https://airbyte.io" rel="nofollow">https://airbyte.io</a>.<p>I’ve been in data engineering for 11 years. Before Airbyte, I was the head of integrations at Liveramp, where we built and scaled over 1,000 data ingestion connectors to replicate 100TB worth of data every day. John, on the other end, has already built 3 startups with 2 exits. His latest one didn’t work out, though. He spent almost a year building ETL pipelines for an engineering management platform, but he eventually ran out of money before reaching product-market fit.<p>By late 2019, we had known each other for 7 years, and always wanted to work together. When John’s third startup shut down, it was finally the right timing for both of us. And we knew which problem we wanted to address: data integration, and ELT more specifically.<p>We started interviewing Fivetran, Stitchdata, and Matillion’s customers, in order to see if the existing solutions were solving their problems. We learned they all fell short, and always with the same patterns.<p>Some limitations we identified are due to the fact that they are closed source. This prevents them from addressing the long tail of integrations because they will always have a ROI consideration when building and maintaining new connectors. A good example is Fivetran which, after 8 years, offers around 150 connectors. This is not a lot when you look at the number of existing tools out there (more than 10,000). In fact, all their customers that we talked to are building and maintaining their own connectors (along with orchestration, scheduling, monitoring, etc.) in-house, as the connectors they needed were either not supported in the way they needed or not supported at all.<p>Some of those customers also tried to leverage existing open-source solutions, but the quality of the existing connectors is inconsistent, as many haven't been updated in years. Plus, they are not usable out of the box.<p>That’s when we knew we wanted Airbyte to be open-source (MIT license), usable out of the box, and cover the long tail of integrations. By making it trivial to build new connectors on Airbyte in any language (they run as Docker containers), we hope the community will help us build and maintain the long tail of connectors. While open-source also enables us to address all use cases (including internal DBs and APIs), it also allows us to solve the problem inherent to cloud-based solutions: the security and privacy of your data. Companies don’t need to trust yet another 3rd-party vendor. Because it is self-hosted, it will disrupt the pricing of existing solutions.<p>Here’s a 2-minute demo video if you want to check out how it looks: <a href="https://www.youtube.com/watch?v=sKDviQrOAbU" rel="nofollow">https://www.youtube.com/watch?v=sKDviQrOAbU</a><p>Airbyte can run on a single node without any external infrastructure. We also integrate with Kubernetes (alpha), and will soon integrate with Airflow so you can run replication tasks across your cluster.<p>Today, our early version supports about 41 sources and 6 destinations (<a href="https://docs.airbyte.io/integrations/destinations" rel="nofollow">https://docs.airbyte.io/integrations/destinations</a>). We’re releasing new connectors (<a href="https://docs.airbyte.io/changelog/connectors" rel="nofollow">https://docs.airbyte.io/changelog/connectors</a>) every week (6 of them have already been contributed by the community). We bootstrapped some connectors using the highest-quality ones from Singer. Our connectors will always remain open-source.<p>Our goal is to solve data integration for as many companies as possible, and the success of Airbyte is predicated on the open-source project becoming loved and ubiquitous. For this reason, we will focus the entirety of 2021 strengthening the open-source edition; we are dedicated to making it amazing for all users. We will eventually create a paid edition (open core model) with enterprise-level features (support, SLA, hosting and management, privacy compliance, role and access management, SSO, etc.) to address the needs of our most demanding users.<p>Give it a spin: <a href="https://github.com/airbytehq/airbyte/" rel="nofollow">https://github.com/airbytehq/airbyte/</a> & <a href="https://demo.airbyte.io" rel="nofollow">https://demo.airbyte.io</a>. Let us know what you think. This is our first time building an open-source technology, so we know we have a lot to learn!
Launch HN: Airbyte (YC W20) – Open-Source ELT (Fivetran/Stitch Alternative)
Hi HN!<p>Michel here with John, Shrif, Jared, Charles, and Chris. We are building an open-source ELT platform that replicates data from any applications, APIs, databases, etc. into your data warehouses, data lakes or databases: <a href="https://airbyte.io" rel="nofollow">https://airbyte.io</a>.<p>I’ve been in data engineering for 11 years. Before Airbyte, I was the head of integrations at Liveramp, where we built and scaled over 1,000 data ingestion connectors to replicate 100TB worth of data every day. John, on the other end, has already built 3 startups with 2 exits. His latest one didn’t work out, though. He spent almost a year building ETL pipelines for an engineering management platform, but he eventually ran out of money before reaching product-market fit.<p>By late 2019, we had known each other for 7 years, and always wanted to work together. When John’s third startup shut down, it was finally the right timing for both of us. And we knew which problem we wanted to address: data integration, and ELT more specifically.<p>We started interviewing Fivetran, Stitchdata, and Matillion’s customers, in order to see if the existing solutions were solving their problems. We learned they all fell short, and always with the same patterns.<p>Some limitations we identified are due to the fact that they are closed source. This prevents them from addressing the long tail of integrations because they will always have a ROI consideration when building and maintaining new connectors. A good example is Fivetran which, after 8 years, offers around 150 connectors. This is not a lot when you look at the number of existing tools out there (more than 10,000). In fact, all their customers that we talked to are building and maintaining their own connectors (along with orchestration, scheduling, monitoring, etc.) in-house, as the connectors they needed were either not supported in the way they needed or not supported at all.<p>Some of those customers also tried to leverage existing open-source solutions, but the quality of the existing connectors is inconsistent, as many haven't been updated in years. Plus, they are not usable out of the box.<p>That’s when we knew we wanted Airbyte to be open-source (MIT license), usable out of the box, and cover the long tail of integrations. By making it trivial to build new connectors on Airbyte in any language (they run as Docker containers), we hope the community will help us build and maintain the long tail of connectors. While open-source also enables us to address all use cases (including internal DBs and APIs), it also allows us to solve the problem inherent to cloud-based solutions: the security and privacy of your data. Companies don’t need to trust yet another 3rd-party vendor. Because it is self-hosted, it will disrupt the pricing of existing solutions.<p>Here’s a 2-minute demo video if you want to check out how it looks: <a href="https://www.youtube.com/watch?v=sKDviQrOAbU" rel="nofollow">https://www.youtube.com/watch?v=sKDviQrOAbU</a><p>Airbyte can run on a single node without any external infrastructure. We also integrate with Kubernetes (alpha), and will soon integrate with Airflow so you can run replication tasks across your cluster.<p>Today, our early version supports about 41 sources and 6 destinations (<a href="https://docs.airbyte.io/integrations/destinations" rel="nofollow">https://docs.airbyte.io/integrations/destinations</a>). We’re releasing new connectors (<a href="https://docs.airbyte.io/changelog/connectors" rel="nofollow">https://docs.airbyte.io/changelog/connectors</a>) every week (6 of them have already been contributed by the community). We bootstrapped some connectors using the highest-quality ones from Singer. Our connectors will always remain open-source.<p>Our goal is to solve data integration for as many companies as possible, and the success of Airbyte is predicated on the open-source project becoming loved and ubiquitous. For this reason, we will focus the entirety of 2021 strengthening the open-source edition; we are dedicated to making it amazing for all users. We will eventually create a paid edition (open core model) with enterprise-level features (support, SLA, hosting and management, privacy compliance, role and access management, SSO, etc.) to address the needs of our most demanding users.<p>Give it a spin: <a href="https://github.com/airbytehq/airbyte/" rel="nofollow">https://github.com/airbytehq/airbyte/</a> & <a href="https://demo.airbyte.io" rel="nofollow">https://demo.airbyte.io</a>. Let us know what you think. This is our first time building an open-source technology, so we know we have a lot to learn!