Issues
- Add title attribute to RESOURCE_DESCRIPTIONSPECBASE-40Resolved issue: SPECBASE-40Thomas Beale
- Change RESOURCE_DESCRIPTION.lifecycle_state type to StringSPECBASE-39Resolved issue: SPECBASE-39Thomas Beale
- Adjust details of computational features of data/time typesSPECBASE-38Thomas Beale
- Add stereotypes to represent Enums from common programming languages.SPECBASE-37Resolved issue: SPECBASE-37Thomas Beale
- Correct rules for matching CODE_PHRASE.terminology_id to allow URIs and non-URI ids.SPECBASE-36Thomas Beale
- Align version_id from ARCHETYPE_ID with the counterpart from ARCHETYPE_HRIDSPECBASE-35Sebastian Iancu
- Allow +14:00 timezoneSPECBASE-34Resolved issue: SPECBASE-34Thomas Beale
- Retrospectively release interim form of Expression LanguageSPECBASE-33Resolved issue: SPECBASE-33Thomas Beale
- Improve Types cross-reference table in Foundation typesSPECBASE-32Thomas Beale
- Improvements to Terminology packageSPECBASE-31Thomas Beale
- Define TEMPLATE_ID syntaxSPECBASE-30Thomas Beale
- Fix version-id syntax issue in ARCHETYPE_IDSPECBASE-29Resolved issue: SPECBASE-29Thomas Beale
- Fix internet_id and uid_based_id confusion in syntax definitionSPECBASE-28Resolved issue: SPECBASE-28Thomas Beale
- Correct OBJECT_REF.namespace regexSPECBASE-27Resolved issue: SPECBASE-27Sebastian Iancu
- Add Built-in classes and functions for use in AQL, ELSPECBASE-26Resolved issue: SPECBASE-26Thomas Beale
- Improve and correct function definitions in Foundation typesSPECBASE-25Resolved issue: SPECBASE-25Thomas Beale
- Improve specifications block diagram and related explanations.SPECBASE-24Resolved issue: SPECBASE-24Thomas Beale
- Add other_contributors to TRANSLATION_DETAILSSPECBASE-23Resolved issue: SPECBASE-23Thomas Beale
- Provide formal definition of URI construction for openEHRSPECBASE-22Thomas Beale
- Update Architecture Overview with new LANG component, and improved explanation of ITSSPECBASE-21Resolved issue: SPECBASE-21Thomas Beale
- Accept URI-style terminology ids.SPECBASE-20Thomas Beale
- Broaden LOCATABLE_REF.as_uri() to allow URIs referring to any health dataSPECBASE-19Resolved issue: SPECBASE-19Thomas Beale
- Update text in Common IM to latest openPGP specification.SPECBASE-18Resolved issue: SPECBASE-18Thomas Beale
- Update Architecture Overview with current high-level elements.SPECBASE-16Resolved issue: SPECBASE-16Thomas Beale
- Add foundation types specification to BASE.SPECBASE-15Resolved issue: SPECBASE-15Thomas Beale
- Move RM common.resource spec to BASE resource spec.SPECBASE-13Resolved issue: SPECBASE-13Thomas Beale
- Add Base Types specification to BASE component.SPECBASE-7Resolved issue: SPECBASE-7Thomas Beale
- Specify language attributes of `RESOURCE_DESCRIPTION_ITEM` and `TRANSLATION_DETAILS` as being coded by a subset of RFC 5646 language tag standard.SPECBASE-6Sebastian Iancu
- Change order of type parameters in Hash<V,K> type to Hash<K,V>SPECBASE-4Resolved issue: SPECBASE-4Thomas Beale
- Add ODIN specification to BASESPECBASE-2Resolved issue: SPECBASE-2Thomas Beale
- Convert Architecture Overview from Release 1.0.2SPECBASE-1Resolved issue: SPECBASE-1Thomas Beale
31 of 31
There are two requirements that have become worth consideration. The first is DV_ORDINAL with real values. The second is the ability to have real values with a coded value instead of a unit. At present we have to use proportion and then another element to achieve this. For example to record how much fruit was eaten it would be possible to use a number and the type of fruit as a coded set. It is also possible that such a datatype could be used for ordinals with real values and it needs careful consideration as a DV_CODED_COUNT has identical features to an ordinal.