Peer learning workflow overviewTopic number: 1526973902335

Within peer learning workflows, radiologists provide individual and group feedback on reports, share knowledge with peers, and indicate learning opportunities.

Use cases for peer learning

A peer learning workflow can be started in the following cases:

  • Users want to share interesting studies with peers or trainees.
  • Users find a gap in a work procedure.
  • Users detect a learning opportunity while reading a study.
  • The outcome of a surgery conference is different from the report conclusion and offers a teaching case for radiologists.
  • Pathology comes back and the result is different from what was assumed in the report.
  • Cases are created as a result of risk management meetings.

Use cases for peer review

A peer learning workflow can be also used for peer review in the following cases:

  • Evaluation of radiologists’ performance (for example, 100% of reports created by a new radiologist are reviewed).
  • Quality assessment campaign as part of the accreditation process. For example, 10% of a radiologist’s reports on CT procedures must be reviewed by colleagues every year.
  • Second reading.

Examples of peer learning workflows

The administrator can configure a peer learning workflow by granting permissions to users to perform tasks. Two main peer learning workflows are explained below.

1) Peer learning workflow for radiologists (simple workflow)

Simple peer learning workflow that can be used by peers to identify the report author is replaced with asterisks in the following fields:

In the basic workflow, radiologists process peer learning cases by performing the following tasks:

Task with iconRoleDescription

New case New case

Case submitters, such as radiologists, technologists, and clinicians

Cases can be created:
  • Manually—If configured by the administrator, when users detect a learning opportunity, they can manually create a new case for a study with or without a report by right-clicking this study and selecting Start new case to start a case by themselves or Create new case to create a case and assign it to another user.
  • Automatically—The administrator configures a workflow rule that triggers the random automatic creation of peer learning cases for a specified percentage of created reports.

    The administrator can define additional conditions under which cases are created: for example, only for reports created for CT studies by the radiologist A who works at the department B.

    When a report is validated, a random number between 0 and 100 is generated, if this number is equal to or less than the percentage specified in the workflow rule, a new case task is created for this study.

    Manually created cases are not included in the percentage of automatically created cases. If a new case already exists for a study, the second case is not created for the same study. You might have to create cases manually if the expected number of automatically created cases was not reached within the expected time frame.

    Automatically created new case tasks are assigned to radiologists (not to the report author).

When performing a new case task, a radiologist (not the report author) evaluates a report, assigns a score to it, and adds comments.

If no other actions must be performed for the current case, the radiologist can close the case. Alternatively, the radiologist can request feedback or submit the case for discussion at a conference.
Right arrow in circle Case feedbackRadiologist

By creating this task, a radiologist requests feedback on a conclusion from another user, such as the report author.

The user to whom the task is assigned provides feedback and sends it to the requester.

New case after feedback Left arrow in circle is assigned back to the original requester.
Start discussion DiscussionRadiologists, Conference ownerCases with discrepancies or those providing a learning opportunity are analyzed by a group of radiologists.

2) Peer learning workflow for radiologists (extensive workflow)

Extensive peer learning workflow

Diagram for extensive peer learning workflow

In the extensive workflow, radiologists perform new case tasks and send cases to the program administrator (for example, head of department or senior radiologist) as a case review task for further processing. In this workflow, the program administrator performs case review and, if required, creates or performs case follow-up tasks:

Task with iconRoleDescription

Case review Case review

Left arrow in circle Case review after feedback (if a case feedback task was performed for this case review task)

Program administrator

When reviewing a case, the program administrator analyzes the report and images, checks the entered data on the peer learning panel, the wording, rewords some content to avoid confronting statements and possibly asks any user for feedback. The program administrator can also notify the report author, if the report will be discussed at a conference.

Case follow-up Case follow-up

Left arrow in circle Case follow-up after feedback (if a case feedback task was performed for this case follow-up task)

Program administrator

The task assignee follows up on corrective actions defined by the program administrator when reviewing a case or by the quality assessment committee during a conference.

Once the necessary actions are taken, the case can be closed.

Purpose of de-identification

