gmane.comp.gnu.medical.devel

Re: promoting GNUmed 2

Busser, Jim — 2012-05-25T15:11:15


and also for patient_photo

... it would be so cool to be able to output a patient photo into a PDF... I don't believe I have witnessed any EMR doing so.

Re: promoting GNUmed 2

Busser, Jim — 2012-05-25T14:12:28


Hmm... I agree this would increase name awareness of GNUmed, but surely seeing GNUmed's name on non-GNUmed print output would confuse the heck out of people?

Re: promoting GNUmed 2

Sebastian Hilbert — 2012-05-25T09:33:35

Thanks. This is excellent work. What I was after is including a reference to 
GNUmed into your existing (other then GNUmed) emr solution :-)

Sebastian

Re: GNUmed billing - Insert vs Add

Busser, Jim — 2012-05-25T08:15:39

Can the billing plugin (in rc4) be clarified?


I am not clear whether both of the following attach bills to a patient:

+ Add

vsfields along the bottom of the plugin window.

Is the idea that the bottom-of-screen method assumes that the billings are to be dated 'today' and that the value which will be charged will be a 'simple multiple' of base rate x factor, whereas if one must assign an earlier date and/or assign some 'over ride' value e.g. other than {base rate x factor} then one requires to use

+ Add (button)

??

Re: GNUmed billing

Busser, Jim — 2012-05-25T08:05:41


ATM (in rc4) no...

While the 'Select' button will indeed invoke an address *picker*, its dialog provides only OK and Cancel but no way to create an address when none exists.

Re: placeholders in latex - vaccinations

Busser, Jim — 2012-05-25T07:51:32

With reference to the screenshot of the vaccination table

[cid:8fd137b5-4c7d-46fa-b648-20c92bcb2118< at >ead.ubc.ca]


1. Can we lose the horizontal line below the table? I understand its intent as a 'footnote separator' but its appearance right below the table border confounds the intention.


2. Can the column heading S/P be replaced with SoaP because
- 'S/P' ambiguates for 'Status Post', and
- 'SoaP' more readily communicates that a value of 'S' will refer to Subjective and 'P' to Plan.


3. Is there a problem in the placeholder code which generates the footnote mark (number), but does not anymore prepend this number to the target text? The hyperref manual at http://www.tug.org/applications/hyperref/manual.html warns that the function hyperfootnotes "Makes the footnote marks into hyperlinks to the footnote text. Easily broken …"


4. CAVEAT misbehaviour of package 'hyperref' when it was not called last, as demonstrated by its inadvertent hyper-linkage of the superscript 1 (next to S/P) to ac

Re: promoting GNUmed 2

Busser, Jim — 2012-05-25T03:38:00


I may have identified something suitable in

        \raisebox

with syntax

\lfoot{
\raisebox{-0.7\height}{\includegraphics[scale=0.275]{/Users/djb/Downloads/gnumed-client.1.1.12/client/bitmaps/gnumedlogo.png}\\
}}

Raisebox permits to adjust the "negative heights" (as a ratio of the GNUmed logo height), and the scale (relative to the original GNUmed logo image size).

Larger images (as would result from a scale of 0.3 instead of 0.25) will require to be lowered by a greater proportion (say, 0.75 instead of 0.7) in order to keep them below the top of the footer.

After three trials, it seemed a scale of 0.275 for the GNUmed logo in a footer may be more suitable than 0.25 (too small) or 0.3 (too large).

So... all we need is a placeholder that can reference gnumedlogo.png ;-)

Re: promoting GNUmed 2

Busser, Jim — 2012-05-25T02:46:24


I think it has only

        gnumedlogo.png

which has the serpent, wrapped by GNU MED, but this png lacks the text

        "A free Project for Paperless General Practice"



ah, I incorporated the above into references now added to

        http://wiki.gnumed.de/bin/view/Gnumed/LaTeX

and I can report some progress. The 'graphicx' package is not satisfied to be fed relative file references to the image in the client

        gnumedlogo.png
        bitmaps/gnumedlogo.png
        ./bitmaps/gnumedlogo.png

