[Top][All Lists]

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

Re: fields in health issues (was Re: [Gnumed-devel] NEW TOPIC - FEATURES

From: Karsten Hilbert
Subject: Re: fields in health issues (was Re: [Gnumed-devel] NEW TOPIC - FEATURES)
Date: Sun, 17 Aug 2008 17:16:04 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Aug 12, 2008 at 02:25:06PM -0700, James Busser wrote:

>> > What I see is a field in the Health Issue field where we could just 
>> click on
>> > (smoking status: never, past, current) and a OB/Gyn field (infant, 
>> fertile,
>> > menopaused, number of births / normal delivery / C sections /  
>> Abortions )
>> Sorry ... it was to be what I would like to see in the future is ... "a 
>> field in the Health Issue ... etc.."
> This is sounding like pre-populating the "health issues" with a variety 
> of specific items
> Perhaps a single health issue row "Risk factor assessment" could include 
> some ascertainment of multiple areas (smoking, alcohol, IV drug use, 
> high-risk sexual activity) with any desired details captured in the 
> narrative and any notable responses codable onto these rows. Any positive 
> items could be promoted to an independent health issue when circumstances 
> warranted.
> Would that work?

That is one way of using issues/episodes to "model"
structures which aren't available explicitely yet:

issue "habits"
 episode "smoking"
  narrative in encounter: "2 pack-years"

issue "family history"
 episode ...

This is in use by two GNUmed users currently.

It can be made easier by means of the hook framework where a
particular Python snippet can be run when, say, a patient is

> I know that the GNUmed design plans, but did not yet implement, for any 
> clinical SOAP row, to be able to be keyed/coded (I forget the precise 
> term) to one or more classification entries e.g. ICD9, Read, Snomed etc


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]