Difference between revisions of "PHEM"
(28 intermediate revisions by 3 users not shown) | |||
Line 5: | Line 5: | ||
== Group Members == | == Group Members == | ||
− | *Alexander Premer | + | *<span style="color:#000000"><span style="background-color:#00ff00">Alexander Premer</span></span> |
− | *Henning G Koller | + | *<span style="color:#000000"><span style="background-color:#00ff00">Henning G Koller</span></span> |
− | *Emil F Østensen | + | *<span style="color:#000000"><span style="background-color:#00ff00">Emil F Østensen</span></span> |
− | *Martin T Vasbotten | + | *<span style="color:#000000"><span style="background-color:#00ff00">Martin T Vasbotten</span></span> |
+ | |||
+ | == Dropouts == | ||
+ | |||
+ | *<span style="background-color:#ff0000">NaN</span> | ||
== Link to repository == | == Link to repository == | ||
Line 19: | Line 23: | ||
::Doctors in the field often have a heavy workload and this can result in discrepancies between the various journals that are stored on the patients. Journals exists in both paperform and in a database. It's important that the database and the papers contains exactly the same information. Therefore a system is needed to easily check that the physical and digital copies are uniform.<br/> | ::Doctors in the field often have a heavy workload and this can result in discrepancies between the various journals that are stored on the patients. Journals exists in both paperform and in a database. It's important that the database and the papers contains exactly the same information. Therefore a system is needed to easily check that the physical and digital copies are uniform.<br/> | ||
+ | ::<br/> | ||
+ | |||
+ | === Planned Features === | ||
+ | |||
+ | The app will consist of two pages. On the first page you will be able to choose program and clinic. After selecting, you will be redirected to the main page. This is where you will fill out the quality-assurance form. The form is dynamically generated from the data elements connected to the application in DHIS. After filling the form and submitting, the form will reset and be ready for a new patient. | ||
=== Summary of requirements === | === Summary of requirements === | ||
Line 32: | Line 41: | ||
*Store the data sent from frontend in a database. | *Store the data sent from frontend in a database. | ||
− | = Architecture = | + | == Architecture == |
+ | |||
+ | We plan on using HTML, CSS, Bootstrap and AngularJS to implement a webpage. On the backend side we'll use javascript. | ||
==== Technology ==== | ==== Technology ==== | ||
− | + | *HTML | |
+ | *CSS | ||
+ | *Bootstrap | ||
+ | *Javascript | ||
+ | |||
+ | #AngularJS | ||
== Time schedule == | == Time schedule == | ||
Line 73: | Line 89: | ||
=== Frontend === | === Frontend === | ||
− | |||
− | |||
*Emil F Østensen | *Emil F Østensen | ||
Line 83: | Line 97: | ||
*Henning G Koller | *Henning G Koller | ||
*Martin T Vasbotten | *Martin T Vasbotten | ||
+ | |||
+ | == == | ||
+ | |||
+ | == Progress == | ||
+ | |||
+ | *We are nearly completed both pages and getting data from DHIS. We have also been able to deploy it as a DHIS webapp. | ||
+ | *Startpage is finished. Programs and clinics are retrived from DHIS. | ||
+ | *Formpage is building a correct table dynamically to the dataElements in the program. | ||
+ | *Payload is building correctly from the table. | ||
+ | *Formpage is more or less finished. | ||
+ | *Both pages need some polishing. | ||
== Screenshots and screen flows == | == Screenshots and screen flows == | ||
+ | |||
+ | Screen Flow: | ||
+ | |||
+ | |||
+ | |||
+ | https://wiki.uio.no/mn/ifi/inf5750/images/b/b0/Flowchart2.png | ||
+ | |||
+ | 1. You start at the index page where you select a program and a clinic. | ||
+ | |||
+ | 2. At the form you manually tick off the boxes that contain info in the different artifacts. | ||
+ | |||
+ | 3. When pushing submit you are taken back to a clean form. | ||
+ | |||
+ | You can not go back to index-page from the form (without going back in the browser).<br/>It's designed this way, because once you have selected the correct clinic, you will never want to switch in the current session. | ||
+ | |||
+ | <br/>[[File:Index.png|border|none]] | ||
+ | |||
+ | <br/>The index page, where you select program and clinic, you can also search for clinics. | ||
+ | |||
+ | |||
+ | |||
+ | [[File:Flow.png|border|none]] | ||
+ | |||
+ | <br/>The flow-chart where you tick of boxes. | ||
== Documented learning during project == | == Documented learning during project == |
Latest revision as of 15:07, 24 November 2014
Contents
- 1 PHEM
- 1.1 Group Members
- 1.2 Dropouts
- 1.3 Link to repository
- 1.4 Tool for Quality Assurance
- 1.5 Architecture
- 1.6 Time schedule
- 1.7 How you are dividing tasks within the group
- 1.8
- 1.9 Progress
- 1.10 Screenshots and screen flows
- 1.11 Documented learning during project
- 1.12 Suggested improvements to APIs
- 1.13 Download link to sample web app or Android app
PHEM
This Wiki is used for documenting the group projects by PHEM
Group Members
- Alexander Premer
- Henning G Koller
- Emil F Østensen
- Martin T Vasbotten
Dropouts
- NaN
Link to repository
Tool for Quality Assurance
The task is to develop an app for registering consistency between hard copies and database.
- Doctors in the field often have a heavy workload and this can result in discrepancies between the various journals that are stored on the patients. Journals exists in both paperform and in a database. It's important that the database and the papers contains exactly the same information. Therefore a system is needed to easily check that the physical and digital copies are uniform.
- Doctors in the field often have a heavy workload and this can result in discrepancies between the various journals that are stored on the patients. Journals exists in both paperform and in a database. It's important that the database and the papers contains exactly the same information. Therefore a system is needed to easily check that the physical and digital copies are uniform.
Planned Features
The app will consist of two pages. On the first page you will be able to choose program and clinic. After selecting, you will be redirected to the main page. This is where you will fill out the quality-assurance form. The form is dynamically generated from the data elements connected to the application in DHIS. After filling the form and submitting, the form will reset and be ready for a new patient.
Summary of requirements
Frontend
- Create a web page with a user interface for registering the difference and equality in the artifacts.
- The data registred is to be sent to backend.
Backend
- Fetch the forms from a database and present it to frontend.
- Store the data sent from frontend in a database.
Architecture
We plan on using HTML, CSS, Bootstrap and AngularJS to implement a webpage. On the backend side we'll use javascript.
Technology
- HTML
- CSS
- Bootstrap
- Javascript
- AngularJS
Time schedule
Milestones
Date |
Milestone |
1st November |
Document features and architecture on Wiki Show understanding of DHIS2 web apps |
15th November |
First bare-bone version - static HTML Uploadable as DHIS2 web app |
30th November |
Finished, if applicable also with mobile app. |
8th December |
Final delivery |
How you are dividing tasks within the group
Frontend
- Emil F Østensen
- Alexander Premer
Backend
- Henning G Koller
- Martin T Vasbotten
Progress
- We are nearly completed both pages and getting data from DHIS. We have also been able to deploy it as a DHIS webapp.
- Startpage is finished. Programs and clinics are retrived from DHIS.
- Formpage is building a correct table dynamically to the dataElements in the program.
- Payload is building correctly from the table.
- Formpage is more or less finished.
- Both pages need some polishing.
Screenshots and screen flows
Screen Flow:
1. You start at the index page where you select a program and a clinic.
2. At the form you manually tick off the boxes that contain info in the different artifacts.
3. When pushing submit you are taken back to a clean form.
You can not go back to index-page from the form (without going back in the browser).
It's designed this way, because once you have selected the correct clinic, you will never want to switch in the current session.
The index page, where you select program and clinic, you can also search for clinics.
The flow-chart where you tick of boxes.