SDMX-HD: Difference between revisions

From IHRIS Wiki
(Created page with ' This describes SDMX-HD implementation for exporting data from iHRIS. Everything will be handled through the custom reports and form relationship modules ==Form Relationships==…')
 
Line 20: Line 20:
*SMDX Meta Data Structure. this is optional  see  A.4 of the [[#user guide | user guider]].  
*SMDX Meta Data Structure. this is optional  see  A.4 of the [[#user guide | user guider]].  


===Domain==
===Domain===
We need to somehow specify the domain for this module which will represent where country/implementation specific database lists such as cadre are applicable to.  For example $domain = 'tanzania_ministy_of_health'  or $domain='tanzaina_CSSC'
We need to somehow specify the domain for this module which will represent where country/implementation specific database lists such as cadre are applicable to.  For example $domain = 'tanzania_ministy_of_health'  or $domain='tanzaina_CSSC'



Revision as of 10:11, 29 October 2009

This describes SDMX-HD implementation for exporting data from iHRIS.

Everything will be handled through the custom reports and form relationship modules

Form Relationships

Add a sub-module of form relationships to allow tagging the form and fields with SDMX-HD data structure. The tags will optionally applied to any of the following:

  • reportform+field
  • reportform+field+aggregate (where aggregate is one of min,max,sum,count,avg)
  • +function
  • +function+aggreagte (where aggregate is one of min,max,sum,count,avg)

The tags will summarize the following:

  • SMDX Data Structure. This is most important see A.3 of the user guider.
    • We may need to specify the Dimension(codelist) and Attribute (codelist or text) for the Data Structre
    • for code lists see page 87/92 of the user guide. In brief it represent the possible values for that data elment.
    • the code lists can be determined automatically in the case of currency or integer
    • for mapped values such as code lists or districts, our mapped values may or may be a ISO/external recgonized data set and this may be an issue. to address this, we need to make sure that all of our database lists can be exported and flagged as being domain specific or not. then the code lists should be like the componetntized form ids such as
      cadre|15@tanznia_ministry_of_health
      here the tanzinar_ministry_of_health is the domain while lists like Country would not domain specific and thus would be like:
      country|17
      . However, this is not particuallarly ideal as country|17' is really only our internal id. So we should be using the from field country+isco_code instead of country+id as the report form field in this case so that we get
      country|TZ
  • SMDX Meta Data Structure. this is optional see A.4 of the user guider.

Domain

We need to somehow specify the domain for this module which will represent where country/implementation specific database lists such as cadre are applicable to. For example $domain = 'tanzania_ministy_of_health' or $domain='tanzaina_CSSC'

Custom Reports

Add functionality to the 'custom report export' module. Already there is an XML export. We will add an SDMX-HD export that will be selectively available to a report view according to the following criteria:

every $reportform+$field(+$aggregate)? or +$functiion(+a$ggregate)?  in the report view has a SDMX-HD tag in the form relationship.


Documents

user guide

The SDMX user guide