Add support for historical data sorting #4245
Open
Conversation
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
This update allows sorting of historical data based on the '_sort' parameter. A new method, 'getHistorySortOrder', validates the provided _sort parameter and a new field, 'historySortOrder', has been added to the FHIRHistoryContext class. Additionally, the error message for invalid _sort parameter has been improved. Signed-off-by: Berkant KARDUMAN <berkant.karduman@tigahealth.com>
Signed-off-by: Berkant KARDUMAN <berkant.karduman@tigahealth.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
In this update, we have introduced a feature allowing the sorting of historical data based on the '_sort' parameter. A method, 'getHistorySortOrder', has been added to validate the provided _sort parameter and a new field, 'historySortOrder', has been attached to the FHIRHistoryContext class.
Now system supports following queries.
Descendion order by lastUpdated
GET {ResourceName}/{id}/_history/?_sort=-_lastUpdated
Ascending order by lastUpdated
Closes Issue #4237