Building: In Basket Pools
Epic InBasket pools are like a group inbox where one person can respond to a message, and it disappears for other members after it's marked as complete. This differs from Classes in Epic, where all users receive the same message individually.
To configure a channel to route incidents to an In Basket Pool, go to manage study > personnel > scroll to the bottom of the page and click the [+new channel] button.
Channel Name: the name for the channel in the W2H system
Pool ID: 6-12+ digit number in PennChart/Epic corresponding to the pool.
The number appears after the Pool name (i.e., POGA COVERING PROVIDER (210138065) has a Pool ID of 210138065). You can ask the project team to provide this to you or login to PennChart, make your way to your In Basket, and search for the Pool by name.
Message Type: corresponds to the folder to which the messages will be routed in PennChart.
1 = Staff messages, default value
2104242026 = Way to Health custom folder, new as of May 2025
Access groups: Select which groups' patient incidents should route to the InBasket Pool you’ve configured.
W2H looks at the union of the selected groups. For example, if HUP/PCAM and PAH were selected for the channel below, patients pertaining to either group would have their incidents routed to the same InBasket Pool.
If no access groups are selected, then all patient incidents will route to the Pool.
Incident types: toggle which incident types should send to the Pool
Way to Health custom folder
As of May 2025, Penn IS created a custom Way to Health folder to which we can route incidents. This way, the automated escalations from Way to Health programs don’t clog up pools' staff msg folders, which are otherwise used for staff to send non-critical messages to each other. We can update channels to route messages to the new folder by modifying the message type from 1 to 2104242026.
Note: I believe that each InBasket Pool has its own set of folders to which messages are routed, as shown below. The Way to Health folder can hold messages for any Pool, but only users who are logged into that Pool will see those messages.