Running a Flawless Diagnostic PSG

A "flawless" study does not mean nothing goes wrong; things always do. It means you run a disciplined process, catch and handle what arises, keep the patient safe, and produce a clean, well-documented, scorable record. That is entirely achievable, and it comes from routine and judgment rather than heroics.

One boundary frames this entire chapter: you are a technologist, not the ordering physician. Throughout, you follow the physician's orders, your lab's policies, your emergency protocols, your employer's rules, and your scope of practice. Nothing in this book is an instruction to independently diagnose or treat. Your job is to acquire an excellent study, recognize problems, and escalate correctly — not to practice medicine on your own authority.

In this chapter you will learn to:

• Describe a diagnostic PSG and the technologist's role from arrival to discharge.

• Review orders, verify patient identity, and gather the pre-study history.

• Perform biocalibrations and start the study correctly at lights-out.

• Monitor signals and recognize respiratory events, limb movements, sleep/wake transitions, and poor data quality during acquisition.

• Judge when to intervene and when not to over-intervene.

• Recognize urgent medical concerns and escalate them per protocol and scope.

• Complete the morning process and write documentation that protects everyone.

What a diagnostic PSG is

A diagnostic polysomnogram is the standard overnight sleep study whose purpose is to gather information for a physician to diagnose a sleep disorder. The word "diagnostic" distinguishes it from a titration study (Chapter 11), where therapy like PAP is applied and adjusted. On a diagnostic night, you are not treating; you are recording — capturing a clean, complete picture of how the patient sleeps and breathes so the physician can interpret it later. Keeping that purpose in mind clarifies your role: your success is measured by the quality and completeness of the data and the safety of the patient, not by any treatment.

The technologist's role from arrival to discharge

Think of the night as an arc with distinct phases: reception and preparation, setup and calibration, acquisition (the long monitoring stretch), and the morning wrap-up. Across all of them you are simultaneously a caregiver, a data-acquisition specialist, and a safety monitor. The figure below maps the whole arc; the sections after it walk through each phase.

Figure — Horizontal workflow diagram with sequential stages: review orders, greet and identify patient, pre-study questionnaire and history, hookup, biocalibration, lights-out, overnight monitoring and documentation, lights-on and morning process, takedown and discharge, final documentation.

Figure 8.1 The full arc of a diagnostic night, from patient arrival through setup, calibration, monitoring, and the morning process to discharge and final documentation.

Before the patient sleeps

Reviewing orders. The night begins with the physician's order. Before anything else, read it and understand what study is ordered (diagnostic, titration, split-night, MSLT to follow, etc.), any special instructions, montage or sensor requirements, and any patient-specific notes. The order is your authority and your roadmap; running the wrong study is a serious error. If an order is unclear or seems inconsistent, clarify it through the proper channel rather than guessing.

Patient identification. Verify you have the right patient using your facility's identification procedure (typically two identifiers). This is a fundamental safety step — mixing up patients or records is a grave mistake. Confirm identity before you begin and ensure the study is recorded under the correct patient.

Pre-study questionnaire. Most labs have the patient complete a pre-study questionnaire covering how they slept recently, symptoms, daytime sleepiness, and related information. Review it; it provides context that helps you and the interpreting physician, and can flag issues to watch overnight.

Medication and sleep history documentation. Document the patient's relevant sleep history and current medications per your lab's protocol. This matters because medications and substances can affect sleep architecture, breathing, and heart rate, and the interpreting physician needs to know what the patient took. Record accurately what the patient reports; note timing where your lab requires it. You are documenting, not adjusting medications — any questions about whether a patient should take something go to the physician or follow standing orders, never your independent decision.

Biocalibrations

Before lights-out, you perform biocalibrations (bio-cals): a standardized set of simple maneuvers that prove each channel is recording what it should. This is the final verification gate, and skipping or rushing it is a serious error, because a channel that isn't actually reading correctly can invalidate hours of data.

In a bio-cal you ask the patient to perform specific actions and you confirm the expected signal appears on the expected channel — for example, looking in different directions and blinking to verify the eye (EOG) channels, clenching or grinding the jaw to verify chin EMG, moving each leg to verify leg EMG, breathing in specific ways to verify airflow and effort channels, and holding still with eyes open and closed to verify EEG. Follow your lab's exact bio-cal script and sequence. The point is that after bio-cals you know every channel works, rather than assuming it.

Figure — Figure 8.2 A representative biocalibration sequence, pairing each patient maneuver with the channel it verifies. Follow your lab's specific protocol.

Figure 8.2 A representative biocalibration sequence, pairing each patient maneuver with the channel it verifies. Follow your lab's specific protocol.

Lights out

