[Top][All Lists]

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

Re: [Gnumed-devel] More lab test result considerations: groupings

From: James Busser
Subject: Re: [Gnumed-devel] More lab test result considerations: groupings
Date: Wed, 13 Feb 2008 09:39:38 -0800

On 13-Feb-08, at 8:43 AM, James Busser wrote:

Come to think of it maybe we don't *need* the various test org "sections"

We don't need them *in their own table structure* however the the test org lab sections (HAEM, CHEM, MICRO, IMMUN) could be usefully imported into a catch-all text field if we were to add one to lab_requests, something like the test_result table note_provider (to be renamed note_test_org)

If we had a field of same or equivalent name in lab_requests, the OBR 024 "Diagnostic Service Section" names could update/append into here. The nice thing about that would be that when reviewing the state of a patient's lab information, an overview might be nicely achieved by looking at the lab_requests history, especially when these would combine labs initiated from within the practice from those passively received as copy-to.

The result could be a simple two-column table that showed the date on which any specimens were collected (whether in the praxis, or elsewhere) along with the kinds or families of tests that would have been involved e.g. HAEM, CHEM, MICRO

That way, if you were to see a patient with continuing urinary symptoms Monday, who reports having been seen by someone else in the praxis (or in a walk-in clinic) three days before when they had some kind of urine test done --- but they didn't know or incorrectly stated if it had been a urinalysis or a culture --- it would be handy to look into the lab_requests and be able to see that what has come back from Friday was only CHEM, or whether it was CHEM MICRO with something pending. You could also helpfully look back to see when they last had any MICRO done.

reply via email to

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