I want to install a new FHIR server from the Management Portal using the below steps, but not able to find FHIR Configuration setting under my newly created foundation namespace.
- Open the Management Portal and switch to the Foundation namespace where you want the FHIR server installed. If you do not have a Foundation namespace, go to Health, and select Installer Wizard from the top menu bar. The Configure Foundation button allows you to create a new Foundation namespace. Be sure to activate the namespace after creating it. Done
- Navigate to Health > MyNamespace > FHIR Configuration. If you do not see the FHIR Configuration menu, make sure you are using a Foundation namespace.
- Select the Server Configuration card.
- In the Endpoints pane, click Add Endpoint to create a new FHIR Endpoint.
- Select a core FHIR package. Each package corresponds to a version of the FHIR standard which the endpoint will support. So, for example, to configure a FHIR endpoint that supports FHIR R4, select the firstname.lastname@example.org package.
- Review the endpoint URL that has been autogenerated according to your choice of the core FHIR package. You can change the endpoint’s URL, but ensure that it begins with a slash (/).
- If you want the endpoint to support additional packages, select them from the Additional Packages drop-down list. For more information about packages, see Profiles and FHIR Adaptations.
- Select the InteractionsStrategy for the endpoint. The default interactions strategy is the Resource Repository (HS.FHIRServer.Storage.Json.InteractionsStrategy), which stores FHIR data as JSON in dynamic objects. If you created a custom InteractionsStrategy, select it from the list.
- By default, data for each endpoint in a namespace is stored in two separate databases. If you do not want to maintain separate databases, clear the Use separate databases for FHIR resource storage field; in this case, all FHIR data is stored in the namespace’s common database files. If you use separate databases. you can accept the default locations or specify your own. The Resource History database contains previous versions of a resource; because these are not accessed as frequently, you could put this database on a slower, less expensive disk.
- Select Add.