// Orbital continuity engine + multi-access diagrams
function Architecture() {
return (
System architecture · Continuity Engine
One intelligence layer. Six connected motions.
Jessie is not a diagnostic AI. It is a continuity loop — six operations running between every encounter, each one built for auditability, configurability, and integration with the workflows the ED already uses.
);
}
function OrbitalDiagram() {
const [hovered, setHovered] = React.useState(null);
const nodes = [
{ id: 'collect', label: 'Collect', angle: -90, body: 'Conversational check-ins via app, facility device, or SMS. Voice, text, or tap. Configurable prompts.' },
{ id: 'compare', label: 'Compare', angle: -30, body: 'Every new response is compared against the patient\'s prior state — triage, previous check-ins, EHR baseline.' },
{ id: 'detect', label: 'Detect change', angle: 30, body: 'Meaningful change is defined by the organization: pain deltas, new symptoms, LWBS intent, custom thresholds.' },
{ id: 'structure', label: 'Structure', angle: 90, body: 'Natural language becomes structured data — codified against the organization\'s existing schema.' },
{ id: 'route', label: 'Route', angle: 150, body: 'Change is delivered into the configured workflow — priority queue, escalation, notifications, EHR entry.' },
{ id: 'followup', label: 'Follow-up loop', angle: 210, body: 'The loop closes and re-arms. Cadence adapts based on acuity, elapsed time, and prior response.' },
];
const R = 240; // orbit radius
const cx = 400, cy = 400;
return (
{/* Node detail on hover — floating panel */}
{hovered ? nodes.find(n => n.id === hovered).label : 'Hover a node to inspect'}
{hovered ? nodes.find(n => n.id === hovered).body : 'Each operation is auditable, configurable per organization, and integrates with existing systems.'}
The app is the primary surface. Continuity shouldn't depend on a patient owning a phone — Jessie also runs on shared facility devices and secure SMS. All three connect to the same continuity engine, which speaks to the customer's existing Epic estate through published integration surfaces.
{/* ────── Three-lane architecture ────── */}
{/* Target-architecture status callout */}
Status · Read this first
Proposed target architecture. No Epic environment connected to date. Designed with HIPAA-aligned safeguards; BAA at contracting.
{/* Lane headers */}
Atronics · Jessie platform — vendor side} />
{/* Lane content */}
{/* ────── LANE 1: PATIENT SURFACES ────── */}
{/* ────── LANE 2: JESSIE PLATFORM ────── */}
Collect → compare vs. prior state → detect meaningful Δ → structure to FHIR → route to care team
{/* How the change gets detected — two-layer stack */}
Symptom extraction + rationale trace on free text · fine-tuned open-weights or BAA'd API, per deployment
Runtime
On-prem inference OR BAA'd vendor · PHI never leaves the tenant boundary
Guardrail: no autonomous action. Rationale trace on every update; human review required on the Epic side. Red-flag symptoms bypass In Basket and page a nurse directly.
}
/>
{/* ────── LANE 3: EPIC EHR ────── */}
{/* ────── Six-step path strip ────── */}
The path, in six steps
{/* Footer note — matches the reference sample */}
Epic-side components (G–L) reflect published Epic developer documentation, Aug 2026 · Jessie components (A–F) are Atronics' own design and not independently verifiable · Target state, not a live integration
);
}
/* ────── Sub-components for the architecture diagram ────── */
function LaneHeader({ label }) {
return (