Repository navigation
fix(pdq): guard null otherDataPoints in loadSearchQuery - #67
Merged
Merged
Conversation
…E on patient search
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
FhirMpiClientServiceImpl.loadSearchQuerythrowsNullPointerExceptionwhenotherDataPointsis null, aborting every FHIR PDQ patient search before any request is sent (and marking the transaction rollback-only).It happens on the standard MPI similar-patient path:
registrationcorecallsfindPreciseSimilarPatients(patient, null, ...), sootherDataPointsarrives null, andloadSearchQuerydereferences it:Fix
Treat a null
otherDataPointsas an empty map at the top ofloadSearchQuery. One guard; no behavior change when the map is supplied.Impact
FHIR PDQ patient search / MPI similar-patient lookup no longer NPEs when called without extra data points; the query is built and sent to the MPI as expected.