Emergency Department Roleplay

From principle to practice

As an emergency department roleplay participant, your aim is to coordinate an urgent fictional scene without losing clarity. The principle in this module becomes useful when you can explain what you would do, why you would do it, and what you would communicate afterward. A convincing title or confident message does not replace an agreed workflow. Begin with the information the participants have actually established and separate it from anything you are assuming.

Before choosing an action, identify the decision that belongs to your role. Name the other participants whose agreement or acknowledgment is needed. If the required information is missing, make that gap visible instead of quietly treating a guess as a fact. This keeps the scene understandable for both the people present now and the person who may take over later.

A practical sequence

Apply the lesson in three stages. First, establish the current shared situation and the boundaries of your assignment. Next, carry out the agreed action using clear, relevant communication. Finally, confirm the outcome or state what remains unresolved. The final stage matters: a message that has been sent is not automatically a task that has been completed.

1. Confirm the current scene and your assigned responsibility.
2. Apply the module’s principle without inventing missing information.
3. Record the next step and obtain acknowledgment when responsibility changes.

What a reviewer should be able to understand

A useful explanation makes your reasoning visible. Identify the information available at the time, the expectation that applied, and the reason for your chosen response. Keep the account focused on observable behavior. Statements about someone’s motives or personality are not substitutes for evidence. If your first response was mistaken, explain the correction plainly and make sure anyone relying on the earlier information receives the update.

End the emergency phase with a usable transition

When the dramatic portion ends, the team still needs to agree what happens next. State the current fictional outcome, identify unresolved story details, and name the receiving role. Ask for acknowledgment before treating the transfer as complete. A debrief should focus on communication and coordination: which instruction was unclear, which handoff was missed, and what could be simplified next time. Avoid presenting a fictional outcome as evidence of real treatment skill.

Apply this to the third case: A complex scene ends with disagreement about what happened in its final minutes. Check whether you have reached an outcome or merely sent a request. Those are different states. If another person must accept responsibility, write the acknowledgment you need to receive before you call the task complete. If that response does not arrive, record the pending status and the agreed fallback.

An appropriate fallback might be a pause, a simpler scene, another available authorized owner, or a later review. Choose one that fits the group’s actual process. Do not invent a permission, a policy, or a successful result simply because the preferred person is unavailable.

Independent practice

Write a four-to-six sentence response to the scenario. Include your opening message, the detail you would clarify, the action you would take, and the way you would confirm completion. Then explain how your response supports the objective of this module.

Write your response in your own notes before reading on. Compare the action you chose, the information you preserved, and who owns the next step with the worked example. This practice is self-reviewed and is not submitted for marking.

Before you continue

• Can you distinguish established scene information from assumptions?
• Have you identified who owns the next action?
• Would the other participants understand what happens next without guessing?