=== modified file 'src/docbkx/en/dhis2_user_man_mobile.xml' --- src/docbkx/en/dhis2_user_man_mobile.xml 2012-04-17 06:42:32 +0000 +++ src/docbkx/en/dhis2_user_man_mobile.xml 2012-10-31 03:27:39 +0000 @@ -25,6 +25,16 @@ DHIS2 can also be used with an earlier J2ME-client that uses SMS as a transport. This client requires some manual configuration on the server side, and is not supported by the standard build of DHIS2. The client is a custom built J2ME mobile application. The SMS-support is separate from the SMS support used in other parts of DHIS2. The solution has mainly been deployed using GSM modems, which are not good for high-volume applications, but can also be used as a basis for a more reliable SMSC-connection. Using SMS as a transport would be an appropriate solution where GPRS/3G is not available, but GSM coverage is available. Updating of forms to the client is not supported at this point in time, and new data sets require a new application install. This solution is described in The DHIS-mobile team is working on a hybrid GPRS and SMS solution that is based on the newer J2ME-client and the new SMS-support within the platform. + + SMS connection + When deploying SMS solutions, the quality and stability of the SMS link is critical for the overall service quality. For small demos and tests, one can use phone modems to send and receive SMS, but our experience is that for any larger installation, one should connect to the mobile operator SMS infrastructure (SMSC) via more robust interfaces. We can either connect directly to the mobile operator SMSC (typically through a protocol called SMPP but sometimes using HTTP or other protocols) or via a service provider called an SMS gateway provider. + + When connecting directly to the operator, for receiving SMS, one has to connect to all the operators whose subscribers should be able to send us messages. The typical scenario is that the operator assigns a short number (4 or 5 digits) to our service, and forward the messages sent to this number to our/your server. The best is to have all operators assign the same number, but this isn't necessarily automatic. + If connecting via an SMS gateway company, they connect to all operators for us and typically put some additional charge on the message price. Since there is a cost per number and per operator, this may sometimes still be price efficient. SMS gateway providers typically connect via HTTP or SMPP. + The simplest and cheapest would be if you already have some SMS connection greement that we could leverage. I would be useful to get this interface up and running as soon as possible, as this really might be the most complex integration point (though in principle it really is quite simple to do when everything runs smoothly). If you do not yet have such an agreement, we can help you in the process. + Note that some operators offer long numbers as a service in addition to short numbers. Then you get what looks like a real mobile number, and it can be accessed by all other operators' customers also. This is often a very simple way of offering SMS as you do not need to connect to all operators. But not many operators offer this. + It is quite relevant for the deployment if the users have subscriptions from a single operator or if many operators are used. One operator is simpler. + === modified file 'src/docbkx/en/dhis2_user_man_mobile_web_based.xml' --- src/docbkx/en/dhis2_user_man_mobile_web_based.xml 2012-07-21 10:38:26 +0000 +++ src/docbkx/en/dhis2_user_man_mobile_web_based.xml 2012-10-31 03:27:39 +0000 @@ -16,6 +16,13 @@ + + + + + + + @@ -23,27 +30,30 @@ - Data Entry: Entries for aggregate data with defined/assigned dataset by organisation-units - - - Name-based Data Entry: - Entries data for the beneficiaries by organisation-units, beneficiaries and programs/program-stages. - - - Beneficiary Registration: - Registry a new beneficiary - - - Beneficiary Enrollment: - Enroll a beneficiary to one or many programs + - Tracking: + + Find Person: find person based on Name or ID, and Organization unit. + + + Activity Plan: Entries data for the persons by organisation-units, persons and programs/program-stages + + + Person Registration: Registry a new person + + + Anonymous: Entries for anonymous person based on programs + + - Messages: Manage the messages and discussions from the server. Message reply is available. - Reports: - The output reports from the server - - - Settings: - User-information (e.g: First-name, Surname, Phone number, E-mail) and the Interface language. - - Feedback: the extra function for creating a new message to send to the server. The new created feedback from this will be listed under "Messages" - - Logout: to log out the application - - Desktop version: navigate to the desktop version of DHIS2 for administration. This require a lof of resources from the client mobile, for example: the sufficient memory to load the pages. Not recommended for the nornal GPRS/3G/... phones. + The output reports from the server. + - Settings: User-information (e.g: First-name, Surname, Phone number, E-mail) and the Interface language. + - Feedback: the extra function for creating a new message to send to the server. The new created feedback from this will be listed under "Messages". + - Logout: to log out the application. + - Desktop version: navigate to the desktop version of DHIS2 for administration. This require a lot of resources from the client mobile, for example: the sufficient memory to load the pages. Not recommended for the normal GPRS/3G/... phones. The list above will be explained in details: @@ -53,7 +63,7 @@ - + @@ -101,8 +111,278 @@ - Name-based Data Entry: - Entries data for the beneficiaries by organisation-units, beneficiaries and programs/program-stages. + Tracking: + Find Person, Activity Plan, Person Registration, Anonymous + + + + + + + + 2.1 + Find Person + : find person based on Name or ID, and Organization unit. + + Step 1: insert Name or ID and select the Organization Unit, then click Search. + + + + + + + + + + Step 2: select a person + + + + + + + + Then all the information of that person will be displayed + + + Step 3: choose the next program stage for entering the data + + + + + + + + To view all the program stages, click on the name of that program (Child Heath Program as the screen shot) + + + + + + + + + + 2.2: Activity Plan: Choose An Organization Unit + + + + + + + + + + + + + + Current Activity Plan: the list of the beneficiaries registered, enrolled, not yet finish/complete a/many program and there is at least a program-stage open for data-entry. + + Step 1: Choose a Person for entry + + + + + + + + + Step 2: Choose a current and active program-stage for entering the data + + + + + + + + You can also see the person's information (ID, gender, Date of Birth, and Blood Group) by clicking on the Details (on top of the list appeared) + + + + + + + + The details information of the chosen person: + + + + + + + + + + All Activity Plan: the list of all beneficiaries registered, enrolled, not yet finish/complete a/many program. + + + Single Event: + + + + + + + + + + 2.3: Person Registration: Registry a new Person + Step 1: Entry personal information + + + + + + + Step 2: Enroll program for the person just been registered, then click "Enroll". + + + + + + + Step 3: Entry required information for the chosen program, then click "Enroll" + + + + + + Here is the result: + + + + + + + + 2.4: Anonymous: Entries for anonymous person based on specific programs + + + + + + + + + + Messages: + Manage the messages and discussions from the server. Message reply is available. + + + + + + + + The number showed is the unread messages. Click on that to view the list of the messages (the unread messages are in bold and dark blue color): + + + + + + + + Then you can pick up the message/topic for the discussions by leaving the reply message, see this example: + + + + + + + + + + + Reports: + The output reports from the server + + + + + + + + (will be updated) + + + + Settings: + User-information (e.g: First-name, Surname, Phone number, E-mail) and the Interface language. + + + + + + + + Here is the form for setting the user account/access and the interface language. Click on "SAVE" for completing the settings, see the example below: + + + + + + + + + + + Feedback: + the extra function for creating a new message to send to the server. The new created feedback from this will be listed under "Messages" + + + + + + + + After clicking on the "Feedback", there will be a form for editing/sending out a new message/discussion. See the example below: + + + + + + + + After sending out the new feedback, the message (feedback) will be listed under "Messages" for further following up. + + + + + + + + + + Logout: to log out the application + + + + + + + + + + + Desktop version: navigate to the desktop version of DHIS2 for administration. + + + + + + + + Here is the GUI of the desktop version (which require much memory for loading), not recommended for normal mobile. The example with DHIS2 Demo (from dhis2.org) + + + + + + + + + + + @@ -173,7 +453,7 @@ - + @@ -181,7 +461,7 @@ - + @@ -189,7 +469,7 @@ - + @@ -199,7 +479,7 @@ - + @@ -211,7 +491,7 @@ - + @@ -219,7 +499,7 @@ - + @@ -227,7 +507,7 @@ - + @@ -237,7 +517,7 @@ - + @@ -245,7 +525,7 @@ - + @@ -253,7 +533,7 @@ - + @@ -265,7 +545,7 @@ - + @@ -273,7 +553,7 @@ - + @@ -281,7 +561,7 @@ - + @@ -294,7 +574,7 @@ - + @@ -307,7 +587,7 @@ - + @@ -315,7 +595,7 @@ - + @@ -327,7 +607,7 @@ - + @@ -335,7 +615,7 @@ - + @@ -343,7 +623,7 @@ - + @@ -353,7 +633,7 @@ - + @@ -364,7 +644,7 @@ - + @@ -372,7 +652,7 @@ - + === modified file 'src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-feedback.png' Binary files src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-feedback.png 2012-04-27 09:21:00 +0000 and src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-feedback.png 2012-10-31 03:27:39 +0000 differ === modified file 'src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-logout.png' Binary files src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-logout.png 2012-04-27 09:21:00 +0000 and src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-logout.png 2012-10-31 03:27:39 +0000 differ === modified file 'src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-reports.png' Binary files src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-reports.png 2012-04-27 09:21:00 +0000 and src/docbkx/en/resources/images/dhis2_mobile_web_based/mobile-browser-reports.png 2012-10-31 03:27:39 +0000 differ