Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R5
-
Orders & Observations
-
Device
DeviceDefinition -
-
Elliot Silver / Yanick Gaudet : 13 - 0 - 0
-
Enhancement
-
Non-compatible
-
R5
Description
There are other models of standards conformance (and compliance certification, and regulatory and legal compliance) than a specialization of IEEE 11073.
- Rename the Device.specialization element to conformsTo to support other approaches.
- Rename the systemType element to something that indicates that the code could be for a standard, rule, regulation, law, certification (or maybe "standard" is sufficient).
- Consider adding a "substandard," "option," or "clause" element (0..* CodeableConcept) to capture implemented options, DICOM SOP classes, IHE Actors and named Options, etc.; alternatively document how to claim conformance to such items.
- Ensure short, definition, and comment of specialization and sub-elements are updated to align. Ensure that the example Device Specialization value set includes non-IEEE 11073 examples, such as Bluetooth, DICOM (or a DICOM SOP class), IHE Profiles. Ensure the examples cover at least one law or regulation.
- Consider if DeviceDefinition.specialization should be updated to better align with Device.specialization (either current or with updates resulting from this ticket).
Please consider the issues raised in FHIR-38058 as included in this ticket by reference, and thus part of the R5 ballot.