Open briandiggle opened 7 years ago
The HDL-188 contains reference to a "Citizen" resource, this is not a valid resource as raised during the development of the PFS proposed changes and the resource was changed to a "Person" resource, I am not sure why it was not changed on the HDL ticket. We should double check the vadility of the solution before putting it in the spec.
The PFS changes are going to be released when needed as a non breaking change by adding requirements for backward compatibility with current JWT. We are not making the changes now as there is outstanding questions relating to what format the stratigic auth JWT will contain and also addition of guidance to providers about filtering content of the response for PFS.
We are going to move it into the next version of the specification when hopefully enough of the questions will have been answered to allow us to add the changes.
The direction of stratigic auth has not yet been finalised and the no investigation into the requirements around patient facing has been done so moving this onto a later release as it will not be done for the next release due to priorities.
Put against 'Future' milestone - wanting to align with Strategic Auth but no clear specification for this as yet
Uplift JWT guidance in https://nhsconnect.github.io/gpconnect/integration_cross_organisation_audit_and_provenance.html to align with requirements for strategic authentication. Also enable support for patient facing use cases.
Link to HDL-188