[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnumed-devel] Re: [Fwd: [torch] views on "clean demo" site]

From: Karsten Hilbert
Subject: [Gnumed-devel] Re: [Fwd: [torch] views on "clean demo" site]
Date: Tue, 1 Jul 2003 15:43:34 +0200
User-agent: Mutt/

Dear GnuMedders,

this came through the TORCH list and subsequently through
the openhealth list. Tim, who is a TORCH developer offered to
export the test data once it's available. I have expressed
interest in the records on behalf of GnuMed.

Please read Dr.Maynards post below and consider joining in. We
will get back better test data if we help out creating it.
When we have the data I will make sure it is made importable
into GnuMed.

On Sun, Jun 29, 2003 at 09:57:36PM -0700, Tim Cook wrote:
> X-Mailer: Ximian Evolution 1.4.0 
> For those healthcare providers not on the TORCH list I wanted to point
> out this effort by Dr. Maynard. 
> If this effort is successful I will develop a method to export these
> records into a file that can be used by other projects that need this
> kind of data.
> -- 
> Tim Cook
> Open Paradigms, LLC

Content-Description: Forwarded message - [torch] views on  "clean demo" site
> Hello torchlist,
>    I want to ask about a barrier to initial impression of TORCH that
> I recall as a newcomer to TORCH and which is also a barrier to thorough
> testing of the modules. There are not enough realistic patient EMR
> entrees in the demo, nor enough with multiple encounters and completed
> encounters.
> What do others think of the following strategy?
>   The Problem
> 1. The public demo or test demo is for all visitors who can leave any 
> amount of unfinished test records and grafitti from learning. Therefore 
> current demo doesnt put the best content forward as an example of 
> various TORCH modules, nor does it  have enough patients entered nor 
> enough multiple visits on most EMR's to depict an up and running practice.
>   Proposal
> 1. A "clean" demo at a separate intranet directory is needed that can be 
> refreshed over the test demo on a regular schedule (perhaps weekly) to 
> remove  remnant EMR's abandoned by test visitors. Test visitors could be 
> advised that test records will be periodically removed.  Anyone visiting 
> the test demo could be invited to contribute to the "clean demo" by 
> contacting address@hidden
>   Healthcare providers motivated to contribute at the clean demo would 
> be asked to focus on reasonably complete EMR's that utilize a full range 
> of modules during each encounter that would be expected in normal health 
> care visits.
> 2. Starting the cycle :
>           Volunteers to create on line at the "clean demo" site:
>    Before changing the existing status quo with notice posted on the 
> public demo  it would be helpful to build a clean demo with at least a 
> few dozen EMRS and multiple visits.
>    This clean demo can be inaugurated when the public demo  is modified 
> with the  warning of the scheduled cycle of cleaning.
>        Mass submission from other TORCH test installations
> any users on this list have collections of  EMR's on a test 
> installation that are realistic EMR's and truely imaginary or thoroughly 
> deidentified?    Contact Tim to contribute ( reminds me, I also would 
> like to see a posting on the method of moving whole EMR's between 
> installations of TORCH)
>     I for one am willing to enroll a few reasonably realistic EMR's 
> with  some complete encounters,evolving condition/problem list and 
> multiple visits .... if I hear that others have the interest... and if 
> there is a good use for the pooled collection.
>  What are other views?
> Rusty Maynard
> **************************************************
> TORCH is supported by the open source community and by Open Paradigms 
> ==^================================================================
> This email was sent to: address@hidden
> EASY UNSUBSCRIBE click here:
> Or send an email to: address@hidden
> TOPICA - Start your own email discussion group. FREE!
> ==^================================================================

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]