Move DV_QUANTIFIED.magnitude_status options to openEHR terminology
Raise CR
Analysis
Execution
Raise CR
Analysis
Execution
Description
Currently DV_QUANTIFIED.magnitude_status is effectively restrained by narrative description in the design specification with the following invariant: Magnitude_status_valid: magnitude_status /= Void implies valid_magnitude_status (magnitude_status).
See https://specifications.openehr.org/releases/RM/Release-1.1.0/data_types.html#_dv_quantified_class
To simplify software implementation, it would be desirable to move the actual list of strings allowed for magnitude_status to a machine-readable format based content such as the openEHR terminology file. Similar example also exists, e.g. the normal_status list of options.
The challenge here is that the attribute magnitude is a string type, unlike code_phrase typed normal_status. Still it's possible to point at the string content of a terminology group without changing the data type to maintain backwards compatibility.
Currently DV_QUANTIFIED.magnitude_status is effectively restrained by narrative description in the design specification with the following invariant: Magnitude_status_valid: magnitude_status /= Void implies valid_magnitude_status (magnitude_status). See https://specifications.openehr.org/releases/RM/Release-1.1.0/data_types.html#_dv_quantified_class To simplify software implementation, it would be desirable to move the actual list of strings allowed for magnitude_status to a machine-readable format based content such as the openEHR terminology file. Similar example also exists, e.g. the normal_status list of options. The challenge here is that the attribute magnitude is a string type, unlike code_phrase typed normal_status. Still it's possible to point at the string content of a terminology group without changing the data type to maintain backwards compatibility.