Administrator workspace
Bed configuration holds admission locations, bed types, and tags used by bed management screens. Patient registry accepts a CSV for bulk staging (browser-only in this demo). Data & storage records per-domain plans (REST, Excel paths, Google Sheets) for your integration layer. Backup, Security, and Email templates (HTML + preview) live in localStorage for governance and integration. Users & roles includes Add user for mock provisioning.
Operational modules (registration, scheduling, live bed board) stay on the hub; this console is for reference data and governance.
Users & roles
Mock directory for the demo. Add rows below; production should call your IdP / HR feed.
| Name | Role | Typical access | Status |
|---|
Bed configuration
Reference lists for admission locations, bed types, and tags. Stored in session storage for this demo.
Admission locations
Wards or logical units that appear when assigning beds (e.g. Medical ward — East).
| Location name | Code |
|---|
Bed types
Standard bed categories (isolation, ICU, bassinet, etc.).
| Type name |
|---|
Bed tags
Labels for capacity planning or infection control (e.g. oxygen, negative pressure).
| Tag | Color hint |
|---|
Patient registry — CSV import / export
Download a template, fill rows offline, then upload. Data stays in this browser session only.
No file loaded yet.
| patient_id | family_name | given_name | gender | dob |
|---|
Audit log
Demo events from this admin page and page load. Cleared if you clear site data.
Inventory policy
Same settings as Finance → Inventory policy (localStorage). Changes here apply to inventory policy behavior (par outlook, zones, defaults).
Data & storage (by domain)
Describe where each part of MedHealth should read and write data in production. Nothing here auto-connects in this demo — your bridge script, desktop agent, or backend reads localStorage key medhealth_data_connectors (or use Copy all domains JSON). In low-connectivity settings, published CSV URLs from Google Sheets and scheduled Excel exports are often the most practical stepping stones before a full SQL cluster.
REST API
Point to your gateway or FHIR facade. Do not paste live secrets into this demo — note where tokens live (env, vault).
Excel & desktop files
Works well when the site runs on a LAN share or a clerk exports nightly from a ward PC. Path can be relative to the web root, a UNC path, or a reminder label for USB sync folders.
Google Sheets
CSV URL is the lightest option on slow links (File → Share → Publish to web, or an Apps Script doGet that returns CSV). Sheets API suits always-on servers with service accounts.
SQL / ODBC / HMIS bridge
Use for national reporting DBs or hospital SQL — store a label or DSN name; credentials belong in your secure runtime, not in this browser demo.
MediQuery (browser client)
Configures the MediQuery page in this browser via medhealth_mediquery_config. Set optional CSS and which datasets and loaders staff may use. Leave Quick Connect in default to keep the built-in WHO and sample list.
kind: who, worldbank, sample (sampleKey: disease|capacity|vaccines), url (url, jsonPath, datasetName).
Load dataset modal — uncheck to hide a source
Laboratory (LIS-style demo)
Controls copy and accession prefix on lab.html. The worklist uses medhealthLabQueue in localStorage (same browser as Clinical laboratory orders). This is not a certified laboratory information system.
Letters/numbers only, up to 6 characters (e.g. MH → MH-00001).
Clinicians pick from this list (plus favorites) and build a panel per patient before sending one requisition to the lab queue.
Backup & retention
Describe how this facility should be protected. This demo only saves a checklist in localStorage under medhealth_backup_config — your backup agent, OS scheduler, or cloud console performs the real work.
Destination
Scope (what to include)
Encryption & verification
Cloud object storage (optional)
For S3-compatible, GCS, Azure Blob — credentials stay in your runner, not in this browser.
Database dumps
Security & compliance (advanced)
Policy targets for identity, transport, application hardening, audit, and incident response. Saved as medhealth_security_config in localStorage — this static demo does not enforce them; your IdP, reverse proxy, and app servers must. Use Copy JSON for security review or SOA attachments.
Identity provider & MFA
Sessions & password policy
Transport, TLS & network edge
Application headers, CORS & APIs
Audit, PHI access & break-glass
Data classification & encryption at rest
Vulnerability management & incident response
Endpoints & MDM
Standard email templates (HTML)
Compose patient- and staff-facing messages with merge tags. The preview column shows how the letterhead and body look with sample data. Production sends should use an absolute HTTPS logo URL so inboxes can load the image.
Tip: Use Save template before switching templates. Letterhead and the source below are saved with Save template or Save letterhead.
HTML — body markup or full document. CSS — optional; merged into <head> for preview and downloads.
Merge tags: {{logoUrl}} {{facilityName}} {{patientName}} {{patientFirstName}} {{appointmentDate}} {{portalLink}} {{amountDue}} {{invoiceNumber}} {{supportEmail}} {{labDepartment}} {{resetLink}} {{staffName}} {{surveyTypeLabel}} {{surveyIntro}} {{surveyLink}} {{surveyClosing}}
Templates show this logo beside the facility name. Clear the field to use the default hub icon in this browser preview. Production inboxes need a public https:// image URL.
Facility settings
Organization name and maintenance banner use session storage (this tab). Contact addresses, SMTP (outbound), and page backgrounds use localStorage for this browser. Static HTML cannot open real SMTP sockets — your server or relay must send mail using the saved profile (medhealth_smtp_config).
Contact & notification emails
Used for labels and future notification hooks (demo). Not sent anywhere until you wire a backend.
Outbound email (SMTP)
For production, keep credentials in a vault or environment variables — this demo stores them in the browser for integration testing only. A real Test send requires your mail gateway (Node, PHP, etc.).
Page backgrounds
Light, semi-transparent mascot or custom image behind selected HTML pages. Put PNGs under assest/, enter a path relative to the site root, or upload an image (stored as data in this browser’s localStorage only).
Use this shortcut to edit login.html background settings quickly.
JPEG/PNG/WebP/GIF — large files are scaled down before save. If save fails, try a smaller photo (localStorage limit).
Position sliders use −50% to 150% (background-position). Custom and Tile use the scale slider; Cover / Contain / half splits use layout keywords (position still nudges framing).
Adjust sliders above; save when it looks right.