-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add $export and $everything operations to generated swagger / openapi #3409
Comments
Dag pointed out that with the Patient and Group level exports listed under those resource types, but bulkdata-status under "Other", that An alternative organization would be to list Group and Patient $export operations together with the system-level $export and $bulkdata-status operations. Then:
|
Due to https://www.ibm.com/support/pages/apar/PH44666 the openapi/ui page is not loading properly. Despite that, I was able to confirm that there are no openapi validation errors during startup and that each of the following exists in the all-in-one openapi.json in fhir-openapi:
Patient/$everything is missing the POST flavor (although thats probably not so bad). More concerning is that While in there, I'll think about reorganizing the operations to address Dag's concern above. |
and group export-related operations together - in the all-in-one they now have tag "Bulk Data" - in the file-per-resource they are all in export-swagger.json / export-openapi.json Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
issue #3409 - add bulkdata-status to all-in-one openapi
Is your feature request related to a problem? Please describe.
instead of biting off all of #865 we'd like to selectively add support in the swagger/openapi for just these couple operations
Describe the solution you'd like
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Acceptance Criteria
WHEN the user navigates to
[base]/openapi/ui
THEN the page contains entries for these operations
AND it should be possible to invoke the operations from the page
Additional context
The text was updated successfully, but these errors were encountered: