You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User-reported improvements on bridge tables, thank you @selinapatel1
Bridge tables are currently focused on producing rates for a given set of episodes or encounters.
This does not easily cater for users who would like to drill down by day.
Bridge tables could have a 'day drill' function to allow users to easily report for whatever period they are interested in, discarding the part of episodes/encounters that fall outside this date.
As part of this we could rethink bridge tables more fundamentally with an OLAP/data cube design.
Bridge tables are currently designed for medication as prescribed, not as administered. Bridge tables should offer both.
The text was updated successfully, but these errors were encountered:
User-reported improvements on bridge tables, thank you @selinapatel1
This does not easily cater for users who would like to drill down by day.
Bridge tables could have a 'day drill' function to allow users to easily report for whatever period they are interested in, discarding the part of episodes/encounters that fall outside this date.
As part of this we could rethink bridge tables more fundamentally with an OLAP/data cube design.
The text was updated successfully, but these errors were encountered: