Morris Medical Monday: Polarion MedPack Work Item Workflows (Part 3 of 3)

By morrisd

Welcome back to Morris Medical Monday: a weekly series for medical device development companies (and companies who are related to such companies), providing some useful information about Polarion solutions and Polarion extensions.

Today we will continue on the subject of Polarion’s MedPack extension, and have a look into MedPack’s Work Item Workflows.

Standard Workflows

According to the table in Part 1 of this post, four standard workflows can be identified for all work items in MedPack.

Verification Workflow

The verification workflow is valid for all work items which are planned and created by the manufacturer and therefore have a verification phase.


Evaluation Workflow

The evaluation workflow is valid for all work items which creation and adaption is not under the full control of the manufacturer and therefore do not have a verfication, but an evaluation phase. Also, there is no creation phase.


Feedback Workflow

The feedback workflow is an extended evaluation workflow with an optional creation phase. Some information might have it’s origin outside of the defined processes, but could also be created inside of them. Therefore, these items might, but not neccessarily have to have a creation phase.


Full Workflow

The full workflow is used for all things that are created and need some kind of execution. Work items with this workflow need to pass all four phases described above.

FullWorkflow_Overview (1)

How to Learn More

For more information about Polarion’s MedPack visit our Extension Portal using following link:

As we are now entering the summer vacation season, I’ll give this series some time off as well. If I run across something especially interesting during the next couple of months, I’ll post it. Otherwise, watch for another Morris Medical Monday article sometime in September. I wish you a nice summer and good holidays, whatever you may be doing!

Medical Device solutions by Polarion Software

Leave a Reply

This article first appeared on the Siemens Digital Industries Software blog at