Quick and Easy Case Building
Functionally, there are only two major roles within MedEdQR, the Case Builder (CB) role and the User role (Student, Faculty or Assistant). The CB accesses the web-based application to construct cases which are composed of textual information (e.g. patient history), physical exams, lab panels, profiles, lab tests, and supporting media (e.g. heart sounds, X-rays and other rich media). To support case construction, an extensive database of standard physical exam components and lab tests are incorporated. Once selected for a case, these elements are made case specific through the entry of test/exam results and interpretations. A comprehensive media database is also incorporated. This library is searchable and its elements easily added to any case, case page, and physical exam or lab test. The CB also has the ability to import additional media into the library as well as reference media from the Internet. A list of Internet available resources is included in the system. In addition to building cases, the CB also manages case metadata, users and groups, and can generate case QR code booklets, case summaries and other reports and analytics. Examples of case metadata include case availability (by dates or by “active” switch), activation status of student decision tracking and content progressive release, and case unit selection (US or SI).
Extensive Library of Physical Exams and Lab Tests
The content elements of a case depend largely on its purpose, focus, intended audience, and delivery modality. Defining the purpose of a case, such as to introduce students to symptoms of a myocardial infarction (MI), is necessary but insufficient by itself to determine the case elements. Is the case to focus on gathering patient history or emphasize patient / doctor interactions (Professionalism)? Is the case to focus on the execution and reporting of physical exam procedures (Clinical Skills)? Or is the case to focus on diagnosing a medical problem (Medical Knowledge), or a combination of all three? Thus, a case is like a recipe with only three ingredients (Medical Knowledge, Clinical Skills, and Professionalism) – yet the amounts of each depends on the purpose, focus, intended audience, delivery modality. To make case development easier, regardless of case purpose, the MedEdQR application provides to the case builder a library of 18 Physical Exam types or categories including Vital Signs, Cardiovascular, Cranial Nerves, Eye, Head and Neck, to name just a few. Each exam type, the Abdomen for example, is made up of one or more result fields; in this case, Observation, Abdomen sounds, Auscultation, Palpation and Percussion.
Likewise, MedEdQR provides a library of more than 280 standard laboratory tests, presented as individual tests or aggregated into Lab Profiles (21) and Lab Panels (11). Lab tests are accessed by name or abbreviation and all have both SI and US lower and upper units pre-defined but can be customized by the CB. When building a case, the case builder selects the lab test, panel or profile and adds the “result” necessary and an interpretation if necessary.
Extensive Library of; Case Media
An important feature of the MedEdQR platform is its extensive pre-populated media library. The default library contains nearly 100 heart sounds and waveforms, more than 60 lung sounds, bowel sounds, lung and heart reference graphics, and a large number of physical examination videos and graphics. The library can be easily expanded to include a department’s specialized content (text, graphics, audio, video, radiology, etc.). Content doesn’t have to be uploaded. Through the use of URL referencing, a CB can add external content to the library. Each library element can be named, categorized, and given a description that is hidden from the students. Media can also be made private or public (which shares it with ALL users of the platform).
Once entered into the media library, media can be searched by name, and description, and filtered by category, or ownership. Any media element can be previewed prior to use, and previewed once added to a case.
To make it easier to find applicable case media, a available Resources page contains hundreds of links to mostly free content.
Case Assignment to Groups and/or Individuals
A department consists of Users, Cases, Devices, Programs, and Groups. The system administrators create the Departments, and Programs, specify the maximum number of Devices that the department can validate and define the department’s Case Builders. The Case Builder is responsible for creating Cases, managing Users, Groups, and Devices, and associating Cases to individuals and/or groups. The purpose of case association is to allow a single case to be used in many ways. For example, Case X could be associated with an individual student for remedial purposes and at the same time be associated with one or more groups under one or more programs for classroom work. With each association, there are a number of options that are independent of other associations of the same case. In one instance, tracking might be engaged while “Progressive Release” might be disabled. Progressive Release is a feature which forces students to progress through case pages linearly – hiding subsequent pages until previous page(s) are viewed. Cases can also be hidden from the group or individual to allow for release timing or pre-release setup.
There is two ways that Case association can be accomplished within the UI; namely from within the Cases workflow, and alternately through the Groups workflow. Assigning cases to an individual can only be done through the Cases workflow. Within the Cases workflow, if associating a case to an individual, a list of students is provided and the student is simply selected. If associating to a group, a list of groups is presented for selection. Within the Groups workflow, the CB selects the group and a list of cases is presented for selection. Once the individual or group is selected, association options are completed and saved.
Of course it’s easy to remove the associations or change association options at anytime.