|Subject:||[Gnumed-devel] stress test for gnumed|
|Date:||Sun, 30 Oct 2005 22:02:16 +0800|
could someone give a synopsis of how to do the client calls
in order to load gnumed with a large amount of test data ?
The test data has the following :-
past history, allergies, rx, scripts, progress notes, letters, pathol, document meta and images of documents, immunizations, diagnoses, pap smears, measurements.
history is like past_history clin_item i think, diagnoses like the name of a clin_episode , progress notes a clin_narrative, pathol is usually
in a block text format with simple formatting, letters can be parsed to text but would be handy if imported items can have their original
form stored as well (? clin_item.raw_import_data) , document meta and images - I would like a description on how to call the api
here. pap smears and measurements - probably can go in clin_results; rx and scripts ? - seems to be an avoided schema topic
A scenario using some fake object /dictionary etc as input and some pseudo code would be extremely helpful, please.
Say the dictionary object can also have entries for largish objects in base64 encoding for the document imaging : linux paging
can handle this , I think, as each document image is about 100K and say there may be at most 30 documents.
Of course, it would be nice to add the ability to browse other kinds of clin items from the emr_browser tree , such as
pathology and letters and document meta and images
:- would this clash with the intentions of the gnumed designers ?
|[Prev in Thread]||Current Thread||[Next in Thread]|