search

ctagroup / home-app

http://www.ctagroup.org/home-app/
Other
7 stars 5 forks source link

client profile: Workflow Discussion #54

Open desaiuditd opened 8 years ago

desaiuditd commented 8 years ago

Workflow

  1. Surveyor will login.
  2. He will search for existing clients
    1. This search would be supported by existing clients from HMIS API
  3. On selection, surveyor can go to client's profile page where he can see client details
    1. These details to be fetched from HMIS API
  4. Surveyor can create new client
    1. This new client should be synced at HMIS database
    2. Meteor app will have a sync script to keep all clients in sync at both ends (Meteor & HMIS)
  5. Surveyor can update client information from Meteor app
    1. This changes should be passed to HMIS API

      HMIS API Support

A app level setting for HMIS App ID & App Secret is given. Admin will setup these options and it will be used to access the HMIS API.

screen shot 2016-03-21 at 17 05 51

Ref: Home App Diagram PDF

screen shot 2016-03-21 at 15 06 43
suryayadavalli commented 8 years ago

Hello Udit, just wanted to ensure that you have all the information you need. Are you looking for any specific information to proceed with this work flow development ?

Also, the Trusted App ID and Trusted App secret are something we provided earlier ?

desaiuditd commented 8 years ago

Hi @suryayadavalli, I just wanted to make sure that the mentioned workflow is correct and that's how the client profile module is supposed to work.

E.g., HOME app will be connected only once with HMIS API (using /authorize, /token endpoints) and we will store those tokens (access, refresh, consent) within HOME app for future API calls. Is this correct?

suryayadavalli commented 8 years ago

Hi @desaiuditd , Yes, that is correct.

Consent is something you don't have to store with in the HOME APP, each time the app makes the call, HMIS platform will validate if the user consents the app to make the calls on his behalf .