instead triggering the error

        File `gnumedlogo.png' not found on input line 235.

and the substitution of an image 'mask'  (see footer 1.png).

A full file specification such as

        /Users/djb/Downloads/gnumed-client.1.1.12/client/bitmaps/gnumedlogo.png

or placing a copy of the png into the relevant /tmp/ folder (and regenerating) will incorporate the png (see footer 2.png).

Some debugging is yet needed to decipher optimal LaTex syntax because -- as shown in footer 2.png -- the use of

Re: promoting GNUmed 2

Karsten Hilbert — 2012-05-24T20:57:20


There are ways, yes.


No, but it is included with the client.


It could, yes.


Yes.


Yes.

http://www.artofproblemsolving.com/Wiki/index.php/LaTeX:Pictures

Karsten

Re: Medication bug

Karsten Hilbert — 2012-05-24T20:20:29


Vaibhav, mind you, I fully understand your desire to be
adding the drugs you need for your practice.

However, in this particular case I believe you can do better
than the drug companies and make a real difference in safety
for your patients !

Best regards,
Karsten

Re: Medication bug

Karsten Hilbert — 2012-05-24T20:13:49


That's right. GNUmed will not let you edit a substance or
brand as long as it is in use with a patient. Allowing that
would be a patient safety issue.


Same as with editing. It would be a patient safety issue.


That is correct. GNUmed will not allow the user to use
identical names for different drugs.

Doing so would be a patient safety issue.

One will need to call each unique drug by a unique name.
Everything else would be a patient safety issue. Yes, drug
companies are patient safety issues, as we all know.

My suggestion would be to call the drugs

***ease 150
***ease 200

Karsten

Re: Medication bug

Sebastian Hilbert — 2012-05-24T20:06:17

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

Re: Medication bug

Sebastian Hilbert — 2012-05-24T20:03:19

Works for me.


In the status line it will tell you that you cannot change it since it is 'in 
use'.


Same as above.


works for me


Ok. When you create a new drug with the same name but changed substance it 
will silently ignore to assign the new substance to the new drug (which has 
the same name as the old drug and technically is not a new drug but an altered 
drug, which does not work)


Morease with 200mg is not even created in my case (and it should not)


At least in Germany there are no two drugs with different dosages sharing an 
identical brand name.

So Morease and Morease cannot exist at the same time containing either 150mg 
or 200mg. The solution here in Germany is to labe the brand name Morease 200 
(containing 200mg) and Morease 150 (for 150mg).

Once can argue that changing sunstances even in already prescribed brands (or 
'in use' could be allowed in some cases. If it is truly an error then all 
records in GNUmed (as in 'in use') would need to be updated. Which would need 
to ask for gm-

Re: promoting GNUmed 2

Busser, Jim — 2012-05-24T17:02:00

Hi again,



... What about placing a GNUmed logo on your current system's documents (bills, referrals letters etc.)
...
<header-logo-gnumed.png>

I am wondering whether some (but not all) GNUmed print output methods can accept to include a referenced object e.g. image.

1) is the GNUmed png already in the bootstrap?
2) is this anything a placeholder can help?
3) is LaTex (plus minus other output methods) able to incorporate such a reference?
4) can LaTex scale the png to fit into some desired limited space.

Do 3, 4 need researching before deciding whether {1,2} should be pursued?

Medication bug

2012-05-24T16:00:59

I think this is possibly already described.
On windows, I added a substance mebeverine sr 150 mg , added brand
***ease and used it for one patient. I realised that mebeverine sr
comes as 200 mg. and tried to correct it without success. Tried to
delete it without success. Added a new substance entry of mebeverine
sr 200 mg and added ***ease with 200 mg as substance. Now when i
attempt to add morease sr 200 mg, only the entry of 150 mg is
displayed and 200 mg is not accepted. That simply means that a brand
name with a single substance with two different dosages can not be
accepted by gnumed. This is purely a safety issue and should be dealt
with on urgent basis

promoting GNUmed 2

Sebastian Hilbert — 2012-05-24T11:23:07

Hi again,

What do you think about showing your support for GNUmed right on existing 
material you create every day ? What about placing a GNUmed logo on your 
current system's documents (bills, referrals letters etc.)

What else would be a good place you can show your support ? Let me know.

Sebastian Hilbert


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

promoting GNUmed

Sebastian Hilbert — 2012-05-24T11:18:22

Hi all,

GNUmed 1.2 and loads of new features are just around the corner. Once it is 
out I would like to make it visible to people.

You could help by updating the screenshots and video material we have.
If you are interested in helping GNUmed getting know please consider working 
with me on updating the content.

Have a look at
http://wiki.gnumed.de/bin/view/Gnumed/GNUmedMovies

We really should redo those.

Anyone ?

Let me know. Any help is appreciated.

Sebastian Hilbert

Gnumed ubuntu live

Vaibhav Banait — 2012-05-23T09:54:24

Please see 
geekconnection.org/remastersys/

Regards
Vaibhav Banait, 
Gastroenterologist,
Nagpur.
Ph: +91 98606 43436

Re: Patient > Merge not working?

Karsten Hilbert — 2012-05-23T09:10:15


I am not sure I understand what you are saying here:

GNUmed did NOT ("in spite of") ask for the gm-dbo password
but you still believe you provided the password correctly ?

Karsten

Re: Patient > Merge not working?

Karsten Hilbert — 2012-05-23T09:08:23


Works for me with 1.1.14.

Will check your log.

Karsten

Re: Patient > Merge not working?

Karsten Hilbert — 2012-05-23T08:57:21


It has and it worked.

I will check the current code.

Karsten