Multitenancy on hapi-fhir server (Backend)

[f-odhiambo]

If you wish to allow a single endpoint to support multiple tenants, you may supply the server with a multitenancy provider. This means that additional logic will be performed during request parsing to determine a tenant ID, which will be supplied to resource providers. This can be useful in servers that have multiple distinct logical pools of resources hosted on the same infrastructure. More details are outlined here.

Some use cases:

1. Large organisations, like UNICEF, might be well served by a tenant per country or regional office in an organisation-wide multi-tenant setup
2. Demos, staging, organisations without on-prem, data isolation requirements can use a multi-tenant server with faster setup
3. On-prem with multi for preview vs production
4. In addition to integration tests, see how we can get check guarantees around data isolation, high risk

Some new questions from today's scoping

1. How do we sync data and configs to build a certain app ?
2. What level of configurability do we aim to achieve above scenario?
3. For Questionnaires how do we make sure we can build 'flavours' of the same app e.g

• WHO Questionnaire no Personal Identifiable Info and removal of risk flagging / adverse effect reactions
• JnJ Questionnaire Comorbidity and Risk Flagging and Adverse effects

3. How do we filter by a practitioner per location per usage/ health vertical?
4. How do we take care of duplicates? Clients/ Patients enrolled on various verticals?
5. How do we go about demarcating and separating client data?