In most customer projects, we end up using the customer's existing enterprise API Gateway to expose FHIR endpoints. This is particularly prevalent with payer customers most recently. Their API Gateway team will request an OpenAPI specification for the FHIR endpoint we are exposing. As you can imagine, with the number of resources available in FHIR, manually generating an Open API spec would be a nightmare. While there have been InterSystems Community tools created for this in the past, I have also made my own tool for the time being. My tool can point at any FHIR endpoint, read the Capability Statement at /metadata and create an OpenAPI spec JSON file.
It would be nice if this was an out of the box feature as it's something just about everyone using a FHIR server would need.
Thank you for submitting the idea. The status has been changed to "Needs review".
Stay tuned!