Botswana FHIR Implementation Guide
1.0.0 - ci-build Botswana flag

Botswana FHIR Implementation Guide, published by Jembi Health Systems. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/jembi/botswana-hie-fhir-ig/ and changes regularly. See the Directory of published versions

Home

Official URL: http://moh.bw.org/ImplementationGuide/botswana.hie.fhir Version: 1.0.0
Active as of 2024-07-25 Computable Name: BotswanaHIE

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

This documentation and set of artefacts are still undergoing development.

 

Introduction

This Fast Healthcare Interoperability Resources (FHIR)® Implementation Guide (IG) is designed to facilitate the standardized exchange of healthcare information in Botswana; specifically the handling of laboratory orders in both OpenMRS and PIMS systems to and from the national laboratory system, IPMS. The guide is crafted for Botswana's Health Information Exchange (HIE) and provides a structured approach to managing lab orders.

The goal of this IG is to ensure that laboratory data can be efficiently exchanged and integrated within Botswana.

This IG implements FHIR bundles that support conditional patient creates and/or updates:

  • Create: Only create the patient in the Client Registry (CR) if no matches are found for a given business identifier.
  • Update: Instead of creating a new patient in the CR, ONLY update the administrative information for the patient matching the given business identifier.

This aims to reduce duplication of patient records and maintain patient data integrity across integrated systems.

This IG currently implements the following two key laboratory profiles to support Botswana's LAB-EMR exchange worflow requirements:

  1. Submitting and managing lab orders
  2. Capturing lab results

Background

To be completed...

Data Flow

The following diagram gives an overview of the flow of data from the EMR systems (OpenMRS/PIMS) to the laboratory system (IPMS) and back.

OpenMRSOpenMRSMFLMFLOpenHIMOpenHIMSharedHealthRecordSharedHealthRecordIPMSIPMSGet facility IDSend Lab order request (FHIR bundle)Forward Lab order requestMap facility ID to IPMS MnemonicsSend HL7 ADT messageSend HL7 ORM messageReturn ORU message (Lab result)Send Lab resultForward Lab request

Download

You can also download:

The source code for this Implementation Guide can be found on GitHub.

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (botswana.hie.fhir.r4) and R4B (botswana.hie.fhir.r4b) are available.

Dependency Table

IGPackageFHIRComment
.. Botswana FHIR Implementation Guidebotswana.hie.fhir#1.0.0R4
... HL7 Terminology (THO)hl7.terminology.r4#6.2.0R4Automatically added as a dependency - all IGs depend on HL7 Terminology
... FHIR Extensions Packhl7.fhir.uv.extensions.r4#5.2.0R4Automatically added as a dependency - all IGs depend on the HL7 Extension Pack

Package hl7.fhir.uv.extensions.r4#5.2.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Globals Table

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.

Intellectual Property Considerations

While this implementation guide and the underlying FHIR are licensed as public domain, this guide may include 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

This specification 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.