dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #14317
[Branch ~dhis2-documenters/dhis2/dhis2-docbook-docs] Rev 404: Added support for SVG files in the docs via the po, . Reworked the section on AWS a bit. Moved the...
------------------------------------------------------------
revno: 404
committer: Jason P. Pickering <jason.p.pickering@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Tue 2011-10-04 16:33:11 +0200
message:
Added support for SVG files in the docs via the po,. Reworked the section on AWS a bit. Moved the glossary up to the main documentation folder. Renamed some PNG to png.Other random fixes and improvements.
renamed:
src/docbkx/en/resources/glossary/glossary_en.xml => src/docbkx/en/glossary_en.xml
src/docbkx/en/resources/images/aws/create_instance.PNG => src/docbkx/en/resources/images/aws/create_instance.png
src/docbkx/en/resources/images/aws/create_key_pairs.PNG => src/docbkx/en/resources/images/aws/create_key_pairs.png
src/docbkx/en/resources/images/aws/instance_prefs.PNG => src/docbkx/en/resources/images/aws/instance_prefs.png
src/docbkx/en/resources/images/aws/instance_size.PNG => src/docbkx/en/resources/images/aws/instance_size.png
src/docbkx/en/resources/images/aws/security_groups.PNG => src/docbkx/en/resources/images/aws/security_groups.png
modified:
pom.xml
src/docbkx/en/dhis2_implementation_guide_installation_detailed.xml
src/docbkx/en/dhis2_user_man_data_elements.xml
src/docbkx/en/dhis2_user_manual_en.xml
src/docbkx/en/glossary_en.xml
--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs
Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription
=== modified file 'pom.xml'
--- pom.xml 2011-09-12 15:09:55 +0000
+++ pom.xml 2011-10-04 14:33:11 +0000
@@ -29,6 +29,7 @@
<build>
<plugins>
+ <!--This section dynamically builds the build.properites which is replaced inside the document preface -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
@@ -74,6 +75,7 @@
<sectionAutolabel>1</sectionAutolabel>
<sectionLabelIncludesComponentLabel>1</sectionLabelIncludesComponentLabel>
<chunkedOutput>true</chunkedOutput>
+ <useEmbedForSvg>1</useEmbedForSvg>
<includes>dhis2_user_manual_en.xml</includes>
<sourceDirectory>${docbook.source}/en/</sourceDirectory>
<targetDirectory>${docbook.target}/en/user/html/</targetDirectory>
@@ -86,8 +88,10 @@
<copy todir="${docbook.target}/en/user/html/resources/images">
<fileset dir="src/docbkx/en/resources/images">
<include name="**/*.png" />
+ <include name="**/*.PNG" />
<include name="**/*.gif" />
<include name="**/*.jpg" />
+ <include name="**/*.svg" />
</fileset>
</copy>
<copy todir="${docbook.target}/en/user/html/resources/css">
@@ -128,6 +132,7 @@
<include name="**/*.PNG" />
<include name="**/*.gif" />
<include name="**/*.jpg" />
+ <include name="**/*.svg" />
</fileset>
</copy>
<copy todir="${docbook.target}/en/end-user/html/resources/css">
@@ -168,6 +173,7 @@
<include name="**/*.PNG" />
<include name="**/*.gif" />
<include name="**/*.jpg" />
+ <include name="**/*.svg" />
</fileset>
</copy>
<copy todir="${docbook.target}/en/implementer/html/resources/css">
=== modified file 'src/docbkx/en/dhis2_implementation_guide_installation_detailed.xml'
--- src/docbkx/en/dhis2_implementation_guide_installation_detailed.xml 2011-05-06 05:57:05 +0000
+++ src/docbkx/en/dhis2_implementation_guide_installation_detailed.xml 2011-10-04 14:33:11 +0000
@@ -658,21 +658,20 @@
<section>
<title> Using Amazon Web services</title>
<para>Amazon Web Services (AWS) offers virtual cloud-computing resources which allow developers and implementers to quickly scale an application, both horizontally and vertically, in a cost effective manner. AWS offers multiple operating systems and instance sizes depending on the exact nature of the deployment. This section will describe a basic setup with the AWS Elastic Cloud Compute (EC2) system using the Basic 32 bit Amazon AMI, which is based on the Red Hat Linux distribution. </para>
- <para>Estimating the cost of an AWS instance can be performed using the<ulink url="http://calculator.s3.amazonaws.com/calc5.html";> "Simple Monthly Cal culator"</ulink>. AWS costs are based entirely on usage. As your applicatio
-n usage grows, you can provision new servers. </para>
+ <para>Estimating the cost of an AWS instance can be performed using the<ulink url="http://calculator.s3.amazonaws.com/calc5.html";> "Simple Monthly Cal culator"</ulink>. AWS costs are based entirely on usage. As your application usage grows, you can provision new servers. </para>
<orderedlist>
<listitem>
<para>You will need an existing AWS account. If you do not have one, you can create one <ulink url="http://aws.amazon.com/";>here</ulink>. Once you have created and enabled your account, login to the<ulink url="https://console.aws.amazon.com/s3/home";> AWS console</ulink>. </para>
</listitem>
<listitem>
- <para>Once you have logged in, select the "EC2" tab. You will need to select a region in which to instantiate your instance. Users in Europeand Africa, should probably use the EU West region, while users in Asia should probably use on of the Asia Pacific regions (either Singapore or Tokyo). Selection of the appropriate region will reduce latency between the server and clients.</para>
+ <para>Once you have logged in, select the "EC2" tab. You will need to select a region in which to instantiate your instance. Users in Europe and Africa, should probably use the EU West region, while users in Asia should probably use on of the Asia Pacific regions (either Singapore or Tokyo). Selection of the appropriate region will reduce latency between the server and clients.</para>
</listitem>
<listitem>
- <para>Click the "Instances" link on the right menu, and thenthe "Launch Instances" button. </para>
+ <para>Click the "Instances" link on the right menu, and then the "Launch Instances" button. </para>
<screenshot>
<mediaobject>
<imageobject>
- <imagedata width="60%" align="center" fileref="resources/images/aws/create_instance.PNG"/>
+ <imagedata width="60%" align="center" fileref="resources/images/aws/create_instance.png"/>
</imageobject>
</mediaobject>
</screenshot>
@@ -683,7 +682,7 @@
<screenshot>
<mediaobject>
<imageobject>
- <imagedata width="60%" align="center" fileref="resources/images/aws/instance_size.PNG"/>
+ <imagedata width="60%" align="center" fileref="resources/images/aws/instance_size.png"/>
</imageobject>
</mediaobject>
</screenshot>
@@ -699,7 +698,7 @@
<screenshot>
<mediaobject>
<imageobject>
- <imagedata width="60%" align="center" fileref="resources/images/a ws/create_key_pairs.PNG"/>
+ <imagedata width="60%" align="center" fileref="resources/images/aws/create_key_pairs.png"/>
</imageobject>
</mediaobject>
</screenshot>
@@ -709,7 +708,7 @@
<screenshot>
<mediaobject>
<imageobject>
- <imagedata width="50%" align="center" fileref="resources/images/aws/security_groups.PNG"/>
+ <imagedata width="50%" align="center" fileref="resources/images/aws/security_groups.png"/>
</imageobject>
</mediaobject>
</screenshot>
=== modified file 'src/docbkx/en/dhis2_user_man_data_elements.xml'
--- src/docbkx/en/dhis2_user_man_data_elements.xml 2011-09-12 18:11:43 +0000
+++ src/docbkx/en/dhis2_user_man_data_elements.xml 2011-10-04 14:33:11 +0000
@@ -39,7 +39,7 @@
</itemizedlist>
<section id="dataElement">
<title>Data elements</title>
- <para>Data elements form the basis of DHIS2. Data elements define what is actually recorded in system, e.g. number of immunisations or number of cases of malaria. The actual creation and definition of the data elements themselves are far beyond the scope of this manual to describe, but it is assumed that an administrator will be provided with a list of standardised data elements for inclusion into the DHIS2 system. </para>
+ <para><?inline true?>Data elements form the basis of DHIS2. Data elements define what is actually recorded in system, e.g. number of immunisations or number of cases of malaria. The actual creation and definition of the data elements themselves are far beyond the scope of this manual to describe, but it is assumed that an administrator will be provided with a list of standardised data elements for inclusion into the DHIS2 system. </para>
<para>To access the data element maintenance module, choose Maintenance -> Data elements and Indicators -> Data element. </para>
<para>The ‘Filter by name’ will allow you to filter a range of data elements if you know either the full name of the data element, or just a part of it. Type the name
into the search field and any matching data elements are displayed below.
=== modified file 'src/docbkx/en/dhis2_user_manual_en.xml'
--- src/docbkx/en/dhis2_user_manual_en.xml 2011-09-19 18:59:06 +0000
+++ src/docbkx/en/dhis2_user_manual_en.xml 2011-10-04 14:33:11 +0000
@@ -93,7 +93,7 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_technical_architechture_guide.xml" encoding="UTF-8" xpointer="technicalPresentationLayer"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_technical_architechture_guide.xml" encoding="UTF-8" xpointer="technicalFrameworkStack"/>
</appendix>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="resources/glossary/glossary_en.xml" encoding="UTF-8"/>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="glossary_en.xml" encoding="UTF-8"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="dhis2_bibliography.xml" encoding="UTF-8"/>
<index/>
</book>
=== renamed file 'src/docbkx/en/resources/glossary/glossary_en.xml' => 'src/docbkx/en/glossary_en.xml'
--- src/docbkx/en/resources/glossary/glossary_en.xml 2010-01-22 08:55:40 +0000
+++ src/docbkx/en/glossary_en.xml 2011-10-04 14:33:11 +0000
@@ -1,209 +1,208 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!-- This document was created with Syntext Serna Free. -->
-<!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml
-/4.4/docbookx.dtd" []>
-<glossary id="dhis2_glossary">
- <glossaryinfo>
- <editor>
- <firstname>Jason</firstname>
- <surname>Pickering</surname>
- </editor>
- <title>DHIS2 Glossary</title>
- <releaseinfo>2.0.3</releaseinfo>
- </glossaryinfo>
- <title>DHIS 2 Glossary</title>
- <glossdiv>
- <title>A</title>
- <glossentry>
- <glossterm>Aggregation</glossterm>
- <glossdef>
- <para>In the context of DHIS2, aggregation refers to how data elements are combined within a particular hierarchical relationship. As an example, all the health facilities in a particular district would contribute to the total value for the particular district in question. Different aggregation operators are supported within DHIS2, such as SUM, AVERAGE, and COUNT.</para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm baseform="aggregateData">Aggregate data</glossterm>
- <glossdef>
- <para>In the context of DHIS2, aggregate data refers to either data elements or indicators that have been derived from other hierarchical data sources. For instance, aggreagte facility data would result from the aggregate totals of all patients that have attended that facility for a particular service. Aggregate district data would result from the aggregate totals of all facilities contained with a particular district.</para>
- </glossdef>
- </glossentry>
- </glossdiv>
- <glossdiv>
- <title>C</title>
- <glossentry>
- <glossterm>Category</glossterm>
- <glossdef>
- <para>Categories are used to disaggreate data elements. As an example, the data element "Number of confirmed cases of malaria" could be disaggregated into an "Age" category, consisting of category options of "Under 1", 1-5" and "Over 5". Category options are used during data entry to simplify the number of data elements that need to be created. During analysis of data, categories function essentially as dimensions. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Category option</glossterm>
- <glossdef>
- <para>Category options are atomic elements that are grouped into categories. Category options are used during data entry to disaggregate data elements into atomic pieces of information. </para>
- </glossdef>
- </glossentry>
- </glossdiv>
- <glossdiv>
- <title>D</title>
- <glossentry>
- <glossterm>Data dictionary</glossterm>
- <glossdef>
- <para>A collection of data elements and indicators, which can be exchanged with other DHIS systems. Typically used to define a set of data elements and indicators when setting up the DHIS system. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Data exchange format</glossterm>
- <glossdef>
- <para>In the context of DHIS2, the "data exchange format" refers to a XML schema that enables the transportation of data and metadata between disconnected DHIS instances, as well as between different applications that suppor the DXF schema. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Datamart</glossterm>
- <glossdef>
- <para>A set of database tables in DHIS2 that contians processed data elements and indicator values that is generated based on aggregation rules and calculated data element and indicator formular. Datamart tables are used for analysis and report production. Typically, users should not work directly with unaggregated data values, but rather with values that have resulted from a datamart export for analysis. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Data element</glossterm>
- <glossdef>
- <para>A data element is the fundemental building block of DHIS2. It is an atomic unit of data with well-defined meaning. Essentially it is a data value that has been actually observed or recorded which is further characterized by a number of dimensions. As an example the data element "Number of fully immunized children" would refer to the number of children that received this particular service. Data elements are always linked to a period as as well as an organizational unit. They optionally may be linked to other dimensions. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Data element group</glossterm>
- <glossdef>
- <para>Data element groups are used to categorize multiple data elements according to a common theme, such as "Immunization" or "ART". Typically, they are used during reporting and analysis to allow related data elements to be analyzed together. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Data element group sets</glossterm>
- <glossdef>
- <para>Data element groups are used to categorize multiple data element groups into a common theme. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Dimension</glossterm>
- <glossdef>
- <para>A dimension is used to categorize data elements during analysis. Dimensions provide a mechanism to group and filter data based on common characteristics. Typically, related data elements may be aggregated or filtered during analysis with the use of dimensions. Dimensions may be a member of a hierarchy. For instance the "Period" dimension may be broken down into "Day->Month->Quarter->Year". </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>DXF</glossterm>
- <glosssee> Data exchange format</glosssee>
- </glossentry>
- </glossdiv>
-<!-- <glossdiv>
- <title>E</title>
- </glossdiv>
- <glossdiv>
- <title>F</title>
- </glossdiv>
- <glossdiv>
- <title>G</title>
- </glossdiv>
- <glossdiv>
- <title>E</title>
- </glossdiv>
- <glossdiv>
- <title>F</title>
- </glossdiv>
- <glossdiv>
- <title>G</title>
- </glossdiv>
- <glossdiv>
- <title>H</title>
- </glossdiv> --> <glossdiv>
- <title>H</title>
- <glossentry>
- <glossterm>Health management information system</glossterm>
- <abbrev>HMIS</abbrev>
- <glossdef>
- <para>Typically, an electronic database system that is used to record aggregated data on service delivery, disease incidence, human resource data and other information used to evaluate the performance of delivery of health services. Typically, an HMIS does not contain the highly detailed data of electronic medical record systems or individual patient data. </para>
- </glossdef>
- </glossentry>
- </glossdiv>
- <glossdiv>
- <title>I</title>
- <glossentry>
- <glossterm>Indicator</glossterm>
- <glossdef>
- <para>The divisor of an indicator. Can be composed of multiple data elements with the use of an indicator formula.<equation>
- <mediaobject>
- <imageobject>
- <imagedata fileref="../images/indicator.png"/>
- </imageobject>
- </mediaobject>
- </equation></para>
- <para>This is obviously a very generalized example. The numerator and indicator themselves can be composed of various data elements, factors, and the four basic operands (addition, multiplication, division and subtraction). </para>
- </glossdef>
- </glossentry>
- </glossdiv>
- <glossdiv>
-<!--<title>J</title>
- </glossdiv>
- <glossdiv>
- <title>K</title>
- </glossdiv>
- <glossdiv>
- <title>L</title>
- </glossdiv>
- <glossdiv>
- <title>M</title>
- </glossdiv>
- <glossdiv> --> <title>N</title>
- <glossentry>
- <glossterm>Numerator</glossterm>
- <glossdef>
- <para>The dividend of a indicator. Can be composed of multiple data elements and factors with the use of indicator formulas.</para>
- </glossdef>
- </glossentry>
- </glossdiv>
- <glossdiv>
- <title>O</title>
- <glossentry>
- <glossterm>Organisational unit</glossterm>
- <abbrev>orgunit</abbrev>
- <glossdef>
- <para>Typically, an orgunit is a unit within a geographical hierarchy. As an example, in the United States, "Georgia" would be considered an orgunit with in the orgunit level of "State". Organizational units can also represent units, such as wards within a hospital, withn a single geographical location. </para>
- </glossdef>
- </glossentry>
- <glossentry>
- <glossterm>Organisational unit level</glossterm>
- <abbrev>Orgunit level</abbrev>
- <glossdef>
- <para>Refers to a level within an organizational hierarchy. Typically, countries are administered at different levels, such as 1) Country 2) States 3) Counties 4) Health facilities. In the context of DHIS2, health facilities typically are the lowest orgunit level. Data is aggregated upwards from the lowest orgunit level to the highest. </para>
- </glossdef>
- </glossentry>
- </glossdiv>
-<!--<glossdiv>
- <title>P</title>
- </glossdiv>
- <glossdiv>
- <title>Q</title>
- </glossdiv>
- <glossdiv>
- <title>R</title>
- <glossentry>
- <glossterm>Report table</glossterm>
- </glossentry>
- </glossdiv>
- <glossdiv>
- <title>S</title>
- </glossdiv>
- <glossdiv>
- <title>T</title>
- </glossdiv>
- <glossdiv>
- <title>U</title>
- </glossdiv>
- <glossdiv>
- <title>W</title>
- </glossdiv>
- <glossdiv>
- <title>X</title>
- </glossdiv>
- <glossdiv>
- <title>Y</title>
- </glossdiv>
- <glossdiv>
- <title>Z</title>
- </glossdiv> --></glossary>
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- This document was created with Syntext Serna Free. --><!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml
+/4.4/docbookx.dtd" []>
+<glossary id="dhis2_glossary">
+ <glossaryinfo>
+ <editor>
+ <firstname>Jason</firstname>
+ <surname>Pickering</surname>
+ </editor>
+ <title>DHIS2 Glossary</title>
+ <releaseinfo>2.0.3</releaseinfo>
+ </glossaryinfo>
+ <title>DHIS 2 Glossary</title>
+ <glossdiv>
+ <title>A</title>
+ <glossentry>
+ <glossterm>Aggregation</glossterm>
+ <glossdef>
+ <para>In the context of DHIS2, aggregation refers to how data elements are combined within a particular hierarchical relationship. As an example, all the health facilities in a particular district would contribute to the total value for the particular district in question. Different aggregation operators are supported within DHIS2, such as SUM, AVERAGE, and COUNT.</para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm baseform="aggregateData">Aggregate data</glossterm>
+ <glossdef>
+ <para>In the context of DHIS2, aggregate data refers to either data elements or indicators that have been derived from other hierarchical data sources. For instance, aggreagte facility data would result from the aggregate totals of all patients that have attended that facility for a particular service. Aggregate district data would result from the aggregate totals of all facilities contained with a particular district.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv>
+ <title>C</title>
+ <glossentry>
+ <glossterm>Category</glossterm>
+ <glossdef>
+ <para>Categories are used to disaggreate data elements. As an example, the data element "Number of confirmed cases of malaria" could be disaggregated into an "Age" category, consisting of category options of "Under 1", 1-5" and "Over 5". Category options are used during data entry to simplify the number of data elements that need to be created. During analysis of data, categories function essentially as dimensions. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Category option</glossterm>
+ <glossdef>
+ <para>Category options are atomic elements that are grouped into categories. Category options are used during data entry to disaggregate data elements into atomic pieces of information. </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv>
+ <title>D</title>
+ <glossentry>
+ <glossterm>Data dictionary</glossterm>
+ <glossdef>
+ <para>A collection of data elements and indicators, which can be exchanged with other DHIS systems. Typically used to define a set of data elements and indicators when setting up the DHIS system. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Data exchange format</glossterm>
+ <glossdef>
+ <para>In the context of DHIS2, the "data exchange format" refers to a XML schema that enables the transportation of data and metadata between disconnected DHIS instances, as well as between different applications that suppor the DXF schema. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Datamart</glossterm>
+ <glossdef>
+ <para>A set of database tables in DHIS2 that contians processed data elements and indicator values that is generated based on aggregation rules and calculated data element and indicator formular. Datamart tables are used for analysis and report production. Typically, users should not work directly with unaggregated data values, but rather with values that have resulted from a datamart export for analysis. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Data element</glossterm>
+ <glossdef>
+ <para>A data element is the fundemental building block of DHIS2. It is an atomic unit of data with well-defined meaning. Essentially it is a data value that has been actually observed or recorded which is further characterized by a number of dimensions. As an example the data element "Number of fully immunized children" would refer to the number of children that received this particular service. Data elements are always linked to a period as as well as an organizational unit. They optionally may be linked to other dimensions. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Data element group</glossterm>
+ <glossdef>
+ <para>Data element groups are used to categorize multiple data elements according to a common theme, such as "Immunization" or "ART". Typically, they are used during reporting and analysis to allow related data elements to be analyzed together. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Data element group sets</glossterm>
+ <glossdef>
+ <para>Data element groups are used to categorize multiple data element groups into a common theme. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Dimension</glossterm>
+ <glossdef>
+ <para>A dimension is used to categorize data elements during analysis. Dimensions provide a mechanism to group and filter data based on common characteristics. Typically, related data elements may be aggregated or filtered during analysis with the use of dimensions. Dimensions may be a member of a hierarchy. For instance the "Period" dimension may be broken down into "Day->Month->Quarter->Year". </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>DXF</glossterm>
+ <glosssee> Data exchange format</glosssee>
+ </glossentry>
+ </glossdiv>
+<!-- <glossdiv>
+ <title>E</title>
+ </glossdiv>
+ <glossdiv>
+ <title>F</title>
+ </glossdiv>
+ <glossdiv>
+ <title>G</title>
+ </glossdiv>
+ <glossdiv>
+ <title>E</title>
+ </glossdiv>
+ <glossdiv>
+ <title>F</title>
+ </glossdiv>
+ <glossdiv>
+ <title>G</title>
+ </glossdiv>
+ <glossdiv>
+ <title>H</title>
+ </glossdiv> --> <glossdiv>
+ <title>H</title>
+ <glossentry>
+ <glossterm>Health management information system</glossterm>
+ <abbrev>HMIS</abbrev>
+ <glossdef>
+ <para>Typically, an electronic database system that is used to record aggregated data on service delivery, disease incidence, human resource data and other information used to evaluate the performance of delivery of health services. Typically, an HMIS does not contain the highly detailed data of electronic medical record systems or individual patient data. </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv>
+ <title>I</title>
+ <glossentry>
+ <glossterm>Indicator</glossterm>
+ <glossdef>
+ <para>The divisor of an indicator. Can be composed of multiple data elements with the use of an indicator formula.<equation>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="resources/images/test_drawing.svg"/>
+ </imageobject>
+ </mediaobject>
+ </equation></para>
+ <para>This is obviously a very generalized example. The numerator and indicator themselves can be composed of various data elements, factors, and the four basic operands (addition, multiplication, division and subtraction). </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv>
+<!--<title>J</title>
+ </glossdiv>
+ <glossdiv>
+ <title>K</title>
+ </glossdiv>
+ <glossdiv>
+ <title>L</title>
+ </glossdiv>
+ <glossdiv>
+ <title>M</title>
+ </glossdiv>
+ <glossdiv> --> <title>N</title>
+ <glossentry>
+ <glossterm>Numerator</glossterm>
+ <glossdef>
+ <para>The dividend of a indicator. Can be composed of multiple data elements and factors with the use of indicator formulas.</para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+ <glossdiv>
+ <title>O</title>
+ <glossentry>
+ <glossterm>Organisational unit</glossterm>
+ <abbrev>orgunit</abbrev>
+ <glossdef>
+ <para>Typically, an orgunit is a unit within a geographical hierarchy. As an example, in the United States, "Georgia" would be considered an orgunit with in the orgunit level of "State". Organizational units can also represent units, such as wards within a hospital, withn a single geographical location. </para>
+ </glossdef>
+ </glossentry>
+ <glossentry>
+ <glossterm>Organisational unit level</glossterm>
+ <abbrev>Orgunit level</abbrev>
+ <glossdef>
+ <para>Refers to a level within an organizational hierarchy. Typically, countries are administered at different levels, such as 1) Country 2) States 3) Counties 4) Health facilities. In the context of DHIS2, health facilities typically are the lowest orgunit level. Data is aggregated upwards from the lowest orgunit level to the highest. </para>
+ </glossdef>
+ </glossentry>
+ </glossdiv>
+<!--<glossdiv>
+ <title>P</title>
+ </glossdiv>
+ <glossdiv>
+ <title>Q</title>
+ </glossdiv>
+ <glossdiv>
+ <title>R</title>
+ <glossentry>
+ <glossterm>Report table</glossterm>
+ </glossentry>
+ </glossdiv>
+ <glossdiv>
+ <title>S</title>
+ </glossdiv>
+ <glossdiv>
+ <title>T</title>
+ </glossdiv>
+ <glossdiv>
+ <title>U</title>
+ </glossdiv>
+ <glossdiv>
+ <title>W</title>
+ </glossdiv>
+ <glossdiv>
+ <title>X</title>
+ </glossdiv>
+ <glossdiv>
+ <title>Y</title>
+ </glossdiv>
+ <glossdiv>
+ <title>Z</title>
+ </glossdiv> --></glossary>
=== renamed file 'src/docbkx/en/resources/images/aws/create_instance.PNG' => 'src/docbkx/en/resources/images/aws/create_instance.png'
=== renamed file 'src/docbkx/en/resources/images/aws/create_key_pairs.PNG' => 'src/docbkx/en/resources/images/aws/create_key_pairs.png'
=== renamed file 'src/docbkx/en/resources/images/aws/instance_prefs.PNG' => 'src/docbkx/en/resources/images/aws/instance_prefs.png'
=== renamed file 'src/docbkx/en/resources/images/aws/instance_size.PNG' => 'src/docbkx/en/resources/images/aws/instance_size.png'
=== renamed file 'src/docbkx/en/resources/images/aws/security_groups.PNG' => 'src/docbkx/en/resources/images/aws/security_groups.png'
