-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Converting ADL schemes into Sql and generating tables #10
Comments
In general is better to have a data model based on the information model not on the archetypes, since structures of the IM are shared between different archetypes. Generating an schema from archetypes is a bad idea because it fragments the IM and makes querying more difficult. |
Hello @ppazos @wolandscat thank you for the response, although it has been a year when i posted the issue :D... |
@fedkh there is some work done in China using that approach, I talked with members of that team and explained why it was not the best approach in general, but it might be useful for small / test systems. Not recommended for big / complex / production systems, querying can get chaotic, since you'll need to get the same data e.g. blood pressure, from different tables. And will difficult database management, since adding new archetypes to the system, will add new tables to the DB. |
@ppazos yes agree with you thank you a lot for the clarification. Moving toward Nosql schema will be more convenient in this context. |
@fedkh not recommending to generate SQL schema from archetypes is not the same as recommending a document or OO database. You can use SQL generating the schema/data model from the openEHR IM. My CDR does that: https://github.com/ppazos/cabolabs-ehrserver |
Hello,
I am having difficulties in converting an archetype into Sql scheme in order to generate the specific tables.
Can anyone please help me understand this further or give me some guidelines.
Thanks a lot
My regards,
Fadoua
The text was updated successfully, but these errors were encountered: