Issue #2300 - Add calls to beforeHistory and afterHistory #3411
Conversation
This file contains 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
lmsurpre
reviewed
Mar 1, 2022
fhir-server/src/main/java/com/ibm/fhir/server/util/FHIRRestHelper.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Troy Biesterfeld <tbieste@us.ibm.com>
tbieste
force-pushed
the
tbieste-issue-2300
branch
3 times, most recently
from
a0ebc91 to
e4bae71
Compare
Signed-off-by: Troy Biesterfeld <tbieste@us.ibm.com>
tbieste
force-pushed
the
tbieste-issue-2300
branch
from
e4bae71 to
d6224c7
Compare
lmsurpre
approved these changes
Mar 3, 2022
Signed-off-by: Troy Biesterfeld <tbieste@us.ibm.com>
Signed-off-by: Troy Biesterfeld <tbieste@us.ibm.com>
Signed-off-by: Troy Biesterfeld <tbieste@us.ibm.com>
Signed-off-by: Troy Biesterfeld <tbieste@us.ibm.com>
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.
Issue #2300 - Add calls to beforeHistory and afterHistory
System-level history: Requires
user/*.readorsystem/*.readauthorityExample: https://localhost:9443/fhir-server/api/v4/_history
System-level history (with
_typeparameter): Requiresuser/<resource_type>.readorsystem/<resource_type>.readauthority to each resource type in the_typeparameter.Example: https://localhost:9443/fhir-server/api/v4/_history?_type=Patient,Observation
Type-level history: Requires
user/<resource_type>.readorsystem/<resource_type>.readauthority to the resource type.Example: https://localhost:9443/fhir-server/api/v4/Patient/_history
Signed-off-by: Troy Biesterfeld tbieste@us.ibm.com