Uploaded image for project: 'PatientManager'
  1. PatientManager
  2. PAM-676

PIXV3 Query does not return expected id when quering with datasource parameter

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 9.11.6
    • Fix Version/s: 9.11.7
    • Component/s: None
    • Labels:
      None
    • Environment:
      ehealthuisse and cts-axsana
    • Severity:
      Critical - Defect that prevent from carrying out a feature, use case could be accomplished with the help of an operator, memory leak
    • Frequency:
      Occasional - May occured/be used from time to time, in specific situation
    • Account:
      Maintenance 2020 (MAINTENANCE2020)

      Description

      Shen several domains are identified with the same universalId, only one of them is used to filter the domain list and it leads to inconsistencies in PIX responses

       Edit Delete

      The issue was caused by duplicated entries in the Assigning Authorities table : there was 6 entries with a Universal ID set to "2.16.756.5.30.1.194.3.1.1". The Namespace ID was different for each entries : when adding a id to a patient, if the Assigning Authorities is not know by PAM it is added in database but because the namespace id was changed several time is was added several time (each time with a different namespace id).

      This might not be an issue itself but the PIX Manager simulator is retrieving ONE assigning authority by datasource instead of all of them (return query.getUniqueResult().

      As a workaround, the duplicated and unused Assigning Authorities in PAM must be updated : change their Universal ID so that there is only of them (the one used by the patient).

        Attachments

          Activity

            People

            Assignee:
            mtoudic Malo Toudic
            Reporter:
            mtoudic Malo Toudic
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 30 minutes
                1d 30m

                  Potential Duplicates