Ccm 17046 new feature pages#234
Conversation
|
|
||
| - [national programmes (like screening or vaccination programmes)]({% link pages/about/national-programmes.md %}) | ||
| - [suppliers of technology services to primary care (GP IT)]({% link pages/about/gpit.md %}) | ||
| - [secondary care organisations]({% link pages/about/secondary-care.md %}) |
There was a problem hiding this comment.
Just a minor thing but do we also want to include the examples of secondary care orgs in brackets like we do for national programmes?
| @@ -5,9 +5,9 @@ | |||
| layout: page | |||
| title: Event based messaging | |||
There was a problem hiding this comment.
Think we need a hyphen for 'event-based' throughout as it's describing a thing
|
|
||
| When you send NHS App messages as part of a campaign with NHS Notify, you must adhere to the following in any onward user journeys: | ||
|
|
||
| - any links should only open a patients web browser |
There was a problem hiding this comment.
apostrophe for 'patient's web browser'
|
|
||
| ## Who can use direct messaging | ||
|
|
||
| Direct messaging with NHS Notify is recommended for organisations, services or GPIT suppliers in secondary care. |
There was a problem hiding this comment.
I'm not sure I understand this sentence - are we saying it's only recommended for these groups in secondary care? There's a bullet underneath referring to primary care.
|
|
||
| ## Examples of campaign messaging | ||
|
|
||
| Create messaging campaigns with NHS Notify to send: |
There was a problem hiding this comment.
Might be better to say 'You could create messaging campaigns with NHS Notify to send:' so it highlights that this is just an example list. Currently, it could be interpreted as a comprehensive list.
|
|
||
| ## Examples of event based messaging | ||
|
|
||
| When an event is triggered you could use NHS Notify to automatically send: |
There was a problem hiding this comment.
add a comma after 'triggered'
|
|
||
| Emails and text messages will fallback to the next channel if they are not delivered after 72 hours. | ||
|
|
||
| Letters do not have any fallback rules as they’re always sent last in message plans for transactional messages. |
There was a problem hiding this comment.
is 'transactional messages' correct here? I think it's referring to event-based messages
There was a problem hiding this comment.
We could probably just remove the last part as we don't need to clarify which types of messages this is for
|
|
||
| Emails and text messages will fallback to the next channel if they are not delivered after 72 hours. | ||
|
|
||
| Letters do not have any fallback rules as they’re always sent last in message plans for transactional messages. |
There was a problem hiding this comment.
Same as this line in the campaign content - can probably remove the bit about 'transactional messages'. If not, refer to them as 'event-based messages' for consistency
| ## Which features you can use | ||
|
|
||
| Find out what features you can and cannot use as a national programme using NHS Notify. | ||
|
|
There was a problem hiding this comment.
In the bit about SMS nudge, we say 'If push notifications are turned off, the recipient will receive a text message (SMS) telling them they have a new message in the NHS App.' Do we want to add 'and your message plan includes a billable channel/a text message or letter'? Or is that too much detail here? Just a thought. Same for this section on the other pages
| ## Which features you can use | ||
|
|
||
| Find out what features you can and cannot use as a national programme using NHS Notify. | ||
|
|
There was a problem hiding this comment.
In the table row about contact restrictions, we say 'For example, sensitive flag'. Can we change this to 'a sensitive flag' or 'sensitive flags'?
| ## Which features you can use | ||
|
|
||
| Find out what features you can and cannot use as a national programme using NHS Notify. | ||
|
|
There was a problem hiding this comment.
For all 4 sector pages, we have the following: 'Personalisation
Add details like your recipients name'
We need an apostrophe for 'recipient's name'
| ## Which features you can use | ||
|
|
||
| Find out what features you can and cannot use as a national programme using NHS Notify. | ||
|
|
There was a problem hiding this comment.
Also need an apostrophe for recipients' (this time it's plural recipients), for all 4 sector pages:
'Automatic contact look up (mandatory) NHS Notify automatically finds and uses your recipients contact details from their NHS number'
|
|
||
| ## Which features you can use | ||
|
|
||
| Find out what features you can and cannot use as a national programme using NHS Notify. |
There was a problem hiding this comment.
Can we change the body text to 'which features' for all 4 sector pages?
2 participants
Description
Added sector-specific feature pages
Created a new "Features by organisation type" section, adding the following pages:
Signposted to these new pages directly from the /about landing page
Updating existing messaging needs pages
Removed 'features' content from these existing pages:
Each of the above page has a section called "Choosing your message order." This section contains the "Message plans" and "Fallback rules" content lifted from the old feature pages.
Context
Notify is moving to 'out of the box' features for specific sectors. Therefore we have created new feature pages for the specific sectors that tell users what they can/can't get.
The generic features lists on the standard messaging pages (/campaigns, /event-based-messaging, /direct-messaging) are no longer accurate under the new model, so they have been removed. The rest of the content on these pages have been retained.
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.