[Gnumed-devel] Latex template incorporating digitized signature

[Busser, Jim]

The attached uses a .png of my signature which I keep stored in the root directory/file

        /gnumed/signature.png

same as gnumedlogo.png which avoids my having to copy it into each new client.

However, this only works for me -- despite that the Tex package

        includegraphics

requires absolute file specifications -- because I am running GNUmed from my laptop as a single user.


Notice, in the attached example (in which I addressed the letter on Kirk to myself) that I had *logged in* to GNUmed as clinician Leonard McCoy, despite which the document bears my signature.

In order to be able to incorporate (support) a distinct per-user signature in a multiuser GNUmed praxis, one must:

- create and choose a different template per-clinician (in order that each template specifies a different signature absolute reference), or

- (at some future time) -- if it was feasible for GNUmed -- to provide a placeholders that can support a user-based file reference, either to a file accessible from the server or maybe a signature image document imported into the GNUmed record of this user.

Already, a user must be a person within GNUmed to enable to specify them as the current provider, and optionally their credentials, via placeholders.

I was wondering whether the clinician could import a signature (e.g. png) as a document, and then somehow reference the document via a placeholder. This might require, in addition to placeholders, a way to more easily identify which document is intended, for example by adding (in the Documents plug, in the "Part Actions" contextual menu) some additional submenu item or an expansion to what is shown among the

        Sign / Edit properties

that could allow the user to copy / paste a reference to the desired blob in GNUmed?

??

-- Jim


       

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
https://lists.gnu.org/mailman/listinfo/gnumed-devel

[Karsten Hilbert]

On Wed, Jul 11, 2012 at 02:49:05AM +0000, Jim Busser wrote:

> The attached

Truly a nice template !  It's great to see GNUmed + LaTeX
being put to good use  :-)

> uses a .png of my signature which I keep stored in the root directory/file
>
> /gnumed/signature.png

I'd be scared. Please make sure its permissions are 0600 ...

> Notice, in the attached example (in which I addressed the
> letter on Kirk to myself) that I had *logged in* to GNUmed
> as clinician Leonard McCoy, despite which the document bears
> my signature.

I see the problem.

A trick can be employed:

        \includegraphics[whatever options]{/gnumed/signature-$<current_provider_external_id::MSP//CA BC::120>$.png}

You will then need to rename *your* signature file to

        /gnumed/signature-<whatever_your_MSP_is>.png

;-)

Eventually, a better solution is to enhance the staff table
to be able to hold a bytea field .signature able to store a
signature image. I would then recommend to store a GPG
encrypted version and have GNUmed ask the user and GPG to
decrypt it on demand.

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

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
https://lists.gnu.org/mailman/listinfo/gnumed-devel

[Karsten Hilbert]

On Wed, Jul 11, 2012 at 11:40:28AM +0200, Karsten Hilbert wrote:

> > Notice, in the attached example (in which I addressed the
> > letter on Kirk to myself) that I had *logged in* to GNUmed
> > as clinician Leonard McCoy, despite which the document bears
> > my signature.
>
> I see the problem.
>
> A trick can be employed:
>
> \includegraphics[whatever options]{/gnumed/signature-$<current_provider_external_id::MSP//CA BC::120>$.png}
>
> You will then need to rename *your* signature file to
>
> /gnumed/signature-<whatever_your_MSP_is>.png

You will want to provide an "empty/1 white pixel"

        /gnumed/signature-.png

for those cases where the MSP evaluates to an empty string
(id est is not registered).

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

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
https://lists.gnu.org/mailman/listinfo/gnumed-devel

[Busser, Jim]

On 2012-07-11, at 2:40 AM, Karsten Hilbert wrote:

>> uses a .png of my signature which I keep stored in the root directory/file
>>
>> /gnumed/signature.png
>
> I'd be scared. Please make sure its permissions are 0600 ...

My laptop is encrypted, but -- for the case where my deployment may be transferred to a server -- thanks!

-- Jim
_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
https://lists.gnu.org/mailman/listinfo/gnumed-devel

[Karsten Hilbert]

On Wed, Jul 11, 2012 at 02:12:14PM +0000, Jim Busser wrote:

> >> uses a .png of my signature which I keep stored in the root directory/file
> >>
> >> /gnumed/signature.png
> >
> > I'd be scared. Please make sure its permissions are 0600 ...
>
> My laptop is encrypted,

I'm preaching to the choir.

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

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
https://lists.gnu.org/mailman/listinfo/gnumed-devel

[Busser, Jim]

On 2012-07-11, at 2:48 AM, Karsten Hilbert wrote:

> On Wed, Jul 11, 2012 at 11:40:28AM +0200, Karsten Hilbert wrote:
>
>>> Notice, in the attached example (in which I addressed the
>>> letter on Kirk to myself) that I had *logged in* to GNUmed
>>> as clinician Leonard McCoy, despite which the document bears
>>> my signature.
>>
>> I see the problem.
>>
>> A trick can be employed:
>>
>> \includegraphics[whatever options]{/gnumed/signature-$<current_provider_external_id::MSP//CA BC::120>$.png}
>>
>> You will then need to rename *your* signature file to
>>
>> /gnumed/signature-<whatever_your_MSP_is>.png
>
> You will want to provide an "empty/1 white pixel"
>
> /gnumed/signature-.png
>
> for those cases where the MSP evaluates to an empty string
> (id est is not registered).

Bearing in mind that my original placeholder -- which resolves to my (existing) MSP# -- is

        $<current_provider_external_id::Billing#//BC.CA_MSP>$

I was able to make it all work nicely. This included my providing, in my root /gnumed/ a 'stub' file

        /gnumed/signature-.png

which covers the contingency of a clinician (like McCoy) for whom no mapped external ID identifier exists (and who accordingly resolves to my 2x2 pixel white space 'stub').

I only am not sure what your suggested placeholder parameter

        ::120

was meant to achieve... is it simply precautionary against some bizarrely long value inputted for an ID?

-- Jim


_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
https://lists.gnu.org/mailman/listinfo/gnumed-devel

[Karsten Hilbert]

On Thu, Jul 12, 2012 at 04:57:41AM +0000, Jim Busser wrote:

> >> A trick can be employed:
> >>
> >> \includegraphics[whatever options]{/gnumed/signature-$<current_provider_external_id::MSP//CA BC::120>$.png}
> >>
> >> You will then need to rename *your* signature file to
> >>
> >> /gnumed/signature-<whatever_your_MSP_is>.png

> Bearing in mind that my original placeholder -- which resolves to my (existing) MSP# -- is
>
> $<current_provider_external_id::Billing#//BC.CA_MSP>$
>
> I was able to make it all work nicely.

> I only am not sure what your suggested placeholder parameter
>
> ::120
>
> was meant to achieve... is it simply precautionary against some bizarrely long value inputted for an ID?

In a way. Also, since I suggested something without testing
I figured to be on the safe side I adhere to the full
placeholder spec (IOW, include a max length).

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

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
https://lists.gnu.org/mailman/listinfo/gnumed-devel