OpenMRS integration

Hi all,

after some discussions with Jørn we have decided that Bob will be
responsible for the OpenMRS - DHIS 2 integration process. This means
that he will come up with a design and plan of action, and suggest who
will be developing on the various components.

I admit that this could have been communicated better and earlier. I
will from now on take more responsibility on coordination of tasks and
communication of what we agree on.

More info from Bob later.

cheers

Lars

Thanks Lars. I will take responsibility for putting together and implementing a plan of action for this. This will have to include absorbing the learning from the various integration efforts which have happened - there is the work Abyot has done, there is work Phumzile and others have done on the OpenMRS side, there is an existing (untouched for two years) DHIS “connector” module for openmrs and there is the most recent effort from Murod. Alongside there have been developments in the availability of xml interchange standards which can impact positively or negatively on the work.

Also there are opportunities to interoperate with other software (such as iHRIS HR package and no doubt others in the future) so it is important to not treat each as a new design program, but rather expose and document a standard process for getting data in and out of DHIS2.

The first step will be to identify the right forum for communication with the relevant people from across projects. I’m interested in people’s thoughts on this.

Regards for now
Bob

···

2009/8/5 Lars Helge Øverland larshelge@gmail.com

Hi all,

after some discussions with Jørn we have decided that Bob will be

responsible for the OpenMRS - DHIS 2 integration process. This means

that he will come up with a design and plan of action, and suggest who

will be developing on the various components.

I admit that this could have been communicated better and earlier. I

will from now on take more responsibility on coordination of tasks and

communication of what we agree on.

More info from Bob later.

cheers

Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Hi,

First of all, glad to see Bob taking this forward, it really needs a firm push to get beyond the typical meeting discussions we’ve had so many of over the last 1-2 years.

When it comes to forum for cross-project collaboration I would like to recommend the recently launched TGHIN.org platform. This would fit well with the intentions behind that site. TGHIN already has a large user community from different projects and country implementations, which could benefit discussions and provide a broader view on things. TGHIN is built on Drupal and we can influence functionality there if more modules are needed. For now there is a forum site where we can post and log discussions. Mail notification is also in place. A chat module is soon released which can help communication as well.

If we need a new mailing list we can of course set up another google group or similar.

I already mentioned in Goa that I will invest some of my time time on this collaboration and similar collaborations among FOSS communities involved with HIS. I will help to document ongoing activities among the major HIS FOSS projects such as HISP, OpenMRS and Capacity project (iHRIS), and help to identify possible collaboration projects.

I think the Cape Town meeting will be an important start and provide the necessary push for DHIS and OpenMRS collaboration.

I’ll be more active on email when I get back from leave in about 10 days.

Ola

···

2009/8/5 Bob Jolliffe bobjolliffe@gmail.com

Thanks Lars. I will take responsibility for putting together and implementing a plan of action for this. This will have to include absorbing the learning from the various integration efforts which have happened - there is the work Abyot has done, there is work Phumzile and others have done on the OpenMRS side, there is an existing (untouched for two years) DHIS “connector” module for openmrs and there is the most recent effort from Murod. Alongside there have been developments in the availability of xml interchange standards which can impact positively or negatively on the work.

Also there are opportunities to interoperate with other software (such as iHRIS HR package and no doubt others in the future) so it is important to not treat each as a new design program, but rather expose and document a standard process for getting data in and out of DHIS2.

The first step will be to identify the right forum for communication with the relevant people from across projects. I’m interested in people’s thoughts on this.


Great. I will propose a strategy within next day or two to dhis group. Assuming we have consensus we can move forward with this in our interaction with openmrs, baobab, ihris and others.

Regards
Bob

···

2009/8/6 Ola Hodne Titlestad olatitle@gmail.com

2009/8/5 Bob Jolliffe bobjolliffe@gmail.com

Thanks Lars. I will take responsibility for putting together and implementing a plan of action for this. This will have to include absorbing the learning from the various integration efforts which have happened - there is the work Abyot has done, there is work Phumzile and others have done on the OpenMRS side, there is an existing (untouched for two years) DHIS “connector” module for openmrs and there is the most recent effort from Murod. Alongside there have been developments in the availability of xml interchange standards which can impact positively or negatively on the work.

