Botswana FHIR Implementation Guide
1.0.0 - ci-build
Botswana FHIR Implementation Guide
1.0.0 - ci-build
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
| Active as of 2025-08-20 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="HIESystemRequirements"/>
<meta>
<profile value="http://moh.bw.org/StructureDefinition/bw-requirements"/>
</meta>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Requirements HIESystemRequirements</b></p><a name="HIESystemRequirements"> </a><a name="hcHIESystemRequirements"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px"/><p style="margin-bottom: 0px">Profile: <a href="StructureDefinition-bw-requirements.html">Requirements</a></p></div><p>These requirements apply to the following actors: </p><ul><li><a href="ActorDefinition-SHRActorDefinitionExample.html">Shared Health Record (SHR)</a></li><li><a href="ActorDefinition-PIMSActorDefinitionExample.html">Patient Information Management System (PIMS)</a></li><li><a href="ActorDefinition-IPMSActorDefinitionExample.html">Integrated Patient Management System (IPMS)</a></li><li><a href="ActorDefinition-InteroperabilityLayerActorDefinitionExample.html">Interoperability Layer (IL)</a></li></ul><table class="grid"><tr><td><b><a name="BOTS.FR-HIE.001"> </a></b>BOTS.FR-HIE.001</td><td/><td><div><p>Should be able to send SMS notifications to patients that require urgent attention-(PIMS).</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.002"> </a></b>BOTS.FR-HIE.002</td><td/><td><div><p>Should be able to allow capturing of certain specific specimen-(PIMS).</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.003"> </a></b>BOTS.FR-HIE.003</td><td/><td><div><p>Should be able to ping SHR for available lab test results and avail them to the clinicians- (PIMS).</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.004"> </a></b>BOTS.FR-HIE.004</td><td/><td><div><p>Should be able to send lab test results to the SHR-(IPMS).</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.005"> </a></b>BOTS.FR-HIE.005</td><td/><td><div><p>Shall include an interface into which a workflow engine can be connected.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.006"> </a></b>BOTS.FR-HIE.006</td><td/><td><div><p>Should support the ability to be extended by allowing additional mediation functions to be added or removed as they are needed.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.007"> </a></b>BOTS.FR-HIE.007</td><td/><td><div><p>Shall support a mechanism for error management and tracking, e.g. a console for viewing failed transactions.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.008"> </a></b>BOTS.FR-HIE.008</td><td/><td><div><p>Shall allow for failed transactions to be grouped by error type and reason so that errors can be rectified efficiently by finding the root cause of the error, fixing the problem, and re-running those transactions.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.009"> </a></b>BOTS.FR-HIE.009</td><td/><td><div><p>Should support the ability for a user to re-run errored transactions through the HIE once the reason for their failure has been rectified.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.010"> </a></b>BOTS.FR-HIE.010</td><td/><td><div><p>Shall provide authorized users with a view of metrics for monitoring the flow of messages through the HIE.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.011"> </a></b>BOTS.FR-HIE.011</td><td/><td><div><p>Shall manage the security of the HIE through authentication (identity verification), authorization (permission to interact with specified HIE components) and encryption and decryption of messages.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.012"> </a></b>BOTS.FR-HIE.012</td><td/><td><div><p>Shall support Authentication and Authorization of systems trying to send data to the HIE.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.013"> </a></b>BOTS.FR-HIE.013</td><td/><td><div><p>Should support the encryption of data in flight (when not on a physically secure network) and at rest (whenever data is stored, e.g. when transactions are stored for logging).</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-HIE.014"> </a></b>BOTS.FR-HIE.014</td><td/><td><div><p>Should capture monitoring statistics, such as transaction loads and performance metrics, and provide a view of these for monitoring the flow of messages through the HIE.</p>
</div></td></tr></table></div>
</text>
<extension url="http://moh.bw.org/StructureDefinition/requirements-type">
<valueCodeableConcept>
<coding>
<system
value="http://moh.bw.org/CodeSystem/cs-requirements-type-codes"/>
<code value="functional"/>
</coding>
</valueCodeableConcept>
</extension>
<url value="http://moh.bw.org/Requirements/HIESystemRequirements"/>
<version value="1.0.0"/>
<name value="HIESystemRequirements"/>
<status value="active"/>
<date value="2025-08-20T07:21:53+00:00"/>
<publisher value="Jembi Health Systems"/>
<contact>
<name value="Jembi Health Systems"/>
<telecom>
<system value="url"/>
<value value="https://www.jembi.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="info@jembi.org"/>
</telecom>
</contact>
<contact>
<name value="Jembi Health Systems"/>
<telecom>
<system value="email"/>
<value value="info@jembi.org"/>
<use value="work"/>
</telecom>
</contact>
<jurisdiction>
<coding>
<system value="urn:iso:std:iso:3166"/>
<code value="BW"/>
<display value="Botswana"/>
</coding>
</jurisdiction>
<actor value="http://moh.bw.org/ActorDefinition/SHRActorDefinitionExample">🔗
<extension
url="http://moh.bw.org/StructureDefinition/actor-classification">
<valueCodeableConcept>
<coding>
<system
value="http://moh.bw.org/CodeSystem/cs-actor-classification-codes"/>
<code value="primary"/>
</coding>
</valueCodeableConcept>
</extension>
</actor>
<actor
value="http://moh.bw.org/ActorDefinition/PIMSActorDefinitionExample">🔗
<extension
url="http://moh.bw.org/StructureDefinition/actor-classification">
<valueCodeableConcept>
<coding>
<system
value="http://moh.bw.org/CodeSystem/cs-actor-classification-codes"/>
<code value="primary"/>
</coding>
</valueCodeableConcept>
</extension>
</actor>
<actor
value="http://moh.bw.org/ActorDefinition/IPMSActorDefinitionExample">🔗
<extension
url="http://moh.bw.org/StructureDefinition/actor-classification">
<valueCodeableConcept>
<coding>
<system
value="http://moh.bw.org/CodeSystem/cs-actor-classification-codes"/>
<code value="primary"/>
</coding>
</valueCodeableConcept>
</extension>
</actor>
<actor
value="http://moh.bw.org/ActorDefinition/InteroperabilityLayerActorDefinitionExample">🔗
<extension
url="http://moh.bw.org/StructureDefinition/actor-classification">
<valueCodeableConcept>
<coding>
<system
value="http://moh.bw.org/CodeSystem/cs-actor-classification-codes"/>
<code value="primary"/>
</coding>
</valueCodeableConcept>
</extension>
</actor>
<statement>
<key value="BOTS.FR-HIE.001"/>
<requirement
value="Should be able to send SMS notifications to patients that require urgent attention-(PIMS)."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.002"/>
<requirement
value="Should be able to allow capturing of certain specific specimen-(PIMS)."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.003"/>
<requirement
value="Should be able to ping SHR for available lab test results and avail them to the clinicians- (PIMS)."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.004"/>
<requirement
value="Should be able to send lab test results to the SHR-(IPMS)."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.005"/>
<requirement
value="Shall include an interface into which a workflow engine can be connected."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.006"/>
<requirement
value="Should support the ability to be extended by allowing additional mediation functions to be added or removed as they are needed."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.007"/>
<requirement
value="Shall support a mechanism for error management and tracking, e.g. a console for viewing failed transactions."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.008"/>
<requirement
value="Shall allow for failed transactions to be grouped by error type and reason so that errors can be rectified efficiently by finding the root cause of the error, fixing the problem, and re-running those transactions."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.009"/>
<requirement
value="Should support the ability for a user to re-run errored transactions through the HIE once the reason for their failure has been rectified."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.010"/>
<requirement
value="Shall provide authorized users with a view of metrics for monitoring the flow of messages through the HIE."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.011"/>
<requirement
value="Shall manage the security of the HIE through authentication (identity verification), authorization (permission to interact with specified HIE components) and encryption and decryption of messages."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.012"/>
<requirement
value="Shall support Authentication and Authorization of systems trying to send data to the HIE."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.013"/>
<requirement
value="Should support the encryption of data in flight (when not on a physically secure network) and at rest (whenever data is stored, e.g. when transactions are stored for logging)."/>
</statement>
<statement>
<key value="BOTS.FR-HIE.014"/>
<requirement
value="Should capture monitoring statistics, such as transaction loads and performance metrics, and provide a view of these for monitoring the flow of messages through the HIE."/>
</statement>
</Requirements>