Definition, boundaries, and system composition
A sleep lab data workstation is a clinical computing platform for receiving, organizing, retaining, retrieving, and reviewing polysomnography and associated study data. A deployment commonly includes supported computer hardware, displays, workstation software, a database or indexing service, network interfaces, and storage connections. It manages raw physiological waveforms, device configuration, calibration information, event annotations, technologist notes, and references to synchronized audio and video. Its central purpose is to let authorized users start from a patient and study identity, return reliably to the complete source record, and trace what happened to that record afterward.
This category is not the amplifier or acquisition box. Front-end equipment converts sensor inputs into digital data, whereas the workstation receives and governs those data. Nor is it the synchronized-video system in entry 750, whose defining task is alignment of audio-video with waveforms. Compared with the PSG reporting workstation in entry 752, this entry emphasizes the data foundation, clinical review, and record governance; a reporting workstation emphasizes statistical summaries, physician interpretation, signing, and distribution. One product may combine all of these functions, but acceptance testing still needs to separate them.
An ordinary personal computer, remote desktop, or shared network folder does not become a qualified workstation merely because a viewer is installed. The complete configuration should identify the supported operating system, processor and memory, graphics hardware and displays, client and server versions, database, network, storage, backup method, identity service, and compatible acquisition systems. Where functions are medical-device software, the intended use, target population, automated-analysis scope, and operating environment must match the actual deployment.
Data intake, identity binding, and study state
When a workstation receives a live stream, a completed acquisition, removable-media import, or server migration, it should verify the patient identifier, study identifier, bed, date, study type, acquisition device, and source. Similar names, temporary identifiers, duplicate registrations, room changes, repeated acquisitions, and outside imports can all produce misassociation. A stable internal identifier and a controlled matching workflow are preferable to treating a filename, folder location, or a technologist's memory as the sole identity control.
Study states should distinguish created, receiving, interrupted, acquisition complete, awaiting quality review, scoring, reviewed, locked, archived, and export complete. A client may continue displaying cached waveforms after a network interruption, which does not establish that data were committed to durable storage. A file on disk likewise does not establish that the database index, video association, and every channel are complete. Recovery should detect gaps, duplicates, out-of-order blocks, and orphaned attachments instead of treating a repeat import as a new complete study.
Merging, splitting, correcting identity, or reversing a mistaken import are high-risk operations. They should be permission controlled, independently checked where appropriate, and preserve the previous relationship, operator, time, reason, and affected objects. If the erroneous record has already been scored, referenced, or reported, the correction process should notify downstream users and identify derived results that require recalculation or withdrawal. Removing a study from the active list does not necessarily erase every copy, while hiding it must not defeat a lawful or policy-based retention obligation.
Raw data, timelines, and interoperability
The source record is more than the curve visible on a screen. It includes each channel's sampling rate, unit, range, gain, polarity, filtering, sensor or derivation label, start and stop times, discontinuities, calibration, and device version. The workstation should preserve enough semantics to reconstruct the clinical display and distinguish processing applied during acquisition from settings adjusted only for review. Changing display sensitivity or filters should not silently rewrite original samples. Resampled, artifact-reduced, or derived channels should identify their algorithm, parameters, source, and version.
Data from multiple sources need a traceable common timeline. Server-arrival time, file-modification time, and workstation display time are not substitutes for acquisition time. Time zones, daylight-saving changes, clock corrections, and reconnections must not create unexplained reversals or overlaps. Waveforms, annotations, position, device logs, and audio-video references should remain aligned across the whole night, with uncertain intervals visibly marked. Successful navigation from an event to a video frame demonstrates an index lookup, not proof that end-to-end synchronization was validated.
Proprietary formats, EDF or EDF+, DICOM waveforms, and hospital interfaces preserve different sets of meaning. Opening a file does not show that patient identity, labels, units, polarity, discontinuities, annotation layers, video references, and edit history can make a lossless round trip. Procurement and migration testing should import, export, and re-read representative studies, documenting unmapped fields and transformation rules. A printed report, summary export, or downsampled trace must be identified as such and not represented as a complete source study that remains suitable for rescoring.
Display, retrieval, and review performance
Clinical review should support whole-night trends, standard scoring windows, and detailed magnification while keeping channel names, laterality, units, polarity, sensitivity, time base, and filter state visible. A narrow window, multi-display scaling, operating-system scaling, or remote session can change pixels per second and the appearance of small waveforms. Acceptance is therefore more than confirming that a monitor turns on: known signals should be used to check amplitude, time, and channel order, and the design should be assessed for color use, type size, contrast, and color-vision differences.
Zooming, panning, rapid browsing, event navigation, and synchronized-video review must distinguish loading, missing data, and the true end of a record. Caching or network congestion may freeze a trace, skip forward, or first show a low-resolution proxy; stale content must not continue to appear live. Opening, scrolling, jumping, and saving should be measured with long studies, dense annotations, multiple videos, and concurrent users. Performance degradation must not silently omit samples, suppress events, or shift their alignment.
Search may use patient, study date, procedure, state, clinician, or laboratory, but results must not collapse namesakes, repeat studies, or test records into one case. Thumbnails and trends are navigation aids, not substitutes for source-waveform review. Remote review also requires control of client version, display quality, bandwidth, session interruption, and input latency. Seeing results in a browser does not prove that the remote interface has the same complete functions or validated presentation as the local workstation.
Annotation, scoring, and clinical workflow
A workstation may provide manual event annotation, sleep staging, measurement cursors, rule checks, and computer-assisted scoring. Automated output should retain the source algorithm, version, configuration, execution time, and intended scope, and it should be examined and edited by appropriately qualified personnel. A high-confidence label, colored prompt, or statistical summary cannot replace inspection of the underlying signals. Unanalyzed intervals, missing channels, and inadequate quality should be exposed rather than silently classified as normal or excluded from denominators.
Each manual change should identify its author, time, object, and state and, where needed, preserve the prior version or a reconstructable audit record. Technical observations, algorithmic suggestions, formal scoring, and physician interpretation are separate layers whose authorship should survive export and merge operations. Collaborative work needs record locking, conflict management, handoff, and review. A later save must not silently overwrite another user's changes; revision of a locked study should follow a controlled process that creates a new traceable version.
The workstation may calculate total sleep time, indices, and trends for a downstream report, but those numbers depend on sleep time, event definitions, excluded intervals, and denominator rules. When data are passed to a reporting system, the study version and scoring status should accompany them so a report cannot unknowingly cite an earlier score set or unfinished record. Final diagnosis, clinical interpretation, electronic signature, and report distribution remain responsibilities of authorized professionals and the reporting workflow; they are not completed merely because a workstation includes automation or templates.
Security, availability, and data governance
PSG waveforms, audio-video, and technical logs can identify a patient and may reveal exceptionally sensitive bedroom behavior and speech. Role-based least privilege should govern viewing, editing, exporting, deleting, account administration, and remote access. Individual authentication should replace shared accounts, and important access and changes should be logged. Screen placement, automatic locking, portable media, screenshots, printing, service access, and copies in test environments all require governance. Removing a name does not necessarily anonymize a night of video, audio, and physiological signals.
Networked workstations require management of operating-system and application patches, malware defenses, ports and services, encryption, certificates, remote support, third-party components, and vulnerability response. Security updates should not be placed blindly into production, but compatibility concerns do not justify remaining indefinitely on unsupported software. Representative testing, a rollback plan, and documentation of residual risk are needed. Once a laboratory network connects multiple medical devices, safety, clinical effectiveness, and security become shared system risks rather than the responsibility of a single vendor alone.
A local disk, server replica, backup, and long-term archive are different states. Capacity monitoring, integrity checks, retention and disposal policies, offline or otherwise protected copies, restore authorization, and recurring restoration exercises should cover databases, source files, annotations, configuration, video associations, and audit records. During planned downtime, power loss, database failure, or ransomware, the laboratory needs conditions for continued acquisition, temporary documentation, recovery-point and recovery-time objectives, and reconciliation of data created during the outage. The data workstation itself is generally not a patient life-safety alarm.
Acceptance, migration, and lifecycle management
Commissioning should start from intended use and risk and use representative PSG records with known content, including different sample rates, long studies, absent channels, discontinuities, extreme amplitudes, dense annotations, synchronized video, and multiple concurrent beds. Tests should cover identity creation, live intake, confirmation of durable storage, amplitude and time accuracy in review, event saving, automation limits, search, permissions, audit, export, backup restoration, and reconnection after failure. A single demonstration study or factory test does not qualify the local combination of server, network, identity service, and workflow.
Software upgrades, server replacement, storage migration, interface changes, and algorithm updates can alter display, calculations, or record relationships. Before change, the affected scope, backup, and rollback conditions should be set. After change, a fixed test set should compare channel semantics, event counts, indices, timelines, video navigation, and exports. Older studies must remain readable throughout their retention period. If access depends on discontinued software or a licensing server, a read-only environment, standardized export, and verifiable migration should be planned before a hardware failure makes decoding impossible.
Ongoing management includes performance trends, capacity forecasts, failures and near misses, anomalous access, vulnerabilities, patch state, user training, and vendor-support dates. Procurement should obtain architecture documentation, a compatibility matrix, data dictionary, export description, backup and restoration method, known limitations, and a retirement plan. The decisive questions are whether patient and study identity remain trustworthy, the source data stay complete and interpretable, modifications are traceable, authorized users can obtain records when needed, and faults or changes are discovered and controlled before they cause clinical harm.