Vianordis
--:--:-- UTCVianordis / SUPPORT
healthcare

Aether

Beta

Aether is the GoSec Cloud clinical workspace for patient records, encounters, clinical notes, audit review, and governed AI-assisted documentation. The current release is a controlled beta and must be used only by authorized healthcare roles within the assigned tenant.

Open Aether
Beta operating manual

Aether beta clinical manual

Use the current Aether electronic-health-record beta for controlled patient and encounter workflows with strict human review.

Manual
Version 1.0
Product
Aether 0.1.0 beta
Verified
July 15, 2026
Language
English · Source
Owner
Aether clinical product and support
Source
aether · a33141d
Review cycle
45 days
Start here

Audience, scope, and prerequisites

Covers only workflows exposed and approved in the current Aether beta: patient records, encounters, notes, audit review, and AI-system governance. Scheduling, reports, advanced clinical handlers, document management, coding, decision support, and AI Scribe remain incomplete or tenant-dependent.

Who this is for

  • Authorized physicians, nurses, and clinical staff
  • Reception and administrative users with bounded access
  • Auditors, data-protection staff, and Aether support

Before you sign in

  • A clinical Aether role in the correct tenant
  • A lawful care or administrative purpose
  • A patient-identity verification procedure
  • Training and authorization for any AI-assisted clinical feature
Access model

Roles and responsibilities

RoleAccessResponsibilities
Clinical readerView permitted patients, encounters, and clinical chart sections.
  • Verify patient identity
  • Access only records required for the current purpose
Clinical writerCreate patients or encounters and update enabled clinical notes.
  • Record accurate source-attributed information
  • Review every AI-assisted statement
Administrator, auditor, or DPOUse authorized audit and AI-system governance views.
  • Investigate access proportionately
  • Document governance decisions and overrides
Workspace map

Navigation

Dashboard

/dashboard

Review enabled patient and encounter summaries.

Patients

/patients

Find or create patient records when the role permits.

Encounters

/encounters

Find, create, and review clinical encounters.

AI Scribe

/scribe

Open the controlled documentation preview when enabled.

Audit

/audit

Review authorized audit events.

AI Systems

/ai-systems

Review the current AI-system governance register.

Chapter 01

Find and maintain patient records

Use at least two approved identifiers and never create a new chart to work around uncertainty.

Procedure 1.1

Find and verify a patient

Open the intended chart only after identity and tenant checks.

  1. 1
    Confirm tenant and role

    Check the signed-in organization and that the current task is within your clinical role.

  2. 2
    Search Patients

    Use approved identifiers rather than browsing unrelated records.

  3. 3
    Verify two identifiers

    Match the organization’s required combination before opening or documenting care.

  4. 4
    Review chart context

    Check allergies, medications, problems, vitals, and recent encounters only as needed.

  5. 5
    Stop on a mismatch

    Do not edit or create a duplicate chart when identifiers conflict.

Expected result

The authorized user opens the correct patient chart and records any identity discrepancy without contaminating another record.

Procedure 1.2

Create a patient record

Create a chart only after duplicate checks and identity evidence are complete.

ForAuthorized physicianNurseAdministrator
  1. 1
    Search for duplicates

    Use name variants and approved demographic identifiers.

  2. 2
    Open New patient

    Proceed only when the role exposes the action and no existing chart applies.

  3. 3
    Enter verified demographics

    Transcribe from the approved source and minimize optional data.

  4. 4
    Review before save

    Check spelling, date values, identifiers, tenant, and contact details.

  5. 5
    Open the saved chart

    Confirm the stable patient identifier and record the provenance required by policy.

Expected result

One correctly identified patient record exists in the proper tenant without an avoidable duplicate.

Chapter 02

Document encounters

Clinical notes must reflect verified observations and accountable human judgment; beta and AI behavior does not change that duty.

Procedure 2.1

Create an encounter

Link the encounter to the verified patient and document the correct clinical context.

  1. 1
    Open the verified chart

    Confirm the patient again before choosing New encounter.

  2. 2
    Enter encounter context

    Record type, date/time, responsible clinician, reason, and other required fields.

  3. 3
    Document source information

    Distinguish patient report, observation, measurement, and clinical assessment.

  4. 4
    Review the note

    Check identifiers, medications, allergies, units, negation, and copied-forward text.

  5. 5
    Save under the approved state

    Use draft, unsigned, or final behavior exactly as exposed by the release.

Expected result

The encounter appears under the correct patient with accurate context and a known signing or completion state.

Procedure 2.2

Review AI-assisted documentation

Treat generated SOAP or scribe text as an unverified draft.

ForAuthorized clinician

Before you begin

  • Tenant AI enablement
  • Patient notice or consent where required
  • An approved clinical AI workflow
  1. 1
    Confirm AI status

    Verify that the feature is enabled, approved, and associated with the correct encounter.

  2. 2
    Generate or open the draft

    Do not assume the beta captured every speaker, term, or clinical fact.

  3. 3
    Compare with source evidence

    Check the encounter, measurements, orders, medication names, negations, and chronology.

  4. 4
    Correct or reject

    Remove unsupported content and document material corrections under the accountable clinician.

  5. 5
    Complete human review

    Do not sign or use the note for care until the designated clinician accepts it.

