| ARCHETYPE ID | openEHR-EHR-SECTION.medication_order_list.v0 |
| Concept | Medication Order List |
| Description | Suggested design pattern for including an Medication Order List in a template. |
| Use | Use to support the representation of statements about medication orders that have been recorded PLUS to make positive statements about the absence of medication orders - either general statements of absence or specific statements of absence of an identified medication order. The existence of known medication orders can be persisted in records. Statements about the absence of medication orders, either general or specific, can only indicate the state of the subject at the time that the information was actually recorded - that is, they are event based. It is not sensible to persist the recording of a positive absence of a medication order as it may subsequently be ordered or self-administered by the patient, which may render any or all previous positive statements of absence obsolete. It is possible to represent both positive statements about identified medication orders alongside specific positive statements about the absence of identified medication orders in a template (eg patient is taking salbutamol and glibenclamide, but has never taken prednisolone). However in most use cases either specific statements about the presence of identified problems/diagnoses (eg patient is taking salbutamol and glibenclamide) or general statements about the positive absence of any known problems/diagnoses will be represented (eg Not currently taking any medication), but not both. While INSTRUCTION.medication and EVALUATION.exclusion-medication and their specialisations have been explicitly included in the slot constraints, other archetypes have not been explicitly excluded. This means that any other archetypes can also be included here, if needed - for example, where structured data is not available or there is a need to provide a synopis, the EVALUATION.clinical_synopsis can be inserted and used. INSTRUCTION.medication is suggested as the best archetype to represent a Medication list in this instance as it generally provides the best representation of a local Current Medication List. Clinicians can enter patient-administered medications or 'over the counter' medications into a Prescribing system as INSTRUCTIONs, which in turn can enable adverse reaction checking against all INSTRUCTIONS, whether prescribed/printed or not. So Current Medication lists can effectively contain all orders for medications, given by both the recording clinician, other clinicians and the patient. A Medication list comprising only ACTIONs will represent only those medication that have been prescribed/printed by the recording clinician. |
| Purpose | To demonstrate a design pattern for representation of a Medication Order List. |
| References | |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 7/03/2010 |
| Other Details Language | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 7/03/2010 |
| OtherDetails Language Independent | {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=, original_namespace=org.openehr, original_publisher=openEHR Foundation, custodian_namespace=org.openehr, MD5-CAM-1.0.1=C8E3ADC1BD9F001642D5E28CAC0235CC, build_uid=8b5686e1-2020-4bb3-8d05-ee2feefa80f5, revision=0.0.1-alpha} |
| Keywords | medication, exclusion, absence, current, list |
| Lifecycle | in_development |
| UID | e017f833-04e4-4e8a-ae51-3ba9735c5b01 |
| Language used | en |
| Citeable Identifier | 1051.32.922 |
| Revision Number | 0.0.1-alpha |
| All | Archetype [runtimeNameConstraintForConceptName=null, archetypeConceptBinding=null, archetypeConceptDescription=Suggested design pattern for including an Medication Order List in a template., archetypeConceptComment=null, otherContributors=Ian McNicoll, Ocean Informatics, United Kingdom Heath Frankel, Ocean Informatics, Australia, originalLanguage=en, translators=
openEHR-EHR-INSTRUCTION.medication.v1 and specialisations or openEHR-EHR-EVALUATION.exclusion-medication.v1 and specialisations, extendedValues=null]], details=[], provider=[], source=[], ism_transition=[], data=[], credentials=[]}, topLevelItems={items=ResourceSimplifiedHierarchyItem [path=ROOT_/items[at0004], code=at0004, itemType=ENTRY, level=0, text=null, description=null, comment=null, uncommonOntologyItems=null, occurencesFormal=null, occurencesText=null, cardinalityFormal=0..*, cardinalityText=Minimum of 0 items, subCardinalityFormal=null, subCardinalityText=null, dataType=ENTRY, bindings=null, values=null, extendedValues=null]}, addHierarchyItemsTo=items, currentHierarchyItemsForAdding=[ResourceSimplifiedHierarchyItem [path=/items[at0004], code=at0004, itemType=SLOT, level=1, text=Medication inclusions/exclusions, description=Slot constrained to specifically include archetypes representing known medication orders and exclusion or absence of medication orders., comment=null, uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=ENTRY, bindings=null, values=Include: openEHR-EHR-INSTRUCTION.medication.v1 and specialisations or openEHR-EHR-EVALUATION.exclusion-medication.v1 and specialisations, extendedValues=null]], minIndents={}, termBindingRetrievalErrorMessage=null] |