Stream: implementers
Topic: Modeling PulseRate/Regularity
Alexander Henket (Feb 13 2019 at 15:33):
I have a functional model (PulseRate)[https://zibs.nl/wiki/PulseRate-v3.1(2017EN)] which includes PulseRateValue which is a SimpleQuantity, and a PulseRegularity (CodeableConcept regular/irregular)
I'm struggling with the latter. Are both values Observation.components? Is the latter the Observation.interpretation of the former? Does the latter qualify the former and how would Observation support that?
Alexander Henket (Feb 13 2019 at 15:53):
Current thinking leans towards
- Observation.code (LOINC 8893-0) Observation.value for PulseRateValue and
- Observation.component.code (SNOMED CT 364074009) and Observation.component.value for PulseRegularity
Lloyd McKenzie (Feb 13 2019 at 16:25):
The first question is whether an observation of "irregular pulse" is useful or typically ever captured on its own. If the answer is "yes", then the relationship between pulse rate and pulse regularity would be similar to the relationship between "white blood cell count" and "hemoglobin" - two separate observations that are often collected together in a panel. If, on the other hand, regularity is almost never collected or interpreted on its own, then treat the two like you do systolic and diastolic blood pressure. In this case, if you deem the pulse rate to be the "primary", it would be ok for it to be captured as the root value and have the regularity to be a component that qualifies it.
Last updated: Apr 12 2022 at 19:14 UTC
