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

FHIR IG Statistics: Requirements/BirthDeathRegistrationRequirements

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

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 BirthDeathRegistrationRequirements

Profile: Requirements

These requirements apply to the following actors:

BOTS.FR-BDRS.001

Should be able to provide a status check that indicates uptime and connection status.

BOTS.FR-BDRS.002

Should be able to authenticate with and connect to the appropriate Oracle View with BDRS registry data.

BOTS.FR-BDRS.003

Should be able to translate the BDRS registry data model into valid FHIR resources.

BOTS.FR-BDRS.004

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 BDRS Oracle View.

BOTS.FR-BDRS.005

Should be able to integrate with an HIE interoperability layer for incoming and outgoing communication.

BOTS.FR-BDRS.006

Should be able to connect with a FHIR-based Client Registry through the HIE.

BOTS.FR-BDRS.007

Should be able to synchronize patient data on demand between the BDRS registry and a FHIR-based HIE Client Registry, with a configurable refresh timespan.


Source

{
  "resourceType": "Requirements",
  "id": "BirthDeathRegistrationRequirements",
  "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/BirthDeathRegistrationRequirements",
  "version": "1.0.0",
  "name": "BirthDeathRegistrationRequirements",
  "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/BDRSActorDefinitionExample",
    "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-BDRS.001",
      "requirement": "Should be able to provide a status check that indicates uptime and connection status."
    },
    {
      "key": "BOTS.FR-BDRS.002",
      "requirement": "Should be able to authenticate with and connect to the appropriate Oracle View with BDRS registry data."
    },
    {
      "key": "BOTS.FR-BDRS.003",
      "requirement": "Should be able to translate the BDRS registry data model into valid FHIR resources."
    },
    {
      "key": "BOTS.FR-BDRS.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 BDRS Oracle View."
    },
    {
      "key": "BOTS.FR-BDRS.005",
      "requirement": "Should be able to integrate with an HIE interoperability layer for incoming and outgoing communication."
    },
    {
      "key": "BOTS.FR-BDRS.006",
      "requirement": "Should be able to connect with a FHIR-based Client Registry through the HIE."
    },
    {
      "key": "BOTS.FR-BDRS.007",
      "requirement": "Should be able to synchronize patient data on demand between the BDRS registry and a FHIR-based HIE Client Registry, with a configurable refresh timespan."
    }
  ]
}