4 Replies Latest reply on Jun 28, 2020 10:41 PM by Sundar Mariappan

    Manual Merge on grand child records

    Sundar Mariappan New Member

      The issue is the grand child record becoming an orphan record during manual merge process. I have explained my issue with the below example.

       

      Before Match & Merge Job Run: (This is snap shot of before merge)

      Job Execution Order - Patient -> Patient Address -> Patient Addr Link

      Patient Table:

      Rowid   CI            FrstName            LastName

      1             4              Michael                Smith

      2              4              Mike                     Smith

      Patient Address Link Table: (PatientId & AddrId are foriegn keys from Patient and Patient Address table respectively)

      Rowid   CI            Patientid              AddrId       AddrType

      1              4              1                              1              Home

      2              4              2                              2              Home

      Patient Address:

      Rowid   CI            Addrline1                      AddrLine2                           City        State

      1              4              180 N KING ST            NORTHAMPTON              MA                       

      2              4              180 N KING ST             NORTHAMPTON              MA  

       

      After Match & Merge Job Run:

      Patient  record matched with fuzzy match on name and waiting for manual merge in IDD(entity 360). The Patient Address & Address link table CI's are promoted to 1 by accept as unique record property.

      Patient Table:

      Rowid   CI            FrstName            LastName

      1             1              Michael                Smith

      2              2              Mike                     Smith

      Patient Address Link Table:

      Rowid   CI            Patientid              AddrId       AddrType

      1              1              1                              1              Home

      2              1              2                              2              Home

      Patient Address:

      Rowid   CI            Addrline1                      AddrLine2                           City        State

      1              1              180 N KING ST            NORTHAMPTON              MA                      

      2              1              180 N KING ST             NORTHAMPTON              MA  

       

      After Manual Merge in IDD:

      Patient record rowid 2 merged with rowid 1 and the child table Patient Address link table re-queued for match &merge as parent records got merged.

       

      Patient Table:

      Rowid   CI            FrstName            LastName

      1             1              Michael                Smith

      Patient Address Link Table:

      Rowid   CI            Patientid              AddrId       AddrType

      1              1              1                              1              Home

      2              4              1                              2              Home

      Patient Address:

      Rowid   CI            Addrline1                      AddrLine2                           City        State

      1              1              180 N KING ST            NORTHAMPTON              MA                      

      2              1              180 N KING ST             NORTHAMPTON              MA  

       

      After MnM Job run :

      The Patient Address link record rowid 2 matched & merged with rowid 1  by the match rule PatientId,AddrType,Addrline1,Addrline2,City & State.

       

      Patient Table:

      Rowid   CI            FrstName            LastName

      1             1              Michael                Smith

      Patient Address Link Table:

      Rowid   CI            Patientid              AddrId       AddrType

      1              1              1                              1              Home

      Patient Address:

      Rowid   CI            Addrline1                      AddrLine2                           City        State

      1              1              180 N KING ST            NORTHAMPTON              MA                      

      2              1              180 N KING ST             NORTHAMPTON              MA  

       

      Now the Issue is => I was expecting the Patient Address table record rowid 2 have to be re-queued and during next batch run, the records will be matched & merged. But it is not happening right now and the Patient Address table rowid 2 become an orphan record with out any relationship record.

       

      Has anyone encountered this issue earlier and have solution for this issue. Your suggestion is much appreciated.

       

      Note - we configured this data model based on the mdm sample Party & Address tables.

        • 1. Re: Manual Merge on grand child records
          Sathiesh M Guru

          Firstly, Address is NOT a grand child per your data model. It is a parent to the Link table similar to Patient table.

          Here Address can be merged by its own match rules, independent of Patient table. This data model is suitable for scenario's like you want to master the Address entity on its own to you can identify the Households belong to same address; doctors practising in same clinic etc

          If that is not of interest to you, then remove the link table and make Address the direct child to Patient

           

          -Sathiesh

          Infa GCS-MDM

          • 2. Re: Manual Merge on grand child records
            Sundar Mariappan New Member

            Thanks Sathiesh for your response. In my case the Patient address table MnM depends on Parent table. It is not an independent table. I cannot have independent match rules here. So for my use case will there be any other workaround other than removing addr link table and linking Addr table directly to the Parent table.

             

            Regards,

            Sundar

            • 3. Re: Manual Merge on grand child records
              Sathiesh M Guru

              If you dont want to master the Address table independently, then the straight forward way is to remove the link table. If you're already in Production with this datamodel, then you can do any workaround like thru userexits to reset the consolidation ind of Address table when Patient records merge. Then run Address table match merge subsequently.

              • 4. Re: Manual Merge on grand child records
                Sundar Mariappan New Member

                Currently we are in development phase. I will think of to remove the Address link table in the data model. Thanks Sathiesh for your inputs.