CDR Tickets

Issue Number 5042
Summary Modify CDR Summary Schema to create new SVPC summary
Created 2021-10-15 09:55:35
Issue Type New Feature
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2021-10-15 10:53:13
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.300612
Description

As a patient summary editor, I want the ability to create a summary document as a SVPC summary in the CDR to support the SVPC initiative. The summaries created using this new functionality will be published to Can combined with other SVPC summaries for the PDQ content partners.

Currently all summaries within the CDR are the usual PDQ summaries. The current PDQ patient liver cancer treatment summaries would be split into multiple SVPC summaries that would be published as their own separate pages on cancer.gov with their own URLs and several individual SVPC summaries will be combined as one master partner summary for the content partners using the vendor filters.

The current summaries schema needs to be modified to allow for the creation of these SVPC summaries.

Scenario: CDR has the ability to create summaries as SVPC summaries

Given: I am a CDR patient summary editor

  And I have permissions to create summaries in the CDR

 And I have permissions to edit summaries in the CDR

When I create a new summary in the CDR

Then I want to be able to designate it as a SVPC summary document in the CDR

 

 

Scenario: CDR has the ability to create summaries as SVPC summaries

Given: I am a CDR patient summary editor

  And I have permissions to create summaries in the CDR

 And I have permissions to edit summaries in the CDR

When I edit a new summary in the CDR

Then I want to be able to designate it as a SVPC summary document in the CDR

Comment entered 2021-10-15 10:53:13 by Kline, Bob (NIH/NCI) [C]

New top-level SVPC attribute installed on CDR DEV.

Comment entered 2021-10-15 11:42:08 by Englisch, Volker (NIH/NCI) [C]

Please note that there are some summary documents that can not be loaded to XMetaL.  We made schema changes for OCECDR-4631 (Keep docs at Refresh)

but these changes were not originally part of Ohm.  I will still need to fold these changes into Ohm to prevent documents including the "KeepAtRefresh" attribute from failing to load.

Comment entered 2021-10-15 11:48:37 by Englisch, Volker (NIH/NCI) [C]

Is there or will there be another ticket to identify a summary as "Export only"?  This new attribute allows us to mark the parts of a split summary but once the legacy summary is split we will also need an indicator for that other summary to easily distinguish it from a legacy summary.

Comment entered 2021-10-25 14:44:12 by Osei-Poku, William (NIH/NCI) [C]


Is there or will there be another ticket to identify a summary as "Export only"?  This new attribute allows us to mark the parts of a split summary but once the legacy summary is split we will also need an indicator for that other summary to easily distinguish it from a legacy summary.

Hi  Can you explain this?  I don't understand this completely.

Comment entered 2021-10-25 14:56:07 by Englisch, Volker (NIH/NCI) [C]

This has been taken care of by Bob with ticket OCECDR-5053 and creating the top-level attribute SVPCMerge.

Comment entered 2021-10-25 15:03:46 by Osei-Poku, William (NIH/NCI) [C]

Verified on DEV. Thanks!

Comment entered 2021-10-29 08:08:52 by Kline, Bob (NIH/NCI) [C]

FYI for this ticket: that attribute has been renamed to PartnerMergeSet.

Comment entered 2022-05-26 13:52:20 by Osei-Poku, William (NIH/NCI) [C]

Verified on QA and PROD. Thanks!

Elapsed: 0:00:00.001278