{"id":832,"date":"2015-09-09T17:59:36","date_gmt":"2015-09-10T00:59:36","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Morris-Medical-Monthly-How-to-use-RiskPack-Part-3-of-4\/ba-p\/380963"},"modified":"2026-03-26T05:31:43","modified_gmt":"2026-03-26T09:31:43","slug":"morris-medical-monthly-how-to-use-riskpack-part-3-of-4","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/morris-medical-monthly-how-to-use-riskpack-part-3-of-4\/","title":{"rendered":"Morris Medical Monthly: How to use RiskPack (Part 3 of 4)"},"content":{"rendered":"

Welcome back to Morris Medical Monthly: a monthly 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 start on the subject of Polarion’s RiskPack extension<\/A>, and have a look into RiskPack’s Basics<\/EM>.<\/p>\n


\n

Risk analysis: Identify sequences of events<\/H1>
\nAfter the first collection of ideas described in the previous section, you need to define complete sequences of
\nevents. You need to create a new sequence of events work item for each sequence of events, and the – according to
\nyour data model – link the data entered in the previous step with the roles starts with, contains and ends with. In any
\ncase, a harm should be the end of the sequence of events and of course, one sequence of events can lead to
\nmultiple harms or can have multiple starting points.<\/p>\n

After that, you have defined a complete and detailed description of how your device can lead to a harm. The
\nSequences Of Events Table helps you to keep control over your data.
\n

\"Mountain<\/A>Risk analysis: Identify risks<\/H1>
\nUp to this point, you only modeled how your device can lead to a harm, but not how likely that is. That’s exactly
\nwhat you need the work item type “Risk” for. Create a new Risk work item and link the sequence of events it considers
\nvia the link role “considers” with the sequence of events. After that, set the “risk probability” attribute of the risk to the
\ncorrect value according to your analysis. Every such Risk entry will produce a line in the Risk Table and an entry in
\nthe Risk Control Matrix. Depending on your risk policy settings, the RiskPack can automatically identify whether the risk is acceptable or not.
\n

How a risk can be linked to harms and sequences of events<\/H2>
\nEvery risk needs an information on the severity of harm it considers. As the severity of harm is an attribute of a harm
\nwork item, every Risk type work item somehow needs to be linked to a Harm type work item. There are multiple ways this can
\nbe achieved.
\n

A harm is linked via a sequence of events<\/H2>
\nIn the example above, a risk is linked to a sequence of events (via “considers”) and that sequence of events end
\nwith a harm. Therefore, it is clear which harm is considered by the risk. If only a sequence of events is linked to a
\nrisk, the severity of the harm linked with that sequence of events is taken for risk consideration.
\n

Multiple harms are linked via a sequence of events<\/H2>
\nIf multiple harms are linked, the RiskPack takes the most severe severity for estimation of the risk.
\n

A harm is directly linked to the risk<\/H2>
\nSometimes, one sequence of events can lead to different harms in the same way, but the harms have different
\nprobabilities of occurrence. For example, a sequence of events can lead to death with a significant lower probability
\nthan to skin burn. In risk management, that leads to two risks: death (high severity, low probability) and skin burn
\n(medium severity, high probability). In the RiskPack, you will model this by creating two risk entries, both linking to
\nthe same sequence of events, but one also linking to death and the other one linking to the sequence of events and
\nthe harm “skin burn”. If a Harm work item is directly linked to a Risk work item, the severity of that directly
\nlinked Risk is taken for risk estimation. In the end, you will have two rows in your Risk Table and two entries in
\nyour risk matrix, with possible different acceptance levels.
\n

Multiple sequences of events are linked<\/H2>
\nOne Risk can be linked to any number of sequences of events. There will always be only one entry in the Risk Table
\nand the Risk Matrix. Doing this can be useful if the same risk control measure can be used to reduce the probability
\nof occurrence of all the sequences of events considered.
\n

Sequences of events that are absolutely impossible to ever take place<\/H2>
\nIf you have identified and documented a sequences of events in an early stage of risk analysis and later you find out
\nthat this sequence of events absolutely cannot take place, there is a special attribute you can use for this. You
\ncan still create a Risk work item and link it to the sequence of events, but you set the “risk type” to “impossible risk”
\nand leave the probability value unset. This will lead to an entry in the Risk Table for documentation, but not to any
\nentry in the Risk Matrix.
\n

Sequences of events that only take place after application of a risk control measure<\/H2>
\nSometimes, a risk control measure can lead to a new sequence of events that was not possible before application of
\nthe risk control measure. Such sequences of events can be entered just like any other and can be estimated by
\nusing a risk work item just like described above. But there is one difference in that case: Such risks should not be
\nshown in the “Risk Matrix before mitigation”. You can use the “risk type” attribute to tell the RiskPack that this is an
\n“Introduced Risk”, meaning, it was not present before application of risk control measure. It will not show up in the
\n“Matrix before mitigation” then.<\/p>\n

For more information about Polarion’s RiskPack visit our Extension Portal using following link:<\/p>\n

http:\/\/extensions.polarion.com\/extensions\/184-polarion-alm-riskpack-iso-14971<\/A>.<\/p>\n

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

<\/p>\n

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

Welcome back to Morris Medical Monthly: a monthly series for medical device development companies (and companies who are related to such companies), providing some useful information about Polar…<\/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-832","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/832","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=832"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/832\/revisions"}],"predecessor-version":[{"id":833,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/832\/revisions\/833"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=832"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=832"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=832"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=832"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=832"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=832"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}