Page Comparison

...

Introduction

Sometimes users wants to close one collection protocol and merge all registrations/data of that protocol with another protocol. In this case, this API is useful to merge two collection protocols . on the basis of the PPID or the participant ID.

Merge happens in following way.Lets say

Source CP - The protocol which wanted is to closebe closed.

Target CP - The protocol in which source CP's registrations wanted are to mergebe merged.

Pre-

...

requisites

1. Only super admin can merge two collection protocols.

...

1. Both CPs must have same label formats for PPI, visit and specimens.
2. Both CPs must belong to same sites.

Merge Logic

...

1. Move all participant registrations to target CP.If
2. participant match found in target CP, then move Match found - Move all visits and specimens of source registration to target registration. If no matched participant found then make source registration
   1. If participant with same PPID is found in target CP
   2. If the participant is registered on both source and target CP
3. Match not found: If participant with same PPID or participant ID is not found, then register the source CP participant to target CP.
4.  Matching Matching of participants is done on basic basis of PPID and participant ID.
5. Map all visits of source CP registration to first event of target CP and mark all created specimens as unplanned.
6. Forms data handling
   1. Participant Level Forms :

      1. For matching registrations,

   it

   1. the system will not merge forms of source registration to target. So in this case forms will deleted along with source registration.

      2.For

   not

   1. non matching participants, forms will be merged along with source registration. Here forms will merge even if that form

   is

   1. does not exist at

   pa*strong text*rticipant

   1. participant level for source cp.

   2. Visit and Specimen Level Forms:

   
   

   1.  All visit and specimen level forms will merge along with visit and specimens.Here same as participant those forms are not a part of target CP those also get merged.

Note: We

...

have not handled/checked container restriction while merging. i.e

...

if specimens are stored in container only for source CP even then

...

registrations will be merged with target CP. We need to handle this manually like change restrictions of container.

 

Use HTTP POST method to call this API by passing the below details in JSON format.

...

URL	http://<host>:<port>/openspecimen/rest/ng/collection-protocols/merge
Method	POST
Request	application/json
json	{      "srcCpShortTitle": "Brain Cancer v2", "tgtCpShortTitle": "Brain Cancer" }
Response	{      "srcCpShortTitle": "Brain Cancer v2", "tgtCpShortTitle": "Brain Cancer" }