To maintain objectivity and prevent bias, sensitive information in the following fields is replaced with asterisks:

  • Patient ID
  • Patient name
  • Accession number (study level)
  • Report author
  • Report signed by
  • Report contributor
  • Reading physician
  • Case submitter

Important!

De-identification is not yet supported when sharing your screen during a conference, or when sharing the Image area with other people via the collaborator tool. In case you need to share the images of a certain study with colleagues in other locations, we recommend using a video conferencing tool.

The link History in the Text area is also disabled.

De-identification can be set at the system and conference levels:

System-level de-identificationConference-level de-identification

If the administrator has enabled the Enable de-identification of peer learning workflow tasks option, sensitive information is hidden during new case, case review, case feedback, and case follow-up tasks.

If a user has the Can overrule system-level de-identification permission, this user can unhide sensitive data by selecting Tools > Show identifiers in the List area.

If the administrator or a user has checked the De-identify option when creating or editing a conference, sensitive information is hidden during discussion tasks of that conference.

If a user has the Can overrule conference-level de-identification permission, this user can unhide sensitive data by clicking Show identifiers in the Text area during a discussion task or in the List area when discussion tasks are listed.

Access to peer learning data

During peer learning tasks, users enter data and select attachment values on the Peer learning tab.

For example, when submitting a new case, a user can type an explanation why a study was selected in the Narrative field and assign to the report a peer review score, such as 1. Concur or 3a. Discrepancy.

Whether or not a user can view, add, or delete the content of a certain attachment on the Peer learning tab, and configure a search field or column for this attachment in the Search area or List area is defined by granted permissions.

Depending on a user’s permissions, the following default attachments can be configured on the Peer learning tab within a peer learning workflow:

Table 1. Peer learning attachments typically used by case submitters
Attachment nameDescription
Learning programIdentifier of a learning program.
NarrativeShort description of a suggested learning opportunity.
ObservationsAdditional observations made during the peer learning workflow.
Peer review scoreScore to indicate the diagnostic accuracy of a report.

Default values correspond to the RADPEER scoring system:

  • 1 - Concur
  • 2a - Understandable miss
  • 2b - Understandable miss but clinically relevant
  • 3a - Discrepancy
  • 3b - Discrepancy and clinically relevant
ScoreA score given by the case submitter. Default values are the following: Agree and Disagree.
Table 2. Peer learning attachments typically used by conference owners
Attachment nameAttachment type
Clinical historyClinical history relevant to the current peer learning case.
Peer learning conference commentsComments made during peer learning conferences.
Table 3. Peer learning attachments typically used by program administrators
Attachment nameAttachment type
Action historyRegistration of actions performed (for example, by the program administrator) during peer learning workflow tasks.
Action itemsList of action items to achieve a learning goal, for example, to review similar studies or to attend a training.
Case submitterUser initiating the case.
ClassificationClassification of a peer learning case. Default values are the following: Perception, Interpretation, Communication, Process/Systems issue.
Clinical follow-upClinical follow-up items, for example, actions required if clinically relevant discrepancies were detected.
Learning pointsList of learning points.
Case rejectedA flag that is set to True if someone rejects the case.
Report excerptsSnippets of related reports, for example, from the active or prior report.

Users can view the Peer learning tab if they perform a peer learning task. They can also access the Peer learning tab outside the peer learning workflow, for example, when opening a study to check for feedback. For this, they need the Can view case outside peer learning workflow permission. By default, the permission is configured as follows:

RolePermission setDescription
Program administratorsAdministrator - peer learning permissionsThe Can view case outside peer learning workflow permission is granted. Users can view peer learning data at any time.
Case reviewers, Conference ownersPower user - peer learning permissions

The Can view case outside peer learning workflow permission has the condition Only if the user contributes to the study as Report contributor, Case contributor. Users can access only peer learning cases for their reports or cases to which they contributed.

Users are considered case contributors if they are assignees of any peer learning task or if they are case submitters.

Case submitters, radiologists performing new case tasksStandard user - peer learning permissions

Peer learning and markup data

We recommend not to add any markup data to images during the peer learning workflow because this data is included when a study is exported.

Customization of peer learning attachments

Your administrator can adapt the peer learning attachment model to your peer learning or peer review process by deactivating existing peer learning attachments and creating new ones.