Difference between revisions of "PHEM"

From mn/ifi/inf5750
Jump to: navigation, search
Line 106: Line 106:
 
We have started implementing both pages and getting data from DHIS. We have also been able to deploy it as a DHIS webapp.
 
We have started implementing both pages and getting data from DHIS. We have also been able to deploy it as a DHIS webapp.
  
== Screenshots and screen flows[[File:Formview.png|none]] ==
+
== Screenshots and screen flows ==
 +
 
 +
<br/>[[File:Indexview.png|left]]
  
 
== Documented learning during project ==
 
== Documented learning during project ==

Revision as of 14:17, 12 November 2014

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.

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.

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
  • Bootstrap-table
  • Javascript
  1. AngularJS
  2. jQuery

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 have started implementing both pages and getting data from DHIS. We have also been able to deploy it as a DHIS webapp.

Screenshots and screen flows


Indexview.png

Documented learning during project

Suggested improvements to APIs

Download link to sample web app or Android app