[EMAIL PROTECTED] wrote: > In response to Tony's pondering we are doing soemthing that is related. > Although let me say this is a research project where we are trying to push > the boundaries rather thatn satisfy a specification. It may not be > everyone's cup-of-tea. > We call the project Generative Hospital Information Systems and it has that > name because we consider it is system to generate special purpose > information systems. Some of its philosophical features are; > 1. The users define the the nature of the data they want to collect ( with > the help of a generic data dictionary) > A necessary start.
> 2. The users define the screen layouts and formats for collecting that > data. > For my vote I would want free text fields with auto-expansion of hot key short cuts. Tabbing around is too difficult in general practice for history taking and probably most examinations. > 3. The patient's information is a story stored in a document repository > rather than a record repository, hence reteival is of a form previously > populated by someone else. > Jon, I think I understand the first bit but not the second. Can you expand? > 4. The fundamental objective of the system is to support analytics, > everything else comes as an adjunct to that objective. This is justified > on the basis that clinicians purposive use of an IS is to get it to answer > questions as distinct from just retreiving patient hi-stories. > And this is why they will come. The next generation of medical software should do two things in addition to storing the data. It should support analytics as Jon is undertaking and it should support fine grained access to the shared medical record. With the continuing change in medical practice and the acceptance of general practice as the repository for the nation's medical data this has become critical. > Our first attempt will be to replicate the processes in the ED at a western > sydney hospital. We spent 3months there last summer doing a process > analysis which we now have on a piece of paper covering the better part of > a small wall. If we hit the spot we will have something that at least > performs up to the current EDIS but can do better with functionality for > clinicians, greater flexibilty to re-engineer and potentially much > superior analytics. We won't have analytics functioning for the first > release. > > Code is written in Python and C# (some compromises made). Linux server - > windows client. > Are wxpython and C# stable in routine use for GUI development. David
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
