Tools for the Medical School



Under construction...

The Pinkas project


The Pinkas is a tool that is being developed for the Medical School to help students build a portfolio of their progress throught the clinical years.
It is, essentially, a group of Advanced features that were added to the Database activity plus various summaries for both students and those responsible for courses and clinical years.
(The summaries combine data across courses and instances of Moodle and - for those responsible - across students and mentors.)

What is a Pinkas?

A Pinkas is a collection of Tasks undertaken by a Student.
Each Task is of a particular Type - perhaps an admission to the ward, or a shift in A&E - and is part of a Database
A Task is supervised by one of the doctors that was present at the time that the student undertook it. These are the Mentors.
A Mentor is required to approve or provide Ranks or a Grade, and or/provide Feedback, on the Students's performance at the Task.
Each course has a Facilitator (aka. Supermentor) who is responsible for ensuring that every Student fulfills the requirements of the Databases.
The requirements may include more than one Database, each with a minimal number of Tasks of each of several Types with approval or sufficient Ranks or Grade.
If Mentors are required to provide Feedback, also their performance may be assessed by the Facilitator.
In each clinical year there is a Coordinator who is responsible for ensuring that each Student fulfills the requirements of all that year's courses.

How is a Pinkas built up?

A Pinkas spans all the clinical years.
Each clinical year is a collection of courses.
  (For some students, a clinical year may span several Moodle years.)
Each course has one or more Database activities that is a collection of Tasks.
A Task is a Database entry.
A Database entry is targetted by the Student to his Mentor for that particular Task.
  He does this by selecting a Target user. Target user is a type of Database field.
Feedback is a Database field that can be edited only by the Target user for that Task.
  Any field can be designated as Feedback.
Rank is a type of Database field that can take a value from a pre-determined selection e.g. Poor, Satisfactory, Outstanding.
Grade is a type of Database field that takes a numeric value that can be calculated automatically from all the Rank fields.
  (Both Rank and Grade are always Feedback fields.)

Roles and capabilities

The following applies if the Target users or Feedback feature is enabled:

  • Only a Student can add entries to the Database (regardless of capability mod/data:writeentry).
    An entry may have one or more Target user fields. Any of the fields can be Feedback fields.
  • A Mentor can view, approve, and edit only entries in which he is a Target user.
    He can edit only Feedback fields. See below
  • A Facilitator can view, approve, and edit all fields of all entries.
A Mentor is any user with capability mod/data:approve (Teacher, TA, Grader...).
A Facilitator is any user with additional capability mod/data:managetargetusers (Supermentor, Coordinator...).
Note: Currently, the Mentor and Supermentor roles are available only in the Dental and Medical Schools.

Database settings

The following features were developed in the Database especially for the Pinkas project.
The Database settings are in section Advanced features.

Show picture
If enabled, the default templates include the name and official picture of the user who created the entry.
The name and picture are not shown to the author of the item.

