About database design

[coderChase]

After view all of the codes, I think this project realized the openEHR standards very well. But if I want to put them into practice, the database design is very important. The openEHR provides a method called "node+path", I don't know whether it would work well with these libs. So my question is if I want to use these codes to build my own EHR project, how should the database be designed to guarantee that the project can work well with large amount of data and the query is efficient. Thank you.

[icorbal]

Hi Chase,
that is quite a complex subject. There are some proprietary solutions, but
nothing yet opensourced.
It depends on how big is your team is and how much effort you want to spend
on it, but I would go for the simplest approach that solves your
requirements.
Trying to develop a solution that allows persistence for the whole openEHR
specs can be quite challenging.

There was some discussion about this on the mailing list, maybe you find
some tips there:

http://lists.openehr.org/pipermail/openehr-implementers_lists.openehr.org/2013-April/001230.html

Cheers,

iago

2013/12/23 coderChase notifications@github.com

After view all of the codes, I think this project realized the openEHR
standards very well. But if I want to put them into practice, the database
design is very important. The openEHR provides a method called "node+path",
I don't know whether it would work well with these libs. So my question is
if I want to use these codes to build my own EHR project, how should the
database be designed to guarantee that the project can work well with large
amount of data and the query is efficient. Thank you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11
.

[coderChase]

