| ARCHETYPE ID | openEHR-EHR-COMPOSITION.medication_list.v0 |
|---|---|
| Concept | Medication list |
| Description | A persistent and managed list of medications that are reasonably assumed to be taken by the individual and that may influence clinical decision-making and care provision. |
| Use | Use to record a persistent and managed list of all medicines, both prescribed and 'over the counter', that are reasonably assumed to be taken by the individual or, alternatively, positive statements about known exclusions or actual absence of any information about medications; This list can be utilised as a source of medicines data as a current medication list, for exchange or as the basis for decision support. This list can be comprised of three types of archetype:
In order for a Medication list to be accurate and safe to use as the basis for decision support activities and for exchange, this Medication List should ideally be curated by a clinician responsible for the health record, rather than managed automatically by the clinical system through business rules alone. There can be a subtle but important difference between types of medication lists. Some examples include: 'Current Medication' or 'Regular Medication'. A 'Current Medication' list may be regarded as a list of all medicines that the individual would have in their body at a given time, including any stat or prn doses of a medicine that should be considered when prescribing to ensure that drug-drug interaction checking continues for the duration of it's physiological effect. A 'Regular Medication' list may only include those medicines that are taken by the individual on a regular and ongoing basis. In addition, it is common in clinical practice to create Medication Lists that have temporal constraints, including 'Admission Medication List' and 'Discharge Medication List', which will be relevant only at a specified point in time. It is probably better practice to record these contextual clinical constructs as the result of a query, rather than represent it within a COMPOSITION to prevent any incorrect assumption that this is an ongoing list of medications. This archetype is intended to be represented and managed as a persistent list, however there are situations where the list may be used within episodic care and require additional attributes such as context etc to enable accurate recording. The openEHR reference model currently only allows context to be recorded within Event-based COMPOSITION archetypes. As a result, this archetype has been modelled as an Event, rather than Persistent, COMPOSITION, to allow for flexibility so that some clinical systems can safely manage Medication lists for episodes of care, while others will choose to implement this COMPOSITION to act in a persistent manner. |
| Misuse | Not to be used to record lists of Medications that are not intended for persistence and ongoing revision and curation. Not to be used to record vaccinations administered - use COMPOSITION.vaccination_list for this purpose. |
| Purpose | To record a persistent and managed list of medicines that are reasonably assumed to be taken by the individual or, alternatively, positive statements about known exclusions or actual absence of any information about medications; all of which may influence clinical decision-making and care provision. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Chunlan Ma Organisation: Ocean Informatics, Australia Email: chunlan.ma@oceaninformatics.com Date originally authored: 2006-11-06 |
| Other Details Language | Author name: Chunlan Ma Organisation: Ocean Informatics, Australia Email: chunlan.ma@oceaninformatics.com Date originally authored: 2006-11-06 |
| Other Details (Language Independent) |
|
| Keywords | medication, medicine, list, ongoing, drug |
| Lifecycle | in_development |
| UID | 2af67d4c-0798-41b1-b4ec-d2392e5d6f16 |
| Language used | en |
| Citeable Identifier | 1013.1.1880 |
| Revision Number | 0.0.1-alpha |
| data | |
| Category | |
| null |
|
| Other contributors | Ian McNicoll, Ocean Informatics, United Kingdom Sam Heard, Ocean Informatics, Australia Sistine Barretto-Daniels, Ocean Informatics, Australia Heather Leslie, Ocean Informatics, Australia |
| Translators |