Enable Target users
If enabled:
  • Settings Approval required, Allow comments on entries, Entries required before viewing and Maximum number of entries are disabled.
    Approval required is set to Yes. Allow comments on entries is set to No. The other two are irrelevant.
  • Field type Target user is available.
    It can be either an autocompletion field or a menu.
    It can be configured to include:
    • All users with particular roles and/or
      • All users in any of the Student's group, or
      • All users in particular groups, or
      • All users in any of the Student's groupings, or
      • All users in particular groupings
    It can be configured to send a notification to the Target user when the field is set or changed .
    (There can be more than one Target user field.)
  • Only Students can create entries
  • Approving an entry simply marks it as approved. It does not release it to the view of anyone else.
  • The View list tab allows selection by Target users, approval status (if approval is required) and submission status (if Submission is enabled).
    A Target user field that is restricted to particular entry Types, is shown only if one of those Types was selected.
    (Target user fields are not included in the default Advanced search template).
  • Tags are disabled. (The default Add and Single templates do not include ##tags##.)
  • If Show picture is enabled, the default templates do not show the name and official picture to the user who created the entry
  • Advanced search does not include Author fields for users who can create entries.

Enable Feedback
If enabled:
  • Any field can be designated as Feedback.
  • Students can edit only fields that are not Feedback.
    (A student's Edit template does not include Feedback fields.)
    Mentors can edit only Feedback fields.
  • The Fields tab shows which are the Feeback fields.

Enable Entry types
A set of Entry types can be configured. For each Type, the minimal number required for course completion can be specified.
If there are any, then:
  • Instead of the Add entry tab, there is an Add tab for each Type.
  • Any of the fields can be configured to be restricted to particular Types.
  • The Type of entry is shown
  • The Fields tab shows the Types of each field.
  • The View list tab allows selection by Type.
    If a Type is selected, Advanced search includes only fields relevant to that type.

Enable Ranking
If enabled:
  • Field type Rank is available.
    It is a set of radiobuttons with each button optionally having an associated number e.g.
      2 Outstanding, 1 Satisfactory, 0 Not satisfactory
    (The numbers are not shown in the templates.)
    There can be more than one Rank field and each can be restricted to particular Entry types
  • Field type Grade is available.
    There should normally be only one such field.
    It is similar to the Numeric field type.
    However, if a value is not set, it shows the sum of the numeric values of the Rank fields of that entry.
    Note: If any of the Ranks for that entry are not set, or do not have a numeric value, the field is empty.
  • (NY) If there is a Grade field, then the student is considered to have met the course requirements if, for each of the Entry types he has at least the number of approved entries specified in the Settings, excluding those with a numeric value of zero in any its Rank fields.
    His grade for the Database is the sum of the Grades for the entries.
    (If he has more than the required number of entries, only the highest grades are considered.)

Enable Autoapproval
If enabled:
  • If there are Rank fields the entry is automatically approved if all are filled.
  • Otherwise, if there are required Feedback fields the entry is automatically approved if all are filled.
  • Otherwise, the item can be un/approved when it is edited by a user with approval capability.
    (Even if not enabled, if Approval is enabled and there are no Feedback fields an item can be approved when edited by a Mentor.)
Entries with Rank fields or required Feedback fields cannot be approved manually.

Enable Submission
If Submission is enabled, it can be either optional (i.e. a Student can save without submitting) or forced (i.e. an entry is immediately submitted on saving).
Students can no longer edit entries that have been submitted.
Mentors see only entries that have been submitted and, if notification is enabled, are notified only when the entry is submitted.
Entries that have been saved but not submitted are highlighted in a different color to entries that have been submitted but not approved.


Templates

The templates determine which fields are displayed:
  • A field that should not be shown to the user who created the entry should have style property @@author@@
  • A Feedback field should have style property @@feedback@@
  • A field that is to be used only in entries of Type xxx should have style property @@xxx@@.
  • Likewise, a field that is used in only in entries of Type xxx and yyy should have style property @@xxx@yyy@@ and so on.
  • A Feedback field that is to to be used only in entries of Type xxx should have style property @@feedback@xxx@@##.
  • Likewise, a Feedback field that is used in only in entries of Type xxx and yyy should have style property @@feedback@xxx@yyy@@ and so on.
The @@...@@ strings are either removed or replaced with display: table-row;, depending on the Type and/or whether the user is a Student or Mentor.
Note: There should not be more than one such string per line of template.

The following alternative syntax is also valid:
  • A field that should not be shown to the user who created the entry should have style display:none;##display: author##
  • A Feedback field should have style display:none;##display: feedback##
  • A field that is to be used only in entries of Type xxx should have style display: none; ##display: xxx##.
  • Likewise, a field that is used in only in entries of Type xxx and yyy should have style display: none; ##display: xxx## ##display: yyy## and so on.
  • A Feedback field that is to to be used only in entries of Type xxx should have style ##display: none; ##display: feedback xxx##.
  • Likewise, a Feedback field that is used in only in entries of Type xxx and yyy should have style display: none; ##display: feedback xxx## ##display: feedback yyy## and so on.
Patterns like ##display ...## are either removed or replaced with display: table-row; depending on the Type and/or whether the user is a Student or Mentor.
Of course, the style should cover also the label.