Adrian Elliot-Smith wrote: > ok i can understand the benefits of the searchability but its still a > mess if the cost of this is "misfiling" under results. surely the > documents section of md could be configured to "look" at both the > independent files database and simultaneously store argus originating > unencrypted documents. wouldn't that essentially be a relatively simple > join of two separate database tables? > > adrian
In the case of MD it is possible to retrieve lists of documents and results and to interleave these into a single dataset. You would need two separate sql queries and then some scripting to fuse the two results so it gets a bit messy. We managed to overcome any hangups about the results table being for pathology results only. We regard it as an appropriate repository for any incoming textual data. The bonus of this approach is that all incomings can be processed via the doctors inboxes. Tony Eviston > > On 31/08/06, *Tony Eviston* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > > Adrian Elliot-Smith wrote: > > so for an md user do they end up in the results section rather than > > documents where most practices would have previously stored scanned > > documents? bit messy if this is the case (would have to look for > > correspondence for a particular patient in two different places) > > Documents are currently stored as independent files with an index kept > in the database. > Results are kept in the database as plain text (unencrypted > thankfully). > This means it would be more readily searcheable. For this reason my > personal preference would be the results table for incoming documents. I > would also prefer incoming documents without any form of markup (html, > rtf, doc etc.) which makes searching more of a possibility. > I note that SQL Server Express (the free one) is now available with full > text indexing/searching so there is excellent potential to bring google > style EHR searching to the GP's desktop. I hope the vendors are up to > the challenge. > > Tony Eviston > _______________________________________________ > Gpcg_talk mailing list > [email protected] <mailto:[email protected]> > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Gpcg_talk mailing list > [email protected] > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
