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).

(Comment 50 - imported by: Ron G. Parker)