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="ClientRegistryRequirements"/>
<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 ClientRegistryRequirements</b></p><a name="ClientRegistryRequirements"> </a><a name="hcClientRegistryRequirements"> </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-ClientRegistryActorDefinitionExample.html">Client Registry (CR)</a></li><li><a href="ActorDefinition-SHRActorDefinitionExample.html">Shared Health Record (SHR)</a></li></ul><table class="grid"><tr><td><b><a name="BOTS.FR-CR.001"> </a></b>BOTS.FR-CR.001</td><td/><td><div><p>Should be able to support configurable entity matching, a service to assist in identifying duplicate patients.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.002"> </a></b>BOTS.FR-CR.002</td><td/><td><div><p>Should be able to support patient linking and de-duplication.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.003"> </a></b>BOTS.FR-CR.003</td><td/><td><div><p>Should be able to support the ability to track and monitor inbound/outbound transactions.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.004"> </a></b>BOTS.FR-CR.004</td><td/><td><div><p>Should be able to support synchronization of client IDs with a Shared Health Record (SHR).</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.005"> </a></b>BOTS.FR-CR.005</td><td/><td><div><p>Should be able to manage a full audit log of changes to data as well as configurations as well as users.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.006"> </a></b>BOTS.FR-CR.006</td><td/><td><div><p>Should have functions including user management and access controls.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.007"> </a></b>BOTS.FR-CR.007</td><td/><td><div><p>Should be able to persist the parent/child relationship, birth order, and multi-birth indicator.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.008"> </a></b>BOTS.FR-CR.008</td><td/><td><div><p>Should support a UI to review and manually adjudicate uncertain (“potential”) matches, and override incorrect matches.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.009"> </a></b>BOTS.FR-CR.009</td><td/><td><div><p>Should support configurable attributes that form a patient record and are used for matching.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.010"> </a></b>BOTS.FR-CR.010</td><td/><td><div><p>Should support configurable attributes to make it easy to add attributes to the schema.</p>
</div></td></tr><tr><td><b><a name="BOTS.FR-CR.011"> </a></b>BOTS.FR-CR.011</td><td/><td><div><p>Should support configurable attributes to make it easy to remove attributes from the default model (or start over from scratch).</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/ClientRegistryRequirements"/>
<version value="1.0.0"/>
<name value="ClientRegistryRequirements"/>
<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/ClientRegistryActorDefinitionExample">🔗
<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/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="secondary"/>
</coding>
</valueCodeableConcept>
</extension>
</actor>
<statement>
<key value="BOTS.FR-CR.001"/>
<requirement
value="Should be able to support configurable entity matching, a service to assist in identifying duplicate patients."/>
</statement>
<statement>
<key value="BOTS.FR-CR.002"/>
<requirement
value="Should be able to support patient linking and de-duplication."/>
</statement>
<statement>
<key value="BOTS.FR-CR.003"/>
<requirement
value="Should be able to support the ability to track and monitor inbound/outbound transactions."/>
</statement>
<statement>
<key value="BOTS.FR-CR.004"/>
<requirement
value="Should be able to support synchronization of client IDs with a Shared Health Record (SHR)."/>
</statement>
<statement>
<key value="BOTS.FR-CR.005"/>
<requirement
value="Should be able to manage a full audit log of changes to data as well as configurations as well as users."/>
</statement>
<statement>
<key value="BOTS.FR-CR.006"/>
<requirement
value="Should have functions including user management and access controls."/>
</statement>
<statement>
<key value="BOTS.FR-CR.007"/>
<requirement
value="Should be able to persist the parent/child relationship, birth order, and multi-birth indicator."/>
</statement>
<statement>
<key value="BOTS.FR-CR.008"/>
<requirement
value="Should support a UI to review and manually adjudicate uncertain (“potential”) matches, and override incorrect matches."/>
</statement>
<statement>
<key value="BOTS.FR-CR.009"/>
<requirement
value="Should support configurable attributes that form a patient record and are used for matching."/>
</statement>
<statement>
<key value="BOTS.FR-CR.010"/>
<requirement
value="Should support configurable attributes to make it easy to add attributes to the schema."/>
</statement>
<statement>
<key value="BOTS.FR-CR.011"/>
<requirement
value="Should support configurable attributes to make it easy to remove attributes from the default model (or start over from scratch)."/>
</statement>
</Requirements>