ARCHETYPE ID | openEHR-EHR-SECTION.adverse_list.v0 |
Concept | Adverse Reaction List |
Description | Suggested design pattern for including an Adverse Reaction List in a template. |
Use | Use to support the representation of statements about known adverse reactions that have been recorded PLUS to make positive statements about the absence of adverse reactions - either general statements of absence or specific statements of absence of an adverse reaction to a specific substance. The existence of known adverse reactions can be persisted in records. Statements about the absence of adverse reactions, 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 an adverse reaction as an adverse reaction that occurs on administration of any substance may render any or all previous positive statements of absence obsolete. In clinical practice this is synonymous with asking a patient if they have a reaction to any medications or substances prior to any and every administration of a medication or substance. It is possible to represent both positive statements about identified adverse reactions alongside specific positive statements about the absence of identified problems/diagnoses in a template (eg patient has had an adverse reaction to tetracycline but never had a reaction to penicillin. However in most use cases either specific statements about the presence of identified adverse reactions (eg patient has had reactions to tetracycline and sticking plaster) or general statements about the positive absence of any known problems/diagnoses will be represented (eg No known adverse reactions), but not both. While EVALUATION.adverse and EVALUATION.exclusion-adverse archetypes 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. |
Purpose | To demonstrate a design pattern for representation of an Adverse Reaction List. |
References | |
Copyright | © openEHR Foundation |
Authors | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 2010-03-07 |
Other Details Language | Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date originally authored: 2010-03-07 |
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, original_namespace=org.openehr, original_publisher=openEHR Foundation, custodian_namespace=org.openehr, MD5-CAM-1.0.1=4B8888E87D20EF23BB9C7FBB2F06A1AA, build_uid=f3da2319-7db6-4f7b-8b1e-ee2e0e7b1b2e, revision=0.0.1-alpha} |
Keywords | adverse, reaction, exclusion, absence, known, list |
Lifecycle | in_development |
UID | 9c72c0bf-7e12-4efb-a35a-e4849bffb56e |
Language used | en |
Citeable Identifier | 1051.32.151 |
Revision Number | 0.0.1-alpha |
All | Archetype [runtimeNameConstraintForConceptName=null, archetypeConceptBinding=null, archetypeConceptDescription=Suggested design pattern for including an Adverse Reaction List in a template., archetypeConceptComment=null, otherContributors=Ian McNicoll, Ocean Informatics Heath Frankel, Ocean Informatics, originalLanguage=en, translators=
openEHR-EHR-EVALUATION.exclusion-adverse_ openEHR-EHR-EVALUATION.adverse_ openEHR-EHR-EVALUATION.exclusion-adverse_ openEHR-EHR-EVALUATION.adverse_ |