You can use simple passwords in your OpenLabyrinth cases to restrict access to parts of your case, using a hidden node.

This is a bit fiddly to do at present, primarily for advanced authors. (To be refined.)

1. In your case map, using Visual Editor, create a new node that is not linked to any other. Once you have updated the master map, make a note of the Node ID number for this hidden node.

2. Create a single-line QUestion in the case, in the usual fashion.

3. Within the Rules for that QUestion, you will use a basic syntax something like this…

The first line says to go to Node 12757 if the answer is blank. The second line says to go to Node 12758 if there is a successful match (but you wouldn’t use something as obvious as “password”, would you? (Yes, I know that millions do!)). The third line tells OLab what to do if there is no match for what has been entered.

Using this approach, the author can control where in the case the User ends up, depending on what they answer. This same approach was originally designed for basic interpretation of free-text entries. But several authors have found this useful for providing password-only access to their Instructor Guides (see previous post).

To facilitate sharing of cases between schools, it is helpful if there is an Instructor Guide (not same as the User Guide for OpenLabyrinth) for each case. This gives some tips to teachers about how best to use the case, special features, learning objectives etc.

At the moment, there is not a common repository for these. When cases are fully published, the Instructor Guides will be available via MedEdPortal. (MedEdPortal requires an Instructor Guide as part of the submission.)

Until recently, we had no particular place to put ’em in a case either. So they only were sent along with a case, if the author remembered.

I am now pleased to say that we can now embed them directly into the case:

1. Upload the guide into the Files section for the case.
2. In the case Details, near the bottom, in a poorly named section called ‘Labyrinth verification’, you will see the last button says ‘Instructor guide complete’.
3. When you click on [Yes], it then provides a drop-own list of stuff from that case’s Files section. Simply point to the guide.
4. [Save changes] blue button at bottom.

Now your Instructor Guide can be moved along with the case when you Export it.

Some sites might be concerned that this is ‘giving away the answers’ along with the test. Taking the above approach does not immediately make the Instructor Guide available to learners; only to authors. You have to embed a link to the Instructor Guide in one of the Nodes if you want learners to see it.

Some of our authors have taken a neat approach where they hide the Instructor Guide in a node behind a password. Then they can control who gets to see the Instructor Guide, without providing author access to the case.

We’ll cover how to use password-protected Nodes in another issue in the blog.

There have been so many changes to OLab3. And, as usual, the documentation is woefully behind.

So I am very grateful to some authors from our SharcTOOTH project who have spent many hours in updating and reorganizing the User Guide.

The official guide for v3.1 of OpenLabyrinth is available from

http://openlabyrinth.ca/wp-content/uploads/2014/02/OpenLabyrinth-v3.1User-Guide.docx

This is always a work in progress – we aim to migrate it from its current state as a MS Word docx file to a wiki, using Atlassian Confluence. This will make it much easier to multiple authors to keep the guide updated, without worrying about version control etc.

While the guide is still being actively updated, the best place to grab the most recent (cluttered) version from is my Dropbox account:

https://dl.dropboxusercontent.com/u/3159431/openLabyrinth_UserGuide_v5m.docx

If anybody has expertise with Confluence and would like to help us migrate this behemoth of a document, I’d love to hear from them. Email us at

info AT openlabyrinth DOT ca

The dev team has created a whole bunch of small improvements in v3.1.1

These improvements are particularly useful for advanced developers and teams.

As usual with a new release, there are likely also some glitches, so if you are using OLab in a production environment where stability is paramount, we suggest that you stick to v3.1 for the moment.

For those who want it, v3.1.1 can be downloaded from Github at

https://github.com/olab/Open-Labyrinth/releases/tag/v3.1.1

The dev team have done a wonderful job in placing some safeguards that help prevent team members from overwriting each others’ work.

Increasingly, we find that great cases are a team effort. But not many virtual patient authoring platforms out there support team authoring. The collaborative touches that we mentioned in January have been improved.

But the big thing is that there is now a check-out mechanism in place. When one author starts editing in a case, other authors are prevented from working in conflicting areas. Some of the editing modules like the Visual Editor open the entire labyrinth at once. So, when such a tool is in use, many other dev tools are locked for that case by OLab.

But when an author is working with a tool that is more focused, such as the Node Editor, only that node in that case is locked. So two authors can be working in two separate areas of the case concurrently.

This is not completely bullet-proof. There is only so much that is feasible in a browser environment, given the funds that we have. But it generally works pretty well and has saved my bacon several times now over the past couple of weeks while we had a team working on some competition cases.

At the end of every case, registered users can have the option to get a detailed feedback report on how they did on the case. But while some of the analytics available were quite powerful, they were not very accessible.

We have been working on improving the Session Reports. On the testbed server at http://demo.openlabyrinth.ca we now have some initial improvements in place. Plus, you can now export this Session Report to Excel for further analysis.

It is now easier for case authors to embed much more sophisticated feedback about your performance. More information on this will shortly be available in the improved User Guide.

If you have particular requests on what you would like to see in these Session Reports or other ways in which to improve them, now is a good time to tell us. info AT openlabyrinth DOT ca

From the last post, you will have seen that anyone can get a case going in OpenLabyrinth. But for more extensive projects involving many cases, it is best to get a team going. A mix of skills and activities often makes for a more productive setup.

Coming soon to OLab3 is a set of enhancements that will make collaborative authoring more feasible. Look for things like hidden node comments (visible only to authors), object annotations, integrated messaging, workflow management (at a simple level).

For example, just finding useful images from the web to illustrate the finer points of your case can be incredibly time consuming. Do you want to burn hours of your skilled clinical authors’ time on this when they can better focus on crafting good case narratives? Our new markup and annotation tools will make it easier to ensure that images are properly attributed and licensed, before publication.

I had a very pleasant surprise today. I just received an email from a medical student at Harvard. She had installed her own OpenLabyrinth server on her Mac, and used it to create her own case from scratch with no outside help.

She was asking for a way to able to publish this for her colleagues. I was delighted to give her an account on our demo server so that she can make this widely available.

But for me, it was a lovely testimony that we are approaching the point where anyone can do this. Now, I admit that setting up your own OpenLabyrinth server is still not as straightforwards as we would like, but you no longer have to be some high powered sysadmin to do so.

Keep the feedback and ideas coming. This platform is gaining strength through your wonderful collaboration.

OpenLabyrinth virtual patient cases are very powerful and allow the case authors to be very creative in terms of case complexity, variety, types of feedback and learner analysis.

But the cases always have the same look and feel… which gets a bit boring after a while.

We are pleased to announce that we are testing some very interesting new layout features that will allow authors to design cases and pages that look very different, and accept a whole new way of interacting with them.

The skin and display editors are still in late alpha/early beta mode. We’ll provide links to some example cases when they are ready.

In the meantime, if you are itching to explore this, give us a buzz.

The OpenLabyrinth team has been working for some time with the College of Family Physicians of Canada (CFPC) SharcFM group on creating virtual patient cases for a shared curriculum in family medicine across Canada.

SharcFM is a coordinated effort, involving all 17 medical schools in Canada, creating shared content and curricular materials for clinical clerks, that can be repurposed and easily adapted to the needs of any group.

For those who are interested in such shared materials, you can find some details here:

https://sites.google.com/site/sharcfm/sharc-fm-home

On December 7th, the University of Calgary Dept of Family Medicine secured some funding and is pleased to lead a collaborative initiative in further developing virtual patient cases for all of the core topics in SharcFM.

If you are interested in collaborating, please contact us:  info AT openlabyrinth DOT ca