Kenya ePrescription FHIR Implementation Guide
0.1.0 - ci-build
Kenya ePrescription FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://nshr-uat.sha.go.ke/ValueSet/controlled-substance-schedule | Version: 0.1.0 | |||
| Active as of 2026-04-24 | Computable Name: ControlledSubstanceScheduleVS | |||
Copyright/Legal: Copyright 2025+ Digital Health Agency, Kenya. This content is licensed under Creative Commons Attribution 4.0 International (CC-BY-4.0). Terminology content from the Kenya Pharmacy and Poisons Board (PPB) via Open Concept Lab (OCL) is subject to separate terms. |
||||
Regulatory schedules for controlled substances as defined under the Kenya Pharmacy and Poisons Act, Cap 244.
References
https://nshr-uat.sha.go.ke/CodeSystem/controlled-substance-schedule version 📦0.1.0
Expansion performed internally based on codesystem Controlled Substance Schedule CodeSystem v0.1.0 (CodeSystem)
This value set contains 4 concepts
| System | Code | Display (en) | Definition | JSON | XML |
https://nshr-uat.sha.go.ke/CodeSystem/controlled-substance-schedule | schedule-I | Schedule I | Substances with high abuse potential and no accepted medical use (e.g. heroin). | ||
https://nshr-uat.sha.go.ke/CodeSystem/controlled-substance-schedule | schedule-II | Schedule II | High abuse potential with severe dependence liability; accepted medical use with restrictions (e.g. morphine, fentanyl). | ||
https://nshr-uat.sha.go.ke/CodeSystem/controlled-substance-schedule | schedule-III | Schedule III | Moderate-to-low physical dependence and high psychological dependence potential (e.g. codeine combinations). | ||
https://nshr-uat.sha.go.ke/CodeSystem/controlled-substance-schedule | schedule-IV | Schedule IV | Lower abuse potential relative to schedule III (e.g. benzodiazepines, tramadol). |
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 |