Care Plan and Care Team Infrastructure

This points to Zus trying to replace the basic unit of healthcare software. Traditional systems are organized around billable events, one visit, one note, one claim. Zus is organizing work around an ongoing treatment plan and the people responsible for it, which matters for virtual care companies that manage patients across messages, follow ups, referrals, labs, and specialist handoffs, not just a single office visit.

• That changes what the software needs to do. Instead of mainly documenting an encounter after it happens, the system has to assign tasks, route updates, track unresolved issues, and let multiple clinicians act on the same patient journey over time. Zus pairs this workflow layer with a unified patient record that pulls medications, labs, history, and social data into one place.
  1 sacra
• The target customer is not a hospital buying another rigid module. It is a digital health builder creating its own care experience. That is why Zus emphasizes APIs alongside user interfaces, and why it talks about a headless EHR path, meaning the data and workflow engine can sit underneath a custom patient and clinician experience.
  1 sacra 2 zushealth
• The bigger ambition is cross company care coordination. One Medical works as a primary care home base, while Oshi staffs GI specialists, dietitians, behavioral clinicians, and care coordinators around digestive care. Zus is aiming to make those separate providers feel like one extended care team instead of disconnected vendors exchanging faxes and PDFs.
  1 sacra 3 time 4 oshihealth 5 beckersasc

If this model works, healthcare software moves closer to a shared operating layer for continuous care. The winners will be platforms that can turn fragmented specialist, primary care, and virtual programs into one coordinated workflow, with data, tasks, and accountability moving cleanly across organizational boundaries.