This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Metadata Export and Import (1.1)
Volker edited this page Jun 5, 2019
·
3 revisions
DHIS 2 Tracker Program related metadata can be exported and imported from and into the Adapter.
One or more Tracker Program including its direct and indirect dependencies are exported. The export will include alls data that is required to setup the Tracker Programs again. The metadata export will be in JSON format. Compression of exported metadata is not yet supported.
curl -u admin:district http://localhost:8081/api/metadata
The following query parameters are supported.
Parameter | Default Value | Description |
---|---|---|
trackerProgramId | All | The Adapter IDs of one or more Tracker Programs that should be exported. |
excludedSystemUri | None | The system URIs of one or more system for which no codes should be exported (e.g. http://snomed.info/sct) |
includeTrackedEntities | false | Specifies if tracked entity mappings should be included in the export. Tracked entity mappings require often profiling and should normally not overridden on other systems. |
includeResourceMappings | false | Specifies if resource mappings should be included in the export. Resource mappings require often profiling and should normally not overridden on other systems. |
download | false | Specifies if the resulting JSON file will be offered as a download by the browser. Otherwise the content of the export may be shown in the browser windows. |
Previously exported metadata can be imported again. Specific parts of the exported metadata can be skipped.
curl -u admin:district -XPOST -H "Content-Type: application/json" -i -d "@metadata.json" http://localhost:8081/api/metadata
The following query parameters are supported.
Parameter | Default Value | Description |
---|---|---|
updateResourceMappings | false | Specifies if resource mappings should be updated. If this is disabled, only new resource mappings will be imported. |
updateCodes | false | Specifies if code related metadata should be updated. If this is disabled, only new code related metadata will be imported. |
updateScripts | false | Specifies if script related metadata should be updated. If this is disabled, only new script related metadata will be imported. |
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