Richard Hosking wrote: > I still struggle with this stuff - isnt an archetype describing > constraints on the data- ie type, bounds etc? Shouldnt this be coded > into the DB? If not where?
No, all those constraints are enforced by the openEHR kernel/engine (you know, the bits that aren't available yet) informed by archetypes expressed as ADL (archetype definition language) files. Ultimately, teh openEHr kernel should be built right intot he underlying database engine - and that is quite possible with extensible database servers such as PostgreSQL - given the right expertise and a bit of funding. In the meantime, it can be implemented as a layer on top of a database engine eg in C#, Java or Python. Tim C > Hugh Leslie wrote: > >> >> An openEHR database schema doesn't contain ANY archetypes - The data >> reflects the openEHR reference model, not the archetype model. If you >> have >> to hard code archetypes in a schema then you have not gained anything at >> all. The archetypes just describe what the data means. >> >> >> >> > _______________________________________________ > Gpcg_talk mailing list > [email protected] > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk > _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