Hi Iago,
After doing some research, as you mentioned, the database design of openEHR system is really complex. There are some solutions I found. Among them, I prefer to use the XML database(I mean NXD), like eXist db. And the java libs provided by your team contains some methods that generating XML files from AOM(what's the purpose?). What's more, the XQuery makes query more efficient.
What's your opinion? Do you think the java libs work well with the eXist db(or NXD )? With the limit information I got, it seems that it is a good way. Because you are familiar with this lib, I really want to hear your opinion. Thank you.

Cheers,

Chase

发自我的 iPhone

在 2013年12月23日，17:34，icorbal notifications@github.com 写道：

Hi Chase,
that is quite a complex subject. There are some proprietary solutions, but
nothing yet opensourced.
It depends on how big is your team is and how much effort you want to spend
on it, but I would go for the simplest approach that solves your
requirements.
Trying to develop a solution that allows persistence for the whole openEHR
specs can be quite challenging.

There was some discussion about this on the mailing list, maybe you find
some tips there:

http://lists.openehr.org/pipermail/openehr-implementers_lists.openehr.org/2013-April/001230.html

Cheers,

iago

2013/12/23 coderChase notifications@github.com

After view all of the codes, I think this project realized the openEHR
standards very well. But if I want to put them into practice, the database
design is very important. The openEHR provides a method called "node+path",
I don't know whether it would work well with these libs. So my question is
if I want to use these codes to build my own EHR project, how should the
database be designed to guarantee that the project can work well with large
amount of data and the query is efficient. Thank you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11
.

—
Reply to this email directly or view it on GitHub.

existDB is a good solution for storing and querying data.

But it is not all you need, for example, validation, datasets against
archetypes.

I wonder how people solve that. What is your suggestion?

Bert

op 24-12-13 16:08, coderChase schreef:

Hi Iago,
After doing some research, as you mentioned, the database design of
openEHR system is really complex. There are some solutions I found.
Among them, I prefer to use the XML database(I mean NXD), like eXist
db. And the java libs provided by your team contains some methods that
generating XML files from AOM(what's the purpose?). What's more, the
XQuery makes query more efficient.
What's your opinion? Do you think the java libs work well with the
eXist db(or NXD )? With the limit information I got, it seems that it
is a good way. Because you are familiar with this lib, I really want
to hear your opinion. Thank you.

Cheers,

Chase

发自我的 iPhone

在 2013年12月23日，17:34，icorbal notifications@github.com 写道：

Hi Chase,
that is quite a complex subject. There are some proprietary
solutions, but
nothing yet opensourced.
It depends on how big is your team is and how much effort you want
to spend
on it, but I would go for the simplest approach that solves your
requirements.
Trying to develop a solution that allows persistence for the whole
openEHR
specs can be quite challenging.

There was some discussion about this on the mailing list, maybe you
find
some tips there:

http://lists.openehr.org/pipermail/openehr-implementers_lists.openehr.org/2013-April/001230.html

Cheers,

iago

2013/12/23 coderChase notifications@github.com

After view all of the codes, I think this project realized the
openEHR
standards very well. But if I want to put them into practice, the
database
design is very important. The openEHR provides a method called
"node+path",
I don't know whether it would work well with these libs. So my
question is
if I want to use these codes to build my own EHR project, how
should the
database be designed to guarantee that the project can work well
with large
amount of data and the query is efficient. Thank you.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/11
.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#11 (comment).

[coderChase]

Hi Bert,
Could you please explain more details about the problems I would meet using
eXist DB, such as validation and datasets against
archetypes? Thank you.

Cheers,

Chase

2013/12/25 Bert Verhees notifications@github.com

existDB is a good solution for storing and querying data.

But it is not all you need, for example, validation, datasets against
archetypes.

I wonder how people solve that. What is your suggestion?

Bert

op 24-12-13 16:08, coderChase schreef:

Hi Iago,
After doing some research, as you mentioned, the database design of
openEHR system is really complex. There are some solutions I found.
Among them, I prefer to use the XML database(I mean NXD), like eXist
db. And the java libs provided by your team contains some methods that
generating XML files from AOM(what's the purpose?). What's more, the
XQuery makes query more efficient.
What's your opinion? Do you think the java libs work well with the
eXist db(or NXD )? With the limit information I got, it seems that it
is a good way. Because you are familiar with this lib, I really want
to hear your opinion. Thank you.

Cheers,

Chase

发自我的 iPhone

在 2013年12月23日，17:34，icorbal notifications@github.com 写道：

Hi Chase,
that is quite a complex subject. There are some proprietary
solutions, but
nothing yet opensourced.
It depends on how big is your team is and how much effort you want
to spend
on it, but I would go for the simplest approach that solves your
requirements.
Trying to develop a solution that allows persistence for the whole
openEHR
specs can be quite challenging.

There was some discussion about this on the mailing list, maybe you
find
some tips there:

http://lists.openehr.org/pipermail/openehr-implementers_lists.openehr.org/2013-April/001230.html

Cheers,

iago

2013/12/23 coderChase notifications@github.com

After view all of the codes, I think this project realized the
openEHR
standards very well. But if I want to put them into practice, the
database
design is very important. The openEHR provides a method called
"node+path",
I don't know whether it would work well with these libs. So my
question is
if I want to use these codes to build my own EHR project, how
should the
database be designed to guarantee that the project can work well
with large
amount of data and the query is efficient. Thank you.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/11
.

—
Reply to this email directly or view it on GitHub.

—

Reply to this email directly or view it on GitHub
#11 (comment).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-31183344
.

You must convert/translate archetypes to a kind of XML Schema before you
can validate your xml data against the archetypes. If you take a look at
the open source Openehr which was announced this week on this list, I think
it may be possible you will find what you look for.

I have nothing to do with that, so I cannot help you any further. Ask the
people behind it, I know them, they are very friendly

Good luck and happy xmas
Bert
Op 25 dec. 2013 03:43 schreef "coderChase" notifications@github.com:

Hi Bert,
Could you please explain more details about the problems I would meet
using
eXist DB, such as validation and datasets against
archetypes? Thank you.

Cheers,

Chase

2013/12/25 Bert Verhees notifications@github.com

existDB is a good solution for storing and querying data.

But it is not all you need, for example, validation, datasets against
archetypes.

I wonder how people solve that. What is your suggestion?

Bert

op 24-12-13 16:08, coderChase schreef:

Hi Iago,
After doing some research, as you mentioned, the database design of
openEHR system is really complex. There are some solutions I found.
Among them, I prefer to use the XML database(I mean NXD), like eXist
db. And the java libs provided by your team contains some methods that
generating XML files from AOM(what's the purpose?). What's more, the
XQuery makes query more efficient.
What's your opinion? Do you think the java libs work well with the
eXist db(or NXD )? With the limit information I got, it seems that it
is a good way. Because you are familiar with this lib, I really want
to hear your opinion. Thank you.

Cheers,

Chase

发自我的 iPhone

在 2013年12月23日，17:34，icorbal notifications@github.com 写道：

Hi Chase,
that is quite a complex subject. There are some proprietary
solutions, but
nothing yet opensourced.
It depends on how big is your team is and how much effort you want
to spend
on it, but I would go for the simplest approach that solves your
requirements.
Trying to develop a solution that allows persistence for the whole
openEHR
specs can be quite challenging.

There was some discussion about this on the mailing list, maybe you
find
some tips there:

http://lists.openehr.org/pipermail/openehr-implementers_lists.openehr.org/2013-April/001230.html

Cheers,

iago

2013/12/23 coderChase notifications@github.com

After view all of the codes, I think this project realized the
openEHR
standards very well. But if I want to put them into practice, the
database
design is very important. The openEHR provides a method called
"node+path",
I don't know whether it would work well with these libs. So my
question is
if I want to use these codes to build my own EHR project, how
should the
database be designed to guarantee that the project can work well
with large
amount of data and the query is efficient. Thank you.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/11
.

—
Reply to this email directly or view it on GitHub.

—

Reply to this email directly or view it on GitHub
#11 (comment).

—
Reply to this email directly or view it on GitHub<
https://github.com/openEHR/java-libs/issues/11#issuecomment-31183344>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-31190078
.