⚡ Updated 12.01.23: added post about our user centric approach to working with AI.

It is hard to “waterfall” development around language models:

On a daily basis, new research or new language models are published that could be applied to Oscar’s stack. And yet, both the fundamental capabilities and the limitations of language models aren’t fully understood by anyone, not even theoretically. This is why we chose to take an iterative approach: generate lots of use cases, test fast, build a library of what works, learn a lot, share a lot.

With that said, let’s publish.

Internally, Oscar tech, operations and business development is organized into what we call the “Oscar Program Structure”. It is the most systematic answer to the question: what are all the components you need to execute well on to manage health risk? All Oscar tech sits somewhere in this tree structure. Click into the structure, and find out how our LLM use cases support those drivers. This is a live document which will keep getting updated as we launch new use cases, pilots and features. Keep checking back and give us feedback & ideas.

Untitled Database

Key

<aside> <img src="/icons/star_blue.svg" alt="/icons/star_blue.svg" width="40px" /> Launched / Coming Soon

</aside>

<aside> <img src="/icons/wrench_blue.svg" alt="/icons/wrench_blue.svg" width="40px" /> Pilot / Prototype

</aside>

<aside> <img src="/icons/light-bulb_blue.svg" alt="/icons/light-bulb_blue.svg" width="40px" /> Idea / Exploration

</aside>

Next: Language Model Landscape