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" : "IntegratedPatientManagementSystemRequirements",
"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 IntegratedPatientManagementSystemRequirements</b></p><a name=\"IntegratedPatientManagementSystemRequirements\"> </a><a name=\"hcIntegratedPatientManagementSystemRequirements\"> </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-IPMSActorDefinitionExample.html\">Integrated Patient Management System (IPMS)</a></li><li><a href=\"ActorDefinition-OmangActorDefinitionExample.html\">Omang</a></li><li><a href=\"ActorDefinition-MFLActorDefinitionExample.html\">Master Facility List (MFL)</a></li></ul><table class=\"grid\"><tr><td><b><a name=\"BOTS.FR-IPMS.001\"> </a></b>BOTS.FR-IPMS.001</td><td/><td><div><p>Must receive a new lab order from the HIE as an ORM Hl7v2 message over MLLP.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-IPMS.002\"> </a></b>BOTS.FR-IPMS.002</td><td/><td><div><p>Must send an ACK message to the HIE with the IPMS-specific lab order number for the lab order generated on the IPMS side by the ORM message AND the IPMS-specific MRN for the existing patient.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-IPMS.003\"> </a></b>BOTS.FR-IPMS.003</td><td/><td><div><p>On registration of a new patient on IPMS, IPMS must send an HL7 v2.3 - Admit, Discharge and Transfer 04 message that includes IPMS-specific MRN and the patient’s Omang and/or passport number to the specified IP and Port number.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-IPMS.004\"> </a></b>BOTS.FR-IPMS.004</td><td/><td><div><p>Should be able to send a HL7V2 ORU message to the HIE with lab order result information as soon as this information is available in IPMS. The message must include IPMS-specific identifiers for the patient and the lab order that correspond to the identifiers sent with the ACK for the ORM messages and with the ADT messages.</p>\n</div></td></tr><tr><td><b><a name=\"BOTS.FR-IPMS.005\"> </a></b>BOTS.FR-IPMS.005</td><td/><td><div><p>Must ensure that IPMS-specific facility identifiers are sent with the ADT and ORU messages, and that these identifiers can be mapped to the BW MFL.</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/IntegratedPatientManagementSystemRequirements",
"version" : "1.0.0",
"name" : "IntegratedPatientManagementSystemRequirements",
"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/IPMSActorDefinitionExample"🔗 ,
"http://moh.bw.org/ActorDefinition/OmangActorDefinitionExample"🔗 ,
"http://moh.bw.org/ActorDefinition/MFLActorDefinitionExample"
],
"_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"
}
]
}
}
]
}
],
"statement" : [
{
"key" : "BOTS.FR-IPMS.001",
"requirement" : "Must receive a new lab order from the HIE as an ORM Hl7v2 message over MLLP."
},
{
"key" : "BOTS.FR-IPMS.002",
"requirement" : "Must send an ACK message to the HIE with the IPMS-specific lab order number for the lab order generated on the IPMS side by the ORM message AND the IPMS-specific MRN for the existing patient."
},
{
"key" : "BOTS.FR-IPMS.003",
"requirement" : "On registration of a new patient on IPMS, IPMS must send an HL7 v2.3 - Admit, Discharge and Transfer 04 message that includes IPMS-specific MRN and the patient’s Omang and/or passport number to the specified IP and Port number."
},
{
"key" : "BOTS.FR-IPMS.004",
"requirement" : "Should be able to send a HL7V2 ORU message to the HIE with lab order result information as soon as this information is available in IPMS. The message must include IPMS-specific identifiers for the patient and the lab order that correspond to the identifiers sent with the ACK for the ORM messages and with the ADT messages."
},
{
"key" : "BOTS.FR-IPMS.005",
"requirement" : "Must ensure that IPMS-specific facility identifiers are sent with the ADT and ORU messages, and that these identifiers can be mapped to the BW MFL."
}
]
}