SleepEdit

What SleepEdit does

SleepEdit supports web and desktop Sleep Note editing, published protocol guidance, medication reference, offline dictation, and controlled administration.

It assists clinical documentation. It does not diagnose patients or replace clinical judgment.

Data handling

During normal editing, the working Sleep Note stays in the current browser or desktop session. SleepEdit does not persist that note in the application database.

Protocol, medication, theme, and enabled-feature settings are administrative data stored in the configured local or shared application data location.

Dictation uses a Vosk speech model loaded in the browser or desktop application. Audio is not sent to SleepEdit or to a speech-recognition provider.

AI safeguards and limits

The AI assistant is optional and controlled by an administrator. Editor text, published-protocol context, and an optional PNG screenshot are transmitted only after a user explicitly selects Ask.

Before an OpenAI request, text is screened locally by the bundled de-identification library. When screenshot analysis is enabled, OCR and redaction also run locally. No separate de-identification server or container is required. A request that fails screening or redaction is not sent. Local screening reduces risk, but it cannot guarantee detection of every identifier.

Attached screenshots are held only for the current request and are not saved by SleepEdit. Only the locally redacted image is sent to OpenAI. Image responses describe visible features and uncertainty; they are not diagnostic interpretations.

OpenAI requests use store: false. Provider abuse-monitoring retention may still apply unless the organization has separately approved different retention controls.

Do not submit protected health information without organizational approval. AI-generated content requires clinical review and must not be treated as a final clinical decision.

Security and quality evidence

SleepEdit publishes rendered results from its automated security, dependency, test-coverage, and code-quality checks. These reports provide evidence of the current measured state; they are not a guarantee that the software is free of every defect or vulnerability.

View security and quality evidence