0-3

1.Investigate(formats of sdmx-hd/dhis2)

2.Familiarize(Reporting module and messaging module)

UI Mockups,Finalized Project schedule,Exact workflow of how the integration between

the reporting module and messaging module can be achieved.

4-6

User Interface

The user interface on the reporting module-selection of the format and the final display of the message.

7-9

SDMX-HD/DHIS2 integration

The code of the renderer.(java classes providing the functionality of transforming the data)

10-11

Buffer time for Cleaning and Testing

The code must be reviewed and test cases must be provided.

12

Documentation and tutorials

Written documentation on project with project details and technical details and how to use it, Video tutorial on how to use it.

1

May 9,2013

Is my flow of understanding correct?(on taking data from reports and converting it into sdmx xml and displaying it to the user)

I was thinking that we would have a report renderer; from the user's point of view, it would be just like running a report and choosing the output type as SDMX/DHIS2+destination; the administrator would already have set up any transmission parameters on an administration page (see the messaging module).  The period indicator report might be a good type of report, but maybe not the only type; it's probably a good place to start, but keep type-specific code isolated maybe in a helper class which implements an interface/extends a base class with a generic representing the type.

May 10,2013

Roger Friedman

2

May 9,2013

Is this only for taking aggregate data as these are finally viewed as indicators? 

Probably we will deliver numerators and denominators separately, but some indicators will be counts only (not a ratio).

May 10,2013

Roger Friedman

3

May 9,2013

In step 1 do we provide the option to (select the aggregate data for multiple questions or single question) per conversion.

Per 1, I would prefer to keep 1 report definition = 1 message, but if it is not easy to duplicate parts of report definitions, then it might be necessary to let users select those outputs to be packaged into the message.

May 10,2013

Roger Friedman

4

May 9,2013

 After the conversion the xml must be displayed to the user?(y/n)

No, but it might be nice to have an xslt to allow them to see it in a simple format.

May 10,2013

Roger Friedman

5

May 9,2013

The xslt structure would remain constant or this must change on user selection?(this doubt is related to doubt 4).

I think the xslt structure would remain constant unless the message definitions changed.

May 10,2013

Roger Friedman

6

May 9,2013

Is the xslt the only integration between DHIS2 and this xml or do we provide some other kind of integration?

I think we should provide a message transport service like the messaging module and/or something special for MIRTH

May 10,2013

Roger Friedman

7

May 9,2013

I suppose the user interface consists of providing an option for selection of question and display of xml in the reporting module itself? or should it be different?

I think what the admin interface needs is a way to associate reports with messaging parameters and dataset contents with indicator definitions.  I think in most cases there will be a message template which includes the indicator IDs; the association with dataset contents will be managed through the interface; you may need the ability to start with an empty template and build it as you go.

May 10,2013

Roger Friedman

8

May 30,2013

What can we take down as the projects objectives or the workflow could be?

-Extending reporting module's tables to persist the requested report's data for this project.

-Understanding the present SDMX integration project and implementing it to the present reporting module.(It is the required use case as per the present requirements)

-Designing the project's plan based on exact requirement of how the exact integration between the reporting and SDMX-HD(presently it is of creating a UI in reporting module to create the report int sdmx format and when the user select that specific option the message would be generated and would be forwarded using the messaging module).

-Possibly integrating the reporting module's rest services project(Currently a GSOC project)  with this module.

-Designing the Module's exact targets.

-Integration between DHIS2 and this module must be discussed

May 30,2013

Roger Friedman

9

June 6,2013

This is also a continuation to the previous doubt but this was discussed with the project champions.

1.export of dhis2 report
2. metadata export of dhis2 --questions form dhis2
3.create an openmrs report having all the indicators user wants mapped to the template
report/template
indicator/dataelement
--admin creates the report
show the disaggregations dhis2 wants and map them to the values in openmrs

4.show this template

5.ready to run-users can run the report

6.report would sent using the messaging module./sent them by email/sent into a queue to be sent to dhis2

June 6,2013

Roger Friedman, Bob Jolliffe,Saptarshi Purkayastha and James M. Kariuki

10

June 6,2013

Todo list for me to get started on the project

1. Use the DHIS2 webAPI to download the dataset definition (template)
2. Create a new annotation for different OpenMRS reporting framework indicators
3. Fill the annotations with created indicator ids (uuids)
4. Load the value into this and send them as dataValueSet into DHIS2 (as the dhisreport module does)

June 6,2013

Saptarshi Purkayastha and Roger Friedman

11

June 7,2013

