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
| Official URL: http://moh.bw.org/ValueSet/vs-actor-classification-codes | Version: 1.0.0 | |||
| Active as of 2025-08-20 | Computable Name: VSActorClassificationCodes | |||
A coded value that represents whether the actor is primary or secondary in the context of the requirements definition.
References
Expansion performed internally based on codesystem Actor Classification Codes v1.0.0 (CodeSystem)
This value set contains 2 concepts
| Code | System | Display | Definition |
| primary | http://moh.bw.org/CodeSystem/cs-actor-classification-codes | Primary Actor | A primary actor is the one who initiates the interaction with the system to achieve a specific goal. They are typically the main users of the system or those who directly benefit from the outcome of the use case. |
| secondary | http://moh.bw.org/CodeSystem/cs-actor-classification-codes | Secondary Actor | A secondary actor is a system, person, or organization that the system needs help from to accomplish the goal of the use case. They support the process but don’t initiate the use case |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |