2.3 Scenario Practice for History and Documentation

2.3 Scenario Practice for History and Documentation

Scenario items put you in the exam lane with a real patient and ask what to record or do next. Practice reading for the role (you are the COA), the cue (the symptom or omission), and the safest, most complete documentation action.

Scenario: the incomplete medication list

A patient lists "a blood pressure pill" but no eye drops. Many patients do not consider drops, over-the-counter products, or supplements to be "medications." The correct action is to probe specifically: ask about glaucoma drops, artificial tears, aspirin, blood thinners, and vitamins. Record each medication with name, dose, and frequency. Tamsulosin (Flomax) is a classic example worth flagging because it is associated with intraoperative floppy iris syndrome (IFIS) during cataract surgery, so the surgeon must know about it in advance.

Scenario: documenting allergies

A patient says, "I'm allergic to sulfa." Chart the substance and the reaction, e.g. "sulfa - hives." Distinguish a true allergy (rash, swelling, anaphylaxis) from a side effect (nausea). If the patient denies any drug allergy, document NKDA (no known drug allergies) rather than leaving the field blank, because a blank field is ambiguous.

Scenario: targeted family history

Family history in ophthalmology is not a formality. The conditions with strong hereditary weight include:

Scenario: matching urgency to workflow

The history is also a triage tool. Certain complaints should be communicated to the physician promptly rather than slotted into the routine queue:

• Sudden, painless loss of vision - possible retinal artery occlusion or detachment.
• Flashes and new floaters, or a "curtain" in the vision - possible retinal tear/detachment.
• Chemical splash to the eye - irrigation comes first; documentation follows.
• Ocular trauma, especially with a possible foreign body or globe injury.
• Acute severe eye pain with halos and a red eye - possible angle-closure glaucoma.

In these scenarios the best answer captures the key history details (onset, laterality, mechanism) and ensures the urgency is conveyed; it does not bury an emergency in a standard intake.

Reading method for scenario items

For each scenario, name your role, underline the symptom or omission cue, decide the most complete documentation action, and predict the downstream effect. When two options look reasonable, prefer the one that records the missing detail (the drop, the reaction, the family history) rather than the one that simply moves the patient along. A medication or allergy gap that reaches the physician can change the surgical plan, so completeness is the higher-value answer.

Scenario: the contact-lens wearer

A patient presenting with a red, painful eye should always be asked about contact lens use: whether they sleep in lenses, how they clean them, and how old the lenses are. Overnight wear and poor hygiene raise the risk of a corneal ulcer, which is sight-threatening. Documenting "soft contact lenses, sleeps in them, replaces monthly" gives the physician the context to evaluate the red eye correctly. Omitting the lens history is a trap because the complaint then looks like ordinary conjunctivitis.

Scenario: the pediatric visit

For children, the history is taken from a parent or guardian, and the high-yield questions shift toward developmental and family factors: birth history, prematurity, a family history of strabismus or amblyopia, and whether the child squints, sits close to screens, or tilts the head. Amblyopia ("lazy eye") is most treatable when caught early, so a family history of strabismus or patching as a child is worth recording specifically.

Worked example

Stem: a 68-year-old scheduled for cataract surgery reports taking "a pill for his prostate." The strongest action is to identify the exact drug, because tamsulosin must be documented so the surgeon can plan for floppy iris syndrome. Recording "prostate pill" without the name leaves a clinically important gap. The same principle applies whenever a patient gives a vague medication, allergy, or symptom: the COA's job is to convert the vague statement into a specific, charted detail that the physician can act on.

Choosing between two plausible answers

Scenario items often offer two options that both sound reasonable. The tie-breaker is usually completeness and safety: prefer the answer that captures the missing clinical detail, escalates a genuine emergency, or verifies before acting. An option that simply advances the patient through the visit without resolving the gap is the weaker choice. Read the stem for the single cue that distinguishes the answers, such as the word "sudden," the mention of contact lenses, or a vague medication name, and let that cue drive your selection rather than a general sense that an answer feels familiar.

Scenario: the vague systemic history

A patient says they have "sugar problems" but cannot name a diagnosis. Diabetes is among the most important systemic conditions in ophthalmology because of diabetic retinopathy, so the COA should clarify whether the patient has diabetes, how long, whether it is controlled, and the last hemoglobin A1c if known. Charting "diabetes, type 2, 10 years, on metformin" is far more useful than "sugar problems." The exam may present this as a choice between accepting the vague phrase and probing for the specifics; the probing answer is correct.