To access the logbook learners must be enrolled in a course that is marked as including clinical experiences, and has loggable curriculum tags configured with minimum requirements.
Learners have a separate page for each course they are enrolled in and can log entries for any course while actively enrolled (i.e., the curriculum period includes the current .
A note on communicating logbook requirements with learners: There is no user interface that easily allows learners to see all details of all their logbook requirements across courses in one table. While learners can view how many entries have to be observed, how many have to be in a particular setting, etc. there is not a matrix view that shows them how these configurations interact. For that reason, you may find it useful to provide students with a table that shows them these requirements, especially if you have complicated logbook requirements.
Click the user icon in the top right and select 'Logbook'.
Click on a course name to switch courses if needed.
You'll see a list of curriculum tags or tag subsets and an overview of the requirements and your progress towards those requirements (e.g., 60% of required entries in an ER setting).
Click on a label (e.g., ER) to view additional details about your logged entries (e.g., 4 Required, 0 Completed).
Grey labels show the entries required and green labels show the entries completed.
Click the chevron on the right side of a tag subset to view completion details for individual tags.
Click the tag name or black chevron beside the tag name to view a list of existing entries.
From the user icon in the top right, select 'Logbook'.
Click 'Log Entry' at the top of the logbook.
Complete the information, noting the following:
Encounter Date: This is required and can be set to before the current date if a learner needs to log a past experience.
Encounter Time: This is automatically set to the time when the current time but can be adjusted as needed.
Rotation: This will be preset with the course you were looking at but can be adjusted as needed.
Clinical Site: Click anywhere in the bar to access a list of available sites, and then click on the appropriate site. (If no sites were configured for the course logbook this option will not appear.)
Patient Age Range and Gender: These will appear as default fields on all logging forms and Gender will automatically be 'Not Specified'.
Clinical Tasks: This is where the learner can indicate which tags they are logging with this form. Learners can add more than one tag to a form; if they do they will have a place to log the details for each tag.
After you specify a clinical task you will be prompted to enter additional information. What you are required to enter and your options for the different fields has been configured by an administrator.
If a learner is logging multiple entries on one form, they will see a Global Preceptor option. This allows them to easily apply the same preceptor to all the tags (although they can still change the preceptor on a specific task).
Preceptor: This field will appear if an observer is required for this entry. Start typing a name to get a list of people, and then click on the appropriate name.
Note that a list of recently used preceptors will display for your convenience.
If you need to add an external user (i.e., someone without an Elentra account), click 'Add external user'
Provide first and last name and email address.
Click 'Create'.
Setting: Click anywhere in the bar to access a list of available settings, and then click on the setting in which you completed this encounter.
Role: Click anywhere in the bar to access a list of available roles, and then click on the role that best describes what you did during this encounter.
Notes
Reflection
Time Spent (minutes): This will only display to learners if the loggable encounter was configured to require time. Time is entered in minutes.
You can clear the contents of a form by clicking the eraser icon.
Users will be asked to confirm their decision. Click 'OK' to confirm.
To deselect a task and remove it from the logging form click the small x beside the eraser icon.
Users will be asked to confirm their decision. Click 'OK' to confirm.
Click 'Save'. You will get a success message and the entry will be added to your list of logged entries.
Navigate to your logbook and select a course.
You’ll see an overview of the requirements for each loggable objective (e.g. setting names, roles, etc.). Click on a specific label to see your requirements and progress within that category.
Click the chevron on the right of the card to expand it and view the overall count of logged entries.
Click the down chevron to view a list of all logged entries within that requirement.
If a top level card is the title of a hierarchical tag set, you’ll see multiple objectives within that set when you expand the card.
Click the down chevron beside an objective to view a list of all logged entries for that objective.
To make curriculum tags available as loggable you must flag them as such in Manage Curriculum. If a tag is not set as loggable you will still be able to assign it to a course, but it will not be visible under the course Logbook tab. You must be a user with administrative role permissions to manage curriculum tags.
In addition to making curriculum tags loggable, you may wish to consider how you store lists of curriculum tags you expect learners to log. How tags are stored in tag sets will impact both how administrators configure logbook requirements for a course and how learners view their logbook requirements.
In the example below the curriculum tag set has three levels. The first level stores a course name, the second includes Procedures and Encounters (as headings) and the third are the loggable tags.
Using a structure like the above, subset of tags (i.e., Procedures and Encounters) can be assigned to a course. If your hierarchy has multiple levels you should assign the second last level hierarchy to the course (e.g., if you have level 1, 2, 3, and 4, assign level 3 to the course and all tags in level 4 will be applied to the logbook).
Administrators can optionally set requirements for all tags within the group at once. (They can further customize each tag as needed.)
Learners will see overall progress for a group of tags and can open each to view details for each tag.
One thing to consider if you store curriculum tags in course specific hierarchical lists is that you may end up with duplicated tags stored for different courses. This may impact reporting you wish to do since learners will have logged entries to different tags even though they represent the same thing (e.g. if hypertension were a tag a subset for a pediatrics and listed again for cardiology).
Because of this some organizations prefer to store their tags in a flat list so that their reporting can be cleaner.
In the example below the tag set has one level, in other words it's a flat list.
Each tag will be assigned to a course individually.
Administrators will set the requirements for each tag individually.
Learners will see a list of all tags when they view their logbook requirements and will have to click in to each to see specific requirements.
Navigate to Admin > Manage Curriculum.
Click 'Curriculum Tags' from the Manage Curriculum card on the left sidebar.
Click the checkbox beside the appropriate curriculum tag set.
Click 'Make all loggable' below the list of tag set titles.
To set all tags within a tag set as not loggable, click 'Make all unloggable'.
If you wish to specify that certain curriculum tags within a tag set are loggable and others aren't, you must individually set each tag as loggable.
Navigate to Admin>Manage Curriculum.
Click 'Curriculum Tags' from the Manage Curriculum card on the left sidebar.
Click on the appropriate curriculum tag set.
In list view, hover over a curriculum tag and click the pencil icon to edit the tag. In table view, click the pencil icon to edit the tag.
Click the checkbox beside "This curriculum tag should be loggable in the Experience Logbook."
Click 'Save'.
Tags set as loggable will be available to any course to which they are assigned as course objectives.
Staff:admin users as well as staff:pcoor and faculty:directors affiliated with a specific course will be able to access Admin > Clinical Experience and the logbook.
Navigate to Admin > Clinical Experience.
To view a logbook for a single learner, search for the learner as necessary and click 'Logbook' on the learner card. You will jump to the Progress Report for that learner.
To view logbook reporting for multiple users, click on the Logbook tab below the Clinical Experience header.
Set course/cohort and curriculum period filters as needed. Click on a filter to open a dropdown selector. Click on the filter again to close it.
Filter by course to view all learners enrolled in a course. Note that you can apply multiple courses so carefully check you’ve included the ones you want. After you select a course, you can set the appropriate curriculum period.
Filter by cohort to view all learners in a cohort.
To remove a course or cohort from the list, deselect the course/cohort name or click 'Clear Filters'.
By default the page will filter to 'Learners who have incomplete logbooks'.
If your organization uses Clinical Experience > Rotation Schedule and has enabled the logbook to use rotation schedules for reporting:
Elentra checks learners’ rotation schedules and sees which rotation the learner is currently scheduled in. If learners are half way through a rotation but have less than 50% of the logging requirements complete, they are deficient. (Note a developer can change this threshold in the database as required. The database setting is logbook_outstanding_percentage)
If a learner is booked into two slots within the same course, the system will take the dates of the second slot to measure completion.
If you are not using Clinical Experience > Rotation Schedule, learner deficient status will be based off of curriculum period dates.
Note that you can download a CSV from multiple pages; each CSV should reflect the information you were viewing in the user interface.
CSV will include: learner name, learner #, learner email, list of courses and number of pending entries for each course.
Some CSV options will offer you two download versions:
Course overview: Show total count of required and logged entries organized by course.
This will include learner name, learner #, learner email, course name (called rotation), objective, required, and logged.
Course entries: List all logged entries for the learner with details like date, role, setting, etc.
This will include learner name, learner #, learner email, course name (called rotation), objective, required, logged, encounter date, patient age range, patient gender, role, setting, site, preceptor, and notes.
You'll see a list of learners and their overall logbook completion status (e.g. 3 Outstanding).
Click the plus icon to open a view of the learners logbook progress in multiple courses.
Click on View Details to open a Progress Report for a specific learner in a new tab.
Filter by course and curriculum period.
Optionally View Details or download a CSV.
If downloading a CSV opt for Course Overview or Course Entries.
Click ‘View Details’ on a course card to see an overview of progress.
From each objective you can click the + icon to see an overview, and then click ‘View entries’ to see a list of individual logged entries.
The logbook module in Clinical Experiences allows an administrator to define requirements like number of entries, learner role in the experience, and the setting of the experience. Learners can log experiences and both learners and admin/faculty can view learner progress in a logbook.
The logbook is an optional feature of Elentra and can be turned on or off using a database setting (logbook_active).
Some additional things to be aware of:
Currently Elentra supports setting logbook requirements per course, per curriculum period. There is not currently a way to set up logging requirements per rotation on a rotation schedule. (If an organization has three courses, and each course has its own rotation, just configure a logbook for each course.)
Learners view their logbook requirements and completion per course.
You can connect the logbook to Clinical Experience > Rotation Schedule so that a learner's logbook deficiency is determined based on how far through a rotation they are. Note that for this deficiency reporting the logbook will apply only the dates of the final booked slot if a learner is booked in multiple slots for a rotation during one curriculum period.
There are not currently automated email notifications for the creation of logbook entries, nor deficient statuses. We hope to restore this ability soon.
There is not currently a link between the logbook and the Assessment and Evaluation module to automatically trigger an assessment form for a procedure when a learner logs a procedure. You can set up procedure assessment forms using workflows so that learners can initiate a form and send it to their preceptor as needed.
Database Setting
Use
logbook_outstanding_percentage
Defines the threshold for level of completion to set 'complete' status in Clinical Experience > Logbook reporting
logbook_log_inactive_rotations
Used to control whether or not to allow learners to create logbook entries for courses where their enrolment in the curriculum period has passed.
Build a curriculum tag set and flag each applicable tag as "loggable" (complete via Manage Curriculum).
Set a course as including clinical experiences and assign the appropriate curriculum tags to the course (complete via Manage Courses > Setup tab and Curriculum Tags tab).
Define the requirements for each loggable encounter (complete via Manage Courses > Logbook tab).
Have learners complete and log encounters (learners access this via the Logbook tab under their user icon).
Report of logbook completion via Admin > Clinical Experiences > Logbook.
After curriculum tags are set as loggable, they must be assigned to a course and curriculum period and the requirements for each tag defined.
To assign objectives to a course you must have administrative role permissions; the task is completed via Admin > Manage Courses on the Curriculum Tags tab for a course.
You can find more detail about the steps required to assign curriculum tags to a course on the Course Setup help page but one important detail to note is how you assign the objectives depending on whether you have a tag set with or without a hierarchy.
If you have a one-level or flat tag set, you should assign each individual curriculum tag that you intend to require logging for.
If you have a tag set with a hierarchy and you want to include all of a subset of tags in the logbook, assign the parent tag of the subset you want to the course. For example, if your tag set has has levels 1, 2, 3, and 4, assign level 3 to the course and all tags in level 4 will be applied to the logbook.
There are three tabs you can use to set up requirements for loggable tags: entries, roles and environment (settings). The options you define on these tabs dictate the requirements learners have to fulfill and also what fields they can must complete when they log an entry.
Entries includes:
the minimum number of times a learner has to log something
whether comments are required for a logged entry
whether reflection is required for a logged entry
whether an observer (e.g., a preceptor) is required for a logged entry
whether time tracking is required for a logged entry
if you require time tracking you must define a minimum number of hours
Roles lets you define which options will be available to a learner to record in what capacity they participated in an encounter.
Note that it is possible to adjust the list of roles and their descriptions in the database (the table is logbook_lu_roles). You will need help from a developer to do this.
Environment lets you define the settings a learner can pick from when they log an entry.
Navigate to Admin > Manage Courses.
Click on the name of a course and then the Logbook tab, OR click the menu cog to the right of the course name and select 'Logbook'.
Make sure you are working in the correct curriculum period, or switch it if necessary.
Click 'Edit' beside any curriculum tag or subset of tags to set the requirements.
If working with a hierarchical tag set, click the plus icon on the 'Overall configuration for <tag set title>' to open the overall configuration options. This allows you to apply a default configuration to all tags in a set and then make individual changes as needed.
Entries options include:
Require Comments: If you check this off, the learner will be required to include comments when they log an entry for this tag.
Require Reflection: If you check this off, the learner will be required to include a reflection when they log an entry for this tag.
Require Observer: If you check this off, the learner will be required to indicate the name of the person who observed them when they log an entry for this tag.
Require Time Tracking: If you check this off you can define a minimum number of hours. Learners will have to log a time estimate when they log an entry.
Min: Use the plus and minus buttons to indicate if there is a minimum number of encounters required for this tag.
If using a hierarchical tag set: The Overall configuration for comments, reflection, observer and time tracking will apply to all included nested tags, however, the Min. set here is for the total number of encounters for the tag subset (i.e., 5 logged encounters across however many tags are included in the subset).
Click 'Apply'.
You will see a success message.
If you are using a hierarchical tag set, the Overall configuration menu will collapse and you can adjust the entry requirements for individual tags as needed (e.g. remove notes requirement from a certain tag, or indicate specific minimum numbers for individual tags).
To adjust the entry requirements for an individual tag (e.g., to remove the requirement for an observer on a particular tag), make the change on the tag card.
Click 'Apply' for each tag when complete.
You will get a success message after your change is saved. Close the window by clicking 'OK'.
On the Roles tab you can define whether or not a learner is required to indicate the role they played in an encounter. The default options are observed, performed with help, and performed independently.
Click 'Edit' beside a tag/tag set.
If you are using a hierarchical tag set, click the plus icon beside the tag set name to reopen the Overall configuration menu, then click on 'Roles' to apply a default setting to all tags.
Check off 'Require Roles', this will open a list of roles to select from.
Check off each role that you want to include for a tag; when you do this you will have the option to set a minimum requirement per role as needed.
Click 'Apply'.
You will see a success message.
If you are using a hierarchical tag set, the Overall configuration menu will collapse.
To adjust the role settings for an individual tag, click on 'Settings'. This will open another menu (you should see your default settings already applied). Adjust the role options and requirements for individual tags as needed.
Click 'Apply' for each tag when complete.
You will get a success message after your change is saved. Close the window by clicking 'OK'.
On the Environments tab you can define whether or not a learner is required to indicate the setting of an encounter, and specify the environments available to learners when they log entries. The default options are displayed below.
Click 'Edit' beside a tag/tag set.
If you are using a hierarchical tag set, click the plus icon beside the tag set name to reopen the Overall configuration menu, then click on 'Environments' to apply a default setting to all tags.
Check off 'Require Environment/Settings'; this will open a list of environments/settings to select.
Check off each environment that you want to include as an option for a tag; when you do this you will have the option to set a minimum required number as needed.
Click 'Apply'.
You will see a success message.
If you are using a hierarchical tag set, the Overall configuration menu will collapse.
To adjust the role settings for an individual tag, click on 'Settings'. This will open another menu; click 'Environments' (you should see your default settings already applied). Adjust the environment options and requirements for individual tags as needed.
Click 'Apply' for each tag when complete.
You will get a success message after your change is saved. Close the window by clicking 'OK'.
You can reopen a curriculum tag card at any time to view a summary of all the minimum requirements you've configured for a tag or tag set. Learners will see similar tags on their logbook entry pages.
In the example below the tag requires 5 entries to be logged in total, and the minimum requirements are that 1 is in the clinic, 1 is in an emergency setting, etc. It is possible for a learner to fulfill multiple requirements with one logged entry (e.g. a task performed with help in an emergency setting). Please see the note here about communicating logbook requirements to learners.
If your organization uses Clinical Experience > Rotation Schedule to schedule learners into rotations, you can optionally select to base your logbook reporting off of the rotation schedules.
If you check off the "Use this course rotation schedule to generate the logbook report" option, Elentra will checks learners’ rotation schedules to determine logbook completion.
If a learner has not yet started a rotation for a particular course, they will not show up as deficient.
For current or past rotations, if learners are half way through the rotation but have less than 50% of the logging requirements complete, they will display as deficient. (Note a developer can make a database setting change to adjust the threshold to measure logbook completeness. The database setting is logbook_outstanding_percentage)
Note that if a learner is booked into two slots within the same course, the system will take the dates of the second slot to measure completion.
If you are not using Clinical Experience > Rotation Schedule, learner logbook deficient status will be based off of curriculum period dates.
Please note that applying the course setting to use the rotation schedule to determine logbook completion is NOT specific to a curriculum period. If you enable this option, it will apply to all curriculum periods associated with the course.
At the bottom of the Logbook page you can define sites available to learners when they log entries for a course. Your options will depend on the sites defined in Manage Locations.
Click anywhere in the 'Select a site' bar.
Hover over a site name and click on it or press Enter to add a site to the list.
Sites will display in the order added to the Course Sites list.
To remove a site from the list click the small 'x' beside the site name.
Click 'Save'.
You will get a success message.
Please note that the Sites list stored with a logbook is not specific to a curriculm period. Therefore, please include all sites that are applicable to all learners in the course (regardless of curriculum period).
