AU Base Implementation Guide
4.2.2-ci-build - CI Build
This page is part of the Australian Base IG (v4.2.1-preview: QA Preview) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 4.1.0. For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org.au/ValueSet/medication-type | Version: 4.2.2-ci-build | |||
Standards status: Trial-use | Maturity Level: 2 | Computable Name: MedicationType | ||
Other Identifiers: OID:2.16.840.1.113883.2.3.4.2.4.1 | ||||
Copyright/Legal: HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved. |
The Medication Type value set may be used to classify the nature of properties defined by the code e.g. branded product with no strength or form. This allows the distinction between codes provided containing container, pack, strength and form explicitly especially where terminologies supplied are unknown or terminology services are unavailable.
References
Generated Narrative: ValueSet medication-type
http://terminology.hl7.org.au/CodeSystem/medication-type
Generated Narrative: ValueSet
Expansion based on codesystem Medication Type v4.2.2-ci-build (CodeSystem)
This value set contains 11 concepts
Code | System | Display | Definition |
UPD | http://terminology.hl7.org.au/CodeSystem/medication-type | Unbranded product with no strengths or form | Unbranded product with no strengths or form. (For AMT this is equivalent to the MP - Medicinal Product concept) |
UPDS | http://terminology.hl7.org.au/CodeSystem/medication-type | Unbranded product with strengths but no form | Unbranded product with strengths but no form. |
UPDF | http://terminology.hl7.org.au/CodeSystem/medication-type | Unbranded product with form but no strengths | Unbranded product with form but no strengths. |
UPDSF | http://terminology.hl7.org.au/CodeSystem/medication-type | Unbranded product with strengths and form | Unbranded product with strengths and form. (For AMT this is equivalent to the MPUU - Medicinal Product Unit of Use concept) |
UPG | http://terminology.hl7.org.au/CodeSystem/medication-type | Unbranded package with no container | Unbranded package with no container. (For AMT this is equivalent to the MPP - Medicinal Product Pack concept) |
BPD | http://terminology.hl7.org.au/CodeSystem/medication-type | Branded product with no strengths or form | Branded product with no strengths or form. (For AMT this is equivalent to the TP - Trade Product concept) |
BPDS | http://terminology.hl7.org.au/CodeSystem/medication-type | Branded product with strengths but no form | Branded product with strengths but no form |
BPDF | http://terminology.hl7.org.au/CodeSystem/medication-type | Branded product with form but no strengths | Branded product with form but no strengths |
BPDSF | http://terminology.hl7.org.au/CodeSystem/medication-type | Branded product with strengths and form | Branded product with strengths and form. (For AMT this is equivalent to the TPUU - Trade Product Unit of Use concept) |
BPG | http://terminology.hl7.org.au/CodeSystem/medication-type | Branded package with no container | Branded package with no container. (For AMT this is equivalent to the TPP - Trade Product Pack concept) |
BPGC | http://terminology.hl7.org.au/CodeSystem/medication-type | Branded package with container | Branded package with container. (For AMT this is equivalent to the CTPP - Containered Trade Product Pack concept) |
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 |