This issue is for tracking milestones and process toward a registry indicators of recent patient entry.
Underlying work occurred in:
513.
514.
515.
516.
517.
518.
520.
522.
523.
524.
525.
526.
527.
530.
This includes several enhancements to the registry PatientStore.
[x] Adds recentEntryCutoffDateTime to patient store.
Defines when "recent entry" begins for each patient.
Currently defined as the past two weeks.
Eventually, could calculate a per-patient cutoff based on social worker marking a patient's data as reviewed.
Development history:
Started in #513.
Updated in #514:
Defined as now minus two weeks, based on a conversation with Jesse.
[x] Refer to as "Entry" rather than "Interaction" or "Activity".
Appears in code naming, let's consistently use recentEntry for related code.
Consistently applied in #522.
Appears in tooltip.
Edited in #523.
[x] "Recent Patient Entry" is consistently defined in terms of "from the point of view of the social worker accessing the registry".
A session / case review is not "recent patient entry", as the provider enters those.
An assessment is "recent patient entry".
A mood log is "recent patient entry".
An activity log is "recent patient entry".
Any value addition or edit is "recent patient entry".
Add activity addition or edit is "recent patient entry".
Any edit of the safety plan is "recent patient entry".
The client does not have access to the history of the document, cannot be more detailed.
A new activity schedule could be considered "recent patient entry", but currently is not.
[x] Define properties that filter "recent entry".
These are intentionally filters (e.g., not a simple count) so they can be used in rendering.
These are generally be derived from the fields that are SortedByDateAndTimeDescending.
These then have a similar name, such as recentEntryActivityLogsSortedByDateAndTimeDescending.
These are generally implemented using findIndex to slice the existing sorted elements.
Some documents do not have a sort defined by DateAndTimeDescending (e.g., an edit to an Activity), because they are never used / presented by that sort (e.g., Activities are instead sorted alphabetically). Those may be handled differently, just as a filter to obtain the "recent interaction".
This issue is for tracking milestones and process toward a registry indicators of recent patient entry.
Underlying work occurred in:
513.
514.
515.
516.
517.
518.
520.
522.
523.
524.
525.
526.
527.
530.
This includes several enhancements to the registry PatientStore.
[x] Adds
recentEntryCutoffDateTime
to patient store.[x] Refer to as "Entry" rather than "Interaction" or "Activity".
recentEntry
for related code.[x] "Recent Patient Entry" is consistently defined in terms of "from the point of view of the social worker accessing the registry".
[x] Define properties that filter "recent entry".
SortedByDateAndTimeDescending
.recentEntryActivityLogsSortedByDateAndTimeDescending
.findIndex
to slice the existing sorted elements.DateAndTimeDescending
(e.g., an edit to an Activity), because they are never used / presented by that sort (e.g., Activities are instead sorted alphabetically). Those may be handled differently, just as afilter
to obtain the "recent interaction".[x] Adds a caseload overview indication of which patients have recent entry.
[x] In the patient detail contents menu, adds a simple indication of the recent entry cutoff.
[x] In the patient detail contents menu, adds badges for specific types of recent entry.
[x] Updates registry view of Values & Activities Inventory to show values that do not have any associated activity.
[x] Adds row highlights to indicate specific new entries in corresponding portions of patient details.
[x] Development included creation and removal of a
RecentInteraction
component:Issues that are known to be outstanding:
[x] Provide support for clearing "New" data by updating the cutoff date.
528.
[x] Review recent entry calculations to check that filters are correct in terms of time zones.
529.
[x] A new activity schedule could be considered "recent patient entry", but currently is not.
recentScheduledActivitiesSortedByDateAndTimeDescending
is currently calculated but not rendered anywhere in the registry.531.