ISO 11239:2012, Health informatics -- Identification of medicinal products -- Data elements and structures for the unique identification and exchange of regulated information on pharmaceutical dose forms, units of presentation, routes of administration and packaging. Available from: https://www.iso.org/standard/55032.html.
ISO 11240:2012, Health informatics -- Identification of medicinal products -- Data elements and structures for the unique identification and exchange of units of measurement. Available from: https://www.iso.org/standard/55033.html.
ISO 11616:2017, Health informatics -- Identification of medicinal products -- Data elements and structures for unique identification and exchange of regulated pharmaceutical product information. Available from: https://www.iso.org/standard/70044.html.
ISO 11615:2017, Health informatics -- Identification of medicinal products -- Data elements and structures for the unique identification and exchange of regulated medicinal product information. Available from: https://www.iso.org/standard/70150.html.
FHIR Resource Medication, HL7 [Internet]. Available at: https://www.hl7.org/fhir/medication.html (Accessed 12 April 2018)
Organisation: Nasjonal IKT HF
Email: silje.ljosland.bakke@nasjonalikt.no
Date originally authored: 2018-06-07
Organisation: Nasjonal IKT HF
Email: silje.ljosland.bakke@nasjonalikt.no
Date originally authored: 2018-06-07
- Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.
- Custodian Organisation: openEHR Foundation
- References: ISO 11238:2018, Health informatics -- Identification of medicinal products -- Data elements and structures for the unique identification and exchange of regulated information on substances. Available from: https://www.iso.org/standard/69697.html. ISO 11239:2012, Health informatics -- Identification of medicinal products -- Data elements and structures for the unique identification and exchange of regulated information on pharmaceutical dose forms, units of presentation, routes of administration and packaging. Available from: https://www.iso.org/standard/55032.html. ISO 11240:2012, Health informatics -- Identification of medicinal products -- Data elements and structures for the unique identification and exchange of units of measurement. Available from: https://www.iso.org/standard/55033.html. ISO 11616:2017, Health informatics -- Identification of medicinal products -- Data elements and structures for unique identification and exchange of regulated pharmaceutical product information. Available from: https://www.iso.org/standard/70044.html. ISO 11615:2017, Health informatics -- Identification of medicinal products -- Data elements and structures for the unique identification and exchange of regulated medicinal product information. Available from: https://www.iso.org/standard/70150.html. FHIR Resource Medication, HL7 [Internet]. Available at: https://www.hl7.org/fhir/medication.html (Accessed 12 April 2018)
- Original Namespace: org.openehr
- Original Publisher: openEHR Foundation
- Custodian Namespace: org.openehr
- MD5-CAM-1.0.1: 2AC0A5FC5AAC3D72188CB7118467A627
- Build Uid: 966aca22-7a83-409c-bfde-a7ba1b1abc03
- Revision: 1.0.6
For example: 'Zinacef 750 mg powder' or 'cefuroxim'. This item should be coded if possible, using for example, RxNorm, DM+D, Australian Medicines Terminology or FEST. Usage of this element will vary according to context of use. This element may be omitted where the name of the medication is recorded in the parent INSTRUCTION or ACTION archetype, and this archetype is only used to record that the form must be or was 'liquid'.
For example: 'tablet', 'capsule', 'cream', 'infusion fluid' or 'inhalation powder'. Coding of the form with a terminology is preferred, where possible. Medicines catalogues may differentiate between administrable form 'solution for injection' and product form 'powder for solution for injection'. The recorded form will depend on the exact context of use but administrable form is likely to be used in most instances.
For example: 'Paracetamol/codeine' is a Multi-ingredient product, while 'Morphine 60 mg + Haloperidol 2 mg + Midazolam 5 mg' is an Ad-hoc mixture, whose composition is fully specified within the order.
Choice of:
Coded Text- Ad-hoc mixture [The medication or medication component is composed of a mixture of ingredients specified within the order. These are typically prepared by pharmacy or ward personnel to suit individual patients.]
- Ingredient [The medication or medication component is an individual ingredient of the medication. This term is used when the archetype is nested within a parent instance of itself, to describe the individual ingredients of a medication.]
- Multi-ingredient product [The medication or medication component consists of a number of active ingredients which are pre-combined into a single form such as a tablet, cream or powder by the manufacturer, for example Paracetamol/codeine.]
- Single-ingredient product [The medication or medication component is a manufactured product containing a single active ingredient.]
- Combination product [The medication or medication component consists of a number of separate products which are pre-packaged by the manufacturer, for example Canesten Combi.]
Text
In some cases, as for liquid or semisolid medications, the denominator of the strength ratio is a physical quantity, for example 2 mg/5 ml. In some of these cases the denominator also reflects the actual volume of the component: 5 ml in the previous example. In this case the 'Strength (concentration)' would be 0.4 mg/ml. In other cases, where the strength involves a denominator which is not a physical quantity, for example 4 mg/tablet, the denominator is expressed as a unitary value '1' with a unit of '1', and 'tablet' is carried in the 'Unit of presentation' element. This arrangement was chosen to align with the approach adopted by the ISO IDMP standard for medication catalogues.
For example: For a presentation strength of '300 µg/0.3 ml', the strength numerator value is '300'. For a presentation strength of '100 mg/tablet', the strength numerator value is '100'.
Property: Qualified real
Units: >=0.0
The strength numerator is usually recorded using mass, volume or arbitrary units. For example: 'mg', 'ml', 'IU'. For a presentation strength of '300 µg/0.3 ml', the strength numerator unit is 'µg'. For a presentation strength of '100 mg/tablet', the strength numerator value is 'mg'.
For example: For a presentation strength of '300 µg/0.3 ml', the strength denominator value is '0.3'. For a presentation strength of '100 mg/tablet', the strength denominator value is '1'.
Property: Qualified real
Units: >=0.0
The strength denominator is usually recorded using mass or volume units. For example: 'g', 'ml'. For a presentation strength of '300 µg/0.3 ml', the strength denominator unit is 'ml'. For a presentation strength of '100 mg/tablet', the strength denominator unit is '1'. For this example, the 'Unit of presentation' element is used to record the presentation unit of the medication, 'tablet'.
For example: 'tablet', 'capsule', 'puff', 'inhalation'. In most cases, like for tablets and capsules, the unit of presentation is identical to the Form. For some presentations such as inhalers, the Form may be 'inhalation powder', 'inhalation aerosol' or 'inhaler' while the unit of presentation is 'inhalation', 'puff', or 'dose'.
This element is used for liquid or semisolid medications, or medications intended to be diluted in a liquid before administration. For example: '10 mg/ml', '20 mg/g', '5 %', '10,000 SQ-U/ml'.
Property: Concentration
For example: 'Abbott'.
Choice of:
- Text
Identifier
Any other form of expiry date, such as time from production or depending on storage environment, can be inserted using a specific CLUSTER archetype in the Substance Details slot or added as part of the Description. For example: '2017-05-23'.
This slot is intended to be used to add details about constituents of the medication or medication component, using nested instances of this archetype. This is not normally required other than where a mixture is being described.
Include:
openEHR-EHR-CLUSTER.medication.v0 and specialisations or
openEHR-EHR-CLUSTER.medication.v1 and specialisations
For example: '1', '1.5', '1000'. Note: the associated unit for this amount is recorded using the 'Amount unit' element.
Property: Qualified real
Units: >=0.0
For example: 'mg', 'ml', 'IU'. Note: The value of the amount is recorded using the 'Amount' element.
The unit of the alternate amount is recorded in the 'Alternate amount unit' element. For example: for a medication with a strength of '5 mg/ml' and where the Amount is '1 ml', the equivalent amount would be 5 mg and the value recorded in this data element would be '5'.
Property: Qualified real
Units: >=0.0
The value of the alternate amount is recorded in the 'Alternate amount' element. For example: for a medication with a strength of '5 mg/ml' and where the Amount is '1 ml', the equivalent amount would be 5 mg and the value recorded in this data element would be 'mg'.
Choice of:
- Coded Text
- Therapeutic [Constituent that alone or in combination with one or more other ingredients is considered to fulfil the intended activity of a medicinal product.]
- Adjuvant [Constituent whose primary function is to modify the activity of an active constituent. An adjuvant constituent itself may or may not be therapeutically active.]
- Excipient [Constituent that is inert in relation to the intended activity of the medicinal product.]
- Text
For example: detailed information about the drug class or intended routes, or additional expiry information.
Include:
All not explicitly excluded archetypes
Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)
Silje Ljosland Bakke, Nasjonal IKT HF, Norway (openEHR Editor)
John Bennett, NEHTA, Australia
SB Bhattacharyya, Sudisa Consultancy Services, India
Sharmila Biswas, Australia
Laila Bruun, Oslo universitetssykehus HF, Norway
Stephen Chu, NEHTA, Australia (Editor)
Matthew Cordell, NEHTA, Australia
Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway
Gail Easterbrook, Flinders Medical Centre, Australia
Stig Erik Hegrestad, Helse Førde, Norway
David Evans, Queensland Health, Australia
Sarah Gaunt, NEHTA, Australia
Heather Grain, Llewelyn Grain Informatics, Australia
Trina Gregory, cpc, Australia
Sam Heard, Ocean Informatics, Australia (Editor)
Hilde Hollås, DIPS AS, Norway
Roar Holm, Helse Vest IKT A/S, Norway
Alfred Honore, Haukeland, Norway
Evelyn Hovenga, EJSH Consulting, Australia
Lars Ivar Mehlum, Helse Bergen HF, Norway
Tom Jarl Jakobsen, Helse Bergen, Norway
Mary Kelaher, NEHTA, Australia
Nils Kolstrup, Skansen Legekontor og Nasjonalt Senter for samhandling og telemedisin, Norway
Harmony Kosola, Alberta Health Services, Canada
Robert L'egan, NEHTA, Australia
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
Mark Luciani, Gloucestershire Hospital NHS Foundation Trust, United Kingdom
Colin Macfarlane, Elsevier, United Kingdom
Siv Marie Lien, DIPS ASA, Norway
James McClay, University of Nebraska Medical Center, United States
Susan McIndoe, Royal District Nursing Service, Australia
David McKillop, NEHTA, Australia
Hildegard McNicoll, freshEHR Clinical Informatics Ltd., United Kingdom
Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)
Chris Mitchell, RACGP, Australia
Stewart Morrison, NEHTA, Australia
Andrej Orel, Marand d.o.o., Slovenia
Chris Pearce, Melbourne East GP Network, Australia
Vladimir Pizzo, Hospital Sírio Libanês, Brazil
Camilla Preeston, Royal Australian College of General Practitioners, Australia
Margaret Prichard, NEHTA, Australia
Cathy Richardson, NEHTA, Australia
Robyn Richards, NEHTA - Clinical Terminology, Australia
Martha Schei Hynne, The Norwegian Medicines Agency, Norway
Anoop Shah, University College London, United Kingdom
Line Silsand, Universitetssykehuset i Nord-Norge, Norway
Trine Strand, Oslo Universitetssykehus (OUS), Norway
Andreas Sundstrom, Capio S:t Gorans Hospital, Sweden
John Taylor, NEHTA, Australia
Rowan Thomas, St. Vincent's Hospital Melbourne, Australia
Richard Townley-O'Neill, NEHTA, Australia (Editor)
Guri Tømmervåg, DIPS AS, Norway
Gro-Hilde Ulriksen, Norwegian center for ehealthresearch, Norway
John Tore Valand, Helse Bergen, Norway (openEHR Editor)
Pelle Viana Lindén, Capio, Sweden
Kylie Young, The Royal Australian College of General Practitioners, Australia
Sam Heard, Ocean Health Systems, Australia
- German: Ramona Wellmann, Natalia Strauch, Medizinische Hochschule Hannover, wellmann.ramona@mh-hannover.de, Strauch.Natalia@mh-hannover.de
- Swedish: Sofia Janstad, SLL, sofia.lang-janstad@sll.se
- Norwegian Bokmål: Silje Ljosland Bakke, Nasjonal IKT HF
- Portuguese: Beatriz de Faria Leao, Bleao Informática em Saúde, bfleao@terra.com.br, MD, PhD
- Dutch: Joost Holslag, Nedap, joost.holslag@nedap.com, MD