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
As a patient, I want Data Integration across: Medical records, fitness tracker data, dietary habits, and medication history.
So that I get more accurate diagnoses, personalized treatment plans, and proactive health management. For instance, combining fitness data with genetic information could guide lifestyle changes to prevent chronic diseases.
Preconditions:
What conditions must be in place or assumed before this use case can begin?
The patient must be a user of a LWS system with control of their data
Trigger:
What (user or system) event or action initiates this use case?
Actors:
Describe the primary actor, and any other relevant actors involved in this use case
The patient may be advised by doctor
Distinction:
What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?
Scenario:
Describe an ideal or happy-case scenario where this use case would play out as intended.
Combining fitness data with genetic information guides my lifestyle changes to mitigate the symptoms of my chronic disease, and gets me selected for the clinical trial of a personalized medicine which cures my condition.
Alternative case(s):
What alternative flows or variations should the system handle for this use case?
As a patient I may refuse permission for this integration or parts of it to be done.
Error scenario:
What unexpected issues or errors might arise, and how should the system handle them?
Acceptance Criteria:
What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?
All processing of any data only happens with my consent
Ethical guidelines are followed
Laws and regulations are followed
References:
List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.
There is a lot of research and there are projects win this space which do not use LDS (yet). Note the FHIR standards and HL7.
The text was updated successfully, but these errors were encountered:
acoburn: (Explained the issue content.) What kinds of labels do we want to add for it?
<bendm> authorization
<csarven> discovery + management
hadrian: I think many (e.g. authorization) are implicit and most use cases will be related to them. So we should add the most relevant ones.
<bendm> +1 on TallTed, that's why I'd add authorization
TallTed: This one may be extremely complex, if considering different laws. May not be a good starting point.
bendm: I think so, so I added authorization
<acoburn> eBremer
eBremer: I agree with TallTed. It's not the best thing we should start to tackle right now.
acoburn: I agree, but we should start to recognize that something are complicated. But we should always finish it in time-frame. … Even if complex, we should still try to categorize it, to help us progress.
<csarven> s/tackle right now. And, probably out of scope./
<eBremer> +1 TallTed
TallTed: Maybe still start with simpler ones, with one or two categories, to better demonstrate. This one, for me, contains all categories (which may be a good thing in fact). I'm sure we will get there, but not right now.
As a patient,
I want Data Integration across: Medical records, fitness tracker data, dietary habits, and medication history.
So that I get more accurate diagnoses, personalized treatment plans, and proactive health management. For instance, combining fitness data with genetic information could guide lifestyle changes to prevent chronic diseases.
Preconditions:
What conditions must be in place or assumed before this use case can begin?
The patient must be a user of a LWS system with control of their data
Trigger:
What (user or system) event or action initiates this use case?
Actors:
Describe the primary actor, and any other relevant actors involved in this use case
The patient may be advised by doctor
Distinction:
What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?
Scenario:
Describe an ideal or happy-case scenario where this use case would play out as intended.
Combining fitness data with genetic information guides my lifestyle changes to mitigate the symptoms of my chronic disease, and gets me selected for the clinical trial of a personalized medicine which cures my condition.
Alternative case(s):
What alternative flows or variations should the system handle for this use case?
As a patient I may refuse permission for this integration or parts of it to be done.
Error scenario:
What unexpected issues or errors might arise, and how should the system handle them?
Acceptance Criteria:
What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?
References:
List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.
There is a lot of research and there are projects win this space which do not use LDS (yet). Note the FHIR standards and HL7.
The text was updated successfully, but these errors were encountered: