This portal provides an open platform for user feedback and product change requests. Anyone can add an idea and remain as a Guest, but please consider signing up so that others can see who has created the ideas!
Note: this is a public facing web portal, any text here can be viewed by anyone over the internet, so please consider carefully the content you wish to share and please do not post anything of a sensitive nature.
ODS and ASID information is not included in context-launch configuration.
This means that GP Connect functionality in the portal cannot be viewed (as there is no accompanying ASID).
Use case
Clinical users accessing the shared care record can access from various different sites. When accessing the system, they will perform tasks such as comparing medication issued in primary care against medication prescribed in acute.
Problem statement
We do not currently audit what ODS and ASID pairing was passed across to allow the user to access GP Connect data.
| As a | Portal administrator / IG officer / reporting consumer |
| I would like | User account context-launch to include practice-specific ODS/ASID pairings |
| So that | an accurate audit is maintained and S1 GP users can access GP data inside the care portal |
| User contact | toby.page1@nhs.net; kerry.cyster1@nhs.net; Rowan.Sil@nhs.net |
|
Other information
This only applies to S1 context-launch. EMIS Web applies this already(?). This has been discussed briefly with Synanetics and it is technically possible (see below from Greg/Anna): When S1 users are registered, their ODS and ASID code should be assigned against their user so that during auditing the users organisation can be determined. To apply this to existing users it may be possible to check that if they don't have those claims against them their user is updated to have the ODS where they launched from. |
|
@Guest Pull a call together with Rowan to better understand this issue.