search

jupyterhealth / jupyter-health-software

A repository to track issues for the JupyterHealth Software Team
0 stars 0 forks source link

Share docs on the TCP stuff (refactor this issue as you see best) #6

Closed colliand closed 3 months ago

colliand commented 3 months ago

Task captured from team discussion on 2024-03-20.

surfdoc commented 3 months ago

This is the general architecture document along with a technical specifications document for the CommonHealth Android Application, CommonHealth Cloud Storage Service (Reference Server), and the CommonHealth Partner Client (Lightweight Python Client for partners to use). Note this document is a work in progress and will be updated. I am linking to where these are found in the Jupyter Health Google Drive so that the documents can be dynamically updated. Architecture Diagram: https://drive.google.com/file/d/1JupkAcP1CHlhOW6qnQib5s29lqOWm-8U/view?usp=sharing Technical Documentation: https://docs.google.com/document/d/1E7t16ok_mUHA5hYVsTQA5MbCruX0DS_Rqsq37dZ48fs/edit?usp=sharing

Let me know if you have any questions. The team is working on getting the client setup with Docker and will share with team hopefully by end of next week.

minrk commented 3 months ago

Thanks! That looks good. If I understand correctly, that means the next step is for you (TCP) to register JupyterHealth client application(s), and I believe we can start testing from there.

Is that right? If so, can you register two clients, one for JupyterHealth-PreMVP, and another JuptyerHealth-PreMVP-testing?

I don't think we've decided on a mechanism for securely distributing secrets. Do you have any preferences?

surfdoc commented 3 months ago

@minrk - I will add both and share credentials once we have the partner client ready for use. We hope will be soon. We use 1Password to share secrets. It will send you a one time link that expires.