T3.2.1 - Development of User Profile APIs to be consumed by the FE (Postaman)

[riccardo-leoni-dw]

T3.2 - Development of User Profile APIs to be consumed by the FE (update endpoint)

[Paride07]

@paolopierantozzi pls check this task

[Paride07]

@paolopierantozzi reported after an internal call with UPM that the patient profile is not linked to the patient account and that UPM will release CRUD associated to the patient account at end of February alongside the authentication WRAPPER. @amedranogil and @abelmarm could you confirm as well this?

[Paride07]

Update 20.02.23 To be postpone to Sprint 3

[Paride07]

Update 27.03.23 Status: Ready to be tested. link of the Swagger: https://github.com/Gravitate-Health/g-lens-profile/blob/main/openapi.json @paolopierantozzi, please provide feedback

[paolopierantozzi]

Initial review update 27.03.23: The openapi interface seems good, but there is the need for the postman collection and the authentication layer in order to provide a complete feedback on the effective working status of the APIs.

Also, for the moment alergies, problem list, intolerances and medicines are treated as strings, while this could be a viable solution for testing, in a real deployment environment it's mandatory to treat them as complete FHIR resources/ json

We list below what is needed from @abelmarm in order to proceed:

• consolidated postman collection in order to review and test the profile API;
• services APis to retrive all the correct and trusted alergies, problem list, intolerances.

[Paride07]

Update 10.03.23:

• consolidated postman collection shared, working only for a demonstration activity

[gmej]

As presented in Rome technical meeting, this task was completed by March 24th, in this commit. However, this development follows a continuous delivery approach and is in constant development.

[gmej]

This implementation is done in these two repositories: keycloak and keycloak-registration. You can find the OAS in the keycloak repository and in the Swagger UI

[sandroconte]

can you show us how to create an ips at user registration? PLEASE DON'T WASTE OUR TIME!

[amedranogil]

We are concentrating in the hackathon, as part of the MVP2. I have asked @gmej to do some house cleaning as per our conversation yesterday. This is part of the technical document we have commited to share with DataWizard this week. IPS creation and user registration will be discussed as per the agreed plan which is after the hackathon.

[sandroconte]

I need to write this comment because for over two weeks the registration API has been returning 500 "server error" to us

[gmej]

Could you please provide a bug report? What steps did you follow? That is not enough information as I am not able to reproduce the error. Are you referring to the OAS to learn how the API must be consumed?

[sandroconte]

Thank you for fixing the bug. We are going to check whole collection another time, after your fix

[amedranogil]

Just as a reminder, the Persona Dimension IG, the new specification for user profiling, was annoced last week. So we should expect changes in these APIs following this new standard.