{"id":966,"date":"2014-08-25T08:14:43","date_gmt":"2014-08-25T15:14:43","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Morris-Medical-Monday-Polarion-MedPack-Role-Concept\/ba-p\/380896"},"modified":"2026-03-26T05:33:13","modified_gmt":"2026-03-26T09:33:13","slug":"morris-medical-monday-polarion-medpack-role-concept","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/morris-medical-monday-polarion-medpack-role-concept\/","title":{"rendered":"Morris Medical Monday: Polarion MedPack Role Concept"},"content":{"rendered":"

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<\/A> and Polarion extensions<\/A>.<\/p>\n

Today we will continue on the subject of Polarion’s MedPack extension<\/A>, and have a look into MedPack’s Role Concept.<\/p>\n


\n

MedPack – Role Concept<\/H3>
\nTo support the demand for independence of creators and reviewers of deliverables, MedPack implements its own role concept in addition to the roles already defined by Polarion ALM. Specific roles are needed to perform certain transitions between the different phases of a work item in its workflow.
\n

MedPack Roles<\/H3>
\nMedPack provides the following four distinct roles.
\n
\n
\n
\n
\n
\n
\n
\n
Role<\/TH>
\n		Name of the role in the Polarion implementation<\/TH>
\n<\/TR>
\n
Admin<\/TD>
\n		project_medpack_admin<\/TD>
\n<\/TR>
\n
Developer<\/TD>
\n		project_medpack_developer<\/TD>
\n<\/TR>
\n
Reviewer<\/TD>
\n		project_medpack_reviewer<\/TD>
\n<\/TR>
\n
Tester<\/TD>
\n		project_medpack_tester<\/TD>
\n<\/TR>
\n<\/TBODY>
\n<\/TABLE>
\nAdmin<\/STRONG>
\nAn admin in a medical project has all rights for the project. Admin can create, edit and read all project texts and work items. Admin can also assign a user to a specific role. An admin user should have an understanding of medical projects and administration of Polarion software.
\nIf a project is really small or if there are other reasons not using specific roles, all MedPack users can be assigned to the Admin role.
\nDeveloper<\/STRONG>
\nA developer is working on work items in the creation phase and is allowed to request reviews of the item whenever he or she thinks the work item is done. A developer cannot close a work item.
\nReviewer<\/STRONG>
\nA reviewer is responsible for the review phase. He or she can pick work items marked as “request review”, perform the review and either reopen or close the work item. A reviewer is not allowed to change a work item itself, which is the job of the developer.
\nTester<\/STRONG>
\nA tester is a special role for any kind of test work items. A tester is only performing a test. The test must first be created by a developer and be reviewed by a reviewer, before the tester can perform the test, document the results and request evaluation of the results. The evaluation of the test result itself is again the job of a reviewer.
\n

Workflow Transitions and Required Roles<\/H3>
\nThe responsibilty of the roles in the work item workflow is shown in the picture and table below.<\/p>\n

\"WorkflowRequiredRoles\"<\/A><\/p>\n

 <\/p>\n

For more information about Polarion’s MedPack visit our Extension Portal using following link:
\nhttp:\/\/extensions.polarion.com\/extensions\/31-polarion-alm-medpack-iec-62304<\/A>.<\/p>\n

I hope you liked this article and you will visit our Blog again when there is another Morris Medical Monday <\/B>article.<\/p>\n


\n

\"webinar<\/A><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"

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 Polario…<\/p>\n","protected":false},"author":63333,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-966","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/966","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/users\/63333"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/comments?post=966"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/966\/revisions"}],"predecessor-version":[{"id":967,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/966\/revisions\/967"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=966"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=966"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=966"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=966"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=966"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=966"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}