organizeOutputBy=Patient query parameter #55
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.
Summary
This PR reworks the $export operation
_bySubject=Patient
query parameter to align with the Argonaut Bulk Data Access IG'sorganizeOutputBy
query parameter.New behavior
The
organizeOutputBy
query parameter is now implemented for resourceType Patient. OnlyorganizeOutputBy=Patient
is implemented. This query parameter works for all $export types- system-level, Patient, and Group. Also removes the_bySubject=Patient
functionality.Code changes
README.md
- replaces_bySubject
query parameter withorganizeOutputBy
src/services/export.service.js
-_bySubject
->organizeOutputBy
test/services/export.service.test.js
- adds unit teststest/util/exportToNDJson.test.js
- remove test relating to_bySubject
Testing guidance
npm run check
npm run start
organizeOutputBy=Patient
UI switch:npm run dev
inbulk-export-app
_bySubject
have been removedorganizeOutputByTests.json