|
»
»
CCHIT AM
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
CCHIT AM
by Jim Busser
::
Rate this Message:
AM 06.04
The
system shall provide the ability to capture patient history as both a presence
and absence of conditions, i.e. the specification of the absence of a personal
or family history of a specific diagnosis, procedure or health risk behavior.
--- (I am using --- above as a separator) How are we (in 0.5 ) accommodating the above? As a Health Issue of "Family History" within which can exist multiple episodes, each given the name of the condition and whether it is present or absent (as described in a minimum of one row of SOAP note) despite that only one of these (considered "active") would be easily edited however a different Family History "episode" item could instead be made the active one, if this other item needed new information. _______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
|
|
Re: CCHIT AM
by Karsten Hilbert
::
Rate this Message:
On Sat, Nov 07, 2009 at 11:24:11PM -0800, Jim Busser wrote:
> AM 06.04 > > The system shall provide the ability to capture patient history as > both a presence and absence of conditions, i.e. the specification of > the absence of a personal or family history of a specific diagnosis, > procedure or health risk behavior. > > --- > > (I am using --- above as a separator) > > How are we (in 0.5 ) accommodating the above? As a Health Issue of > "Family History" within which can exist multiple episodes, each > given the name of the condition and whether it is present or absent > (as described in a minimum of one row of SOAP note) Or right inside the episode name. > despite that > only one of these (considered "active") would be easily edited > however a different Family History "episode" item could instead be > made the active one, if this other item needed new information. Yes. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
|
|
Re: CCHIT AM
by Rogerio Luz Coelho
::
Rate this Message:
Can ALL patient have a "Family History" Health Issue ? Automatically at patient creation?
Maybe this would suffice Rogerio 2009/11/8 Karsten Hilbert <Karsten.Hilbert@...>
_______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
|
|
Re: CCHIT AM
by Karsten Hilbert
::
Rate this Message:
On Tue, Nov 10, 2009 at 02:40:47PM -0200, Rogerio Luz Coelho wrote:
> Can ALL patient have a "Family History" Health Issue ? Automatically at > patient creation? > > Maybe this would suffice Sure, use a hook script hooking into "post_patient_activation". Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
|
|
Hook scripts (was Re: CCHIT AM)
by Jim Busser
::
Rate this Message:
On 2009-11-10, at 12:29 PM, Karsten Hilbert wrote:
> On Tue, Nov 10, 2009 at 02:40:47PM -0200, Rogerio Luz Coelho wrote: > >> Can ALL patient have a "Family History" Health Issue ? >> Automatically at >> patient creation? >> >> Maybe this would suffice > > Sure, use a hook script hooking into > "post_patient_activation". If people would develop and contribute hook scripts, where in the CVS would we propose that these be stored? Do we create a new directory "hookscripts" at the same level as /client /server ?? _______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
|
|
Re: Hook scripts (was Re: CCHIT AM)
by Karsten Hilbert
::
Rate this Message:
On Tue, Nov 10, 2009 at 02:38:52PM -0800, Jim Busser wrote:
> >Sure, use a hook script hooking into > >"post_patient_activation". > > If people would develop and contribute hook scripts, where in the > CVS would we propose that these be stored? > > Do we create a new directory "hookscripts" at the same level as > > /client > /server I would suggest gnumed/client/hookscripts/ Note, however, that locally it would need to live under ~/.gnumed/scripts/ Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
|
|
Re: Hook scripts (was Re: CCHIT AM)
by Jim Busser
::
Rate this Message:
On 2009-11-11, at 5:18 AM, Karsten Hilbert wrote: I would suggest gnumed/client/hookscripts/ So... stored/archived, in CVS and in downloaded copies of the client under gnumed/client/hookscripts/ because whether or not they would run is controlled at the level of the client, and that control is further determined at run time by the presence of the script under ~/.gnumed/scripts/ as per ps in the above hook_script_example what would the line do: # enc = 'cp850' # FIXME: configurable _______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
|
|
Re: Hook scripts (was Re: CCHIT AM)
by Karsten Hilbert
::
Rate this Message:
On Wed, Nov 11, 2009 at 06:35:58AM -0800, Jim Busser wrote:
> >I would suggest gnumed/client/hookscripts/ > > > >Note, however, that locally it would need to live under > >~/.gnumed/scripts/ > > So... stored/archived, in CVS and in downloaded copies of the client > under > > gnumed/client/hookscripts/ > > because whether or not they would run is controlled at the level of > the client, More specifically at the level of the local *user*, yes. > and that control is further determined *only* > at run time by the presence of the script under > > ~/.gnumed/scripts/ yes > as per > > http://cvs.savannah.gnu.org/viewvc/gnumed/gnumed/client/doc/hook_script_example.py?root=gnumed&view=markup yes > ps in the above hook_script_example what would the line do: > # enc = 'cp850' # FIXME: configurable It defines the encoding to use for that particular GDT export file. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list Gnumed-devel@... http://lists.gnu.org/mailman/listinfo/gnumed-devel |
| Free embeddable forum powered by Nabble | Forum Help |