Lights-out is the formal start of the recording period and it is documented to the minute. Before you call lights-out, run the before-lights-out checklist from Chapter 6: all sensors on and secured, all signals clean, impedances acceptable, bio-cals done and verified, the patient comfortable and knowing how to call you, the room dark and at the right temperature, video/audio confirmed, and recording running. Note the lights-out time precisely — it anchors the timing of the entire study. Then let the patient sleep.

Monitoring the study

Now begins the long acquisition stretch, where much of your professional skill lives. Monitoring is active, not passive: you continuously watch the incoming signals, keep them clean (troubleshooting from Chapter 7), watch the patient's safety, and document. Recall from Chapter 4 that the quiet hours and the circadian low are exactly when vigilance must rise even as your own alertness sags.

Recognizing respiratory events during acquisition

As you monitor, you'll begin to recognize respiratory events forming in real time — reductions or pauses in airflow, changes in effort, and associated oxygen drops. Chapter 10 covers the formal definitions and scoring; during acquisition your job is to recognize that events are occurring, ensure your signals are capturing them cleanly (not mistaking a real apnea for artifact, per Chapter 7), watch the associated oxygen levels for safety, and document notable patterns. You are observing and recording events, not diagnosing their significance — that interpretation belongs to the physician.

Recognizing limb movements

You'll also learn to spot limb movements on the leg EMG — leg activity that may occur in repetitive patterns and can fragment sleep. Distinguish genuine movements from artifact by their character and by correlating with video and other channels (Chapter 7). Note significant movement activity; formal scoring comes later.

Recognizing sleep/wake transitions

Watching the EEG, EOG, and chin EMG together, you'll see the patient move between wakefulness and sleep and through the stages (the full architecture is Chapter 9). Recognizing these transitions in real time helps you monitor intelligently — for instance, knowing the patient has entered REM (low chin tone, eye movements, irregular breathing) tells you certain breathing changes are expected, not alarming. Real-time stage awareness also matters for protocols like split-night studies (Chapter 11), where decisions may hinge on how the patient is sleeping.

Recognizing poor data quality

Constantly ask whether the data you're capturing is actually good. A signal that has quietly degraded is recording nothing useful. Watch for the artifacts and failures from Chapter 7, and hold yourself to the standard that every channel should be scorable. Catching poor quality early — ideally correcting a marginal signal before it fails completely — is a defining habit of a strong technologist.

When to intervene, and when not to over-intervene

This is the judgment that Chapter 7 introduced, applied across the whole night. Intervene when a signal critical to the study or to safety is lost or degrading and won't self-correct, when the patient needs help, or when protocol requires action. Don't over-intervene when an artifact is likely self-limiting, when the patient is simply shifting position, or when a non-critical signal can wait for a natural awakening — because every unnecessary entry risks waking the patient and costing sleep data. The mature technologist neither ignores problems nor hovers anxiously; they act deliberately, fix remotely when possible, and enter the room quietly only when it's warranted. Balance is the skill. And one rule overrides the balance: anything that is a genuine safety concern is always acted upon.

Recognizing urgent medical concerns and escalating

Most nights are routine. But a sleep lab is a clinical environment, and occasionally something genuinely urgent happens. Your responsibility is to recognize these situations and escalate them according to your physician orders, lab policy, emergency protocol, and scope of practice. You are not expected — or permitted — to independently diagnose or treat serious medical events on your own authority. You are expected to notice, respond within your training and protocol, summon the right help, and document.

Urgent concerns you must be alert to include:

• Severe desaturation — oxygen levels dropping to concerning levels, especially if sustained.

• Chest pain — a patient reporting chest pain or pressure.

• Respiratory distress — a patient struggling to breathe, gasping, or in obvious respiratory difficulty.

• Confusion — new confusion, disorientation, or altered mental status.

• Falls — a patient falling, or found on the floor, or at clear risk (e.g., trying to get up entangled in wires).

• Seizure-like activity — convulsive movements or other behavior suggesting a seizure.

• Serious arrhythmia concern — a cardiac rhythm on the EKG that appears dangerous or markedly abnormal.

For each of these, the response follows the same shape: recognize it early, stay calm, respond within your protocol and training, activate your escalation pathway (call for the appropriate help — nursing, physician on call, emergency services, or code procedures as your facility dictates), stay with and support the patient within your scope, and document what happened and what you did. What you do specifically is defined by your lab's protocols and your scope — follow them exactly. This book does not, and cannot, give you independent medical-treatment instructions; the correct source is your facility's policies, your standing orders, and your training. When in doubt, escalate sooner rather than later. No one is ever criticized for appropriately summoning help for a patient who turned out to be fine; the dangerous error is hesitating on something serious.

Figure — Decision-tree flowchart starting with "Do I see an urgent concern?" and branching through: is it immediately life-threatening; follow emergency protocol and call for help; if not immediately life-threatening, notify per protocol and monitor; always stay with the patient within scope and document.

