Exam Configurations
# Exam Module — Configuration Menu This guide explains every menu item available under **Exams → Configuration**. These are administrator-level master data lists that power the drop-downs, templates, and wizards the clinical team uses inside a patient exam. > **Who can see this menu?** Only users in the *Exam Admin* group. Front-desk and clinical users consume these values inside exams but typically cannot edit them here. The Configuration menu is organized in two groups: 1. **Exam** — the core reference lists used throughout an exam. 2. **HPI** — the value lists that drive the *History of Present Illness* wizard. --- ## 1. Exam ### Refractive Type **Path:** Exams → Configuration → Exam → Refractive Type **Purpose:** Maintain the list of refractive glasses types (e.g. Single Vision, Bifocal, Progressive, Readers) that the provider can pick from when recording a glasses prescription during an exam. **When to use:** Add a new type when the practice begins prescribing a lens category that is not currently in the list; deactivate an entry that is no longer offered so it stops appearing in drop-downs. **Fields:** *Name* only. ### Allergy Reaction **Path:** Exams → Configuration → Exam → Allergy Reaction **Purpose:** Master list of the **reactions** a patient can have to an allergen (e.g. Rash, Swelling, Anaphylaxis, Itching). Selected in the patient allergy section of an exam. **When to use:** Add the reaction types your clinical documentation workflow requires. Standardizing this list keeps patient charts searchable and reportable. ### Allergy Type **Path:** Exams → Configuration → Exam → Allergy Type **Purpose:** Master list of **allergen categories** (e.g. Drug, Food, Environmental, Latex). Used together with Allergy Reaction when documenting patient allergies. **When to use:** Add or rename entries so providers can classify allergies consistently across charts. ### Chief Complaint **Path:** Exams → Configuration → Exam → Chief Complaint **Purpose:** Pre-defined list of the most common reasons a patient presents for an exam (e.g. "Blurred vision", "Eye pain", "Annual check-up"). These appear as quick-pick options on the Chief Complaint field of the exam. **When to use:** Add common complaints your providers see so they can click instead of type. Keeping this list short and high-signal speeds up charting. **Fields:** *Name* only (entered inline). ### Exam Section **Path:** Exams → Configuration → Exam → Exam Section **Purpose:** Defines the **named sections** that make up an exam layout (e.g. Anterior, Posterior, Contact Lens, Refraction). Each entry can be flagged as Contact Lens, Anterior Exam, or Posterior Exam, and can group a default set of eye-section values. **When to use:** Tailor how exam forms are organized. Use the checkboxes to indicate which exam workflow a section belongs to, and set *Default* values so new exams start pre-populated. **Fields:** Name, Sequence, Active, Contact Lens, Anterior Exam, Posterior Exam, Eye Section list, Default. ### Exam Template **Path:** Exams → Configuration → Exam → Exam Template **Purpose:** Build reusable **exam templates** that prefill common findings (e.g. "Normal Comprehensive Adult", "Diabetic Follow-up"). Providers can load a template during charting to jump-start documentation instead of filling fields from scratch. **When to use:** Create a template whenever your providers repeatedly enter the same findings for a particular visit type. Update templates when clinical protocols change. ### Exam Tests **Path:** Exams → Configuration → Exam → Exam Tests **Purpose:** Master list of tests that can be ordered or documented as part of an appointment (e.g. OCT, Visual Field, Fundus Photo). Used on the appointment/exam to record which tests were run. **When to use:** Keep this list aligned with the diagnostic equipment and procedures your clinic actually performs. **Fields:** *Name* only. ### Family History **Path:** Exams → Configuration → Exam → Family History **Purpose:** Pick-list of **family medical conditions** (e.g. Glaucoma, Diabetes, Macular Degeneration) used in the patient's Family History section of the exam. **When to use:** Curate conditions that are clinically relevant to eyecare so providers can click through the history quickly. **Fields:** *Name* only. ### Medical History **Path:** Exams → Configuration → Exam → Medical History **Purpose:** Pick-list of general **past/present medical conditions** (e.g. Hypertension, Diabetes, Thyroid Disease) documented in the patient's medical history. **When to use:** Standardize the terms used in charts so data can be reported on consistently. ### Ocular History **Path:** Exams → Configuration → Exam → Ocular History **Purpose:** Pick-list of **past ocular conditions** (e.g. Amblyopia, Retinal Detachment, Dry Eye) used in the patient's ocular history. **When to use:** Add eye-specific conditions your practice needs to track, separate from general medical history. ### Ocular Surgical History **Path:** Exams → Configuration → Exam → Ocular Surgical History **Purpose:** Pick-list of **previous eye surgeries** (e.g. Cataract Surgery, LASIK, PRK, Corneal Transplant). Used in the patient history section to flag prior ocular procedures. **When to use:** Keep in sync with the surgical procedures your providers need to know about before examining a patient. ### Plan **Path:** Exams → Configuration → Exam → Plan **Purpose:** Pre-defined **diagnosis plans** — a plan text (treatment plan / follow-up instructions) paired with the diagnoses it applies to. When a matching diagnosis is added to an exam, the provider can quickly select the associated plan. **When to use:** Create a plan whenever providers repeatedly write the same instructions for a given diagnosis. Mark the plan as *Default* if it should be the pre-selected option for that diagnosis. **Fields:** Plan text, Sequence, Diagnosis, Default. ### Snippets **Path:** Exams → Configuration → Exam → Snippets **Purpose:** Reusable **text snippets** providers can insert into exam notes (e.g. standard phrasing for counseling, normal findings, referral language). Saves retyping common narrative text. **When to use:** Capture any wording your providers use repeatedly. Snippets are especially helpful for plans, patient education notes, and normal-finding descriptions. ### Surgical History **Path:** Exams → Configuration → Exam → Surgical History **Purpose:** Pick-list of **non-ocular past surgeries** (e.g. Appendectomy, Cardiac Bypass, Joint Replacement). Used in the patient's general surgical history section. **When to use:** Add surgeries that are clinically relevant to anesthesia risk, systemic disease history, or medication reconciliation. ### Recall Type **Path:** Exams → Configuration → Exam → Recall Type **Purpose:** Defines the **types of recalls** (e.g. Annual Exam, 6-Month Follow-up, Contact Lens Check) attached to a patient at the end of an exam so the practice can bring them back on schedule. **When to use:** Add or retire recall categories to match how your front desk schedules return visits. These recall types feed the recall reporting in the inventory/recall module. ### Rx Pad **Path:** Exams → Configuration → Exam → Rx Pad **Purpose:** A **quick-pick prescription library**. Each entry stores a drug with its common strength, dosage form, frequency, route, refills and instructions. When a provider writes a prescription in the exam they can pick an Rx Pad entry to auto-fill all of those fields. **When to use:** Create Rx Pad entries for every medication your providers routinely prescribe. Well-maintained Rx Pad entries dramatically reduce the time to write a prescription and eliminate typos in dosage/frequency. **Fields:** Drug, Strength, UOM, Dosage, Form, Frequency, Route, As Written, Refills, Instructions. ### Dilation Medications **Path:** Exams → Configuration → Exam → Dilation Medications **Purpose:** List of **dilating drops** (e.g. Tropicamide 1%, Phenylephrine 2.5%) that the provider can record as administered during the dilation step of an exam. **When to use:** Keep this list aligned with the dilating agents your clinic stocks. **Fields:** *Dilation Medications* (name) only, required. --- ## 2. HPI (History of Present Illness) All HPI sub-menus drive the drop-downs inside the HPI wizard the provider opens during an exam. Each list maps to one of the classic HPI elements. Keeping each list short, clinic-relevant, and free of duplicates makes HPI documentation fast and consistent. ### HPI Condition **Purpose:** The **primary conditions/complaints** documented in HPI (e.g. Redness, Itching, Blurred Vision, Flashes). ### HPI Context **Purpose:** The **context** in which a symptom occurs (e.g. While Reading, At Night, After Screen Use, During Exercise). ### HPI Duration **Purpose:** **How long** the symptom has been present (e.g. 1 Day, 1 Week, 1 Month, Chronic). ### HPI Factors **Purpose:** **Modifying factors** — what makes the symptom better or worse (e.g. Relieved by Rest, Worsened by Light, No Change with Drops). ### HPI Location **Purpose:** **Anatomical location** of the symptom (e.g. OD, OS, OU, Lid, Conjunctiva, Periorbital). ### HPI Quality **Purpose:** **Character/quality** of the symptom (e.g. Sharp, Dull, Burning, Itchy, Gritty). ### HPI Symptoms **Purpose:** **Associated symptoms** occurring alongside the chief complaint (e.g. Headache, Nausea, Photophobia, Tearing). ### HPI Timing **Purpose:** **When or how often** the symptom occurs (e.g. Morning, Evening, Constant, Intermittent, With Activity). --- ## General Tips for Administering This Menu - **Inline editing:** Most of these lists open as editable list views. Click into a row to edit the *Name*; click "New" to add. - **Keep entries concise.** The values display inside drop-downs during a live exam — long text makes charting slower. - **Avoid duplicates.** Duplicate entries (e.g. "Diabetes" and "Diabetes Mellitus") fragment reports and confuse providers. - **Archive, don't delete.** For lists that support *Active*, deactivate old entries instead of deleting so existing patient records keep their references intact. - **Company-aware lists:** Some lists (Exam Section, Exam Section List, Refractive Glasses Type, Diagnosis Plan) store a Company so multi-company tenants can maintain separate values per company. - **Changes are immediate.** Newly added values appear in the exam UI as soon as they are saved — no restart needed.