Hi,
Someone have a look at
http://susestudio.com/a/ZnK1SC/dcm4che-jboss-suse
and add this to the opensuse-medical image.
I would like to see
1.) gnumed-client, gnumed-server
2.) freediams
3.) ginkgo-cadx (even if not packaged)
4.) dcm4che fully configure
5.) firefox with pubmed bookmarks and search, zotero plugin
Would make a nice cardiology/radiology distribution
Regards,
Sebastian Hilbert
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Hi,
I have recently tried to boostrap on openSUSE again. This failed with the
following errors.
linux: # gm-bootstrap_server
===========================================================
Bootstrapping latest GNUmed database.
This will set up a GNUmed database of version v16
with the name "gnumed_v16".
Creating module import symlink ...
real dir: /usr/lib/client
link: /usr/lib/Gnumed
Adjusting PYTHONPATH ...
Traceback (most recent call last):
File "./bootstrap_gm_db_system.py", line 71, in <module>
from Gnumed.pycommon import gmLog2
File "/usr/lib/python2.7/site-packages/Gnumed/pycommon/gmLog2.py", line 270,
in <module>
__setup_logging()
File "/usr/lib/python2.7/site-packages/Gnumed/pycommon/gmLog2.py", line 219,
in __setup_logging
_logfile = codecs.open(filename = _logfile_name, mode = 'wb', encoding =
'utf8', errors = 'replace')
File "/usr/lib/python2.7/codecs.py", line 881, in open
file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 2] No such file or directory:
'/var/log/gnumed/server/bootstrap-latest.log'
Bootstrapping "gnumed_v16" did not finish successfully. Aborting.
linux:/usr/lib # gm-bootstrap_server
===========================================================
Bootstrapping latest GNUmed database.
------- This did not create a log file and it created a strange symlink
------- called 'GNUmed' pointing to '/usr/lib/client'
------- running it again brings up the following error
This will set up a GNUmed database of version v16
with the name "gnumed_v16".
Creating module import symlink ...
real dir: /usr/lib/client
link: /usr/lib/Gnumed
Traceback (most recent call last):
File "./bootstrap_gm_db_system.py", line 63, in <module>
os.symlink(real_dir, link_name)
OSError: [Errno 17] File exists
Bootstrapping "gnumed_v16" did not finish successfully. Aborting.
------- I cannot see that a log file was created
------- Any help is appreciated
Sebastian Hilbert
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Hi,
Someone from India contacted me because he could not download the GNUmed Live-
CD form SUSE studio.
Would anyone be willing to download it, verify that it works so that I can put
it in a torrent ?
BTW. I am preparing 1.1.4 in SUSE studio right now.
Regards,
Sebastian Hilbert
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Le 25 novembre 2011 17:32, Karsten Hilbert <Karsten.Hilbert(a)gmx.net> a écrit :
> On Fri, Nov 25, 2011 at 05:05:31PM +0100, Eric Maeker wrote:
>
>> > While I agree the logical and lofty goal would be to create
>> > a "Linux Medical Taskforce" I also know that doing so will
>> > not achieve anything tangible.
>>
>> Not sure, Debian Med is getting bigger and bigger, MedFloss too.
>> May be we can go one step further !
>> There are volonteers but they scattered on multiple projects while a
>> more unifying project can arise.
>
> What would be the precise, medically relevant goal of this project ?
>
> Without one it'd be useless.
The very basic reflexion can be the following.
This kind of project involves a too heterogeneous population that we
need to precised in more details. I propose two very simple dichotomy:
* The first dichotomy:
- the end user
- the developper
* In user/developper we have another dichotomy :
- working in a (or for a) medical area
- not working in a (or for a) medical area
This lead to four profiles that have different needs and wishes.
--
Eric Maeker, MD (FR)
http://www.freemedforms.com/http://www.ericmaeker.fr/
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Le 25 novembre 2011 13:21, Karsten Hilbert <Karsten.Hilbert(a)gmx.net> a écrit :
> On Fri, Nov 25, 2011 at 12:08:38PM +0100, Eric Maeker wrote:
>
>> I've added to this post the Debian Med, OpenSuse Medical, Neuro Debian
>> teams, MedFloss manager and the EFMI LIFOSS WG.
>> Also created a new thread.
>
>> >> Currently we are duplicating work in Debian-med, Fedora-medical and
>> >> openSUSE- medical. What a waste of human ressources.
>
> While I agree the logical and lofty goal would be to create
> a "Linux Medical Taskforce" I also know that doing so will
> not achieve anything tangible.
Not sure, Debian Med is getting bigger and bigger, MedFloss too.
May be we can go one step further !
There are volonteers but they scattered on multiple projects while a
more unifying project can arise.
> I think your FreeDiams prescriber is a perfect example.
One little piece of the edifice only...
--
Eric Maeker, MD (FR)
http://www.freemedforms.com/http://www.ericmaeker.fr/
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Hi all,
I've added to this post the Debian Med, OpenSuse Medical, Neuro Debian
teams, MedFloss manager and the EFMI LIFOSS WG.
Also created a new thread.
Le 25 novembre 2011 10:24, Simon Slater <pyevet(a)iinet.net.au> a écrit :
> On Fri, 25 Nov 2011 18:55:15 Sebastian Hilbert wrote:
>> On Friday, November 25, 2011 02:05:11 AM Simon Slater wrote:
>> > On Wed, 23 Nov 2011 07:02:42 susmit shannigrahi wrote:
>> But if you really want to make a difference for healthcare put effort into
>> getting people from different distributions together to share their work.
>> Currently we are duplicating work in Debian-med, Fedora-medical and
>> openSUSE- medical. What a waste of human ressources.
I fully agree to this. We should work together. There are lots of
projects but no (visible) joined effort.
Packaging can be quite different distro to distro but the main work
(package selection, upstream contact and management, configuration
helpers, license analysis...) can be shared.
We can share our competence whatever are our difference (of Linux
distro and project).
>>
> Any common forums existing at the moment?
Not yet already.
As a french MD, open source developper and Linux user I'd like to help
on any work that can lead to a global "Linux Medical Team" effort
(including nurses, dentists, pharmacists...).
Any comment ?
--
Eric Maeker, MD (FR)
http://www.freemedforms.com/http://www.ericmaeker.fr/
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Hello team,
My name is Stathis, I'm postgraduate Veterinary Medicine Student. I was
given the responsibility to coordinate the team.
In openSUSE community I joined ambassador program and I help the
marketing team. I'm also openSUSE member.
Some of those who don't know me, I'm one of the 2 who started organizing
the Greek openSUSE community.
Well this is a short openSUSE resume of me.
All this time, I didn't write my thoughts because we had the 12.1
release. Now it's all done so we can focus on our goal.
I wrote down some things that must be done (in my opinion). Not
particularly in that order. The second step will be to set timetable.
1. Try to separate the project into 2 different sub-projects. The first
will be a livecd with an Electronic Medial Record program (such as
openEMR [1]) that will focus on doctors-clinics environment. This livecd
will include also some software that we'll find out after a
survery-research we'll do (I started a Google Code In task that we'll
continue[2]).
The second sub-project will be to create a livecd that will focus on
bio-informatics. That means we'll search all possible program that can
be found, obs it to medical repository.
2. The 2 above livecds will be created using KIWI. Also the above
livecds need base system stability. Need something like Tubleweed or
Ubuntu's LTS. So we create them once and then only update the medical
software from the repository. I don't want us to create very fast a
livecd based on 12.1 but I want us to create a livecd just like
described above. We must make something the right way and keep it forever.
3. The livecds must be modified according to the needs of doctor. It's
good if we add cool artwork, we'll find the right desktop environment
(from the survey-research we'll do) etc.
4. Make our Portal wiki, real Portal. I mean every program we'll add to
our repository, we'll create a TUTORIAL (how to install and maybe small
how to use it, pictures, video, where to find help, mailing list, IRC,
forum).
5. During creating the above sub-projects, we'll plan to meet on IRC
once or twice every month to see what we've done from last meeting and
set new goals for the next meeting. This way, we'll keep our timetable
running.
6. Use support channels more often. Mailing list, IRC channel and maybe
a forum section.
7. After (or during) the process, we'll use social media (connect,
twitter, identica, facebook etc). We'll use our marketing channels to
make noise to the world.
Of course all above cannot be done by one person. As I told you above,
I'm Veterinary Medicine Student. I don't have a clue how to KIWI or to
obs. So we need people to help us.
When we'll be enough people, the best way to proceed is to work inside
teams of 2-3 people. Some of the teams will be
1. distro maintainers: they'll be responsible to keep the distro working
2. packagers or obs-ers ;-)
3. software scouters and testers: strange name, they'll find the
packages, try to install them, use them and then announce to the list.
All those programs that we MUST add to our repository are already
listed, so we can start right away.
4. documentation: they'll write the documentation to the Portal. I guess
they'll be the same who will maintain our wiki.
5. artwork: if we cannot find someone, then we can ask the openSUSE
artwork team.
6. marketing: will promote the project (social media etc)
The final step for our product is to be tested with real equipment. When
we'll be at this stage, we'll search for equipment (personally I have
some channels where I can test them).
Well, saying all the above, I want you:
1. To add something that you think it'll help us grow.
2. To add your name if you want to help and what subject can you help.
You better reply to opensuse-medical(a)opensuse.org (it's our meeting place).
Contribute to medical project and have a lot of fun!!!
Thanks for your help.
Stathis
[1] http://www.oemr.org/
[2]
http://en.opensuse.org/openSUSE:Research_tasks#Research_about_community_and…
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Hello team,
My name is Stathis, I'm postgraduate Veterinary Medicine Student. I was
given the responsibility to coordinate the team.
In openSUSE community I joined ambassador program and I help the
marketing team. I'm also openSUSE member.
Some of those who don't know me, I'm one of the 2 who started organizing
the Greek openSUSE community.
Well this is a short openSUSE resume of me.
All this time, I didn't write my thoughts because we had the 12.1
release. Now it's all done so we can focus on our goal.
I wrote down some things that must be done (in my opinion). Not
particularly in that order. The second step will be to set timetable.
1. Try to separate the project into 2 different sub-projects. The first
will be a livecd with an Electronic Medial Record program (such as
openEMR [1]) that will focus on doctors-clinics environment. This livecd
will include also some software that we'll find out after a
survery-research we'll do (I started a Google Code In task that we'll
continue[2]).
The second sub-project will be to create a livecd that will focus on
bio-informatics. That means we'll search all possible program that can
be found, obs it to medical repository.
2. The 2 above livecds will be created using KIWI. Also the above
livecds need base system stability. Need something like Tubleweed or
Ubuntu's LTS. So we create them once and then only update the medical
software from the repository. I don't want us to create very fast a
livecd based on 12.1 but I want us to create a livecd just like
described above. We must make something the right way and keep it forever.
3. The livecds must be modified according to the needs of doctor. It's
good if we add cool artwork, we'll find the right desktop environment
(from the survey-research we'll do) etc.
4. Make our Portal wiki, real Portal. I mean every program we'll add to
our repository, we'll create a TUTORIAL (how to install and maybe small
how to use it, pictures, video, where to find help, mailing list, IRC,
forum).
5. During creating the above sub-projects, we'll plan to meet on IRC
once or twice every month to see what we've done from last meeting and
set new goals for the next meeting. This way, we'll keep our timetable
running.
6. Use support channels more often. Mailing list, IRC channel and maybe
a forum section.
7. After (or during) the process, we'll use social media (connect,
twitter, identica, facebook etc). We'll use our marketing channels to
make noise to the world.
Of course all above cannot be done by one person. As I told you above,
I'm Veterinary Medicine Student. I don't have a clue how to KIWI or to
obs. So we need people to help us.
When we'll be enough people, the best way to proceed is to work inside
teams of 2-3 people. Some of the teams will be
1. distro maintainers: they'll be responsible to keep the distro working
2. packagers or obs-ers ;-)
3. software scouters and testers: strange name, they'll find the
packages, try to install them, use them and then announce to the list.
All those programs that we MUST add to our repository are already
listed, so we can start right away.
4. documentation: they'll write the documentation to the Portal. I guess
they'll be the same who will maintain our wiki.
5. artwork: if we cannot find someone, then we can ask the openSUSE
artwork team.
6. marketing: will promote the project (social media etc)
The final step for our product is to be tested with real equipment. When
we'll be at this stage, we'll search for equipment (personally I have
some channels where I can test them).
Well, saying all the above, I want you:
1. To add something that you think it'll help us grow.
2. To add your name if you want to help and what subject can you help.
You better reply to opensuse-medical(a)opensuse.org (it's our meeting place).
Contribute to medical project and have a lot of fun!!!
Thanks for your help.
Stathis
[1] http://www.oemr.org/
[2]
http://en.opensuse.org/openSUSE:Research_tasks#Research_about_community_and…
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
Hi all,
Thanks to Boris Manojlovic (from #opensuse-buildservice) we updated the rpm file for FreeMedForms to 0.6.0.
I think package can be available in few days in the OpenSuse Medical.
Thank you Boris
-----
Eric Maeker, MD (Fr)
http://www.freemedforms.comhttp://www.ericmaeker.fr
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org
PING:
On Sunday, October 30, 2011 09:56:00 PM Stathis Iosifidis (aka
diamond_gr) wrote: Hi,
>> Good luck with your studies Athanasios-Ilias. It's pretty hard to study
>> and do other things as well. I'm at the end of my studies and I have
>> more free time to help the project.
>> I have couple of fresh ideas that I can combine them with marketing and
>> PR skills.
>>
>> If it's not problem, I would like to take over but I'll ask for help
>> from all of you. My major is Vet Medicine and I don't have technical
>> skills, programming etc.
>>
--
To unsubscribe, e-mail: opensuse-medical+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-medical+owner(a)opensuse.org