Hosted version of Flexpa

[samirunni]

Right now, customers have to stand up and maintain FE and BE servers to use Flexpa. A hosted version would make it more accessible to new customers, by eliminating that need on day 1.

This would be a natural addition to the new caching architecture, since the point of integration could be querying a FHIR store with the cached resources.

There are probably a few ways this could work:

1. Hosted FE and BE: least lift for customer, at the cost of swivel-chairing onto a MyFlexpa-like FE for auth.
   a. Being able to whitelabel the FE would be a nice-to-have.
2. iframe-based integration: customer iframes FE into workflow
3. Hosted BE only: customer creates/operates custom FE, but resources are stored by default in the caching architecture, eliminating the need for customers to host a Flexpa-specific BE.

[healthbjk]

Hey @samirunni, thanks for this request. While we do not offer a hosted front end today beyond the Flexpa Link experience, we'd love to understand the request more. A couple of clarifying questions:

• What extent of front end would you imagine for the "Hosted FE and BE" and "iframe-based integration" options?
  • Does this include a patient facing display of retrieved resources?
  • If so, which resources would be important to display?
  • What interface customization and white labeling would you want or expect?
• In options 1 and 2, how would you expect to receive back the access token necessary to query the FHIR store?
  • In our current flow, you receive this in the callback from launching Flexpa Link.
  • If you are querying the FHIR store, who would you be using the data? You'd need a backend to store the data or your own front end to show it.
• Can you explain the "Hosted BE only" option a bit more? Today, using the Flexpa improved API experience, we do indeed store resources to the cache as described.

[samirunni]

What extent of front end would you imagine for the "Hosted FE and BE" and "iframe-based integration" options?

1. A FE for auth'ing and triggering retrieval of resources. This already exists in MyFlexpa.
2. Support for iframing that auth flow into other web UIs. Looks like this already exists with Link.

There's no need to support viewing the resources. Just recommend partners for that. E.g., you already have this with Tuva.

In options 1 and 2, how would you expect to receive back the access token necessary to query the FHIR store?

Via the Dev Portal.

If you are querying the FHIR store, who would you be using the data? You'd need a backend to store the data or your own front end to show it.

Correct, I still need to build/maintain those components myself. They just can be kept separate from the FE for the auth flow.

Can you explain the "Hosted BE only" option a bit more?

It sounds like you already have this with the caching architecture—that's basically what I'm referring to.