Ccm 23095 get started guidance - #283
jamestynan-content wants to merge 2 commits into
Conversation
| --- | ||
|
|
||
| Before we can invite you to onboard with NHS Notify, you need to: | ||
| Use this page to check you're ready to use NHS Notify. You can then complete our online form to register your interest and speak to a member of our team. |
There was a problem hiding this comment.
Could we change the second sentence to match the CTA button at the bottom more clearly?
'You can then complete our online form to check which features you can get and register your interest. This will allow you to speak to a member of our team.'
| - [NHS Notify API](https://notify.nhs.uk/about/api) | ||
| - [NHS Notify MESH](https://notify.nhs.uk/about/mesh) | ||
|
|
||
| Your technical team should review the API and MESH guidance and decide which option best fits your organisation. |
There was a problem hiding this comment.
'is best for' rather than 'best fits' (plainer language, less metaphorical)
|
|
||
| ## Check if you need to apply for NHS login | ||
|
|
||
| If you're sending NHS App messages that contain links to a service that requires users to sign in, you'll need to apply for NHS login. |
There was a problem hiding this comment.
This sentence makes sense but is a little tricky to read, with the number of 'thats' and clauses.
We should also probs stick to 'log in', in line with NHS style.
Lastly, I'm not clear on whether we're referring to NHS services specifically here (requiring a log in). Not sure if we need to be explicit about that or if it's already obvious to users?
Some options:
'If you’re sending NHS App messages including / containing links to services that require users to log in, you’ll need to apply for NHS login.'
'You'll need to apply for NHS login if your NHS App messages link to a logged-in service.'
'You'll need to apply for NHS login if your NHS App messages link to a service requiring users to log in.'
|
|
||
| If you're sending NHS App messages that contain links to a service that requires users to sign in, you'll need to apply for NHS login. | ||
|
|
||
| This means users stay logged in and do not have to enter their login details again. |
There was a problem hiding this comment.
'This will allow users to stay logged in [into the NHS App?] and not have to enter their details again.'
or
'This means users can stay logged in and do not have to enter their details again.'
|
|
||
| If your organisation is not part of NHS England, you'll need to agree to a <a href="https://digital.nhs.uk/services/partner-onboarding/operations#connection-agreement" target="_blank">connection agreement (opens in a new tab)</a>. | ||
|
|
||
| We’ll send you copies to sign when you have been invited to onboard. |
There was a problem hiding this comment.
'We’ll send you copies to sign when/after we invite you to onboard.'
(active voice :) )
|
|
||
| - check your organisation can use it | ||
| - understand our terms and conditions | ||
| Complete our online form to confirm you can use NHS Notify, see which features you can get, and register your interest. |
There was a problem hiding this comment.
is 'confirm you can use NHS Notify' not the same as 'register your interest'? Or by 'confirm' do we mean the user is going through the act of checking and confirming? Either way, it's probably not needed and better to stick to the same wording as the button CTA.
Also, good to avoid the word 'see'.
I propose:
'Complete our online form to check which features you can get and register your interest.'
|
|
||
| published: true | ||
| --- | ||
| You can start onboarding with NHS Notify once we've invited you. If we haven't invited you yet, find out how to [get started with NHS Notify](https://notify.nhs.uk/get-started/). |
There was a problem hiding this comment.
If we have not invited you yet, find out how to get started with NHS Notify.
^ to avoid the negative contraction :) (minor style guide thing)
2 participants
Description
Updated 'get started' pages following stakeholder feedback. The main changes are:
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.