{"id":1016,"date":"2014-06-02T14:24:54","date_gmt":"2014-06-02T21:24:54","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Morris-Medical-Monday-Polarion-MedPack-Traceability\/ba-p\/380870"},"modified":"2026-03-26T05:33:33","modified_gmt":"2026-03-26T09:33:33","slug":"morris-medical-monday-polarion-medpack-traceability","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/morris-medical-monday-polarion-medpack-traceability\/","title":{"rendered":"Morris Medical Monday: Polarion MedPack Traceability"},"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 Traceability.
\n

Traceability<\/H2>
\nAlong with reviews, providing traceability (see IEC 62304:3006->3.32) between deliverables (see IEC 62304:3006->3.6) is one of the main requirements of IEC 62304. By providing traceability it can be proved that decisions have been thoroughly reflected and possible consequences have been considered. Therefore, it is one of the most important factors for quality and patient and user safety, which is the focus of IEC 62304.
\n

Traceability Requirements of IEC 62304:2006<\/H2>
\nThe picture below shows the traceability requirements for the deliverables of IEC 62304:2006 with dashed lines. The labels describe the type of link and the clause of the standard requiring the links (in brackets). MedPack represents most of these deliverables with Work Items, some with dedicated wiki pages.<\/p>\n

\"Traceability\"<\/A>
\n

How MedPack handles traceability<\/H2>
\nTraceability is provided by Polarions’ standard link roles. However, special link roles according to the diagram above are defined for MedPack’s work item types. The table below shows these link roles.
\nMedPack Link Roles<\/STRONG>
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
traceability meaning<\/TD>
\n		impact meaning<\/TD>
\n		Description<\/TD>
\n<\/TR>
\n<\/THEAD>
\n
traces to<\/TD>
\n		leads to<\/TD>
\n		Used for decision traceability.<\/TD>
\n<\/TR>
\n
covers<\/TD>
\n		covered by<\/TD>
\n		Used for relations between documentation and development artifacts.<\/TD>
\n<\/TR>
\n
implements<\/TD>
\n		implemented by<\/TD>
\n		Used for relations between concepts and concrete deliverables implementing those.<\/TD>
\n<\/TR>
\n
part of<\/TD>
\n		decomposed into<\/TD>
\n		Used to describe relationships of architectural elements (SW System, SW Item, SW Unit and SOUP)<\/TD>
\n<\/TR>
\n
detected by<\/TD>
\n		detects<\/TD>
\n		Used for relations of qm measures and resulting error descriptions.<\/TD>
\n<\/TR>
\n<\/TBODY>
\n<\/TABLE>
\nThe provision of links is not enforced in any way, any work item can be created, modified and closed without any checks. This keeps MedPack flexible for any kind of development lifecycle model. However, checking and analysing the existences of links is a focus of the wiki pages in the Product Documentation Wiki<\/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>. 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


\n\"Webinar<\/A>
\n<\/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 Polarion sol…<\/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-1016","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/1016","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=1016"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/1016\/revisions"}],"predecessor-version":[{"id":1017,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/1016\/revisions\/1017"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=1016"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=1016"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=1016"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=1016"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=1016"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=1016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}