Hopefully HISP India will have taken this even further after spending much time with iHRIS people this and the coming week.
Ola
Yes, we have been discussion with them and are planning out a pilot strategy where we will be able to implement iHRIS as well as integrate these two applications with live data
With or without SDMX_HD. We will also try to integrate with Bob’s XML transforms to DXF and ideally have file-based exchange as the first step and then doing it through SOAP, protobuf or MoM like xmlBlaster, activeMQ etc. Once we really decide on the pilot states and start the work of integration, we will post and discuss with benchmarks on the mailing list
···
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme
My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE
2009/11/20 Ola Hodne Titlestad olatitle@gmail.com
Hopefully HISP India will have taken this even further after spending much time with iHRIS people this and the coming week.
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
Thanks for the update Saptarshi, that’s great news.
I also think a first step can be done easily without fully supporting the SDMX-HD standard (which is not finalised either).
Bob and Luke (from iHRIS) sat together a few weeks ago and transformed an iHRIS reports into DXF, so that seems like the way to go yes. I am sure you are in contact with Bob on the details of this.
Apart from the more technical discussion on the interoperability between these two systems it would also be good to share ideas on what kind of data elements DHIS can pull from iHRIS (and potentially also what iHRIS can pull from DHIS). Ideally we could streamline some of these data elements (incl. dimensions) and reuse across countries.
Look forward to more updates from India on this. Again, thanks for sharing these news.
Ola Hodne Titlestad |Technical Officer|
Health Metrics Network (HMN) | World Health Organization
Avenue Appia 20 |1211 Geneva 27, Switzerland | Email: titlestado@who.int|Tel: +41 788216897
Website: www.healthmetricsnetwork.org
Better Information. Better Decisions. Better Health.
···
2009/11/20 Saptarshi Purkayastha sunbiz@gmail.com
Yes, we have been discussion with them and are planning out a pilot strategy where we will be able to implement iHRIS as well as integrate these two applications with live data
With or without SDMX_HD. We will also try to integrate with Bob’s XML transforms to DXF and ideally have file-based exchange as the first step and then doing it through SOAP, protobuf or MoM like xmlBlaster, activeMQ etc. Once we really decide on the pilot states and start the work of integration, we will post and discuss with benchmarks on the mailing list
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems ProgrammeMy Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE
2009/11/20 Ola Hodne Titlestad olatitle@gmail.com
Hopefully HISP India will have taken this even further after spending much time with iHRIS people this and the coming week.
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
Hi,
Yes, we have been discussion with them and are planning out a pilot strategy where we will be able to implement iHRIS as well as integrate these two applications with live data
great that things are happening on this.
With or without SDMX_HD. We will also try to integrate with Bob's XML transforms to DXF and ideally have file-based exchange as the first step and then doing it through SOAP, protobuf or MoM like xmlBlaster, activeMQ etc. Once we really decide on the pilot states and start the work of integration, we will post and discuss with benchmarks on the mailing list
That is a pretty diverse and heavy set of technologies. Can you tell a bit more about the requirements and architecture that might require the use of the WS-* stack, binary, compiled formats or a fullblown messaging infrastructure. What are the potential reasons for not just using the existing web infrastructure both applications are deployed to?
Jo
···
Den 20. nov. 2009 kl. 09.44 skrev Saptarshi Purkayastha:
iHRIS uses PHP, runs on Apache or another web server
DHIS2/OpenMRS, runs on Java Servlet Container
They could be on the same machine, across VMs, different machines… connected/disconnected, offices etc.
···
Regards,
Saptarshi PURKAYASTHA
Director R & D, HISP India
Health Information Systems Programme
My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE
2009/11/20 Jo Størset storset@gmail.com
Hi,
Den 20. nov. 2009 kl. 09.44 skrev Saptarshi Purkayastha:
Yes, we have been discussion with them and are planning out a pilot strategy where we will be able to implement iHRIS as well as integrate these two applications with live data
great that things are happening on this.
With or without SDMX_HD. We will also try to integrate with Bob’s XML transforms to DXF and ideally have file-based exchange as the first step and then doing it through SOAP, protobuf or MoM like xmlBlaster, activeMQ etc. Once we really decide on the pilot states and start the work of integration, we will post and discuss with benchmarks on the mailing list
That is a pretty diverse and heavy set of technologies. Can you tell a bit more about the requirements and architecture that might require the use of the WS-* stack, binary, compiled formats or a fullblown messaging infrastructure. What are the potential reasons for not just using the existing web infrastructure both applications are deployed to?
Jo
iHRIS uses PHP, runs on Apache or another web server
DHIS2/OpenMRS, runs on Java Servlet Container
They could be on the same machine, across VMs, different machines… connected/disconnected, offices etc.
Of course, and this illustrates my question perfectly.
···
Den 20. nov. 2009 kl. 10.36 skrev Saptarshi Purkayastha:
2009/11/20 Jo Størset storset@gmail.com
That is a pretty diverse and heavy set of technologies. Can you tell a bit more about the requirements and architecture that might require the use of the WS-* stack, binary, compiled formats or a fullblown messaging infrastructure. What are the potential reasons for not just using the existing web infrastructure both applications are deployed to?
Given the diverse contexts, introducing technological complexity through technology like SOAP, MoM or the like, introduces complexity in addition to the one thing that is already linking the two applications: the web.
It might be that we can´t rely on the two applications being networked (disconnected, above), but then it wouldn´t exactly be wise to introduce “SOAP, protobuf or MoM like xmlBlaster, activeMQ etc.”.
Given that we have some sort of network between the two applications, we know, since they are both web based, that they can talk over http without adding any fancy technology (think REST or just plain old “xml over http”).
So, since both applications are both deployed to the web, and thereby can talk to each other over this existing infrastructure, what are the requirements or architectural constraints that would make adding the technological complexity wise?
Jo