dhis2-devs team mailing list archive

[Knut Staring <knutst@xxxxxxxxx>]

Use of messaging (Mirth) for OpenMRS - DHIS integration:

---------- Forwarded message ----------
From: Carl Fourie <carlsbox@xxxxxxxxx>
Date: Tue, Apr 14, 2009 at 3:10 PM
Subject: Re: [OPENMRS-DEV] Messaging Module proposal
To: openmrs-devel-l@xxxxxxxxxxxxxxxxxx


 Hi Ryan,

Just to echo my support on this too especially in the light of our upcoming
TRACNet development and the DHIS integration. A generically styled solution
which is configurable for different systems is a great step forward and will
definitely open up the possibilities of other systems exchanging data with
OpenMRS.

-Carl

Brian McKown wrote:

Hi, Ryan:

I think this could be very useful for the AMPATH implementation in Kenya.
We have several peripheral systems needing to receive and send messages to
OpenMRS (a.k.a. AMRS for AMPATH).  These include pharmacy system,
nutritional information system, a diabetes program database, a financial
program in the works.  We are also connected to a pcstech lab system - but
that uses the REST module for patient lookup. For sending HL7 to AMRS we are
currently only connected by folder sharing on a LAN instead of TCP, which
may have been better.

I think the module would be very useful. Thanks.

-Brian

Ryan wrote:

Hi,

I would like to propose an idea for a module that I would like to develop.
We have been making use or Mirth
<http://www.mirthproject.org><http://www.mirthproject.org>quite a bit
for doing some integration tasks with various external systems. My idea is
to then create a module that allows for easy sending and receiving of basic
TCP messages.

The module could allow for the creation of "channels". These channels would
contain all the connection information for that channel and external modules

could register to use these channels to send and receive messages.

The main focus would be on implementing a basic communication facility to
allow messages to be sent and received from Mirth however, this could work
for any communication where TCP message are required.

Would anyone else find this useful? Any thoughts or comments?

Regards,
Ryan

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
LISTSERV@xxxxxxxxxxxxxxxxxx with "SIGNOFF openmrs-devel-l" in the  body (not
the subject) of your e-mail.

[mailto:LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-devel-l<LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-devel-l>]



_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
LISTSERV@xxxxxxxxxxxxxxxxxx with "SIGNOFF openmrs-devel-l" in the  body (not
the subject) of your e-mail.

[mailto:LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-devel-l<LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-devel-l>]


 ------------------------------
Click here to unsubscribe<LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-devel-l>from
OpenMRS Developers' mailing list



-- 
Cheers,
Knut Staring