Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R5
-
Orders & Observations
-
Device
DeviceDefinition -
-
Lorraine Constable / Elliot Silver : 10-0-2
-
Enhancement
-
Non-compatible
-
R5
Description
Currently, issues are being considered that suggest using Device.property for intended use and instructions for use text. Since FHIR generally frowns upon key-value pair lists, especially when we can identify some likely keys, would it make sense to add specific elements to Device and/or DeviceProperty.
Alternatively, should we determine that tracking those values is out of the 80%-use case, and, rather than capture them in `property`, define standard extensions for these elements?