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" : "ImmigrationCitizenshipSystemRequirements",
"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 ImmigrationCitizenshipSystemRequirements</b></p><a name=\"ImmigrationCitizenshipSystemRequirements\"> </a><a name=\"hcImmigrationCitizenshipSystemRequirements\"> </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-ICSActorDefinitionExample.html\">Immigration and Citizenship System (ICS)</a></li><li><a href=\"ActorDefinition-InteroperabilityLayerActorDefinitionExample.html\">Interoperability Layer (IL)</a></li><li><a href=\"ActorDefinition-ClientRegistryActorDefinitionExample.html\">Client Registry (CR)</a></li><li><a href=\"ActorDefinition-APIActorDefinitionExample.html\">Cross-Service API (API)</a></li><li><a href=\"ActorDefinition-OmangActorDefinitionExample.html\">Omang</a></li></ul><table class=\"grid\"><tr><td><b><a name=\"BOTS.FR-ICS.001\"> </a></b>BOTS.FR-ICS.001</td><td/><td><div><p>Should be able to provide a status check that indicates uptime and connection status.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-ICS.002\"> </a></b>BOTS.FR-ICS.002</td><td/><td><div><p>Should be able to authenticate with and connect to the appropriate Oracle View with ICS registry data.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-ICS.003\"> </a></b>BOTS.FR-ICS.003</td><td/><td><div><p>Should be able to translate the ICS registry data model into valid FHIR resources.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-ICS.004\"> </a></b>BOTS.FR-ICS.004</td><td/><td><div><p>Should be able to provide a FHIR Search API layer for handling queries for Omang patients by all identifiers and demographic parameters available in the ICS Oracle View.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-ICS.005\"> </a></b>BOTS.FR-ICS.005</td><td/><td><div><p>Should be able to integrate with an HIE interoperability layer for incoming and outgoing communication.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-ICS.006\"> </a></b>BOTS.FR-ICS.006</td><td/><td><div><p>Should be able to connect with a FHIR-based Client Registry through the HIE.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-ICS.007\"> </a></b>BOTS.FR-ICS.007</td><td/><td><div><p>Should be able to synchronize patient data on demand between the ICS registry and a FHIR-based HIE Client Registry, with a configurable refresh timespan.</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/ImmigrationCitizenshipSystemRequirements",
"version" : "1.0.0",
"name" : "ImmigrationCitizenshipRequirements",
"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/ICSActorDefinitionExample"🔗 ,
"http://moh.bw.org/ActorDefinition/InteroperabilityLayerActorDefinitionExample"🔗 ,
"http://moh.bw.org/ActorDefinition/ClientRegistryActorDefinitionExample"🔗 ,
"http://moh.bw.org/ActorDefinition/APIActorDefinitionExample"🔗 ,
"http://moh.bw.org/ActorDefinition/OmangActorDefinitionExample"
],
"_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"
}
]
}
}
]
},
{
🔗 "extension" : [
{
"url" : "http://moh.bw.org/StructureDefinition/actor-classification",
"valueCodeableConcept" : {
"coding" : [
{
"system" : "http://moh.bw.org/CodeSystem/cs-actor-classification-codes",
"code" : "secondary"
}
]
}
}
]
},
{
🔗 "extension" : [
{
"url" : "http://moh.bw.org/StructureDefinition/actor-classification",
"valueCodeableConcept" : {
"coding" : [
{
"system" : "http://moh.bw.org/CodeSystem/cs-actor-classification-codes",
"code" : "secondary"
}
]
}
}
]
},
{
🔗 "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-ICS.001",
"requirement" : "Should be able to provide a status check that indicates uptime and connection status."
},
{
"key" : "BOTS.FR-ICS.002",
"requirement" : "Should be able to authenticate with and connect to the appropriate Oracle View with ICS registry data."
},
{
"key" : "BOTS.FR-ICS.003",
"requirement" : "Should be able to translate the ICS registry data model into valid FHIR resources."
},
{
"key" : "BOTS.FR-ICS.004",
"requirement" : "Should be able to provide a FHIR Search API layer for handling queries for Omang patients by all identifiers and demographic parameters available in the ICS Oracle View."
},
{
"key" : "BOTS.FR-ICS.005",
"requirement" : "Should be able to integrate with an HIE interoperability layer for incoming and outgoing communication."
},
{
"key" : "BOTS.FR-ICS.006",
"requirement" : "Should be able to connect with a FHIR-based Client Registry through the HIE."
},
{
"key" : "BOTS.FR-ICS.007",
"requirement" : "Should be able to synchronize patient data on demand between the ICS registry and a FHIR-based HIE Client Registry, with a configurable refresh timespan."
}
]
}