FHIR © HL7.org  |  Server Home  |  XIG Home  |  XIG Stats  |  Server Source  |  FHIR  

FHIR IG Statistics: Requirements/IntegratedPatientManagementSystemRequirements

Packagebotswana.hie.fhir
Resource TypeRequirements
IdIntegratedPatientManagementSystemRequirements
FHIR VersionR5
Sourcehttp://moh.bw.org/https://build.fhir.org/ig/jembi/botswana-hie-fhir-ig/Requirements-IntegratedPatientManagementSystemRequirements.html
URLhttp://moh.bw.org/Requirements/IntegratedPatientManagementSystemRequirements
Version1.0.0
Statusactive
Date2025-05-19T15:02:57+00:00
NameIntegratedPatientManagementSystemRequirements

Resources that use this resource

No resources found


Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: Requirements IntegratedPatientManagementSystemRequirements

Profile: Requirements

These requirements apply to the following actors:

BOTS.FR-IPMS.001

Must receive a new lab order from the HIE as an ORM Hl7v2 message over MLLP.

BOTS.FR-IPMS.002

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.

BOTS.FR-IPMS.003

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.

BOTS.FR-IPMS.004

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.

BOTS.FR-IPMS.005

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.


Source

{
  "resourceType": "Requirements",
  "id": "IntegratedPatientManagementSystemRequirements",
  "meta": {
    "profile": [
      "http://moh.bw.org/StructureDefinition/bw-requirements"
    ]
  },
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "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-05-19T15:02:57+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."
    }
  ]
}