Hi Neza, the correct way for OpenMRS to handle this is through the SDMX module. What you should do first is to create the SDMX-HD descriptor files for the latest version of the MoH HMIS report -- i will send you the latest draft. You've seen the sample SDMX descriptor files for the tracnet integration, so for HMIS they should look similar. It shouldn't be your problem to add necessary functionality to DHIS -- when its ready, its ready.
I suppose the only reason not to use SDMX-HD is if DHIS can only accept csv files or something like that. Bob? d On 11/2/11, Guillaine Neza <[email protected]> wrote: > > > Hi Bob, > > Thanks for replying, according to Rowan and me, the purpose for the > module is to export data from OpenMRS into DHIS. I found this > link: http://archive.openmrs.org/index.php?title=Proposed_OpenMRS_DHIS2_Integration&redirect=no#DHIS_exports_an_Indicator_Group_to_OpenMRS > but as you mentioned it is for a long time ago. > > The specification for the project is: > > > 1. to create and be able to generate reports using the reporting framework, > 2. be able to import those in DHIS > 3. have a tool that will allow the transfer for data from Openmrs to the > DHIS system (either the SDMX-HD, DIM or something else) and display those on > a graph > > So Bob, do you think the SDMX-HD can itself generate and allow this > transfer? How will the DHIS system will be able to display automated > imported indicators on it UI? Are there any interoperability between DHIS2 > and SDMX-HD? Please tell me what you think is possible if the purpose here > is to display in DHIS the trend of these indicators over daily, weekly, > monthly, quarterly, and yearly periods. > > The reporting framework has a pre-defined SQL Cohort definition now which is > more generic and flexible for all types of calculations and uses the cohort > indicator to count and display the cohort built than just specific cohort > indicators. I guess it will not be a problem for our indicator calculations > to be parsed and imported in the DHIS. > > I need your suggestion, what you think might be the best way for me to > proceed, and if there is anyone who has worked on something similar, please > share your experience. > > Thanks. > Neza. > > > _________________________________________ > > To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-devel-l" in the body (not > the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
