C.5 Use Case Feature 4 - use case needs to be improved once device coupling is resolved
Open
Nobody has claimed this yet.
Ensemble
Volume 1
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Section Number
C5.4.3ff.
Priority
Medium
Issue
If backfilling is supposed to work, we need to define at least a validation mechanism and a way to assign data to a patient/location/ensemble.
Proposed Change
Add information to enable backfilling once the device coupling topic is resolved.
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.
Research direction
Start with section C5.4.3ff and review the unresolved device coupling topic, since the issue names no files, tests, or entry points. Define the validation mechanism and the assignment of backfilled data to a patient, location, or ensemble once that dependency is resolved; done means the specification contains those details.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100