You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Technical_flow.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,9 @@ Streams structure of a Dr Account
18
18
- patients-validated: contains validated patient
19
19
(credentials are moved from Inbox in this stream)
20
20
- Forms
21
-
- Questionnary A
22
-
- Questionnary B
23
-
- Questionnary ...
21
+
- Questionnaire A
22
+
- Questionnaire B
23
+
- Questionnaire ...
24
24
25
25
```
26
26
@@ -84,13 +84,13 @@ This will allow the Patient's app to publish it's authorization to the Dr's Acco
84
84
85
85
##### Flow Patient Web App
86
86
87
-
The link to the patient webApp contains in its query the Dr's apiEndpoint
87
+
The link to the patient webApp contains in its query the Doctor's apiEndpoint
88
88
89
-
1- The WebApp query HDS to figure out which questionnary to display (hardcode 1st version)
89
+
1- The WebApp query HDS to figure out which questionnaire to display (hardcode 1st version)
90
90
91
91
2- The WebApp present the description of HDS, the recipient of the form (the Dr) and propose to register or login in
92
92
93
-
3- After Log-In the App recieves and API endpoint
93
+
3- After Log-In the App receives and API endpoint
94
94
95
95
- The app check the state of this form with the latest event in `demo-dr-form` stream event-type `demo-dr-form-state/questionnary-x`
96
96
- If this is the first time the use logs-in with this form the WebApp creates and `sharing` api-endpoint for the Dr and publish it in his `inbox` stream
0 commit comments