C.3 Use Case Feature 2: Device coupling & patient conflicts
Open
@AnnaFeiler is already working on this.
Since Feb 3, 2023.
Ensemble
Volume 1
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Section Number
C.3 Use Case Feature 2: C.3.3 & C.3.4
Priority
Medium
Could be postponed to version 1.1
Issue
How do we handle conflicting patient information?
This needs to be solved together with the whole device coupling discussion.
Proposed Change
Describe device coupling mechanism (patient vs. location based) and add a use case like:
Given: Dashboard can connect to devices providing patient information (patient context)
When: The patient information is contradicting.
Then: The Dashboard will display an error message.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.