Issue Number | 5053 |
---|---|
Summary | Modify the summary schema to create master partner summaries. |
Created | 2021-10-18 18:20:03 |
Issue Type | New Feature |
Submitted By | Osei-Poku, William (NIH/NCI) [C] |
Assigned To | Kline, Bob (NIH/NCI) [C] |
Status | Closed |
Resolved | 2021-10-25 12:27:02 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.300779 |
As a patient summary editor, I want to be able to create or modify a summary document that would be used as the master partner document for generating content for the PDQ partners.
The current PDQ patient liver cancer treatment summaries will be split into multiple summaries that would be published as their own separate pages on cancer.gov. We are currently working on being able to create the individual SVPC summaries in the CDR (OCECDR-5042). These summaries would be combined to form one master partner summary in the CDR, and it will be used by the vendor filters to form one summary (per summary topic) for the PDQ content partners.
We want to be able to mark a summary as a master partner summary using a top level attribute on the summary document.
Scenario: CDR has the ability to mark a summary as a master partner summary
Given I am a patient summary editor
And I have permissions to create summaries
And I have permissions to edit summaries
When I create or edit a new summary in the CDR
Then I want to be able to designate it as a master partner summary
Were you asking for suggestions regarding the new attribute name at the meeting? Here are some
PartnerSet
PartnerMerge
PartnerMergeSet
PartnerFuse
PartnerGroup
ExportSet
SummaryJoin
SVPCJoin
SVPCMerge
Or something like that. My preference is SVPCMerge
New SVPCMerge attribute installed on DEV.
Verified on Dev. Thanks!
We decided to change the name of the attribute to
PartnerMergeSet
.
The renamed attribute has been installed on DEV, and the sample document modified to match.
Verified on QA and PROD. Thanks!
Elapsed: 0:00:00.001456