Digests: for when you just want to stay in the loop

Update from Care Opinion tech

Posted by on

 

picture of James Munro

Patient Opinion subscribers know that we have a dizzying array of real-time alerts on offer. For example, we can tell you when a story or response is published, your response was rated helpful, or you've forgotten to follow up on a planned change. The alerts arrive in real-time to help you stay in control.

But some Patient Opinion users want something different: not "tell me as it happens" but "tell me what's been happening recently". If that sounds like you, we have something new for you: a digest.

What's a digest?

Thanks for asking. A digest is a weekly email (on a day of your choice) with an overview of what's happened in the past week. At this point, the digest includes:

  • recent stories, responses and changes
  • the three "most read" stories of the week
  • recent blog posts
  • total number of times your stories have been read

We have a few more things we'd like to add, and we'd like your feedback on what you would find useful too.

Can I have a digest just for my service or specialty?

Yes, you can. Like many things on Patient Opinion, you begin with a search, and then create the digest. So if you can search for it (by tags, services, treatment functions and so on) you can digestify it!

Can I have more than one digest?

Now you're getting carried away. But yes, you can have as many as you like.

How do I start my digest?

You create digests just like you might create alerts, reports or visualisations. You can either

  1. go to your saved things page, select the Digest tab, and start creating your digest, or
  2. search for the kinds of stories you want in your digest, and then click "save my search as" and select the Digest tab

Can everyone in my subscription have a digest right away?

Yes they can - but at this point we don't have a simple short-cut for creating all the digests at once. So if you think you'd like this, let us know and we can help you with it.

No responses to this post

This blog post is closed to responses.