What Weams Actually Does For Healthcare Education
Weams is an online examination and learning management platform used primarily in medical and healthcare schools. It handles everything from multiple-choice quizzes to OSCE station tracking. The system is used by universities across Europe and parts of Asia. If you are setting up exams or managing question banks, Weams is one of the more common tools on campus. It has a specific interface that some staff find clunky, but it gets the job done once you figure out the quirks. People often talk about Weams as if it is transforming healthcare, which is a stretch. What it actually does is digitize assessment workflows that used to involve paper, spreadsheets, and a lot of manual grading. That shift matters. A single examiner in my program used to spend three days manually scoring and compiling results from printed questionnaires. With Weams configured correctly, the same process runs in under an hour. The "revolution" part is just automating that boring administrative work. The platform works through a web browser. You create a test, populate it with questions, assign it to students, and the system grades it automatically for objective question types. For essay-style answers, you export the data and grade it manually within the system or in an external tool. It is not particularly clever about that second part. But for MCQs, single-answer, and multiple-answer questions, the automation is reliable.
Setting Up Your First Exam
I have configured dozens of exams in Weams over the years. Here is how the process actually goes, not the simplified version from the manual. First, log into the institutional Weams portal. You will be given a default account by your university's IT or exam office. If you do not have one yet, contact them directly. Personal sign-ups are generally not available for student or staff accounts. Once logged in, navigate to the Exams section and click Create New Exam. Here is where most people hit their first problem. The exam creation form has multiple tabs, and some fields are hidden behind dropdowns that do not expand properly on older browsers. Use Chrome or Firefox. Do not use Edge if your institution runs an older Weams version, because the JavaScript sometimes fails to load the question bank selector. I lost two hours to this exact issue during finals week one semester.
Fill in the basic exam metadata: title, course code, date, duration, and the number of attempts allowed. Set the time zone carefully. If your students are in different locations, mismatches here have caused genuine grading disputes. One student complained her exam auto-submitted before the scheduled start time because the server timezone and her local timezone were eight hours apart. This happened to me once with a partnered overseas campus. Now I always check the timezone line twice before publishing. For the question bank, you can create questions directly inside Weams or import them. The import feature supports CSV files. I recommend building your questions in a spreadsheet first, then importing, because Weams has no bulk-edit capability. Edit 200 questions one by one inside the system and you will understand why nobody does it that way. The CSV format expects these columns at minimum: question text, type, option A, option B, option C, option D, correct answer, and explanation. You can add more columns for points, tags, and difficulty level, but keep the core ones exact. Weams is rigid about column order in its import parser. Rename a column and the entire file imports as blank questions. I learned that the hard way.
Get the Full Details
Question Types and What Actually Works
Weams supports several question types. Most healthcare programs use these four regularly: Single-answer MCQ is the bread and butter. Students pick one correct option. Simple. Reliable. Grading is instant. This is what you should default to for knowledge-based assessment. Multiple-answer MCQ lets students select more than one option. The tricky part is configuring the scoring rule. By default, Weams applies partial credit proportionally. If there are four correct options and a student picks three, they get 75 percent. That behavior is configurable per question, but the setting is buried inside the question edit screen under a dropdown labeled Scoring Method. Most staff never find it. If your program wants strict all-or-nothing grading for safety-critical questions, set it there.
Match the pairs works for drug-disease or pathway associations. I have used this for pharmacology exams. The interface for building matches is drag-based and somewhat slow. Building a 50-pair question takes about ten minutes. Factor that into your scheduling. Open-ended questions are text boxes where students write answers. Weams does not grade these automatically. You review and score them. The value here is that the system timestamps every submission and prevents edits after the exam closes. That matters for audit purposes during accreditation reviews. One counter-intuitive detail: Weams does not penalize blank answers automatically unless you configure a penalty rule. Some universities assume a wrong answer gets zero and a blank gets zero. They are right by default. But if your rubric requires a penalty for unanswered items, you must enable that in the exam settings before publishing. It is off by design.
The OSCE Module and Why It Needs Attention
If your program runs OSCEs, Weams has a module for it. This is the part that most people struggle with. The OSCE builder lets you create stations, assign time limits, link patient scenarios, and track examiner scores in real time using tablet or phone devices. The problem is the device compatibility layer. The OSCE scoring app works on iOS and Android, but older Android versions have a known issue where the timer desyncs from the server by up to thirty seconds. This sounds minor until you are running a tight six-minute station cycle and examiners are arguing about whether a student had enough time to finish the physical exam portion. I ran into this during a trial run. The workaround was switching to the web-based scoring interface instead of the app for those particular stations, which avoided the desync entirely. Another thing the documentation does not emphasize enough: examiner login credentials for the OSCE app must be pre-created in the system before the exam day. If you try to add examiners on the fly, the sync takes long enough that people miss their rotation window. Plan credential creation at least two days ahead. I have seen programs scramble because someone forgot this step.
Data Export and Reporting
After an exam runs, Youams generates reports. The built-in analytics show class averages, question difficulty indices, and item discrimination values. The discrimination metric is useful for catching poorly written questions. If a question has negative discrimination, meaning high-performing students got it wrong and low-performing students got it right, the system flags it. I use this filter to catch ambiguous questions before they come up in appeals. Export options include CSV, SPSS, and PDF. The SPSS export is the one most faculty need for research or program evaluation. It preserves variable labels and value sets. Make sure you select the SPSS option if your statistical workflow depends on labeled variables. The CSV export strips labels by default, which causes confusion later.
Limits You Should Know About
Weams is not a perfect system. It has real limitations. The platform does not support integration with many LMS products out of the box. If your university runs Canvas or Moodle and you want single sign-on or grade passback, check with your IT department first. Some campuses have built custom connectors. Others have nothing, and you manage grades separately in Weams and manually enter them into the LMS. The system also lacks real-time collaborative editing. You cannot co-author a question bank with another faculty member simultaneously. If two people edit the same question at the same time, the last save wins. This is a genuine risk during busy exam construction periods. I solved it by designating a single question owner per bank and sharing updates through email rather than direct simultaneous edits. Mobile testing for students is supported, but the experience is not smooth on small screens. The interface was designed for desktop use. Students taking exams on phones report layout issues with multi-select questions and longer text passages. If your student population includes many mobile-only users, consider providing lab access or advising against phone-based testing.
What You Should Check Before Going Live
Here is a short checklist I follow before publishing any exam in Weams, based on mistakes I have made and fixed: Verify timezone settings match your student body's primary region. Test the exam as a student by enabling preview mode and walking through every question. Check that the grading scheme matches your intended scoring policy. Confirm all required attachments or media files are embedded and not just linked from an external server. Review the export format to ensure it matches your reporting needs. Send a trial run to a small group of students before the full launch. I skip none of these steps. Each one has saved me from a problem that took hours to untangle after the fact.
Weams is a functional tool for healthcare assessment. It is not elegant, and it has friction points that matter during busy exam periods. But once you understand how it works, the repetitive grading and tracking work disappears into the background. That is the real benefit. Not revolution. Just a less painful administrative process.