project beginners info on hisp india module and integration with dhis2

  1.  The hisp module assumes that the DHIS2 instance is accessible to the OpenMRS instance.  I think that we still have to support a distributed (i.e. intermittent synchronization) model.  Perhaps the easiest way to do this would be to have a DHIS2 instance co-located on the OpenMRS server; it could accept DHIS2 metadata updates from the central server.  That might not work if there were multiple DHIS2-based systems in the country, e.g. a routine health data system run by the Ministry of Health and a TB indicator system run by an NGO.  Alternatively, we could process the metadata export ourselves, perhaps using code from DHIS2, although I don't like that tight coupling.
    2.  The hisp module assumes that the OpenMRS data maps to exactly one organizational unit in DHIS2.  I think we must allow for an OpenMRS containing data on multiple organizational units; the central-and satellite form of deployment using the synch module is a common (but not well-supported) use case for OpenMRS.
    3.  I would like to keep the message structure the same and use the <annotation> tag to store our mapping data.  I would suggest we add an "annotation type" attribute to the XSD which would default to "sql" using the body of the tag; our mappings should be expressed in other attributes on the annotation.  We are also going to have to define a way of mapping the category option combos to OpenMRS concept values or reporting cohorts.  More on this later.
    4.  The existing module has a single location and a single data element and a single category combo value per annotation (SQL query).  Our hope is to collect multiple locations, data elements and category combo values per OpenMRS report definition, then generate multiple data rows (perhaps in multiple data files) from them.  We would be sorting report outputs into DHIS2 bins rather than iterating over DHIS2 bins and getting their contents.  Note that it is a very common DHIS2 use case for multiple data elements to be used in lieu of a single data element with categories, so we might be using filter values to distinguish between data elements as well as between categories.  So we are mapping location, data element and category combo value on the DHIS2 side to dataset, cohort, variable, filter values on the OpenMRS side (all within a single DHIS2 dataset or OpenMRS report specification). 
    5.  The existing sdmx module (Ryan Crichton's) is already integrated into the reporting framework.  I chatted with Mike Seaton this morning and he suggested looking at Reporting Module release notes subsequent to 0.7.3 on which the sdmx module is based to see what non-backwards-compatible changes have been introduced.  Much of the guts of the hisp module would be used (the transfer file format and operations based on it); I have to look at both

June 7,2013

Roger Friedman and supported by Bob Jolliffe with suggestions.

12

June 11,2013

First Testing Use case for trying out the functionality

1.  OpenMRS large dataset is basis
2.  Data will be obs_datetime in [2006/02,2006/06]
3.  Data will be obs of concepts 5356 CURRENT WHO STAGE and 5497 CD4 COUNT.  The answers to concept 5356 are concepts 1204-1207, WHO STAGE 1-4 ADULT.
4.  Monthly indicators:
    a) NUMBER OF PATIENTS OBSERVED WITH WHO STAGE 1-4 (4 indicators), potentially disaggregated by age (0-5,5-14,14-21,21-49,50+) and sex; 
    b) NUMBER OF PATIENTS OBSERVED WITH ANY WHO STAGE, sum of indicators in A, potentially disaggregated by age (0-5,5-14,14-21,21-49,50+) and sex; 
    c) NUMBER OF PATIENTS WITH A CD4 COUNT, potentially disaggregated by CD4 Count<=250 and CD4Count>250; and 
    d) NUMBER OF NEW PATIENTS BY CD4 COUNT, where a new patient is one whose first CD4 count is in the reporting month, disaggregated by CD4 Count<= or >250 and sex and concept 5272 PREGNANCY STATUS whose values are 1055 YES and 1066 NO.
5.  The test data has only one location.  It will be modified on the following basis: new locations will be created 2 REGION A, 3 HOSPITAL X (child of 2), 4 FACILITY Y (child of 2), 5 IN-PATIENT (child of 3), 6 OUTPATIENT (child of 3).  Encounters will be assigned randomly to locations 4-6.  DHIS2 will have org units for REGION A, HOSPITAL X and FACILITY Y.  (See ticket REPORT-288)

June 11,2013

Roger Friedman

13

June 11,2013

Tips for starting the module

Exploring Reporting module with test data and period indicator reports.

June 11,2013

Roger Friedman

14

June 20,2013

What exactly are disaggregations

Disaggregations are segregation of the report data obtained into a more detailed data parts having information about them. Meaning if a data such as current who stage is generated, separating the data obtained based on age groups can be called disaggregation.

June 20,2013

Roger Friedman

15

June 20,2013

Suggestion by Roger to start coding

Create a basic module using the maven archetype which can take in report definition.

June 20,2013

Roger Friedman

16

June 20,2013

i am facing difficulties in creating the disaggregations in the report

That's an area we need to investigate and discover how we need to acheive that.

June 20,2013

Roger Friedman

17

June 27,2013

Is the following flow fine or do I need to change it?

1>> I'm trying to run the definitions that are existing in the database(the ones created as cohort queries) 

2>> I'll work on giving controls to take in definitions from the user/which can be added from a function.

3>> Then i plan to take in the DHIS2 xml and map it to our data elements.

4>> Run the Reports and Generate the SDMX-HD  message.

Rather than giving an option or writing a function it's better to use the preexisting api.

In the first step also instead of using the services try to use the reporting api directly

June 27,2013

Roger Friedman

18

June 27,2013

In the first step mentioned above is it fine if i use the services such as the ones used in the query parameter class? to obtain the

It's better if in the beginning we take the test data and analyze that and provide the functionality from the testing procedure and later on we can add more complexities based on the requirement.

June 27,2013

Roger Friedman