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-04-01 |
{
"resourceType" : "Requirements",
"id" : "HIESystemRequirements",
"text" : {
"status" : "generated",
"div" : "<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><a name=\"HIESystemRequirements-en-US\"> </a><p>These requirements apply to the actor <a href=\"ActorDefinition-HIESystemActorDefinitionExample.html\">HIE System</a></p><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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</div></td></tr></table></div>"
},
"url" : "http://moh.bw.org/Requirements/HIESystemRequirements",
"version" : "1.0.0",
"name" : "HIESystemRequirements",
"status" : "active",
"date" : "2025-04-01T12:19:20+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/HIESystemActorDefinitionExample"
],
"statement" : [
{
"key" : "BOTS.FR-HIE.001",
"requirement" : "Should be able to send SMS notifications to patients that require urgent attention-(PIMS)."
},
{
"key" : "BOTS.FR-HIE.002",
"requirement" : "Should be able to allow capturing of certain specific specimen-(PIMS)."
},
{
"key" : "BOTS.FR-HIE.003",
"requirement" : "Should be able to ping SHR for available lab test results and avail them to the clinicians- (PIMS)."
},
{
"key" : "BOTS.FR-HIE.004",
"requirement" : "Should be able to send lab test results to the SHR-(IPMS)."
},
{
"key" : "BOTS.FR-HIE.005",
"requirement" : "Shall include an interface into which a workflow engine can be connected."
},
{
"key" : "BOTS.FR-HIE.006",
"requirement" : "Should support the ability to be extended by allowing additional mediation functions to be added or removed as they are needed."
},
{
"key" : "BOTS.FR-HIE.007",
"requirement" : "Shall support a mechanism for error management and tracking, e.g. a console for viewing failed transactions."
},
{
"key" : "BOTS.FR-HIE.008",
"requirement" : "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."
},
{
"key" : "BOTS.FR-HIE.009",
"requirement" : "Should support the ability for a user to re-run errored transactions through the HIE once the reason for their failure has been rectified."
},
{
"key" : "BOTS.FR-HIE.010",
"requirement" : "Shall provide authorized users with a view of metrics for monitoring the flow of messages through the HIE."
},
{
"key" : "BOTS.FR-HIE.011",
"requirement" : "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."
},
{
"key" : "BOTS.FR-HIE.012",
"requirement" : "Shall support Authentication and Authorization of systems trying to send data to the HIE."
},
{
"key" : "BOTS.FR-HIE.013",
"requirement" : "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)."
},
{
"key" : "BOTS.FR-HIE.014",
"requirement" : "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."
}
]
}