Also there are opportunities to interoperate with other software (such as iHRIS HR package and no doubt others in the future) so it is important to not treat each as a new design program, but rather expose and document a standard process for getting data in and out of DHIS2.

The first step will be to identify the right forum for communication with the relevant people from across projects. I’m interested in people’s thoughts on this.

Hi,

First of all, glad to see Bob taking this forward, it really needs a firm push to get beyond the typical meeting discussions we’ve had so many of over the last 1-2 years.

When it comes to forum for cross-project collaboration I would like to recommend the recently launched TGHIN.org platform. This would fit well with the intentions behind that site. TGHIN already has a large user community from different projects and country implementations, which could benefit discussions and provide a broader view on things. TGHIN is built on Drupal and we can influence functionality there if more modules are needed. For now there is a forum site where we can post and log discussions. Mail notification is also in place. A chat module is soon released which can help communication as well.

If we need a new mailing list we can of course set up another google group or similar.

I already mentioned in Goa that I will invest some of my time time on this collaboration and similar collaborations among FOSS communities involved with HIS. I will help to document ongoing activities among the major HIS FOSS projects such as HISP, OpenMRS and Capacity project (iHRIS), and help to identify possible collaboration projects.

I think the Cape Town meeting will be an important start and provide the necessary push for DHIS and OpenMRS collaboration.

I’ll be more active on email when I get back from leave in about 10 days.

Ola

Thanks Lars. I will take responsibility for putting together and implementing a plan of action for this. This will have to include absorbing the learning from the various integration efforts which have happened - there is the work Abyot has done, there is work Phumzile and others have done on the OpenMRS side, there is an existing (untouched for two years) DHIS “connector” module for openmrs and there is the most recent effort from Murod. Alongside there have been developments in the availability of xml interchange standards which can impact positively or negatively on the work.

Also there are opportunities to interoperate with other software (such as iHRIS HR package and no doubt others in the future) so it is important to not treat each as a new design program, but rather expose and document a standard process for getting data in and out of DHIS2.

The first step will be to identify the right forum for communication with the relevant people from across projects. I’m interested in people’s thoughts on this.

Hi,

First of all, glad to see Bob taking this forward, it really needs a firm push to get beyond the typical meeting discussions we’ve had so many of over the last 1-2 years.

When it comes to forum for cross-project collaboration I would like to recommend the recently launched TGHIN.org platform. This would fit well with the intentions behind that site. TGHIN already has a large user community from different projects and country implementations, which could benefit discussions and provide a broader view on things. TGHIN is built on Drupal and we can influence functionality there if more modules are needed. For now there is a forum site where we can post and log discussions. Mail notification is also in place. A chat module is soon released which can help communication as well.

I agree with this, and soon this will be supplemented by a (doku)wiki at www.openhealthconsortium.org

If we need a new mailing list we can of course set up another google group or similar.

Again, there already is a google group which can be usefully employed:

http://groups.google.com/group/openhealth

Knut

···

On Thu, Aug 6, 2009 at 5:24 PM, Ola Hodne Titlestad olatitle@gmail.com wrote:

2009/8/5 Bob Jolliffe bobjolliffe@gmail.com

I already mentioned in Goa that I will invest some of my time time on this collaboration and similar collaborations among FOSS communities involved with HIS. I will help to document ongoing activities among the major HIS FOSS projects such as HISP, OpenMRS and Capacity project (iHRIS), and help to identify possible collaboration projects.

I think the Cape Town meeting will be an important start and provide the necessary push for DHIS and OpenMRS collaboration.

I’ll be more active on email when I get back from leave in about 10 days.

Ola


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp


Cheers,
Knut Staring

Hi Yusuph

Thanks for this update. This is interesting to me as I think it is my first sighting of another implementation of dxf format in the wild! That’s important to know if we start tweaking with the format.

I haven’t looked at care2x for a long time. Last I looked it was based on PHP (v4). There was still some angst about adopting the right framework for move to PHP5. I guess that is all resolved now. Or maybe they decided to stary put with php4. Is your php implementation of dxf available anywhere? I’d like to take a look.

