DHIS2 Example FHIR Implementation Guide
1.0.0 - ci-build International flag

DHIS2 Example FHIR Implementation Guide, published by DHIS2. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/JohanGHole/alldevs-demo-ig and changes regularly. See the Directory of published versions

Home

Official URL: https://dhis2.org Version: 1.0.0
Draft as of 2023-09-20 Computable Name: dhis2fhiralldevsdemo

Contents:

This is our FHIR Implementation Guide. It contains the specifications developed by our community.

This documentation and set of artefacts are still undergoing development. This content is only for demonstrative purposes.

 

Content

The top menu allows quick navigation to the different sections, and a Table of Contents is provided with the entire content of this Implementation Guide. (Be aware that some pages have multiple tabs).

Introduction

This is a demo Implementation Guide (IG) focused on integrating FHIR with DHIS2 for the HIV Case Surveillance Metadata Package. In this preliminary version, we have developed logical models for the main components of the HIV Case Surveillance DHIS2 tracker program. Additionally, we have included models for core DHIS2 static components such as organization units and option sets. The terminologies and structures are evaluated iteratively, to ensure proper representation of the underlying DHIS2 data model. While we plan to separate and refine these into distinct IGs, the current content demonstrates the application of FHIR within DHIS2. While the foundational logical models are in place, we have yet to expand extensively on FHIR profiles. Please note that this IG is a work in progress, and your feedback is valued as we continue development.

Intellectual Property Considerations

While this implementation guide and the underlying FHIR are licensed as public domain, this guide includes examples making use of terminologies such as LOINC, SNOMED CT and others which have more restrictive licensing requirements. Implementers should make themselves familiar with licensing and any other constraints of terminologies, questionnaires, and other components used as part of their implementation process. In some cases, licensing requirements may limit the systems that data captured using certain questionnaires may be shared with.

Disclaimer

The specification herewith documented is a demo working specification, and may not be used for any implementation purposes. This draft is provided without warranty of completeness or consistency, and the official publication supersedes this draft. No liability can be inferred from the use or misuse of this specification, or its consequences.