Issues
- Serial data format for DV_QUANTITY is ambiguousSPECPR-448
- Detailed review of DIRECTORY operations on the Service ModelSPECPR-338
- Create ITS artifacts for JSON and XML serialization of AQL query result setsSPECPR-321Sebastian Iancu
- Definition and conformance tests for I_TERMINOLOGYSPECPR-309
- Improvements for the I_EHR_COMPOSITION interfaceSPECPR-308
- POST /composition needs some comments about implicit CONTRIBUTIONSPECPR-305Thomas Beale
- I_EHR_CONTRIBUTION.list_all_contributions and I_EHR.list_contributions seem to be the same operationSPECPR-304Thomas Beale
- Simplify SM openEHR platform, I_EHR_SERVICE create EHR operationsSPECPR-303Thomas Beale
- Do we need an "invalid_artefact" call status type for the I_DEFINITION_ADL2 interface?SPECPR-293Thomas Beale
- Improvements for the I_DEFINITION_QUERY interfaceSPECPR-292Thomas Beale
- Add explicit functions to validate archetypes and opts on I_DEFINITION_ADL14 and I_DEFINITION_ADL2 interface definitionsSPECPR-291Thomas Beale
- Change list_all_* functions for list_*, and merge with list_matching_* to simplify APISPECPR-290Thomas Beale
- Add functions to count items on SMSPECPR-288Thomas Beale
13 of 13
In https://specifications.openehr.org/releases/SM/latest/serial_data_formats.html#_openehr_reference_model_data_value_types The format for DV_QUANTITY is "<value>,<unit>" example: "78.500,kg" This is not considering on some locales like French, Russian, Uruguayan, etc. the decimal point in numbers is actually a comma, so the example becomes "78,500,kg". Though it's possible to parse it either way, it can become a source of errors depending on how that is parsed and noting that the parsing might depend on the locale. I would prefer to change the comma separation for something else like value|units. Also not that the names "value" and "unit" are not the names of the fields in DV_QUANTITY but "magnitude" and "units". Another item to consider is what to do with the rest of the attributes in DV_QUANTITY like precision, units_system, accuracy, magnitude_status, normal_range, etc. The proposed format doesn't seem to be enough.