Re: [Gnumed-devel] placeholders

[Karsten Hilbert]

On Tue, Jan 22, 2013 at 11:11:45PM +0530, address@hidden wrote:

> When an encounter expands to latex formatted text, you
> have to fix up the template to accommodate the latex
> formatted information.

That is correct.


> Though this might have advantages, It takes away the
> flexibility of having a template which expands to simple
> text.

That is correct as well.

> If instead you have placeholder "s" which only pulls
> "subjective" information from the database, the ultimate
> formatting can be achieved using latex template or as a
> simple text format.

Correct. And we do:

        Subjective:
                $<progress_notes::s//%(date)s | %(provider)s | 
%(narrative)s::9999>$
        Objective:
                $<progress_notes::o//%(date)s | %(provider)s | 
%(narrative)s::9999>$
        Assessment:
                $<progress_notes::a//%(date)s | %(provider)s | 
%(narrative)s::9999>$
        Plan:
                $<progress_notes::p//%(date)s | %(provider)s | 
%(narrative)s::9999>$
        Unspecified:
                $<progress_notes::u//%(date)s | %(provider)s | 
%(narrative)s::9999>$
        Administrivia:
                $<progress_notes:: //%(date)s | %(provider)s | 
%(narrative)s::9999>$

Wait, good that I looked at this - it needs improvement. Done.

> This choice then rest on user's expertise and or liking.

Indeed.

One downside is that in this case one cannot smartly handle
empty fields (they are replaced by '', sure, but they cannot
be omitted).

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346