Emergency Medicine and Intensive Care: Stabilize, Diagnose, Treat
Emergency and critical care questions reward a structured approach under time pressure. Master the primary survey, shock recognition, airway management, and the common emergencies: cardiac arrest, acute coronary syndrome, stroke, sepsis, anaphylaxis, and trauma.
Concepts to master
- ABCDE approach and reassessment after every intervention.
- Shock types: hypovolemic, cardiogenic, distributive, obstructive; matching fluids, vasopressors, or decompression.
- Airway: indications for intubation, rapid sequence intubation, and rescue devices.
- Sepsis bundles: cultures, antibiotics, fluids, and source control.
- Post-resuscitation care and prognostication.
Traps
Questions often present a patient who looks stable but has compensated shock (normal blood pressure, rising lactate). Another trap is choosing a diagnostic test before stabilizing the patient. Be careful with fluid overload in cardiogenic shock and with delaying antibiotics in sepsis. Watch for reversible causes in cardiac arrest (Hs and Ts).
Worked rule of thumb
In any shock: identify the type, then treat the cause. Hypovolemic → fluids and blood; cardiogenic → inotropes and careful fluid; distributive → fluids plus vasopressors; obstructive → decompress (needle thoracostomy, pericardiocentesis). Reassess perfusion after each step.
Medical Informatics and Health Management: Data, Systems, and Quality
This domain tests how information systems support care and how health services are managed. Understand electronic health records, clinical decision support, data quality, privacy, and quality improvement.
Concepts to master
- Electronic health records: functions, interoperability, and meaningful use.
- Clinical decision support: alerts, order sets, and the problem of alert fatigue.
- Data quality: completeness, accuracy, timeliness, and standardization (terminologies, coding).
- Privacy and security: access control, audit trails, and consent.
- Health management: resource allocation, quality indicators, and continuous improvement (PDSA cycles).
Traps
Questions often confuse data availability with data quality. Another trap is assuming more alerts improve safety; alert fatigue is a real hazard. Be careful with privacy questions: legitimate access still requires a need-to-know basis. Watch for quality questions that ask for a process measure versus an outcome measure.
Worked rule of thumb
For any informatics question, ask: Who needs the data, for what decision, and how will it be kept accurate and secure? For quality improvement, use the PDSA cycle (Plan-Do-Study-Act) and measure both process and outcome.