Introduction

Atomic Workspace.

A platform where clinical teams and AI agents build production healthcare apps inside an isolated digital-twin environment — and ship them straight to EHR systems without leaving the project.

01 Atomic Workspace Project 1 Project 2 Project 3 …N The platform — manages N isolated project sandboxes. 02 Project Sandbox Twins App Copilots Skills People + AI agents build inside this isolated env. 03 Deploy Pipeline Staging Production Automated deploy — virtual EHR → real Epic. CREATES SHIPS

Digital twin of production systems

Virtual FHIR CDR, Workflow Engine, Portal, Warehouse — an exact replica of prod services, scoped to one project.

Isolated environment per project

Each workspace gets its own environment with all services, so projects don't step on each other.

A team of humans and AI agents

Physicians, engineers, and coding agents (Claude Code, Codex, GitHub Copilot) work in one shared space via the ACP protocol.

Managed like a coding project

Standard TypeScript project on our framework. Automated deploy — no humans in the release loop, just review.

02 · Workspace — Sandboxes

One workspace manages N isolated project sandboxes.

One Atomic Workspace managing two isolated project sandbox environments, each with prod-service digital twins, service codebase and runtime, and copilots.

isolation

Each project gets its own environment with all services — projects never step on each other.

03 · Inside a sandbox

What's inside a single Project Sandbox.

Inside a single project sandbox: digital twins (Virtual FHIR CDR, Workflow Engine, Virtual Portal, Warehouse), Service Codebase and Runtime with the App and project source code, Copilots driven by a Coding Agent over ACP, skills/plugins/knowledge, vendor agents (Claude Code, Codex, GitHub Copilot), and knowledge bases.

app

App is a running project with backend + frontend.

agents

We don't write our own agent — we use the best on the market via the ACP protocol.

skills

Skills are where our expertise lives — reusable across projects.

04 · Deploy pipeline

Staging → Production — automated deploy.

Automated deploy from Staging to Production: the same App ships from a staging environment (virtual Portal, Workflow Engine, Warehouse, FHIR CDR, virtual EHR) to production, where it connects to a real xPortal and Epic via SMART launch and HL7v2 / FHIR.

automated deploy

  • no humans for deploy
  • just review

why a separate CDR — not Epic FHIR API

  • read-only
  • partial FHIR support

note

Staging is a digital twin with a virtual EHR. After review the same App ships to production and connects to a real Epic via SMART launch and HL7v2 / FHIR.

1 / 4