[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* t
From: |
Busser, James |
Subject: |
Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused |
Date: |
Mon, 31 Oct 2011 19:00:50 +0000 |
On 2011-10-30, at 9:12 PM, Busser, James wrote:
> therefore GNUmed client must be objecting to a change that I made in the data?
Since updating my v15 to v16 I only put in one further patient.
I did, however, also hereafter clean out more sample data (that which I did not
need), and I also installed some data packs, and completed more configuration
options in v16.
For this reason, if it is easily enough identifiable what GNUmed client did not
like about my encounter_type renaming, I would prefer to 'unbork' my v16, if
possible.
If not possible, my loss will be non-catastrophic, however I *will* want to
better understand the problem, and also what I (we) can do to resolve the
handling of the multi-named encounter types in the contexts where they may not
(all) be desired to be seen.
-- Jim
- [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused, Busser, James, 2011/10/30
- Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused, Busser, James, 2011/10/30
- Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused, Busser, James, 2011/10/31
- Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused,
Busser, James <=