| ARCHETYPE ID | openEHR-EHR-OBSERVATION.pulse.v1 |
|---|---|
| Concept | Pulse |
| Description | Measurement of the pulse rate, or heart rate, and description of associated characteristics. |
| Use | Use to record the presence or absence of a pulse rate or heart rate. Use to record the measurement of the pulse rate, or heart rate, and observation about the associated rhythm. Use to record a simple description of characteristics that are associated with the pulse or heart beat, that might be commonly recorded as part of a vital signs obervation. Measurements such as the maximum pulse or heart rate over an interval of time can be recorded using "Maximum' event. Others point-in-time or interval events may be specified within a template or at run-time. In practice, the terms heart rate and pulse rate are often used interchangeably. This archetype allows either term to be used when the measurement site is not specified, to suit clincian preferences. In certain situations, however, it is important to differentiate between a pulse rate observed at a peripheral artery, such as the radial artery, in contrast to the centrally observed heart rate. This archetype allows the data to be very specific and differentiate between central heart rate and the pulse rate recorded at a specified artery. |
| Misuse | Not to be used to record the R-R rate in the context of an Electrocardiograph report - this is to be recorded using the OBSERVATION.ecg archetype. Not to be used to record other details of the full cardiovascular examination or assessment. Other specific CLUSTER archetypes will be used to record characteristics such as apex beat, murmurs and bruits, auscultatory findings, In particular, this archetype is not intended to record the assessment of peripheral vascular disease, which requires documentation of the presence and strength of each peripheral pulse. A specific CLUSTER archetype will be used to record the general findings on examiantion of peripheral pulses. Not to be used to record fetal heart rate - this is recorded using the OBSERVATION.fetal_heart archetype. Concepts such as Target Heart Rate should be recorded in separate EVALUATION archetypes related to goals and exercise assessment. |
| Purpose | To record the measurement of the pulse rate, or heart rate, and description of associated characteristics as one component of a vital signs observation. |
| References | Direct communication with clinicians. Pulse (renamed from Heart Rate), draft archetype, openEHR Clinical Knowledge Manager [Internet]. London: openEHR Foundation. Authored: 26 Mar 2006. Major update: 20 Feb 2013. Available at: http://www.openehr.org/knowledge/OKM.html#showarchetype_1013.1.170_5 (accessed 20 Feb 2013). |
| Copyright | © openEHR Foundation |
| Authors | Author name: Sam Heard Organisation: Ocean Informatics Email: sam.heard@oceaninformatics.com Date originally authored: 2006-03-26 |
| Other Details Language | Author name: Sam Heard Organisation: Ocean Informatics Email: sam.heard@oceaninformatics.com Date originally authored: 2006-03-26 |
| Other Details (Language Independent) |
|
| Keywords | rate, rhythm, beat, pulse, heart, vital, sign |
| Lifecycle | CommitteeDraft |
| Language used | en |
| Citeable Identifier | 1013.1.1412 |
| state | |
| Position | Position: The body position of the subject during the observation.
Assumed value: Sitting |
| Confounding Factors | Confounding Factors: Narrative description about any incidental factors that may be affect interpretation of the physical findings. For example, presence of a pacemaker, level of anxiety; pain or fever etc. |
| Exertion | Exertion: Details about physical exertion being undertaken during the examination. Include: openEHR-EHR-CLUSTER.level_ |
| events | |
| Any event | Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time. |
| Maximum | Maximum: Maximum rate of the pulse or heart beat observed during a period of exertion. Math. function: Maximum |
| protocol | |
| Method | Method: Method used to the pulse observe the pulse or heart beat. For example, auscultation or electronic monitoring.
|
| Findings Location | Findings Location: Body site where the pulse or heart beat findings were observed.
|
| Device | Device: Details about the device used to observe the pulse or heart beat. Include: openEHR-EHR-CLUSTER.device.v1 and specialisations Exclude: All not explicitly included archetypes |
| data | |
| Pulse Presence | Pulse Presence: Identification of a pulse or heart beat. It can be implied that the pulse is present if Rate >0 beats/min.
|
| (Rate) | (Rate): The rate, measured in beats per minute. Run-time name constraints have been specified, in order to simplify the renaming of this data element to Pulse Rate or Heart Rate, as required. Property: Frequency Units: >=0.0 /min Limit decimal places: 0 Runtime name constraint:
|
| Regularity | Regularity: The observed regularity of the pulse or heart beat.
|
| Character | Character: Description of the character of the pulse or heart beat. Coding with a terminology is desired, where possible. For example: full, thready, bounding, slow rising, or collapsing. Multiple terms may be recorded. |
| Clinical Description | Clinical Description: Narrative description about the findings. |
| Clinical Interpretation | Clinical Interpretation: Single word, phrase or brief description represents the clinical meaning and significance of the pulse or heart beat findings. Coding with a terminology is preferred, where possible. For example: Bradycardia, Extrasystoles or Sinus rhythm. Multiple statements are allowed. |
| Other contributors | Koray Atalag, University of Auckland, New Zealand Rong Chen, Cambio Healthcare Systems, Sweden Stephen Chu, NeHTA, Australia Angela de Zwart, Orion Health, New Zealand Graham Denyer, Australian Antarctic Division, Australia Paul Donaldson, Nursing Informatics Australia, Australia Sebastian Garde, Ocean Informatics, Germany Sam Heard, Ocean Informatics, Australia Evelyn Hovenga, EJSH Consulting, Australia Eugene Igras, IRIS Systems, Inc., Canada Athanasios Kleontas, Ergobyte Informatics, Greece Shinji Kobayashi, Ehime University, Japan Robert Legan, NEHTA, Australia Heather Leslie, Ocean Informatics, Australia (Editor) Rohan Martin, Ambulance Victoria, Australia Ian McNicoll, Ocean Informatics, United Kingdom (Editor) Jeroen Meintjens, Medisch Centrum Alkmaar, Netherlands Monica Merchat, Hospital Cardiac Electrophysiology, MS Health Informatics Student, former ICU nurse, former Anesthesia Technician, United States Arturo Romero, SESCAM, Spain |
| Translators |
|