Add optional fields in visits
Visits, as are implemented now, have a fixed number of fields with a fixed meaning. The idea of giving to the user the possibility to choose the fields was discarded at the start of the project because that would have been added a not-so-useful layer of complexity to the management of the patients. It would be nice, though, to be able to add custom fields to every visit on per-visit basis.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Leonardo Robol
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
You should be able to rename some fields, in particular the "Histopathology" field to suit your particular needs.
In my opinion, Histopatology is one of the least common diagnostic tools. ECG or x-rays are more common. You could consider adding "ECG" and "Diagnostic imaging" fields in the fu=rture releases.
- Łukasz Cieliński
From further discussion, we have reached the conclusion to choose the following strategy:
1) Implement just the basic fields in the standard visits
2) Make a visit expandable with custom fields
3) Let a user choose which extra fields should be present by default
- Leonardo Robol
Work Items
Work items:
Rework the Visit object to have a custom number of extra fields: TODO
Extend SqliteDataProvider to handle the database upgrade: TODO
Adapt SqliteDataProvider to handle this: TODO
Adapt NetworkedDataPr
Adapt DataServer to format the Json data accordingly to the changes: TODO
Change the VisitTap UI to make it possible to view a custom number of fields and add/remove them: TODO
