diff --git a/input/pagecontent/dynamic-data.md b/input/pagecontent/dynamic-data.md index 5b3deb8..aa8cf78 100644 --- a/input/pagecontent/dynamic-data.md +++ b/input/pagecontent/dynamic-data.md @@ -14,7 +14,7 @@ All information in Welldata will be placed under the following root container of Information about the patient that fits in the FHIR resource [patient](https://www.hl7.org/fhir/patient.html) must be stored at the following location: -`/weare/https%3A%2F%2Fwww.hl7.org%2Ffhir%2FPatient/.ttl` +`/weare/http%3A%2F%2Fwww.hl7.org%2Ffhir%2FPatient/.ttl` Information that will be stored in the resource: - Gender @@ -27,7 +27,7 @@ Information that will be stored in the resource: ### Observation Observations are stored in the pod at the following location as a [FHIR resource](https://www.hl7.org/fhir/observation.html) -`/weare/https%3A%2F%2Fwww.hl7.org%2Ffhir%2FObservation/.ttl` +`/weare/http%3A%2F%2Fwww.hl7.org%2Ffhir%2FObservation/.ttl` Each observation should be stored in its individual resource with a unique uuid as shown above. @@ -152,4 +152,4 @@ Please find other kinds of observations here: [Artifacts Summary - WellData Impl A resource of the type QuestionnaireResponse is stored as a [FHIR resource](https://www.hl7.org/fhir/questionnaireresponse.html) at the following location in the users's pod: -`/weare/https%3A%2F%2Fwww.hl7.org%2Ffhir%2FQuestionnaireResponse/.ttl` +`/weare/http%3A%2F%2Fwww.hl7.org%2Ffhir%2FQuestionnaireResponse/.ttl` diff --git a/input/pagecontent/primary-use-case.md b/input/pagecontent/primary-use-case.md index 4b66c0d..62ab920 100644 --- a/input/pagecontent/primary-use-case.md +++ b/input/pagecontent/primary-use-case.md @@ -8,7 +8,7 @@ The following sequence diagram describes user interactions and backend processes --- -###### Key Participants and Their Roles +#### Key Participants and Their Roles - **User**: The end-user interacting with the system. - **Well Data Portal (portal)**: Provides access and acts as a gateway to various services. - **Athumi Approved IdP (idp)**: Handles Solid OIDC login for authenticating the user. @@ -22,9 +22,9 @@ The following sequence diagram describes user interactions and backend processes --- -###### Grouped Processes in the Diagram +#### Grouped Processes in the Diagram -####### 1. Login +##### 1. Login - **User** accesses the Well Data Portal (**portal**). - **Portal** redirects the user to **IdP** for login. - User authenticates with **Athumi Approved IdP (idp)** using Solid OIDC login. @@ -32,7 +32,7 @@ The following sequence diagram describes user interactions and backend processes --- -####### 2. Launch +##### 2. Launch - The user selects **Selfcare** from the **portal**. - **Portal** redirects the user to **Selfcare** with an HTI launch, passing the WebID. - **Selfcare**: @@ -49,18 +49,18 @@ The following sequence diagram describes user interactions and backend processes --- -####### 3. Questionnaire -######## Steps: +##### 3. Questionnaire +###### Steps: 1. The user selects a questionnaire in **Selfcare**. 2. **Selfcare** requests an **FHIR questionnaire** from **Zipster**, which sends back the questionnaire. 3. The questionnaire is displayed to the user by **Selfcare**. -######## Data Retrieval: +###### Data Retrieval: - **Selfcare** may load existing FHIR data from the **User POD**, based on: - **Access grants** retrieved from **Athumi VC Service (avcs)**. - Identifiers (e.g., SNOMED concepts) that inform which resources to use. -######## Data Entry: +###### Data Entry: - The user fills out the questionnaire in **Selfcare** through an iterative process: 1. Each response is submitted to **Selfcare**. 2. **Selfcare** updates the questionnaire responses in the **User POD** (under the `/questionnaireresponse` container). @@ -68,7 +68,7 @@ The following sequence diagram describes user interactions and backend processes --- -####### 4. Analysis +##### 4. Analysis - Upon questionnaire completion, **Selfcare** sends the responses to **Zipster**. - **Zipster**: 1. Processes the responses. @@ -80,7 +80,7 @@ The following sequence diagram describes user interactions and backend processes --- -###### Key Notes from the Diagram +#### Key Notes from the Diagram 1. **HTI Launch**: The purpose of passing the WebID via the HTI launch is questioned in the diagram. 2. **FHIR Questionnaires**: - Existing FHIR data from the POD could be used in the questionnaire.