Reduce documentation burden
The ambient scribe workflow is designed around patient consent, transcription, generated SOAP notes, and clinician review before finalization.
Vianordis--:--:-- UTCVianordis / ED. 02 / 2026
§ 07 — App support
Aether
AI-native clinical records for healthcare teams that need control, auditability, and EU-first governance.
Aether gives clinics and care organizations a governed EHR foundation for patient records, encounters, SOAP documentation, consent workflows, AI oversight, and audit-ready clinical operations without treating compliance as an afterthought.
01 — Problem
Clinical teams are squeezed between documentation workload, AI risk, and regulatory pressure.
Healthcare providers need faster documentation and better clinical workflows, but patient data, AI recommendations, consent, access, and audit obligations cannot be handled like ordinary SaaS data. Legacy EHRs create friction, while generic AI tools create governance and residency risk.
- Clinicians spend too much time documenting encounters instead of focusing on patients.
- Patient records, notes, consent, and audit trails are often split across disconnected tools.
- AI scribe and decision-support tools are difficult to prove, disable, override, or explain.
- GDPR data subject rights and consent requirements create manual administrative work.
- EU AI Act requirements demand transparency, decision logging, human oversight, and stop controls.
- Healthcare organizations need EU-first deployment options without losing interoperability.
02 — Solution
Aether brings clinical records and AI governance into one healthcare workspace.
Aether combines a clinical web application, a Go/Fiber API, PostgreSQL healthcare schemas, Keycloak identity, GDPR consent workflows, and EU AI Act control surfaces. It is built for a phased path from core EHR foundations to AI-assisted documentation and clinical decision support.
- Patient and encounter workflows provide the operational base for clinical documentation.
- SOAP notes, encounter signing, and lock states support reviewed clinical records instead of ungoverned drafts.
- Consent, data subject request, and audit structures support privacy operations from the data model upward.
- AI systems, decisions, overrides, and kill switches give clinical AI a visible governance layer.
03 — Benefits
Healthcare software that starts with the regulatory reality.
Aether is designed for clinics, healthcare operators, and regulated teams that want AI-assisted records without hiding the controls clinicians and DPOs need.
Keep clinicians in control
AI outputs are treated as assistive recommendations with human review, override capture, and stop controls rather than autonomous clinical authority.
Support GDPR operations
Consent purposes, patient consent records, data subject requests, and audit logs are part of the platform foundation.
Prepare for EU AI Act governance
High-risk AI systems can be registered, monitored, disabled, and reviewed through dedicated AI oversight surfaces.
Unify patient context
Patients, encounters, notes, vitals, problems, medications, allergies, providers, and organizations share one clinical data model.
Deploy in controlled environments
The architecture is built for Kubernetes, PostgreSQL, Keycloak, Infisical-managed secrets, and EU-first infrastructure patterns.
04 — How it works
From patient context to reviewed clinical record.
- 01
Identify the patient and care context
Users sign in through Keycloak, work inside their organization context, and search or create the patient record before documentation begins.
- 02
Document the encounter
Clinicians create encounters, record SOAP notes, review vitals and clinical context, and optionally start an AI scribe workflow with consent.
- 03
Review, sign, and audit
Clinical notes are reviewed before signing, AI decisions can be logged or overridden, and compliance teams can inspect consent, DSR, and audit records.
05 — Features
What teams can actually do in Aether.
Patient registry
Create, search, update, and view patient records with MRN, demographic, contact, language, status, and organization context.
Clinical patient view
Review clinical summaries, encounters, problems, medications, allergies, and vital-sign context from one patient workspace.
Encounter workflow
Create encounters, document SOAP notes, update encounter notes, sign records, and lock completed clinical documentation.
AI ambient scribe workflow
Guide clinicians through consent, recording, transcription, generated notes, and provider review with EU AI Act oversight messaging.
AI systems registry
Track registered AI systems with risk level, MDR class, status, model information, accuracy notes, decision counts, override counts, and stop controls.
Human oversight controls
Expose override capability, kill-switch patterns, human review requirements, and automation-bias warnings for high-risk AI workflows.
GDPR consent management
Manage consent purposes, patient consent grants and withdrawals, legal basis fields, expiry metadata, and consent audit context.
Data subject request workflow
Support access, status tracking, and processing workflows for GDPR data subject requests through dedicated API and schema foundations.
Audit-ready API foundation
Use health, patient, encounter, consent, DSR, AI system, AI decision, enable, disable, and override endpoints as the platform control surface.
06 — Architecture
Architecture and security model.
Aether separates clinical user experience, API policy, identity, records, AI oversight, and operations so healthcare workflows can be governed deliberately.
- Next.js and React provide the clinical dashboard, patient workspace, encounters, AI scribe page, reports, settings, and AI systems UI.
- A Go/Fiber API exposes health, patient, encounter, consent, data subject request, AI system, AI decision, enable, disable, and override endpoints.
- PostgreSQL stores shared admin users plus Aether healthcare tables for organizations, providers, patients, encounters, notes, clinical data, consents, scribe sessions, AI systems, AI decisions, and audits.
- Prisma models the frontend-facing clinical schema while the API uses service layers for patients, encounters, consent, AI, and audit workflows.
- Keycloak and NextAuth connect users to organization context and map FreeIPA groups into physician, nurse, admin, DPO, auditor, operator, and user roles.
- GDPR structures cover consent purposes, patient consents, data subject requests, legal basis fields, and processing audit metadata.
- EU AI Act structures cover high-risk AI system records, decision logging, human override, enable and disable workflows, and scribe-session consent state.
- Kubernetes deployment, PostgreSQL HA, Infisical-managed secrets, and internal service URLs support controlled platform operations.
07 — Use cases
Where Aether fits.
Primary-care documentation
Give clinicians a patient and encounter workspace for routine visits, SOAP notes, follow-up plans, and reviewed documentation.
AI scribe governance
Introduce ambient documentation with patient consent, clinician review, AI transparency, decision logging, and stop controls.
Healthcare privacy operations
Support DPO teams with consent records, data subject request workflows, audit trails, and GDPR-oriented processing metadata.
Clinical AI oversight
Track high-risk AI systems, active or disabled status, documented limitations, overrides, and human review requirements.
Multi-provider clinical records
Model organizations, providers, patients, encounters, and clinical context in a shared tenant-aware records foundation.
Phased EHR modernization
Start with patient and encounter foundations, then expand into documents, clinical data handlers, decision support, and interoperability.
08 — Integrations
Built for the healthcare platform stack.
Aether uses standard identity, data, API, deployment, and AI infrastructure so healthcare teams can operate it inside controlled environments.
Keycloak
Keeps access tied to organization accounts, roles, and sign-in policy.
NextAuth
Shows how this service fits into the wider Vianordis environment instead of standing alone.
FreeIPA groups
Shows how this service fits into the wider Vianordis environment instead of standing alone.
PostgreSQL
Stores structured service records in a controlled tenant-aware backend.
Prisma
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Go Fiber
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Next.js
Shows how this service fits into the wider Vianordis environment instead of standing alone.
React
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Kubernetes
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Infisical
Shows how this service fits into the wider Vianordis environment instead of standing alone.
GSC AI Hub
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Whisper
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Ceph RGW
Provides the governed place where service data and files are stored.
FHIR roadmap
Shows how this service fits into the wider Vianordis environment instead of standing alone.
09 — Trust
Designed around clinical accountability.
Aether treats medical data and AI decisions as governed records with identity, consent, audit, and human oversight requirements.
Identity
Keycloak authentication connects users to organization context and mapped clinical roles.
Role separation
Physician, nurse, admin, DPO, auditor, operator, and user roles support differentiated access.
Consent
Consent purposes and patient consent records include legal basis, explicit consent, grant, withdrawal, and expiry fields.
DSR workflow
Data subject request endpoints and schema support GDPR request intake and status tracking.
AI logging
AI decision records are designed for high-risk system traceability, confidence, recommendations, and override state.
Human oversight
High-risk AI workflows emphasize clinician review, override capture, stop controls, and automation-bias warnings.
Clinical record state
Encounter signing and lock fields support reviewed records instead of silently mutable notes.
Operational secrets
Infisical-managed secrets and Kubernetes deployment patterns keep credentials out of application code.
10 — Pricing
Pricing based on clinical scope, deployment model, and AI governance needs.
Aether is sold as part of the GoSec Cloud application suite. The right plan depends on provider count, deployment model, compliance responsibilities, AI scribe usage, data migration, integration scope, and whether the customer needs cloud, on-premises, or hybrid operation.
11 — FAQ
Questions technical buyers usually ask.
Who is Aether for?
Aether is for healthcare providers and regulated clinical teams that need patient records, encounter documentation, AI assistance, consent management, and auditability in a controlled environment.
Is Aether only an AI scribe?
No. The scribe is one workflow inside a broader EHR foundation that includes patient records, encounters, notes, consent, DSR, AI oversight, and audit structures.
Does Aether replace clinician judgment?
No. AI outputs are positioned as draft support or recommendations. Clinicians must review, edit, override, or stop AI-assisted workflows before relying on them clinically.
How does Aether handle GDPR needs?
Aether includes consent purposes, patient consent records, data subject request workflows, legal-basis fields, audit logging, and privacy-oriented patient metadata.
How does Aether support EU AI Act oversight?
Aether models AI systems, high-risk status, decision logging, human overrides, disable and enable controls, transparency warnings, and review requirements.
What clinical data is modeled?
The current schema covers organizations, providers, patients, encounters, encounter notes, problems, medications, allergies, vitals, documents, scribe sessions, consents, AI systems, and AI decisions.
Can Aether run in controlled infrastructure?
Yes. The architecture is built around Kubernetes, PostgreSQL, Keycloak, internal service URLs, and Infisical-managed secrets, with cloud, on-premises, and hybrid deployment patterns in scope.
Is every planned EHR module complete today?
No. Aether is being built in phases. The product foundation covers core records, encounters, consent, AI oversight, and UI/API scaffolding, with deeper clinical modules and interoperability continuing through the roadmap.
12 — Next step
Build clinical AI on records, consent, and oversight from the start.
See how Aether can give your healthcare team an EU-first foundation for patient records, clinical documentation, AI scribe governance, and compliance-ready operations.