Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

R6
Work Group:

Devices
Related URL:
http://build.fhir.org/devicemetric.html
Related Artifact(s):

DeviceMetric
Resolution Description:

Hide

Motion to accept issue as PERSUASIVE and to update DeviceMetric accordingly.

(Cooper / Silver, 10/0/1, 2024.01.30)

Note: DeviceMetric updates should not be applied until after approval of the DeviceAlert new FHIR resource proposal.

Show
Motion to accept issue as PERSUASIVE and to update DeviceMetric accordingly. (Cooper / Silver, 10/0/1, 2024.01.30) Note: DeviceMetric updates should not be applied until after approval of the DeviceAlert new FHIR resource proposal.
Change Category:
Enhancement
Change Impact:
Compatible, substantive
Applied for Version:

R6

DEV WG / ~~PSS-2005~~ Device Alerting Project has decided to update the DeviceMetric resource (R6) with a new data element: alertDetection. This is consistent with a similar update to the Device resource (see FHIR-43660) and the new [DeviceAlert FHIR resource being proposed|https://confluence.hl7.org/display/FHIR/DeviceAlert+FHIR+Resource+Proposal]

Proposed data element structure (see structure mockup page)

Name	Flags	Card.	Type	Description and Constraints	Long Definition / Implementer Comments
alertDetection		0..*	BackboneElement	Describes the alert detection activation states and other relevant information.	If code is not present, activationState represents the overall state for the device metric. Additional entries may provide deviating state for specific alerts. If code is not present, limitRange applies to DeviceMetric.type. For metrics with multiple components (e.g., blood pressure measurement) the code identifies the component.
code		1..1	CodeableConcept	Alert code for specific alert activation state all \| high respiration rate \| sensor disconnected binding:FHIR Alert Code Value Set ( example )
activationState		1..1	code	on \| off \| paused binding:FHIR Alert Activation State Value Set ( required )
priority		0..1		high \| medium \| low \| info	May omit if it applies to all priorities
limitRange		0..1	Range	Alarm limits that are applied in the determination of the alert condition	Alert limits may be upper, lower or both. Note: If units are present in the Range, they should be the same as in the DeviceMetric. If units are not present in the Range, they are are assumed to be the same as in the DeviceMetric.