Expected result

Only clinician-verified content enters the patient record and the use of AI remains traceable.

Chapter 03

Review audit and AI governance

Governance views are for authorized review and should not be used for general employee or patient monitoring.

Procedure 3.1

Review an audit event

Investigate a bounded access or change question using minimum necessary data.

ForAdministratorAuditorDPO
  1. 1
    Define the question

    Record the patient, user, action, time range, and authorization for review.

  2. 2
    Open Audit

    Apply the narrowest available filters.

  3. 3
    Correlate evidence

    Compare the event with role, patient assignment, incident time, and related clinical record.

  4. 4
    Preserve findings

    Record event identifiers and conclusions without copying excess PHI.

  5. 5
    Escalate proportionately

    Follow privacy, security, or clinical safety procedures when the event remains unexplained.

Expected result

The review answers a defined question or produces a traceable, proportionate escalation.

Procedure 3.2

Review an AI system entry

Check the governance register before relying on an AI-assisted feature.

  1. 1
    Open AI Systems

    Locate the feature by name and intended clinical purpose.

  2. 2
    Review status and risk

    Confirm deployment state, high-risk classification, oversight, and available disable or override controls.

  3. 3
    Compare intended use

    Ensure the current task is within the approved purpose and population.

  4. 4
    Stop unsupported use

    Do not use a disabled, unregistered, or out-of-scope system for patient care.

Expected result

The user can show that the AI-assisted workflow is enabled, governed, and used only for its approved purpose.

Operating rules

Security and data handling

  • Treat every patient and encounter record as protected health information.
  • Use minimum-necessary access and verify two patient identifiers.
  • Never place PHI, tokens, screenshots, or full clinical notes in ordinary support tickets.
  • Require accountable human review for all AI-generated or AI-extracted clinical content.
  • Report wrong-patient access, cross-tenant visibility, or unexplained audit events immediately.
Current release

Known limitations

Read before relying on an unsupported workflow

These limits describe the source-pinned Aether 0.1.0 beta scope and must be rechecked when the product changes.

  • The source describes Aether 0.1.0 as a foundation release with the frontend and several clinical handlers incomplete.
  • AI Scribe, document management, coding, decision support, scheduling, reports, and other roadmap capabilities may be missing or non-functional.
  • The aether-v2 frontend is an isolated preview and is not cut over to the live host.
  • Visible routes do not prove a workflow is clinically validated or enabled for the tenant.
  • This manual does not establish legal authority, medical-device status, or clinical suitability.
Problem solving

Troubleshooting

You cannot sign in to Aether

Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.

  1. Open the application from the approved portal and complete sign-in again.
  2. Confirm that the correct organizational identity and tenant are selected.
  3. If access is still denied, record the time and request an entitlement check from support.

A documented action or navigation item is not visible

Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.

  1. Confirm the role and prerequisites listed for the procedure.
  2. Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
  3. Ask the product owner whether the feature is enabled for the tenant before reporting a defect.

A saved change or background operation is not visible

Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.

  1. Review inline validation, status indicators, filters, and the selected tenant or workspace.
  2. Refresh once and search for the item by its stable name or identifier.
  3. Do not repeat irreversible or externally visible actions until the original operation status is known.

A patient chart section is empty or unavailable

Likely cause: The handler is incomplete, the role cannot read it, or no data exists for that patient.

  1. Confirm patient identity and role without opening unrelated charts.
  2. Check whether the section is enabled in the current beta.
  3. Use the approved source system and escalate; do not infer a negative clinical fact from an empty beta panel.

AI-assisted text is incorrect or unsafe

Likely cause: The beta model or source context omitted, misheard, or generated material.

  1. Do not sign or use the text.
  2. Preserve a sanitized description and record the affected encounter identifier securely.
  3. Correct through the approved clinical workflow and report the model issue.
Escalation

Contact support

Contact support when

  • A repeatable Aether error blocks an approved workflow
  • Expected data, permissions, or tenant boundaries appear incorrect
  • A security, privacy, compliance, or data-loss concern is suspected
  • Wrong-patient or cross-tenant access is suspected
  • A clinical note or AI output may create patient-safety risk
  • Audit or AI-governance state is inconsistent

Include

  • The page, action, and expected result
  • The exact error text and time of occurrence, including time zone
  • Your tenant, role, browser, and a sanitized record or item identifier
  • Whether the problem can be reproduced and which troubleshooting steps were tried

Never include

  • Passwords, access tokens, API keys, recovery codes, or session cookies
  • Unredacted personal, health, financial, or other regulated data
  • Private encryption keys or complete confidential documents unless an approved channel is provided
  • Patient names, national identifiers, diagnoses, full encounter text, or other PHI in an unapproved ticket
Contact support