A department asks you to resolve a gap in one of its workflows. You agree that the request is reasonable and promise to look into it.

Suppose the request refers to a certain functionality in a specific solution area. Knowing who in your team can address the issue is straightforward. But who can consider all solutions and configuration options?

The solution for a particular workflow gap could be anywhere: an additional column in a Request List may help, or a Pre-Processing script could resolve the issue.

I help my clients find options for implementing requirements across various solutions and functionalities.

Following is a recent example: a client asked me how they can identify a population of patients. Dynamic WorkLists was the first option we considered. After discussing the design options, we concluded that for this scenario, we would do the following:

1. We will create a new modify-person conversation with user-defined fields.
2. Nurses are to run the conversation from PMConversations in PowerChart to include or exclude patients from this population.
3. Nurses can see patients in a custom patient list implemented with CCL, HTML, and CSS.
4. Nurses can click on the patient's name from the custom patient list to open the patient's chart.

We could design a workflow with which the end-users were very happy. Having someone who understands the request and, at the same time, knows what options are available made it much easier to reach this design.