{"id":1262,"date":"2014-10-06T18:39:07","date_gmt":"2014-10-07T01:39:07","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Morris-Medical-Monday-Work-Item-type-Change-Request\/ba-p\/380911"},"modified":"2026-03-26T05:36:40","modified_gmt":"2026-03-26T09:36:40","slug":"morris-medical-monday-work-item-type-change-request","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/morris-medical-monday-work-item-type-change-request\/","title":{"rendered":"Morris Medical Monday: Work Item type Change Request"},"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 Change Request Work Item.<\/p>\n


\n

Change Request<\/H1>
\n

Description<\/SPAN><\/H3>
\nA change request resulting from either a risk control measure or a problem report, according to clause 9.2 of the IEC 62304:2006. Any issue of this type must be linked to the risk control measure or the problem report it springs from and to the software requirement following the request.
\n

Workflow Steps<\/SPAN><\/H3>
\nThe Change Reques Item uses the standard Feedback Workflow<\/SPAN>.<\/p>\n

\"FeedbackWorkflow_Overview\"<\/A>
\n

Traceability & Impact<\/SPAN><\/H3>
\nA Change Reques Item must be traceable to a Problem Report<\/SPAN> Work Item and has an impact on a Software Requirement<\/SPAN> Work Item.
\nFor more information on traceability and impacts, see the Traceability wiki page<\/SPAN>.
\n

Attributes<\/SPAN><\/H3>
\n

Work Item Attributes<\/SPAN><\/H4>
\nThe following custom fields must be filled out before evaluation can be requested:
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Attribute Name<\/TH>
\n		Type<\/TH>
\n		Description<\/TH>
\n<\/TR>
\n<\/THEAD>
\n
Effect on the organisation [B,C]<\/STRONG><\/TD>
\n		Text<\/TD>
\n		All effects on the organisation have to be analyzed.
\n(as required by IEC 62304:2006<\/SPAN>->6.2.3)<\/TD>
\n<\/TR>
\n
Effect on released software products and systems [B,C]<\/STRONG><\/TD>
\n		Text<\/TD>
\n		All effects on released software products and system have to be analyzed.
\n(as required by IEC 62304:2006<\/SPAN>->6.2.3)<\/TD>
\n<\/TR>
\n
User must be informed<\/STRONG><\/TD>
\n		Enum (Yes\/No)<\/TD>
\n		Decision whether the user must be informed.
\n(as required by IEC 62304:2006<\/SPAN>->6.2.5).<\/TD>
\n<\/TR>
\n
Action taken to inform users<\/STRONG><\/TD>
\n		Text<\/TD>
\n		(as required by IEC 62304:2006<\/SPAN>->6.2.5).<\/TD>
\n<\/TR>
\n
Have additional potential causes been introduced contributing to hazardous situation?<\/STRONG><\/TD>
\n		Enum (Yes\/No)<\/TD>
\n		(as required by IEC 62304:2006<\/SPAN>->7.4.1a)<\/TD>
\n<\/TR>
\n
Are additional software risk control measures required?<\/STRONG><\/TD>
\n		Enum (Yes\/No)<\/TD>
\n		(as required by IEC 62304:2006<\/SPAN>->7.4.1b)<\/TD>
\n<\/TR>
\n
Does the change interfere with existing risk control measures?<\/STRONG><\/TD>
\n		Enum (Yes\/No)<\/TD>
\n		(as required by IEC 62304:2006<\/SPAN>->7.4.2)<\/TD>
\n<\/TR>
\n<\/TBODY>
\n<\/TABLE>
\n

Evaluation Attributes<\/SPAN><\/H4>
\nThe following custom fields must be filled out before evaluation can be finshed and the work item can be closed:
\n
\n
\n
\n
\n
\n
\n
\n
Attribute Name<\/TH>
\n		Type<\/TH>
\n		Description<\/TH>
\n<\/TR>
\n<\/THEAD>
\n
Reviewer<\/STRONG><\/TD>
\n		Text<\/TD>
\n		Person(s) to perform, performing or have performed a review.<\/TD>
\n<\/TR>
\n
Review summary<\/STRONG><\/TD>
\n		Text<\/TD>
\n		Short summary of the review. Attachments should be used for additional information.<\/TD>
\n<\/TR>
\n
Last review date<\/STRONG><\/TD>
\n		Date<\/TD>
\n		Hidden field automatically set when review has been finshed. Intended to be used for sorting and statistical analysis.<\/TD>
\n<\/TR>
\n<\/TBODY>
\n<\/TABLE>
\n

Evaluation Checklist<\/SPAN><\/H4>
\nThe following checklist must be filled out before evaluation can be finshed and the work item can be closed:
\n
\n
\n
\n
Checklist entry<\/TH>
\n		Description<\/TH>
\n<\/TR>
\n<\/THEAD>
\n<\/TABLE>
\n

Possible Resolutions<\/SPAN><\/H4>
\nThe following table shows the possible resolution values when the work item is closed:
\n
\n
\n
\n
\n
\n
\n
\n
\n
Resolution Name<\/TH>
\n		Description<\/TH>
\n<\/TR>
\n<\/THEAD>
\n
Approved<\/STRONG><\/TD>
\n		The change request has been approved and needs to be implemented.<\/TD>
\n<\/TR>
\n
Not Approved<\/STRONG><\/TD>
\n		The change request has not been approved. No further action is needed.<\/TD>
\n<\/TR>
\n
Obsolete<\/STRONG><\/TD>
\n		The change request has become obsolete and is no longer needed.<\/TD>
\n<\/TR>
\n
Discarded<\/STRONG><\/TD>
\n		The work item entry has been discarded. No further attention is needed.<\/TD>
\n<\/TR>
\n<\/TBODY>
\n<\/TABLE>
\nFor 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

FREE WHITEPAPER<\/P>
\n

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