Key Information

Register
Submit
The challenge is finished.

Challenge Overview

1.    Project Overview

1.1    System Description

This assembly must make changes in HPN qCare healthecare mobile application and APIs as per the attached list and enhancement authentication process as per the task below. 

1.2    Competition Task Overview

Time constraint
This project has tight timeline so
1) we would like to avoid any timeline extension, please ask questions early we will attempt to address them as quickly as possible.

Given that it is the Final assembly, it is supposed that any existing bugs you faced must be raised at the forum and fixed either by submitters or by previous contests supporting winner.

1.2.1. Authentication Updates Task overview

  1. Collect username and password and connect to client’s DBs: qMasterAuthentication (DDL attached). You need to configure SQL Server connection so that in QA and production it will be possible to access this DB deployed at Azure.  You must use data from this DB to figure out to which Product (ACO, HMO and/or PPO) and Service user is able to authenticate. You have to authenticate into each products master auth tables to see what product and services should be made available. More details are explained in the video posted at the forum, as well as details in the forums. Please note that if as per this DB user is entitled to access multiple Products/Services than the app must show a list of all available options for user to choose.
  2. Allow the user to select from a list of patients that they have access to, this is also stored in qMasterAuthentication DB.  Once a user is selected the system will authenticate to the user webservice and extract the user data to populate in the application.  More details in the forum.  
  3. The mobile device must not store any user data related to this application after the app is closed.
  4. Business workflow details can be found at the assembly forum http://apps.topcoder.com/forums/?module=Thread&threadID=861462&start=0&mc=1#2038921

Architecture-wise:

  1. SecurityService method maybe enhanced and/or appended with auxiliary methods that checks User ID, user group, product and service against the client’s DBs. This logic will reside in qCare back-end. It will also pull data from client's qMasterAuthentication.
  2. Since user is supposed to be authenticated by a fingerprint against the system overall (before matching to user group, product, company etc.) we need to implement a method which returns user ID by a fingerprint.

 

1.3    Approval phase

- The winner may be asked to merge the codebase into main branch and deploy it.

- Some minor UX/UI fixes may be requested by the client during approval phase.

- The winner may be provided with the access to the client's VM to set the sumbission up in UAT or production environment.



Final Submission Guidelines

Standard TC assembly deliverables:

 - updated working code

- updated deployment guide with verfication steps

A complete list of deliverables can be found in the TopCoder Assembly competition Tutorial at: http://apps.topcoder.com/wiki/display/tc/Assembly+Competition+Tutorials

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30050805