Saturday, February 19, 2011

How to contribute templates

We have started a Wiki page to support sharing templates you have created for GNUmed (all kinds of reports, letters, medication lists etc.)

Please send your template via e-mail to We will then have a look, check it in our systems and upload it. You might attach it (see Attach at the bottom) here as well.

Please provide:

filename: e.g. medication_list.tex
description: e.g. a list of past and prestent medications taken by the patient
version: e.g. 0.1 please increase the version when you update the template
date: when was it you created the template
targeted GNUmed version: e.g. 0.8.x
license: GPL , FDL or anything you would like
source: either your name or 'VCS' when it gets incorporated into the main GNUmed repository

We hope to have a lot of templates up for download soon.

Monday, February 14, 2011

GNUmed - job openings

This is not meant to be overly serious. However below is a bit of information what it would take to develop GNUmed from scratch. I encourage everyone to apply for one of these jobs. You will be reimbursed by the respect from your peers and the cosy feeling of having done the right thing.

GNUmed public relations manager

It will be your job to handle all kinds of communication with interested parties such as media, users, developers and either respond yourself or forward the issue to one or more people on the team that might handle the issue more profound. Furthermore it will be your job to research document and shape if neccessary the GNUmed project's visibility in media , search engines and user/developer communities. When new releases are made it part of the job to forward information or press releases to interested parties and parties that might have interest.

GNUmed wiki manager

It will be your job to document important information from all kinds of sources (e.g. design discussions on the mailing-list). You will be responsible for updating content as the need arises (e.g. new GNUmed release). It will be part of the job to work with the public relations manager and the IT-system administrator to keep the Wiki running and secure. This includes monitoring security related announcements. Furthermore it will be your job to initiate and work on improvements to the content and usability of the Wiki with regards to GNUmed users and developers.

GNUmed system admin

It will be your job to keep the infrastructure such as webserver, buildserver running. You will be responsible for security related issues and it is expected of you to initiate, plan and execute inprovements to the infrastructure.

GNUmed release manager

It will be your job to communicate with all parties regarding new releases of the GNUmed software. You will working with the PR manager and the system admin. It is your responsibility to ensure the availability of packages for all major platforms. You will be responsible for the creation and availability of demo media such as Live-CD, VMware images.

GNUmed webinterface developer

It will be your job to work with all other developers to develop a webbased interface for GNUmed. Preferred technologies are python based frameworks and a modern UI framework (e.g. AJAX, HTML5, no Flash). It is exprected that you have very good skills in python, Javascript, webframeworks or are willing to invest significant time into learning those skills in a reasonable timeframe. You will work with the interface designer to develop and deploy an interface that fits a physician's workflow.

GNUmed medical user interface designer

It will be your job to design medical user interfaces (web, fat client) that fits physician's workflow. You are expected to communicate with all developers including the webinterface developer and the core developers. You should have at least basic knowledge in python. It is expected of you that you have good skills or are willing to learn interface design and that you keep in mind industry standards.

GNUmed application developers

It will be your job to research , develop and deploy the GNUmed application. You will be responsible for creating , documenting and maintaining a solid database backend based on proved database technology (e.g. PostgreSQL). You will be writing code to abstract the user interface from the backend. It is essential for senior application developers to have excellent python, wxpython, SQL skills and a track record of active communication with all team members.

GNUmed application documentation manager

It will be your job to work with the developers and testing specialists to establish and keep up to date all programming information, guidelines, manuals. You will be working with users to find out what information is missing and you will be responsible for creating missing content. You will be responsible for setting up

GNUmed application testing specialist

It will be your job to establish a toolchain and testbed for continous testing of all aspects of the GNUmed application. You will be responsible for creating test routines and working with developers to turn test results into a better application.

GNUmed application support specialist

It will be your job to take care of the infrastructure to handle incoming support requests. You should furthermore have experience in triaging support requests and working with application developers and all other team members until an issue is resolved. It is part of the job to gather missing information and interact with the inquiring party until a solution has been found.

GNUmed translator

It will be your job to translate the user interface, the technical and user
manuals and the online content into a number of languages. It is part of the
job to work with users and developers to find the correct translation not only
literally but context-wise and language-specific

Ubunteros - we need you for GNUmed

Providing packages for various distributions is both challenging as well as rewarding. Many users are greatful when GNUmed is packaged for their favorite distribution. The challenge comes from the sheer number of operating systems and Linux distributions.

If you are a happy Ubuntu user and would like to support GNUmed by cooking up Ubuntu packages we would very much appreciate that. The nice thing about Ubuntu packages is that they pretty much stem from Debian packages without any change. And since Andreas Tille has continously provided high quality packages for Debian producing Ubuntu packages can be produced in about 30 minutes.