On the question of organisation hierarchy, I’ve had this discussion with a few people and maybe your experience will confirm. It is only DHIS which really needs to have a knowledge of the tree. For a hospital or facility running care2x or openmrs it presumably doesn’t matter. What matters is that it has an identifier which is recognizable by DHIS. Am I right in thinking this?

I’m interested in your translation of icd10 codes to dataelements. Am I right in thinking that for each named ic10 code you have (potentially) a dhis dataelement with the same name? Or you have a mapping between named icd10 codes and named dhis data elements? I’m wondering if there might be something general we can extract from this, like a standardized ICD10 dataelement mapping for other contexts. Possibly not. But what actual data have you imported? I know that care2x has a lot of tables ranging from canteen to patient record. I guess if you are focussed on ICD10 it is derived from patient record. So you have aggregated monthly, weekly or what have you within care2x and then exported to DXF?

Most importantly, why have you done this? I am looking for proven use cases where dhis is linked to another system and there is a clear and tangible beneficial outcome.

Sorry for all the questions.

Regards

Bob

···

2009/8/6 Yusuph Kassim yusuph28@hotmail.com

Hi,

Just to high light the work done in integrating the DHIS and care2x which also is the same way used in integrating with the other afya pro system is to produce an xml file with dfx format for that particular system, the idea is that DHIS mainly finds the dataelement, the organization unit, the period and the values (which references the later) as the main fields, the good thing about it, if you have the names of the organization unit and the name of dataelements and the date format exactly as in DHIS then the import is easy, so what we actully did, is to map the names of the ICD10 in care2x and the names of data element in DHIS and everything was automatic.

hope this highlights what we did.

NB. the organizationunitrelationship (the parent and the child mainly depends if you are importing data for the first time, but if you have all the names of facility in your system, the hierachy will sort itself out)

cheers

Date: Thu, 6 Aug 2009 10:06:39 +0200
Subject: Re: OpenMRS integration
From: jornbraa@gmail.com

To: anthony_muyepa@yahoo.co.uk; muyepaa@gmail.com; bobjolliffe@gmail.com; dhis2-devs@lists.launchpad.net; juma.lungo@zalongwa.com; johnlewis.hisp@gmail.com; larshelge@gmail.com; sundeep.sahay@yahoo.com; yusuphk@gmail.com; yusuph28@hotmail.com

Bob and all,
think broader than openmrs. In tanzania we have also care2x and
another hospital sw, which will also come to malawi, where baobab,
which uses openmrs data structure, is a priority.

Bob, include tz and mw in your mandate for dhis integration. We want
generic approach to mapping and etl w dhis as destination. Note that
baobab should be thight as openmrs as they are large national project

w whom we working. Openmrs is also in mw, so same approach for both.

Discuss w yusuph how they do care2x in tz.

Jorn, on mobile

On 8/5/09, Bob Jolliffe bobjolliffe@gmail.com wrote:

Thanks Lars. I will take responsibility for putting together and
implementing a plan of action for this. This will have to include
absorbing
the learning from the various integration efforts which have happened -

there is the work Abyot has done, there is work Phumzile and others have
done on the OpenMRS side, there is an existing (untouched for two years)
DHIS “connector” module for openmrs and there is the most recent effort

from
Murod. Alongside there have been developments in the availability of xml
interchange standards which can impact positively or negatively on the
work.

Also there are opportunities to interoperate with other software (such as
iHRIS HR package and no doubt others in the future) so it is important to
not treat each as a new design program, but rather expose and document a

standard process for getting data in and out of DHIS2.

The first step will be to identify the right forum for communication with
the relevant people from across projects. I’m interested in people’s

thoughts on this.

Regards for now
Bob

2009/8/5 Lars Helge Øverland larshelge@gmail.com

Hi all,

after some discussions with Jørn we have decided that Bob will be
responsible for the OpenMRS - DHIS 2 integration process. This means

that he will come up with a design and plan of action, and suggest who
will be developing on the various components.

I admit that this could have been communicated better and earlier. I

will from now on take more responsibility on coordination of tasks and
communication of what we agree on.

More info from Bob later.

cheers

Lars


Mailing list:
https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>

Post to : dhis2-devs@lists.launchpad.net
Unsubscribe :
https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>

More help : https://help.launchpad.net/ListHelp


Share your memories online with anyone you want anyone you want.