[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Past history
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Past history |
Date: |
Mon, 6 Aug 2012 19:57:38 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Mon, Aug 06, 2012 at 02:06:52PM +0000, Jim Busser wrote:
> > If you are using the "PHX" placeholder (which maps to health
> > issues) you can access the 'age_noted' field which may help
> > some.
>
> So… age_noted would either carry a numeric value, or be null.
>
> If the date at which the problem / event occurred would
> have been inputted, would age_noted be computed?
Yes.
> Also with a placeholder, the user could potentially attempt
>
> <Problem> at age <value>
>
> however in the case of no value entered the display would be
>
> Influenza at age
> Foo2 at age 27
> Foo3 at age 35...
Correct.
> so am not sure if there is any suggested workaround
> (unless the placeholder can replace a missing value for age
> with "?").
We would need to define a string to use instead of NULL. The
default is ''. Note that that string would be applied to
*all* fields evaluating to NULL which are being used in that
placeholder instance.
> > The "problems" placheolder can only offer 'problem_active'
> > and 'clinically_relevant'.
>
> do the above return / supply "TRUE" ("true") and "FALSE" ("false")?
In this very case translations of "yes" and "no" would be
returned:
def _get_variant_PHX(self, data=None):
...
return separator.join ([
template % phx.fields_as_dict (
date_format = date_format,
escape_style = esc_style,
bool_strings = (_('yes'), _('no'))
) for phx in phxs
])
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346