Re: openEHR-technical Digest, Vol 47, Issue 31

lates? In our architecture, we shred compositions on archetype-level so that all data referring to a particular archetype can be queried with and without its context. As sparse columns are supported by SQL Server, it's not a big deal to have these created. Best, Birger Am 27.01.2016 u

Re: openEHR-technical Digest, Vol 47, Issue 26

Dear all, I am a student of Prof Lu. I was working on the implementation of the ARM approach last year. I'd like to give some more information about our work. As Ian McNicoll said, mapping archetype to relational database tables will generate sparse tables. In addition, archetypes can only sp

OPT generation

Hi, everyone. I was trying to implement a web OET editor to edit template and use OPT to generate the user interface for users to type in data. I met a problem when trying to convert OET to OPT. I found no libraries that can achieve this. Though I found a OET flattener that can flaten an OET to

Problem with version and specialisation

Dear All, I met a problem when using specialisation and version. For example, I have two archetypes, openEHR-DEMOGRAPHIC-PERSON.patient.v1 and openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1. Archetype openEHR-DEMOGRAPHIC-PERSON.patient-specialise.v1 is specialised from openEHR-DEMOGRAP