A social worker should be able to mark that they have reviewed a patient's recent entries, that patient will then not flag as "New" until they enter more data.
PatientDetailPage includes a stub of the interface for this, currently commented.
[x] Requires a new type of document, with associated schema and endpoints.
Perhaps recentEntryReview.
Implemented as a set, so the client has access to the history of marks.
Include two DateTime:
When the mark was created (e.g., like an edited time).
When the mark is effective (e.g., to support your undo / rollback proposal).
Does the AuthStore allow us to know who the provider is, to include that in the document?
[x] recentEntryCutoffDateTime will then be calculated from these documents.
[x] And the button stubbed in PatientDetailPage will create a new document.
The created datetime and the effective datetime will be the same.
[x] An "Undo Previous Mark" text button can then revert marks.
It identifies the most recent mark which is less than the current effective mark (e.g., filter all that are less than the current effective mark, then take the max of those).
Disabled if there is no mark less than the current effective mark (e.g., this seems to be the same filter).
jayfo
commented
1 month ago
A social worker should be able to mark that they have reviewed a patient's recent entries, that patient will then not flag as "New" until they enter more data.
PatientDetailPageincludes a stub of the interface for this, currently commented.[x] Requires a new type of document, with associated schema and endpoints.
recentEntryReview.AuthStoreallow us to know who the provider is, to include that in the document?[x]
recentEntryCutoffDateTimewill then be calculated from these documents.[x] And the button stubbed in
PatientDetailPagewill create a new document.[x] An "Undo Previous Mark" text button can then revert marks.