HealthView OS

Visual OS for Personal Healthcare. The dashboard of your body.

Inspiration

As a doctor and surgeon, I have always wished patients would have better insights about how their body works. Like the Tesla UI where you can see your car, its vitals, insights, data and take appropriate action on time. We already have a lot of the pieces: national db, public apis, wearables, ai and machine learning, 3d visuals. Someone has to bring the pieces together to get the whole picture and take autonomous actions.

What it does

With HealthView OS, now you get the full puzzle and a smart assistant to guide you. You get a visual understanding on how your body is working, what is showing warning signs and take action appropriately to find healthcare services, expected costs, coverage and billing. Ask it how is your health. How does the cardiovascular system works, what are you allergic to, what bills are pending.

How we built it

• It is essential to start with a familiar, intuitive, minimalist design to make the user feel welcomed and not overwhelmed. So carefully designed the interface first.
• Privacy and local-first should be a priority. We have 0 data management remotely. The user owns its database/files locally with optional sync and optional encryption to the user own cloud.
• AI should enable the user to get wherever it needs in the app seamlessly through voice. We built a command layer from the start and gave the AI assistant tools to enable it to be actually helpful and take autonomous action.

Challenges we ran into

• Providers public APIs are still scarce
• Testing this is still synthetic since there is not a comprehensive synthetic patients database
• Privacy is hard when building with current SOTA AI models, local is an option but we lose capabilities

Accomplishments that we're proud of

• Web, desktop and mobile apps developed and shipped in less than one day.
• We were able to integrate lightweight 3d visuals that the AI understands
• Navigation through the app is very natural through xAI Voice API

What we learned

• Best way to avoid breaking HIPAA handling is to avoid handling PHI at all. Let user own locally its data, always ask for permission and risks, avoid server management as much as possible.
• Insurances public APIs are scarce but growing.
• It is best to build apps CLI/API first to enable coding agents and in-app agents to control the app and figure out problems on its own.
• Data should record provenance for high confidence management and analysis.

What's next for HealthView OS

• Moving from synthetic data to real patients testers
• Connecting to wearables and services apis
• Improving AI assistant insights skills

Built With

• expo.io
• openhumanatlas
• pnpm
• react
• react-native
• tauri
• three.js
• typescript