You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using the $mdm-link-history operation gives 404 Not Found after doing a $mdm-clear and $mdm-submit first.
To Reproduce
Steps to reproduce the behavior:
Setup MDM module
Create a Patient resource. This creates source resource Patient/1 and golden resource Patient/2
Perform a $mdm-link-history?resourceId=1 query. Notice successful response.
Perform a $mdm-clear and wait for the job to complete
Perform a $mdm-submit to re-submit Patient/1. This will create a link between Patient/1 and a new golden resource Patient/3
Perform a $mdm-link-history?resourceId=1 query --> Operation gives 404 response with the following body
Expected behavior
Operation succeeds and should show the link that exists after clear and submit, (in this example, the one between Patient/1 and Patient/3)
Environment (please complete the following information):
HAPI FHIR Version: master branch
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Using the
$mdm-link-history
operation gives 404 Not Found after doing a$mdm-clear
and$mdm-submit
first.To Reproduce
Steps to reproduce the behavior:
Patient/1
and golden resourcePatient/2
$mdm-link-history?resourceId=1
query. Notice successful response.$mdm-clear
and wait for the job to complete$mdm-submit
to re-submitPatient/1
. This will create a link betweenPatient/1
and a new golden resourcePatient/3
$mdm-link-history?resourceId=1
query --> Operation gives 404 response with the following bodyExpected behavior
Operation succeeds and should show the link that exists after clear and submit, (in this example, the one between
Patient/1
andPatient/3
)Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: