This section describes the expected capabilities of the Botswana HIE server actor which is responsible for providing responses to the queries submitted for lab orders. The list of FHIR profiles and operations supported by the Botswana HIE server are defined.

This bundle contains all of the lab order profiles for managing lab orders.

While this bundle contains all of the lab order profiles for managing lab orders as defined in the bundle for "Lab Orders", it also includes the "RestrictedPatient" profile that will replace the "Botswana Patient" in the FHIR server.

Represents the results for the lab order.

Represents the current facility at which the patient is receiving health services.

Represents the patient's test result for a given lab order.

Is used to document demographics and other personal information about an individual receiving care or other health-related services.

Is used by the Client Registry to re-identify the patient with his/her corresponding longitudinal clinical record.

Represents the practitioner who participated in the health related service.

Represents the requirements for the use case described in this Implementation Guide.

Organization providing health related services.

Represents the service request for lab orders.

The specimen associated with the lab order.

Assists with tracking the state of the lab order and its completion status.

An extension to capture whether the actor is primary or secondary in the context of the requirements defintion.

An extension to reference the Actor Resource describing additional details regarding the actor.

An extension to capture the type of requirements contained in the Resource.

A coded value that represents whether the actor is primary or secondary in the context of the requirements definition.

Codes used during lab orders.

Codes found in the MFL.

A coded value that represents the type of requirements contained in the Resource.

A coded value that represents whether the actor is primary or secondary in the context of the requirements definition.

A coded value that represents the technical details of the usage of an endpoint.

Codes found in the MFL.

Codes used during OpenMRS lab orders.

Codes used during PIMS lab orders.

A coded value that represents the type of requirements contained in the Resource.

A coded value that represents the HTTP method when sending a request to a specified endpoint.

Demonstrates the process flow to submit a cancellation request for an active lab order from the Point-of-Service application to the FHIR server.

Demonstrates the process flow to submit lab results from the Point-of-Service application to the FHIR server.

Demonstrates the process flow between the Client Registry and FHIR server during patient registration.

Demonstrates the process flow between the Client Registry and FHIR server during patient registration.

Demonstrates the process flow to submit a rejection request for an active lab order from the Point-of-Service application to the FHIR server.

Demonstrates the process flow to retrieve a patient record from the Client Registry and FHIR server.

Demonstrates the process flow to submit a new lab order from the Point-of-Service application to the FHIR server.

Represents the system used for recording births and deaths, ensuring that citizens are formally recognized and provided with legal identification.

Represents the system designed to uniquely identify individuals who receive healthcare services, often by maintaining a central record of patients and their demographics, assigning unique identifiers, and enabling healthcare workers to identify facilities where a patient has received care.

Represents the individual responsible for the care of patient.

Represents the system used to provide a single entrypoint for demographic search queries that might have a mix of various query parameters.

Represents a centralized electronic medical record (EMR) system implemented by the Ministry of Health and Wellness. It aims to enhance patient care by providing a unified platform for managing medical records across public health facilitie.

Represents the system used to manage the entry, stay, and exit of foreign nationals and to govern the acquisition and loss of citizenship in the country.

Represents the architectural component responsible for coordinating transactions from one system to another during Health Information Exchange.

Represents the individual responsible for conducting lab tests.

Represents a comprehensive, standardized registry of all health facilities—both public and private—across the country. Managed by the Ministry of Health and Wellness, the MFL assigns unique codes to each facility, ensuring accurate identification and facilitating interoperability across health information systems. This system supports efficient health data management, reporting, and planning.

Represents the system used for national identification of the population in Botswana.

Represents an open-source electronic medical record system that is used to manage patient data, support HIV care, and strengthen health information systems across the country’s healthcare facilities.

Represents the system used to collect, manage, and track patient health records across healthcare facilities, supporting improved care, reporting, and decision-making.

Represents the system that stores a defined set of normalized patient data, serving as a longitudinal health record across different facilities, ensuring continuity of care.

Birth and Death Registration System Functional Requirements

Is used to document demographics and other personal information about an individual receiving care or other health-related services.

Lab order has been cancelled

Submit new lab orders

Submit new lab orders.

Note: This bundle includes the Patient Resource as a conditional create!

Submit new lab orders.

Note: This bundle includes the Patient Resource as a conditional update!

Submit new lab orders.

Note: This bundle includes Resources without explicitly provided Resource ID's! 
The system will auto-generate the Resource.id values (Literal ID) during the POST request.

Submit new lab orders (incl. Patient Resource)

Submit new lab orders and replace the patient profile resource that supplied the data with the "RestrictedPatient" profile resource.

Lab order has been completed

Lab order has been rejected

Client Registry Functional Requirements

Clinician Functional Requirements

Cross-Service API Functional Requirements

Represents the results for the lab order.

Represents the current facility at which the patient is receiving health services.

The patient resource that should be stored in the FHIR database when using a Client Registry.

HIE System Functional Requirements

Immigration and Citizenship System Functional Requirements

The patient resource after having its data populated by the Client Registry.

Integrated Patient Management System Functional Requirements

Interoperability Layer Functional Requirements

Laboratory Technician Functional Requirements

Interoperability layer receives an MPI as part of the response from the CR when creating new patients.

Non Functional Requirements

Documents the patient's diagnostic test result.

Omang Functional Requirements

OpenMRS Functional Requirements

Current organization providing health related services.

Patient Information Management System Functional Requirements

Represents the practitioners who participated in the health-related event.

Point-of-Service systems can submit "PUT" or "POST" requests using a FHIR Bundle Resource.

Interoperability layer receives an outcome response for each CRUD request.

Interoperability layer receives a response from the CR for the search request.

Interoperability layer searches for a patient in the client registry using business identifiers (Omang, BDRS, Immigration) or Demographics.

Point-of-Service systems can search for a patient in FHIR using one or more business identifiers (Omang, BDRS, Immigration) or Demographics.

Represents an active service request for the lab order.

Represents a completed service request for the lab order.

Represents a service request that has been revoked before it could be fully attended to.

Represents a service request that has been revoked before it could be fully attended to.

The specimen associated with the lab order that was considered ready for testing but the service request was revoked due to an unsatisfactory specimen.

The specimen associated with the lab order that was used during testing.

The specimen associated with the lab order that was used during testing.

The specimen associated with the lab order that will be used during testing.

Indicates that the task that has been initiated for the lab request has been cancelled by the requestiong organization/practitioner.

Indicates that the task that has been initiated for the lab request has now been completed and the lab result issued.

Indicates that the task that has been initiated for the lab request has been rejected by the receiving laboratory/lab technician.

Represents a task that has been initiated to facilitate the overall progress of the new lab request.

FHIR uses its $validate operation to ensure that data provided in the Patient Resource is compliant with the specified FHIR Profile.