Figure 8.4 A general decision path for responding to an urgent concern. The specific actions at each step are defined by your lab's protocols, physician orders, and scope of practice — always follow those.

Emergency escalation checklist

• Recognize the concern early and stay calm.

• Ensure immediate patient safety within your scope and training.

• Activate the correct escalation pathway per your protocol (nurse, on-call physician, emergency services, code team as applicable).

• Communicate clearly (see below) — who you are, the patient, the situation, what you observe.

• Stay with and reassure the patient within your scope.

• Follow directions from the physician/emergency personnel.

• Document the event, timeline, and actions thoroughly.

Professional communication with physicians, managers, and emergency personnel

In both routine and urgent situations, clear professional communication matters. When you contact a physician, manager, or emergency personnel, be concise, accurate, and organized: identify yourself and the patient, state the situation and what you've observed (objective signals and behavior), and state what you need. In an emergency, calm, structured communication speeds help; rambling or panic slows it. Report what you observe — "oxygen dropped to X and is not recovering; patient reports chest pain" — rather than offering a diagnosis, which is outside your role. Good communication is part of patient safety, and it also builds the professional trust that makes you valued in the lab.

Lights on and the morning process

At the scheduled wake time (or per protocol), you reach lights-on, the documented end of the recording period — again noted to the minute. The morning process then includes performing any end-of-study procedures your lab requires (sometimes a repeat bio-cal), stopping the recording properly, gently removing all the sensors, and attending to the patient: helping them clean up (electrode paste, adhesive residue), answering their questions appropriately, and preparing them for discharge. Remember that patients often want to know "how did I do?" — respond kindly but stay within your role: you gathered the data, and their physician will review and discuss the results. Do not offer interpretations or results you're not authorized to give.

Then you discharge the patient per protocol, ensuring they're safe to leave (especially important to consider given they may be sleep-deprived and driving — a natural place to reinforce the drowsy-driving awareness from Chapter 4 if appropriate and within your role), and you prepare the data and equipment for the next steps.

Final documentation

Finally, you complete the study documentation: the technologist's record of the night. This pulls together everything — lights-out and lights-on times, bio-cal completion, notable events and patterns you observed, any troubleshooting and deviations (Chapters 5–7), any patient issues or urgent concerns and how they were handled, medications and history as recorded, and anything the scorer and physician need to interpret the study correctly. Thorough, accurate, objective documentation is the capstone of a flawless study.

Writing precise tech notes

Throughout the night and at its end, you write tech notes — the running, timestamped record of what happened. Precise notes are objective, specific, timestamped, and factual. They describe what you observed and what you did, without speculation or diagnosis.

Figure 8.3 What separates a strong technologist note from a weak one.

Example tech notes (good practice)

"22:52 — Lights-out. All channels clean, impedances within target, bio-cals completed and verified."

"00:15 — Brief diffuse movement artifact; patient repositioning; signals recovered without intervention."

"02:30 — Cluster of respiratory events noted in supine REM with associated desaturations; oxygen recovered between events; continued monitoring; no intervention required per diagnostic protocol."

"06:00 — Lights-on. Repeat bio-cals completed. Sensors removed, patient assisted with cleanup, discharged per protocol at 06:25. No urgent concerns overnight."

Why good tech notes protect the patient, the lab, and the technologist

It's worth stating plainly why documentation deserves this much attention. For the patient, accurate notes ensure the scorer and physician interpret the study correctly, leading to the right diagnosis and care; they preserve the context (artifact, deviations, events) that raw data alone can't convey. For the lab, thorough records support quality, accreditation, and continuity, and demonstrate that care met the standard. For you, the technologist, good documentation is your professional protection: if a question ever arises about what happened on a given night, a clear, timestamped, objective record shows exactly what you observed and did — that you followed protocol and acted appropriately. Vague or missing notes protect no one. In a field where a study may be reviewed long after the night, your notes are your voice. Make them precise, objective, and complete.

Full diagnostic PSG workflow checklist

• Orders: Read and understand the physician's order; clarify anything unclear.

• Identity: Verify the patient with two identifiers; confirm correct record.

• History: Complete pre-study questionnaire; document sleep history and medications accurately.

• Hookup: Apply and secure all sensors (Chapter 6); verify signals and impedances.

• Bio-cals: Perform and verify every channel; follow lab script.

• Lights-out: Run the checklist; note the exact time; confirm recording.

• Monitor: Actively watch signals and patient; recognize events, movements, transitions, and poor quality.

• Intervene wisely: Fix critical/safety problems; avoid unnecessary disturbance; safety overrides all.

• Escalate: Recognize urgent concerns; follow protocol, orders, and scope; communicate clearly; document.

• Lights-on: Note the time; end-of-study procedures; stop recording properly.

