What a HEENT Interview Actually Looks Like
Standing in an OR or clinic, you learn pretty quickly that asking a patient to describe their symptoms in plain language is a different skill than reading a chart. The ear, nose, throat, and head structures don't announce themselves the way a broken bone does. A chronic sinus infection gets filed under "headache" for months. A thyroid nodule shows up as "hoarseness" on a routine physical. The interview matters because the physical exam only gets you so far. I spent three years rotating through ENT clinics before I picked up on something most residents miss. You can ask the textbook questions — when did the hearing loss start, do you have nasal congestion, any facial pain — and still walk away with a vague picture. The real diagnostic signal usually comes from how a patient describes what seems like an unrelated problem. Someone will tell you their "allergies got worse this spring" and you notice they haven't mentioned a unilateral ear fullness or a persistent cough that only happens when they lie down. That's the gap between a scripted interview and a useful one.
The Health Heent Interview Guide
A HEENT interview isn't a single protocol. It's a framework for extracting information across five anatomical zones while staying alert to the systemic connections between them. The core structure covers: The guide itself is most useful when you treat it as a checklist for completeness, not a script to read verbatim. Patients don't appreciate being interrogated. They appreciate being heard. The art is in weaving the questions into a natural conversation while hitting every necessary node. Here's the practical workflow I use. It usually takes 10 to 15 minutes for a straightforward complaint and 20 to 30 minutes when there are multiple issues or red flags.
Start with the chief complaint. Let the patient say it in their own words. Don't interrupt. Write down the exact phrase — it's often more revealing than the medical translation you'll apply later. "My ear keeps popping" means something different clinically than "I feel pressure in my ears," even though they're the same symptom. Map the HPI across zones. Ear, nose, throat, head/neck, and eyes get treated as connected systems. A sore throat question always loops back to nasal drainage and tonsil history. A headache question branches into vision changes, jaw clenching, and sinus patterns. I keep a mental grid: for each symptom, I note which zone it belongs to, what's related, and what I still need to ask. Run the review of systems with a purpose. Generic ROS questions waste time. Frame them around the presenting complaint. If they came in for hearing loss, ask about tinnitus, otorrhea, vertigo, and noise exposure. If they're here for snoring, ask about witnessed apneas, morning headaches, daytime somnolence, and nasal obstruction. The more targeted the ROS, the faster you close the loop.
Get the Full Details
Document as you go. I used to wait until the end to write notes. That was a mistake. By the time I sat down to document, I'd already revised my differential three times based on new information. I keep an open note and fill it in during the interview. It takes an extra two minutes but saves ten minutes of reconstruction later.
Common Pitfalls and Where the Guide Falls Short
The biggest problem I've seen with structured HEENT interviews is that they encourage linear thinking in a nonlinear organ system. You ask about ears, then nose, then throat, and miss the connection between otitis media with effusion and adenoid hypertrophy in a pediatric patient who never mentioned nasal breathing difficulty. The guide won't catch that for you. You have to stay aware of the anatomical relationships. Another trap: the tendency to under-question social history. Smoking, vaping, occupational dust, GERD, and vocal overuse all masquerade as primary ENT complaints. I had a patient in his forties who presented with persistent hoarseness and a negative laryngoscopy twice. Third time, I asked about his job — he was a construction supervisor who spent eight hours a day around silica dust and never mentioned it because he didn't think it was relevant. The vocal cord changes were irritant-induced, not neoplastic. A simple follow-up question saved him an unnecessary biopsy. The guide also doesn't help much with pediatric patients, who rarely volunteer relevant history. In those cases, you're interviewing a parent while simultaneously observing the child. The parent's description of "ear drainage" might mean cerumen, pus, or CSF leak. The guide gives you the question structure, but the clinical judgment to differentiate comes from the physical exam and pattern recognition, not the interview itself.
What Makes This Different From a General Interview
Most general practice interviews treat the head and neck as an afterthought. HEENT interviews require that region to carry disproportionate weight because the structures are densely packed, innervation overlaps heavily, and symptoms frequently refer across boundaries. A dental infection can present as a headache. A cervical lymph node enlargement can signal oral cavity cancer without an obvious primary. The interview has to probe beyond the patient's initial framing. Cranial nerve assessment during the interview is another distinguishing factor. You're not just collecting a symptom list. You're simultaneously testing II (vision), V (facial sensation), VII (facial symmetry), IX and X (gag, voice, swallowing), XI (shoulder shrug), and XII (tongue deviation) through conversation and observation. The interview and the neuro exam overlap significantly in HEENT. I find the most value in using the guide as a safety net — a way to ensure I haven't missed a critical question — rather than a rigid protocol. The moments that matter most are the ones the guide doesn't structure: the pause before a patient volunteers something, the hesitation when asked about home remedies, the detail that seems incidental but becomes the key finding.
