-
Notifications
You must be signed in to change notification settings - Fork 13
Initial Setup (1.1)
After installing and configuring the Adapter, the initial setup can be made. For the initial setup of the Adapter a simple user interface is provided. This user interface may be replaced by a more comprehensive setup app in the future (has not yet been decided).
With the default configuration the initial setup user interface can be accessed in any web browser by using http://localhost:8081/setup
. The web browser will ask for a username and password of a DHIS2 user that has privilege ALL or F_SYSTEM_SETTING. After successful authentication a setup form will be displayed with further instructions and examples. The initial setup can be made once only and the initial setup form will not be accessible anymore.
The setup can be made with or without a connected FHIR Server. If the setup should be made with a FHIR Server, imports must have been enabled. The snippet below contains the relevant settings.
spring:
# Settings of the Artemis message queueing system. For a non-clustered
# installation the embedded client can be used where the data is stored
# on the local file system.
artemis:
# Settings for the embedded client, that can be used for a non-clustered
# installation.
embedded:
# Specifies of the embedded client should be enabled. If the adapter
# runs in a clustered environment the embedded client must not be enabled
# and host, port, username and password for the Artemis broker must be
# specified.
enabled: true
management:
health:
jms:
# JMS health check can be enabled when Artemis queue is available.
enabled: false
dhis2.fhir-adapter:
# Specifies if the automatic import of FHIR resources to DHIS2 is enabled.
import-enabled: true
More comprehensive setups must be made by using the API for administration and configuration of the Adapter. It is not required to use this simple initial setup user interface to use the Adapter.
Copyright (c) 2004-2019, University of Oslo. All rights reserved.
- Default FHIR Patient to DHIS 2 Tracked Entity Instance Mapping
- FHIR Administrative Gender to DHIS 2 Code Set Code
- Initial Setup
- Excel Import of Mappings
- FHIR REST Interfaces
- Connect a new FHIR Server
- Constants
- Coding Systems
- Configure FHIR Resources
- Export and Import
- Limitations
- REST API for Administration and Mapping
- Javascript API for Rules and Transformations to DHIS 2
- Javascript API for Rules and Transformations from DHIS 2
- Connect HAPI FHIR JPA Server
- Connect Jembi HEARTH FHIR Server
- Direct FHIR Import from OpenMRS
- Default FHIR Patient to DHIS 2 Tracked Entity Instance Mapping
- FHIR Administrative Gender to DHIS 2 Code Set Code
- Create Tracker Program with Vital Sign
- Add SNOMED CT Code for Vital Sign
- Export Organizations and Locations to FHIR Server
- Export Patients to FHIR Server
- Handle custom Tracked Entity Instance with no Attributes
- Mapping of Organizations