Please help out by donating 30 minutes each time a new version of GNUmed is released. Fellow Ubuntu users will be greatful. Help doctors install and update easily so they can have the best tools available to treat patients (which one day could be you)

Saturday, February 12, 2011

Is there a need for a single-PC GNUmed ?

Following up on the issue of GNUmed's user interface.

In some countries the health system requires overly complex user interfaces and smart EMR and in some countries it seems to be possible to build you own EMR on OpenOffice and a Spreadsheet program.

I wonder if anyone feels that a special (reduced) version of GNUmed would make sense.

This version would
a) be non-network capable and therefore ship its own local (not systemwide) Postgresql (hidden from the user
b) get rid of server profiles in the login dialog (just one local server)
c) be Windows-only as non-systemwide installations of e.g. Postgresql on Linux and Mac is way too much work
d) have a local (non system wide) installation (hidden from the user) of Latex and pre-configured batch file for printing

I do not have the time to produce and maintain this but anyone wanting to do this can speak up.

It would be a one-time effort of 20-40hours (automate the changes) and another 2 hour effort for every GNUmed update.

Friday, February 11, 2011 fading out was offered free of charge by dyndns. Recently there was a change where this domain name is only offered for a monthly fee.

We are currently replacing all instances which use this domain name (e.g. public database, online database schema documentation) by a new reference.

The new domain name will be

This change will be effective in the Wiki immediately and in the GNUmed client starting with the next release.

Please let us know if you still find non-working references to

Best regards,

Friday, February 04, 2011

GNUmed wants you for translations

Hi all,

GNUmed 0.9 is nearing completion. This obviously will be the last major version before a 1.0 release. Generally 1.0 is seen as a stable release and creates all the media buzz.

Apart from the feature set I would really like to see a good set of translations. So if you have a few minutes to spare please consider translation a string or two into you mother tongue.

Head over to

and help out by giving GNUmed an interface in your language.

Much to my surprise Italian translation is about 85% complete. Thanks for that and thanks to all who have contributed to date.

Best regards,
Sebastian Hilbert

Thursday, February 03, 2011

GNUmed 0.9 call for testing

We are nearing feature completion for GNUmed 0.9. Only minor
enhancements / fixes are planned to be added for this

The current Git master at is fit for testing.
Downloading the "master" branch as a tarball, unpacking, and
running ./ from that should work. Note that
you need a properly upgraded database.

Please test, test more, test again, and report problems.


Here is the preliminary changelog:


NEW: use much enhanced, file-based FreeDiams API
NEW: support primary provider on patients along with configurable fallback
NEW: support array of contextual FKs per inbox message
NEW: support dicomscope as DICOM viewer
NEW: support summary field on health issues and episodes
NEW: translate database strings from within client and contribute translations
NEW: simplistic coding systems browser
NEW: cloning of workplaces
NEW: hook "post_person_creation"
NEW: placeholder: "emr_journal::soap//%(narrative)s//255//tex::9999"
NEW: LaTeX template: chronological EMR journal
NEW: full manual management of substances/drug components/branded drugs
NEW: implement our own date picker
NEW: implement searchable tags with image/name/comment on patients

IMPROVED: link test results directly to requests for them
IMPROVED: much better EMR tree root node tooltip
IMPROVED: improved adding of vaccinations
IMPROVED: now listing episodes/health issues at time of creation in EMR journal
IMPROVED: Boesner score now has internationally usable name: "Marburg CHD score"
IMPROVED: much better integration of visual progress notes
IMPROVED: procedures now support a duration and an "ongoing" state
IMPROVED: adjust to modified API of MMI/Gelbe Liste
IMPROVED: master data management interface
IMPROVED: fix "Current Substance Intake" edit area usability glitches
(schedule, substance, preparation)
IMPROVED: much saner "deletion of substance intake entry" workflow
IMPROVED: logically cleaner substance intake handling
IMPROVED: find gm-print_doc in git tree, too
IMPROVED: relax URL sanity checks since Web 2.0 confuses all but the most
sophisticated browsers
IMPROVED: default server profile names in gnumed.conf example
IMPROVED: alpha-sort list of master data lists as per mailing list
IMPROVED: external patient sources now generically import external IDs/comm
IMPROVED: fix detection of existing patient when loading from external source
IMPROVED: workplace plugin configuration using item picker
IMPROVED: in phrasewheel support dynamic part of tooltip based on selected item
IMPROVED: location PRW in procedure EA: re-use hospitals from hospital stays
IMPROVED: support arriba 2.2.2 and its new file-based API
IMPROVED: substance intake grid: display unapproved by default
IMPROVED: default temporary directory now /tmp/gnumed/gm-<unique ID>/ per
GNUmed instance
IMPROVED: menu structure creation such that accelerator keys work more reliably
GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346