Records For Living Community

One aspect of medical ‘care’ these days is communication with the receptionist, referral coordinator, admin assistant, etc… those other than the doctor or nurse. Conceivably Encounters>Communication category is intended for, let’s say, the ‘medical’ aspects where the Individuals and Organizations are the primary players. In a question, is the Encounters>Communication category intended to include the administrative ‘support’ personnel as Provider>Individuals? The reports include these support personnel if logged as ‘Individuals’ within the Organization, which seems inappropriate. On the other hand, having the names/duties and logging certain communications with these people is important too.

            HealthFrame may have a better solution, but consider adding an input field in the Individuals>Provider(New) area to identify the person as primary (to be included in the Provider reports) or support (not in the Provider reports).Is there an existing approach that would satisfy this situation?

Dear Robert,

Thanks for bringing up this particular use case scenario.

To recap, it is useful to:

1. Track individuals who are part of the support staff (e.g. administrators)
2. Track communications with support staff (in addition to communications with medical staff)
3. Be able to suppress listing support staff in reports that list 'providers'

First, let me start by saying that - as we've mentioned before in the forum - improving our data filtering abilities in future releases is one of our key objectives.  If we had a more robust filtering mechanism, you'd be able to enter certain individuals as 'administrative support personnel' and when you wished to generate a report with a list of providers, you could then filter out all 'administrative support personnel'.  Does this seem like something that would be useful to you?  Alternativelly, we could 'default' filtering behavior so that support personnel would be typically excluded from reports.

With the current release, you can do something similar with customizations.  Please assume you've taken these steps:

1. Create an 'individual provider' whose role reflects the administrative support nature of their job, e.g. 'administrative assistant'
2. Assume you've exchanged some communications with this individual and you use the communications feature to track those communications
3. Now you want to print a report that includes providers - for instance the Health Care Providers Summary and you'd like to not have the support staff be listed in the report.

What you should do is create a (named) customization that excludes those individuals from the report:

• Click on the customization/ellipsis (...) button on the navigation/title bar.  Select the Edit Customization... menu item
• Click on the Providers tab and select the ones you want to exclude (you can use shift-click or control-click if you're selecting multiple providers)
• Click on the << Remove << button
• Click on the OK button (Note that the ellipsis changes to indicate you have customized the default settings...)
• Click again on the customization button and select the Save Customization As...  Enter the name of your customization and click OK.  Note the navigation/title bar has changed to indicate the active customization.
• From now on, for the customized report, you can now select the customization you created and eliminate the selected providers.

Thanks again for the suggestion,

Support Team

Records For Living

Relative to your question - "..... filter out all 'administrative support personnel'.  Does this seem like something that would be useful to you?  Alternativelly, we could 'default' filtering behavior so that support personnel would be typically excluded from reports.".

I would like to be able to properly identify the support personnel with specific titles like 'nurse', 'receptionist', etc., not just 'admin support'. Default filtering support persons out of reports sounds reasonable, but having a selection box to include or exclude each individual seems more appropriate and flexible.

Thanks for the further clarification!

Support Team