Page Comparison

Background 

In today's health informatics ecosystem, there is no standard way to write an "App" that interacts with patient-level health data. Just as OpenMRS allows extensibility through modules, every EMR provides its own distinct extensibility interfaces. The result is a heterogeneous landscape where it's very difficult to deploy a single app across multiple systems.

...

• Questions to ponder
  • How to install a SMART app?
  • Is it worth implementing the REST api instead of the direct javascript connect POST methods?
  • How to require that concepts be mapped to the vocabularies SMART uses (SNOMED for problems, RxNorm for medications)

...

The folowing UI allow administer to install new apps or remove apps that are already installed.The appropriate place to display this UI is Administration->manage smartapps.
While administrator wants to add new SMART Apps he have to click on add button in above UI.This will give a popup window that allow administrator to up load a SMART App manifest or give a link to a manifest file.

Database Table Design
The module has to manage installed application and user.The information regarding apps and user have to be modeled to save in to the database.OpenMRS already has user object(can be found here),so the details about this object is avoided.

...

• Implementation of data model
  • Creating required database tables --Done
  • Creating required basic classes(App,AppService....) --Done
• Implementation of UIs
  • Installing module will create
    • A tab in patient dashboard --Done
    • A horizontal tab in user option page --Done
    • A link in Admin page --Done
  • Creating main page at patient dashboard --Done
  • creating manage app page at user option page --Done
  • Creating manage app page and app upload window at admin page --Done

• Implementation of SMARTAPIService
  • Creating RDF Service --Done
  • Creating Concept Mapping Service --Done
  • Creating method to access patient demographics, drugs and problems --Done

 (Above goals will be achieved before midterm evaluation )

• Enhancing SMART API --Exposed Lab Result and Vital Sign**
•  Adding Extra methods to SMARTAPIService and Controllers --Done
• Adding Authentication --Instead of adding authentication the code was reorganized 
• Documentation
  • Technical design documentation --Done
  • User documentation

Extra Credit(If time permit)

• Develop methods for access to users  --Done
• Develop methods for access to allergies
• Develop methods for access to labs  --Done

Detailed Time Line