Medtech ALEX® AU Implementation Guide
1.0.0 - Trial Use
Medtech ALEX® AU Implementation Guide
1.0.0 - Trial Use
Medtech ALEX® AU Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://alexapi.medtechglobal.com.au/fhir/ValueSet/medicationrequest-status | Version: 1.0.0 | |||
| Active as of 2025-08-28 | Computable Name: MedicationRequestStatus | |||
Defines the status for medication request
References
http://hl7.org/fhir/CodeSystem/medicationrequest-status| Code | Display | Definition |
| active | Active | The prescription is 'actionable', but not all actions that are implied by it have occurred yet. |
| stopped | Stopped | Actions implied by the prescription are to be permanently halted, before all of the administrations occurred. This should not be used if the original order was entered in error |
Expansion performed internally based on codesystem Medicationrequest status v4.0.1 (CodeSystem)
This value set contains 2 concepts
| Code | System | Display | Definition |
| active | http://hl7.org/fhir/CodeSystem/medicationrequest-status | Active | The prescription is 'actionable', but not all actions that are implied by it have occurred yet. |
| stopped | http://hl7.org/fhir/CodeSystem/medicationrequest-status | Stopped | Actions implied by the prescription are to be permanently halted, before all of the administrations occurred. This should not be used if the original order was entered in error |
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 |