Documentation, records & traceability
Learning objectives
- Produce a usable fictional record for Pharmacist Roleplay License.
- Distinguish a completed action from an unresolved task.
- Communicate a correction without concealing earlier uncertainty.
Records help a team continue a shared scene consistently. In Pharmacist Roleplay License, a useful record explains the agreed situation, the action taken, the current status, and who owns the next step. It should be short enough to use and detailed enough that another player does not need to reconstruct the entire conversation.
Build a record that someone can use
Start with the purpose of the record. A handoff, referral, incident note, and staffing decision serve different tasks, but each needs a clear subject and current status. Include only information needed for the fictional workflow. Distinguish what a participant reported from what the group actually agreed. If a question remains open, write that it is unresolved and identify who should clarify it.
For a pharmacist roleplay candidate, the record should support the responsibility to review and hand over fictional pharmacy requests with traceable clarification. Avoid impressive-sounding detail that does not help the next player. A long narrative can still be unusable if it leaves out the next action. Conversely, a brief structured note can be effective when it names the relevant facts, uncertainty, and receiving owner.
Worked record
Request ID: fictional scene label. Character: confirmed with requesting role. Status: clarification completed. Change: story request updated. Handoff: receiving player acknowledged current version. No real medication instructions.
Read the example as a structure rather than a script to copy word for word. Each field answers a practical question: what is this about, what is known, what is pending, and who will continue? Adapt the labels to the scene you are actually running. Do not add a made-up observation just to fill an empty field.
Corrections and version changes
If an important detail changes, make the correction explicit. State what has changed, why the current version differs, and who needs the update. Do not silently rewrite a record after another player has relied on it. If a mistaken detail affects a handoff, communicate directly with the receiving player instead of assuming they will discover the edit.
Keep real names, passwords, contact details, and real health records out of fictional learning records. Share information only with the participants who need it for the agreed task. The public MHCLP registry displays credential information; it is not a place to store private scene notes or allegations.
Record workshop: replace vague statements with usable evidence
Compare this weak record — “Handled the issue; everything is fine” — with the program example: Request ID: fictional scene label. Character: confirmed with requesting role. Status: clarification completed. Change: story request updated. Handoff: receiving player acknowledged current version. No real medication instructions.
The weak record hides the subject, decision, basis, and remaining responsibility. It cannot tell a later reader whether the issue was resolved, deferred, or handed off. Rewrite one field at a time. First state the fictional situation or administrative request. Next identify the relevant agreement or rule. Then record the action actually completed. Finally name the next owner and any unresolved question.
Add a change note if a detail is corrected: “Update: the receiving player is unavailable; the scene is paused by agreement until a replacement accepts.” This preserves the distinction between the original plan and the current arrangement. Do not silently edit “pending” into “complete” without evidence that the missing step happened. A record should support a later decision, not merely look official.
Make the next decision
A teammate receives this record but still asks, “What am I expected to do next?” Review the example and identify what additional scene-specific detail would make the receiving task clear.
Reveal the model response & reasoning
Response: Name the receiving role, state the unresolved question or requested action, and ask the teammate to confirm acceptance. If the information is not yet known, say so and identify who will obtain it.
Why: The record’s purpose is continuity. A document that looks polished but leaves responsibility ambiguous has not completed that purpose.
Independent practice
Draft a fictional record for the first worked scenario in this program. Use four labels: situation, agreed action, unresolved detail, and next owner. Add one correction note showing how you would update the record if the agreed scene changed.
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
- Does the record reflect the current shared scene?
- Are facts, reports, and uncertainty distinguishable?
- Is the next action assigned and acknowledged?
Check your understanding
Practice does not affect your exam score or issue a credential.