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 |
{
"resourceType" : "Requirements",
"id" : "ClientRegistryRequirements",
"meta" : {
"profile" : [
🔗 "http://moh.bw.org/StructureDefinition/bw-requirements"
]
},
"text" : {
"status" : "generated",
"div" : "<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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</div></td></tr></table></div>"
},
"extension" : [
{
"url" : "http://moh.bw.org/StructureDefinition/requirements-type",
"valueCodeableConcept" : {
"coding" : [
{
"system" : "http://moh.bw.org/CodeSystem/cs-requirements-type-codes",
"code" : "functional"
}
]
}
}
],
"url" : "http://moh.bw.org/Requirements/ClientRegistryRequirements",
"version" : "1.0.0",
"name" : "ClientRegistryRequirements",
"status" : "active",
"date" : "2025-08-20T07:21:53+00:00",
"publisher" : "Jembi Health Systems",
"contact" : [
{
"name" : "Jembi Health Systems",
"telecom" : [
{
"system" : "url",
"value" : "https://www.jembi.org"
},
{
"system" : "email",
"value" : "info@jembi.org"
}
]
},
{
"name" : "Jembi Health Systems",
"telecom" : [
{
"system" : "email",
"value" : "info@jembi.org",
"use" : "work"
}
]
}
],
"jurisdiction" : [
{
"coding" : [
{
"system" : "urn:iso:std:iso:3166",
"code" : "BW",
"display" : "Botswana"
}
]
}
],
"actor" : [
🔗 "http://moh.bw.org/ActorDefinition/ClientRegistryActorDefinitionExample"🔗 ,
"http://moh.bw.org/ActorDefinition/SHRActorDefinitionExample"
],
"_actor" : [
{
🔗 "extension" : [
{
"url" : "http://moh.bw.org/StructureDefinition/actor-classification",
"valueCodeableConcept" : {
"coding" : [
{
"system" : "http://moh.bw.org/CodeSystem/cs-actor-classification-codes",
"code" : "primary"
}
]
}
}
]
},
{
🔗 "extension" : [
{
"url" : "http://moh.bw.org/StructureDefinition/actor-classification",
"valueCodeableConcept" : {
"coding" : [
{
"system" : "http://moh.bw.org/CodeSystem/cs-actor-classification-codes",
"code" : "secondary"
}
]
}
}
]
}
],
"statement" : [
{
"key" : "BOTS.FR-CR.001",
"requirement" : "Should be able to support configurable entity matching, a service to assist in identifying duplicate patients."
},
{
"key" : "BOTS.FR-CR.002",
"requirement" : "Should be able to support patient linking and de-duplication."
},
{
"key" : "BOTS.FR-CR.003",
"requirement" : "Should be able to support the ability to track and monitor inbound/outbound transactions."
},
{
"key" : "BOTS.FR-CR.004",
"requirement" : "Should be able to support synchronization of client IDs with a Shared Health Record (SHR)."
},
{
"key" : "BOTS.FR-CR.005",
"requirement" : "Should be able to manage a full audit log of changes to data as well as configurations as well as users."
},
{
"key" : "BOTS.FR-CR.006",
"requirement" : "Should have functions including user management and access controls."
},
{
"key" : "BOTS.FR-CR.007",
"requirement" : "Should be able to persist the parent/child relationship, birth order, and multi-birth indicator."
},
{
"key" : "BOTS.FR-CR.008",
"requirement" : "Should support a UI to review and manually adjudicate uncertain (“potential”) matches, and override incorrect matches."
},
{
"key" : "BOTS.FR-CR.009",
"requirement" : "Should support configurable attributes that form a patient record and are used for matching."
},
{
"key" : "BOTS.FR-CR.010",
"requirement" : "Should support configurable attributes to make it easy to add attributes to the schema."
},
{
"key" : "BOTS.FR-CR.011",
"requirement" : "Should support configurable attributes to make it easy to remove attributes from the default model (or start over from scratch)."
}
]
}