{"id":838,"date":"2016-01-25T19:08:06","date_gmt":"2016-01-26T03:08:06","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Morris-Medical-RiskPack-Data-Type-34-Sequence-of-Events-34\/ba-p\/381026"},"modified":"2026-03-26T05:31:49","modified_gmt":"2026-03-26T09:31:49","slug":"morris-medical-riskpack-data-type-sequence-of-events","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/morris-medical-riskpack-data-type-sequence-of-events\/","title":{"rendered":"Morris Medical: RiskPack Data Type "Sequence of Events""},"content":{"rendered":"

Welcome back to Morris Medical: a eries for medical device development companies – and companies who are related to such companies – providing useful information about Polarion solutions<\/A> and Polarion extensions<\/A>.<\/p>\n

Today we will discuss the subject of Polarion’s RiskPack extension<\/A>, and have a look at RiskPack Data Types.<\/p>\n


\n

Data Type “Sequence of Events” (sequenceOfEvents)<\/H3>
\nDocumenting sequences of events that lead to harms is the main task during risk analysis. Therefore, the
\nRiskPack provides a distinct work item type for sequences of events. A sequence of events can be modelled as
\ncomplex or as simple as needed for the device under consideration.<\/p>\n

Therefore, a lot of information can be stored in other work items and linked to the sequence of events (in complex cases) or the whole sequence of events can be described within the work item’s description field (in simple cases). However, it is important that the harm the
\nsequence of events leads to is documented in a separate work item (of type “harm”) and linked with the
\n“ends_with” linkrole.<\/p>\n

To work properly, the RiskPack expects Sequence of Events work items to meet the requirements listed below:<\/p>\n

Required Custom Fields:<\/STRONG>
\n