I’m quite surprised that this is not supported, yet requests from 2021 tickets (now closed without fixing it). Underpinning Archie library supports it as this data type is part of the RM spec. This is particularly important for building and persisting PROMs/PREMs and other scales where there’s SUBSTANTIAL activity and market need too. @Paulmiller@vanessap@siljelb@Kanthan_Theivendran maybe we should stick with DV_ORDINAL for the time being until this feature is implemented - I know it’s not idea but the alternative is worse! After all, we can migrate DV_ORDINAL to DV_SCALE with 100% confidence no data and semantics will be lost. Thoughts?
On a side note, as an open source software I’d expect to see reference to the license (Apache license 2.0) on the landing page (https://docs.ehrbase.org/) - right now no mention except for a link to GitHub which doesn’t guarantee open source.
@Koray_Atalag without making any promisses I can say that we are in a process of updating some of the legacy parts of EHRbase. You can see some of those changes in the latest release Release v2.30.0 · ehrbase/ehrbase · GitHub .
Even if Arche is used in EHRbase, many aspects of the RM model validation or support are not fully delegated to it, and we plan to address that step by step in the near future. I cannot give a timeline; all I can say is that we’re taking an opportunistic approach, addressing areas we already touch based on our internal prioritization.
