One host, one lab data directory#
The application serves a browser interface from a local Node.js host. The chosen data directory stores the lab’s configuration, database and related artifacts. Keep the same directory and profile when restarting. A different directory is a different lab; the public website does not store or restore your local data.
Obtain the application build and its start instructions from the project owner. The developer download contains the Apache SDK and examples, not the complete proprietary application or a production installer. Public npm availability is not assumed.
Accounts and permissions#
Use the administrator’s issued account or owned host setup flow. No default credentials are published here. The navigation shows pages your account may open; a direct URL does not grant extra permission. Facilitator, technician and administrator roles have different authority. Keep administrator links/tokens out of learner invitations, videos and support bundles.
Sign out on shared computers. A local host URL, profile name and account identity matter when troubleshooting an apparent empty lab. Check them before importing data again.
Model providers and keys#
AI extraction, optional debrief drafting and transcription use separately configured capabilities. A provider endpoint, supported API shape and model must match. Configure approved credentials through the host’s key/settings controls or the administrator’s secret reference mechanism. The authoring key panel describes whether entered keys last only for the current server session; follow that displayed lifetime.
The local app can retain source material and provider history. Review the input disclosure before sending source text, code, audio or learner information externally. Put no real patient data into this demonstration. Provider prices, quotas and terms belong to the selected provider; a successful local UI check is not a guarantee about them.
Site configuration#
Use Lab administration → Site to configure rooms, stations, units, visible EPR fields and debrief section order where enabled. Export the site before making substantial changes. Inspect validation and compatibility after importing a changed profile. A site import does not approve clinical values or install an absent plugin automatically.
Backups and recovery#
Use the host’s documented backup/restore controls and retain the backup in an access-controlled location. A backup may contain scenarios, learner/session data, recordings and sensitive configuration. Credential protection can depend on the operating-system account; copying protected bytes to another account may require reconnecting services rather than revealing old secrets.
Stop the owned host normally before maintenance that requires it, and verify restore into a separate owned directory first. Do not delete the active data directory or replace a running lab with a developer checkout. Restoring a reference cannot undo arbitrary side effects already performed by an enabled plugin.
Network and device access#
Loopback operation is the default developer path. Access from another machine requires the real listening address, firewall/network permission and, for secure browser features, HTTPS and trust. Configure the narrow addresses the lab needs. Do not install a system certificate or expose a host publicly merely to dismiss a browser warning.
Windows/Chrome and Linux local MVP evidence is available. Actual Safari/iPad, macOS, external OAuth/registry operation, clinical approval and general release gates remain open. A browser window resized like an iPad does not qualify an actual iPad.
Troubleshooting#
| Symptom | Check first |
|---|---|
| Browser cannot connect | Is the owned host running, and is the URL the one it printed? Check listener/address before changing data. |
| Sign-in unavailable | Confirm account/role with the host administrator. No shared password is supplied by this website. |
| Pages or commands missing | Check role and enabled profile contributions. A declared service type is not an active provider. |
| AI fails after restart | Read key lifetime and provider settings. Re-enter a session-only key using the host control if needed. |
| Disk fills | Keep builds and test artifacts separate from live lab data; back up before cleanup. |
| Plugin change blocked | A running or paused session can block ordinary Store changes. End it deliberately or use only the documented emergency disable route. |