Welcome to scenario creation for Pharmacy Simulator. We’re glad to see you taking an interest in creating scenarios and sharing them with our learning community. This document is intended to give you guidance on how to write scenarios that are easy to play, achieve their intended learning outcomes, and maintain high standards for quality. If you are not yet familiar with the basics of how to use the Scenario Editing tools in Pharmacy Simulator, you may want to first read the relevant user manual.
Before you begin, it’s probably best to calibrate your expectations. If you have never written a Pharmacy Simulator scenario before there is a learning curve to overcome. Although we have made every effort to make this process accessible and easy to understand, there are still areas that we need to improve, and there is a base level of difficulty that simply cannot be avoided. For first time scenario authors we recommend you choose a relatively simple scenario to write. Even then, from experience we have observed that for a first time scenario author you can expect to spend at least half a day and probably more like a full working day or even more, depending to some extent on the level of complexity of the scenario and how much dialog and depth you decide to consider. This is due mainly to two factors:
You can expect that your second and third scenarios will be developed much more quickly, but even the most proficient scenario author will not be able to write a complex scenario from scratch in less than half a working day. However, it is important to remember that you do not always need to write scenarios from scratch – explore the list of scenarios before you begin: does the scenario you’re trying to write already exist? Has someone already written a similar scenario that you can modify to suit your needs? It is always possible to clone this scenario, and modify it.
But for the purpose of this document, let’s assume you want to write a new scenario from scratch. Before you load up the scenario editor in Pharmacy Simulator, you should have a plan of the type of scenario you want to create. Although there is no fixed way of going about designing your scenario, there are a few key factors that it is often wise to consider:
Ask yourself what you’re trying to teach the user. In the general sense, are you wanting your students to be more familiar with a particular health condition, a particular type of patient, a particular class of medicines, or perhaps with the details of a prescription?
Once you have decided the general topic, you should try to narrow it down to a particular patient encounter that demonstrates some key factor. For example, if you want students to be familiar with heart disease, what aspect of this disease are you going to focus on in your new scenario? Perhaps a patient who has been recently diagnosed? Perhaps a patient who has been recently discharged following an event? Perhaps a patient who has just started a new medicine?
Note: It is generally best to pick one key focus for a particular scenario. You can always create additional scenarios, or variants on your scenario, to cover different areas of the topic. See cloning a scenario in the scenario editing manual for more information about this.
The way you write the scenario needs should generally be adapted based on the level of your intended learner. This should always be varied based on the needs of your particular target group of students, but some general guidelines and tips based on a four year tertiary level Pharmacy program are below, but you will need to accelerate this for shorter programs with higher entry level requirements.
It is important to come up with a mental model for the type of patient in your scenario, that can be best employed to illustrate the key learning objectives you have in mind. Try to consider the following patient characteristics:
To inject personality into the patient and make their responses to student queries seem more organic it may also be useful to come up with something of a back-story for the patient. We tend to find this is more important for more experienced students who are looking for a more authentic patient experience, whereas less experienced students are often more focused on the technical details and may not engage with the patient back-story so much. At the very least you may find this helps make it easier for you when it comes time to write the dialog responses. Some example questions to stimulate your process are provided below, but really it’s up to you. Feel free to use your imagination.
It is usually easiest to start by identifying the perfect and correct way to complete the scenario. Identify all the questions the student must ask the patient, identify all the advice they must provide, and the appropriate course of action i.e. to dispense a particular type of product, to refer the patient to another health service, to provide advice only.
At this point you may wish to open up the scenario editor, create the patient, and start adding all the dialog options/responses and rules that are necessary to achieve the perfect outcome. You may wish to preview the scenario at this point and see if it “feels” correct, like a real patient encounter. At this point you can also set the maximum score for the scenario.
It is important now to add opportunities to fail. It is of very limited value for students to load a scenario, click every option, and then get a perfect score. This would not prompt them to think, reflect, or research from reference materials.
Use your experience as a Pharmacy educator and/or Pharmacist to come up with several plausible ways in which a student or pharmacist could do the wrong thing. Some common areas to think about include:
Having thought up several ways in which students can plausibly make mistakes, you must think about what the consequences of these mistakes would be. This requires a bit of imagination to think out what the likely outcomes would be. In simple terms – whenever you provide the student with an incorrect option to take, it will often to require the addition of extra incorrect options, or the modification of the responses the patient may give, further down the track.
As a rough guideline, for each key element you should consider adding around 2 mistake options. One which you think students are quite likely to choose, and one which is perhaps more evidently incorrect but which is nevertheless plausible. If you’re feeling playful, you might also choose to add a "joke" option, which is clearly incorrect but which a student might try just to see what happens. It may help to imagine that you are writing a multiple choice questionnaire, where there is often one best option, two ok but inferior options, and a fourth bad option to choose from. The goal is to prompt the student to think.
It is important to replay the scenario several times and explore both the correct and the incorrect paths the student might take. By previewing the scenario in this way you’ll be able to identify sections that don’t feel right, or are logically inconsistent, and can typically fix the issues quite easily. This is a very important quality assurance step – if you don’t do this, students who play your scenario may become confused and frustrated when the scenario doesn’t make sense and isn’t behaving in the way they expect. Common things to look out for during this process:
Your workflow for fixing these issues may vary. Some will prefer to play through the whole scenario noting down errors as they encounter them, then fixing them in a batch. Others will prefer to play until they identify an error, fix it immediately, then restart the process.
We have observed that students typically go through the following learning process with their scenario:
Because of this final behaviour, we have found it is interesting for the students if we add points of interest that allow the students to have a bit of fun. Consider the following examples of things that we have observed that students like to experiment with:
In some cases there are default options that will occur if the student performs these actions, but as the scenario author you are always free to add custom responses to any of these options and more. Custom responses you add will override any default responses that are built into the engine.
Ultimately our goal when writing scenarios is to give students a learning experience. There are a lot of factors that can go into achieving this goal, and there's really no set method. Take everything in this document as well intentioned advice, use it as a framework if you find that helpful. But if you can come up with interesting and creative ways of achieving your goals, don't worry if you don't see them talked about in this document. You know your students and you know your objective. If you think it works, you're probably right.
Remember, if you're unsure of what you've created, or just need more help and guidance, feel free to reach out to us via email for some personalised support.