Recently, a conversation around how to structure dialogue in the "History" section between student and patients came up. We thought the group would benefit from the details of the discussion...
Questions:
How are you dealing with history taking?
How many questions should be included page, and how should they be lumped together?
Does the rollover function in the CASUS software allow us to separate questions out more than previously – when the cost of each question was one click?
Response:
Excellent questions, indeed. With the click-and-wait in the
previous software version we knew we were choosing to limit irritation
over modeling the bad habit of asking two questions at once.
The new mouse over functionality makes the answer to this question even more subtle, however. Here is how we suggest approaching this:
1) First, limit scrolling -> which may mean breaking the questions up
into two screen cards.
2) Although there is no longer the click-and-wait issue, you will still
lose students' attention if there are too many questions in a row.
Therefore, I would still ask yourself if each question is truly needed,
and ensure that the patient answers remain somewhat "rich" -> which
means modeling asking open-ended questions.
3) Look at the questions in order and by themselves. Do they model a sort of "script" that a student could then use to ask a similar patient in
clinic?
4) Make sure that subsequent questions don't "give away" info from
previous patient questions.
Tuesday, February 17, 2009
Friday, February 13, 2009
Authoring Tip #1
Case Outlines: Changes and Hyperlinks
The outlines for your cases are based upon the curricular mapping completed by your mentors at the outset of the project. Each document represents a portion of a larger content matrix. For this reason, it is important that you don’t modify the outlines in the wiki. If you do wish to make changes, these suggestions need to be discussed with your mentor directly. At the end of the case writing process, these case outlines will be reconciled with the final content.
You may have also noticed the “C” and “D” at the end of each objective are functional hyperlinks. These were created to facilitate a dialogue between you and your editor about these specific objectives once the case drafts are complete. We will provide more on this as we get farther into the authoring process. If you wish to place comments on the outline itself, please use the “Comment?” tab at the top of the card, which will place your signed and dated comment at the bottom of the page.
Saving Drafts
Our advice: SAVE EARLY AND SAVE OFTEN! This may seem obvious, but it is worth reinforcing. Whenever you complete major work on your cases, please save a draft of your wiki case using the “print case” function. Detailed instructions for printing and saving your case are included in the wiki cheat sheet distributed at the work shop (and attached to the “Help” wiki).
The outlines for your cases are based upon the curricular mapping completed by your mentors at the outset of the project. Each document represents a portion of a larger content matrix. For this reason, it is important that you don’t modify the outlines in the wiki. If you do wish to make changes, these suggestions need to be discussed with your mentor directly. At the end of the case writing process, these case outlines will be reconciled with the final content.
You may have also noticed the “C” and “D” at the end of each objective are functional hyperlinks. These were created to facilitate a dialogue between you and your editor about these specific objectives once the case drafts are complete. We will provide more on this as we get farther into the authoring process. If you wish to place comments on the outline itself, please use the “Comment?” tab at the top of the card, which will place your signed and dated comment at the bottom of the page.
Saving Drafts
Our advice: SAVE EARLY AND SAVE OFTEN! This may seem obvious, but it is worth reinforcing. Whenever you complete major work on your cases, please save a draft of your wiki case using the “print case” function. Detailed instructions for printing and saving your case are included in the wiki cheat sheet distributed at the work shop (and attached to the “Help” wiki).
Friday, January 30, 2009
Welcome
Welcome to the fmCASES Blog!!!
Please use this blog to find group news, receive updates from mentors, post questions, and collaborate on the case development process.
Please use this blog to find group news, receive updates from mentors, post questions, and collaborate on the case development process.
Subscribe to:
Posts (Atom)
Posts
