Stap, R.E. (Roel) wrote: > Hello Koray, > > Reading your issues around cardinallity, perhaps you can solve this > issue with help of constrains/business rules. E.g. if you consider in > the Archetype model the ability to have a cardinality between A and B > of (0..N), you can constrain practically this cardinality to a maximum > of e.g. 4. The risk of modelling you cardinalities so precise in the > archetype model is that if in future this is changed, your system > (e.g. database schema's or applications) needs to be updated if this > cardinality changes. If you are able to define the reason of this > cardinality in rules you may create the flexibility in future to adapt > this without changing systems or applications. I am not sure if this > will help you, but consider this mechanism to handle cardinalities issues. > I hope this may help you in finding a solution for your issue, > > regards > Roel > > Hi Roel,
Thanks for the information you provided; especially the one about the effect of archetype design on the resulting software and database schema. I would still like to take your attention to my specific questions 2 and 3. These point out to very detailed aspects of archetype design - ones that most probably will never encounter while designing their archetypes. Best regards and Bedankt! -koray _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
