Skip to content

Electronic health record

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical EHR
Prototype reference EHR prototype (ConnectSoft.DesignPrototypes)
Managed edition ManagedPlus (D33, D34)
Data residency tenant-region (restricted data) (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

A clinic network needs patient records, scheduling and referrals that satisfy health-data rules and work in Hebrew and English.

Product intent

A clinical record with patients, encounters, scheduling, referrals and prescriptions under restricted-data controls, RTL-first.

What the Factory makes different here: restricted classification on every clinical table; no raw content in telemetry; RTL from the UX Blueprint.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Vision Architect Agent, Security Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, database, security
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent ux, frontend, localization
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Vision Architect Agent, Security Architect Agent, Backend Developer Agent, UX Designer Agent, Frontend Developer Agent, QA Agent, Compliance Officer Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test, observability
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: security-and-compliance-workflows, research-and-ux-ui-design-workflows.

Generated product shape

C4Context
    title Electronic health record system context
    Person(user, "Users", "EHR users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Electronic health record") {
        System(ctx_Patients, "Patients", "demographics, consent")
        System(ctx_Encounters, "Encounters", "visits, notes, orders")
        System(ctx_Scheduling, "Scheduling", "slots, appointments")
        System(ctx_Referrals, "Referrals", "referrals, results")
    }
    Rel(user, ctx_Patients, "uses through the product gateway GW-07")
    Rel(factory, ctx_Patients, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Patients demographics, consent PatientRegistered
Encounters visits, notes, orders EncounterClosed
Scheduling slots, appointments AppointmentBooked
Referrals referrals, results ReferralIssued

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
API gateway connectsoft-apigateway
Clinic shell connectsoft-blazor-saas-shell
Identity connectsoft-identity
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

EHR prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

ManagedPlus with restricted-data residency; the reference lineage of DerechHaLev applies.