• Morning: Remove sensors, assist patient, answer within your role, discharge safely.

• Document: Complete thorough, objective, timestamped final documentation.

Clinical Takeaways

• A diagnostic PSG gathers data; your success is measured by clean, complete data and patient safety, not treatment.

• Start every night by reviewing the order and verifying patient identity — foundational safety steps.

• Bio-cals are the final verification gate; never skip or rush them.

• Monitoring is active: recognize events, movements, transitions, and degrading quality in real time.

• Intervene for critical or safety issues; avoid unnecessary disruption otherwise — but safety always overrides.

• Recognize urgent concerns and escalate per protocol, orders, and scope; never independently diagnose or treat.

• Precise, objective, timestamped documentation protects the patient, the lab, and you.

Study Questions

1. How does a diagnostic PSG differ from a titration study, and how does that shape your role?

1. Why are order review and patient identification the first steps, and what can go wrong if they're skipped?

1. What are biocalibrations, and why are they the final verification gate before lights-out?

1. Describe how you decide when to intervene versus when not to over-intervene during the night.

1. List several urgent medical concerns and explain the general shape of an appropriate response, staying within scope.

1. Why should you report observations rather than diagnoses when communicating with a physician or emergency personnel?

1. Explain three ways good tech notes protect the patient, the lab, and the technologist.

Lab Reality Check

Running a full diagnostic study is where all your separate skills finally braid into one smooth performance — and the first few times, it won't feel smooth at all. You'll be watching signals, timing lights-out, soothing a patient, and writing notes all at once, and it's a lot. It gets easier fast, because the workflow is the same every night; you build a rhythm. The two things that most distinguish a trusted technologist are judgment and documentation. Judgment is knowing when a wobbling signal can wait and when a desaturation can't — and, crucially, knowing that the second something looks like a real medical concern, you escalate and let the protocol and the physicians take over rather than trying to be a hero. Documentation is the quiet discipline of writing notes so clear that a scorer, a physician, or a manager reading them a year later knows exactly what happened. Nobody sees your notes on the night you write them; everybody relies on them later. Master the routine, exercise good judgment, stay firmly inside your scope, and document like it matters — because it does.

Explain Like I Am 10

Running a sleep study is like being the captain of a ship for one night. The captain has a plan to follow (that's the doctor's orders), makes sure the right passenger is on board (checking the patient's identity), and does a systems check before setting sail. That systems check is called biocalibration — the technologist asks the person to blink, look around, clench their jaw, and wiggle their legs, just to make sure every sensor is working before the "voyage" (sleep) begins. Then the lights go out and the real trip starts.

All night, the captain watches the instruments. They notice when the person's breathing pauses, when their legs move, and when they drift between being awake and asleep. Most of the time everything's calm and the captain just watches and takes notes. But a good captain also knows the difference between a tiny problem (a wire being silly — fix it quietly) and a big one. If something serious happens — the person can't breathe, grabs their chest, gets very confused, falls, or has shaking that looks like a seizure — the technologist does NOT try to be the doctor. They follow the emergency plan, call for the right help fast, stay with the person, and write down exactly what happened. Getting help quickly is always the smart, brave choice.

The captain's secret superpower is the logbook — writing clear notes with times, like "at 2:05 the oxygen dropped." Later, the doctor reads these notes to understand the whole night. Good notes help the patient get the right answer, help the lab, and protect the technologist too, because they show exactly what happened and that they did the right things. A vague note like "patient slept ok" helps nobody. A clear note is like a good map — anyone can follow it.

Remember This

• Follow the doctor's orders and always check you have the right patient.

• Biocalibration is the "systems check" — make sure every sensor works before sleep starts.

• Watch all night: fix little wire problems quietly, but for anything serious, call for help right away and follow the emergency plan.

• Never try to be the doctor — a technologist recognizes and escalates, and stays within their job.

• Write clear notes with times — they help the patient, the lab, and you.

Quick Review Questions

1. Why does the technologist check the patient's identity before starting?

1. What is biocalibration, and why do it before the lights go out?

1. If something looks like a serious medical emergency, what should the technologist do (and not do)?

1. Why are clear notes with times so important?

1. Why is calling for help quickly a smart and brave thing to do, not a weak one?

Common Mistakes

• Not fully reading the order. Running the wrong study or missing special instructions.

• Skipping careful patient identification. A grave and avoidable safety error.

• Rushing or skipping bio-cals. It can invalidate hours of data.

• Passive monitoring. Zoning out and missing degrading signals or forming events.

• Over-intervening or under-intervening. Waking patients needlessly, or ignoring a dying signal or a real concern.

• Overstepping scope. Offering diagnoses/results to patients or trying to independently manage a medical emergency instead of escalating.

• Weak documentation. Vague, untimed, subjective notes that protect no one.