Fix Swaqgger Doc pathing issue

[pat-johnson-dev]

Happened to notice what looks like an issue with the Swagger documentation when looking at it today. See screenshot below, looks like we're duplicating endpoints due to trailing / character.

While updating this, please note in the documentation whether or not the binary data being passed in the payload should be base64 encoded or not.

[ratheesh-kr]

@pat-johnson-dev

We are supporting both endpoints—/bundle/ and /bundle—to ensure compatibility and flexibility for users consuming the FHIR Bundle API.

While this may appear as duplication in the documentation, it reflects the actual design of the API. If required, we can work on updating the Swagger documentation to provide additional clarity on this point.

We will update the documentation to clarify whether binary data in the payload needs to be base64 encoded. For your reference, the data we are receiving is in the form of a zip file. This detail will be added to the documentation to ensure clarity.

[pat-johnson-dev]

@ratheesh-kr In both cases, I was looking at the Swagger page while on a call with a colleague and the questions arose as it wasn't totally clear.

I think supporting both with and without the / makes sense but maybe it can be noted somehow that either is valid? The question of which one to use was instantly brought up.

Regarding the payload, I think we can ignore that. I think initially they were sending an actual string in the payload but once we pointed out the requirement to use multipart/form-data, we no longer needed to worry about the encoding.