Trust self-signed certificates when using the eHX FHIR proxy

[DanPaseltiner]

PULL REQUEST

Summary

The eHealth Exchange FHIR proxy currently uses a self-signed TLS certificate. Since we are no longer trusting self-signed certs globally in the application to restore our connection with eHX we need to configure trust them when making requests to eHX

Related Issue

Fixes #2578

Acceptance Criteria

Please copy the acceptance criteria from your ticket and paste it here for your reviewer(s)

For frontend PR’s - include a description (including anything that’s out of scope) for what you want the designers to review

• ex: “Check out the whitespace on the page, as well as the dropdowns in the form. Here is the corresponding Figma link. You can ignore everything else. Also, the button at the bottom doesn’t work now”

Additional Information

Anything else the review team should know?

Checklist

• If this code affects the other scrum team, have they been notified? (In Slack, as reviewers, etc.)

[robertandremitchell]

looks good. seemed a tad slow when I tested with Cucumber Hill but otherwise worked

[DanPaseltiner]

looks good. seemed a tad slow when I tested with Cucumber Hill but otherwise worked

Using eHX adds more hops to responses are slower and if you used the Cerner server that one tends to be slower still because there is an auth process that happens as well.