Repository navigation
feat(golden-id): return OpenCR golden id (CRUID) to the EMR and store as ECID - #68
Merged
Merged
Conversation
… as ECID on patient save
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.
What
After a patient is fed to OpenCR and deduplicated, resolve the golden record id (CRUID) and store it on the local patient as the ECID identifier — so the EMR holds the enterprise identity the Client Registry returns.
How
MpiClientService.getGoldenRecordId(patient)— queries OpenCR by the patient's iSantePlus ID, finds the linked golden record (by golden tag), and followsreplaced-byto the surviving golden on merges. Returns null if unmatched.MpiClientService.synchronizeGoldenRecordId(patient)— resolves it and stores it as the identifier type configured bympi-client.pid.goldenRecordType(default ECID), suppressing the export advice so the write does not re-trigger a feed.PatientUpdateWorker— runs on patient save after the PIX feed, so registration automatically stamps the golden id locally.mpi-client.pid.goldenRecordType(defaultECID).Notes
mpi-client.goldenRecordUuid).