Skip to content

Feature/finalize fhir rdf #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
beauvangemert1990 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Feature/finalize fhir rdf #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aed9dc0
Update headings in primary-use-case.md for consistent markdown structure
rolandgroen Dec 5, 2025
4f1ee95
Fix FHIR folder to write to.
beauvangemert1990 Dec 19, 2025
67bdf2f
Merge branch 'main' into feature/finalize-fhir-rdf
beauvangemert1990 Dec 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions input/pagecontent/dynamic-data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

`<user pod>/weare/https%3A%2F%2Fwww.hl7.org%2Ffhir%2FPatient/<uuid>.ttl`
`<user pod>/weare/http%3A%2F%2Fwww.hl7.org%2Ffhir%2FPatient/<uuid>.ttl`

Information that will be stored in the resource:
- Gender
Expand All @@ -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)

`<user pod>/weare/https%3A%2F%2Fwww.hl7.org%2Ffhir%2FObservation/<uuid>.ttl`
`<user pod>/weare/http%3A%2F%2Fwww.hl7.org%2Ffhir%2FObservation/<uuid>.ttl`

Each observation should be stored in its individual resource with a unique uuid as shown above.

Expand Down Expand Up @@ -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:

`<user pod>/weare/https%3A%2F%2Fwww.hl7.org%2Ffhir%2FQuestionnaireResponse/<uuid>.ttl`
`<user pod>/weare/http%3A%2F%2Fwww.hl7.org%2Ffhir%2FQuestionnaireResponse/<uuid>.ttl`
20 changes: 10 additions & 10 deletions input/pagecontent/primary-use-case.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -22,17 +22,17 @@ 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.
- Authentication results in the portal receiving an **access token** containing the user's WebID.

---

####### 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**:
Expand All @@ -49,26 +49,26 @@ 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).
3. Responses are confirmed and the next question is rendered.

---

####### 4. Analysis
##### 4. Analysis
- Upon questionnaire completion, **Selfcare** sends the responses to **Zipster**.
- **Zipster**:
1. Processes the responses.
Expand All @@ -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.
Expand Down