Thanks Laura,
That is very helpful clarification. It is unfortunate that much of the
interesting work being done in the English NHS is 'hidden away' either
with the TRUD mechanism or in the case of the Clinical Data Standards
work, behind the N3 firewall. I know steps are being taken to address
-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110603
Avanzada
Av. Manuel Siurot, s/n.
C.P.: 41013SEVILLA
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110603/38f0bfbf/attachment.html
Hi, I'm somewhat new to the group and openEHR (on technical level). So excuse
my ignorance. I was wondering about the use of non sql databases. Has anyone
tried to see if something like couchDB or MongoDB could be used to store EHR
data. I know there are definate performace gains with nonsql
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110603/f1e7378c/attachment.html
Hi Robert,
The kind of systems you mentioned have the main advantage of scaling
up without very expensive software licenses. I would not say anything
about definite performance gains without having a well defined context
though.
These persistence mechanisms mainly serve large data processing
/openehr-technical
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110603/836a5915/attachment.html
7 matches
Mail list logo