From:
Sanju Nannuri
To:
Alan Monnox
Cc:
Rama Kumble; Asfahaan Mirza; Digital Health Identity Integration; Kate A Williams; Tony Madsen; Manvir Singh
Subject:
RE: Estimation - MHA Phase 1 Dev Completion
Date:
Friday, 5 May 2023 12:39:28 pm
Attachments:
image001.png
image002.png
image003.png
image004.png
Hi Alan
We can see the updated URL now.
Thank you.
1982
Act
Information
Official
the
Regards
Sanju
From: Alan Monnox <[email address]>
Sent: Monday, May 1, 2023 9:02 AM
To: Sanju Nannuri 9(2)(a)
Cc: Rama Kumble 9(2)(a)
Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
under
Health Identity Integration <[email address]>; Kate A Williams <[email address]>; Tony Madsen
<[email address]>; Manvir Singh 9(2)(a)
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Sanju,
This change has been applied. Can you confirm?
Cheers,
Alan
From: Sanju Nannuri 9(2)(a)
Released
Sent: Saturday, 29 April 2023 5:17 pm
To: Alan Monnox <[email address]>
Cc: Rama Kumble 9(2)(a)
Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>; Kate A Williams <[email address]>; Tony Madsen
<[email address]>; Manvir Singh 9(2)(a)
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Alan,
As per the deployment schedule, last night we have deployed the MHA integration for Manage My Health Portal. So far 12 users successfully
logged into Patient portal using My Health Account login details.
And I noticed one issue in 9(2)(c)
portal under connected services.
MMH URL is showing as beta.managemyhealth.co.nz instead of app.managemyhealth.co.nz.
You might have configured the old url when you prepared the prod credentials last year.
can you please update the Url to 9(2)(c)
here is the screenshot of connected services section showing wrong Url
1982
Act
Information
Official
the
under
Released
Regards,
Manvir
From: Tony Madsen <[email address]>
Sent: Wednesday, 26 April 2023 1:19 pm
To: Manvir Singh 9(2)(a)
; Alan Monnox <[email address]>; Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>; Kate A Williams <[email address]>; Devanathan R
9(2)(a)
Latha Patel 9(2)(a)
Parthiban Palanivel 9(2)(a)
Subject: RE: Estimation - MHA Phase 1 Dev Completion
I’m a level 3N account using RealMe verified
From: Manvir Singh9(2)(a)
Sent: Wednesday, 26 April 2023 1:16 pm
To: Alan Monnox <[email address]>; Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Tony Madsen <[email address]>
Cc: Rama Kumble 9(2)(a)
Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>; Kate A Williams <[email address]>; Devanathan R
9(2)(a)
Latha Patel 9(2)(a)
Parthiban Palanivel 9(2)(a)
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Alan,
1982
Thank you for your reply and good to know My Health Account login works for Tony as an existing user in Manage My Health.
We have list of other scenarios to test e.g. Who is not an existing Manage My Health user, full list can be provided to you soon once our QA team is
online as they are managing the testing side of this integration.
Act
@Tony Madsen, I hope you just navigate to our pre-prod environment login view and login there using your My Health Account credentials. Did it
login you straight into our Application as you are an existing MMH user? It is possible for you to share with us the confidence level of the account
you used to Sign In.
Regards,
Manvir
From: Alan Monnox <[email address]>
Sent: Wednesday, 26 April 2023 12:20 pm
To: Manvir Singh 9(2)(a)
Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
Asfahaan Mirza 9(2)(a)
Dylan Nyika <[email address]>; Digital
Information
Health Identity Integration <[email address]>; Kate A Williams <[email address]>; Tony Madsen
<[email address]>; Devanathan R 9(2)(a)
Latha Patel 9(2)(a)
; Parthiban Palanivel
9(2)(a)
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Manvir,
Tony has tested using the link provided below and he could successfully access his details.
He is an existing user of Manage My Health and used his personal account for the test.
Official
I hope this helps but suggest you have other users confirm the functionality, as this test was just for one account.
Tony is cc’d on this email thread and he is happy to take any questions on how he confirmed his access.
Cheers,
the
Alan
From: Manvir Singh 9(2)(a)
Sent: Wednesday, 26 April 2023 11:43 am
To: Alan Monnox <[email address]>; Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
under
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>; Kate A Williams <[email address]>; Tony Madsen
<[email address]>; Devanathan R 9(2)(a)
Latha Patel 9(2)(a)
Parthiban Palanivel
9(2)(a)
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Alan,
We are planning to go live tomorrow provided all the test cases work in our pre-prod environment. Currently we will be going live with web app
only.
So, as you mentioned you can assist us in some of our testing and we can’t have test accounts for the production environment. We have set up a
Released
pre-prod environment and it is up and running. It will be same as our production environment. Below is the URL for our pre-prod.
9(2)(c)
So please let us know if you will be able to test for us in this above-mentioned link or is there any other way you can
support and assist us.
Regards,
Manvir
From: Alan Monnox <[email address]>
Sent: Wednesday, 26 April 2023 9:53 am
To: Manvir Singh 9(2)(a)
Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>; Kate A Williams <[email address]>; Tony Madsen
<[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Manvir,
By production login credentials I’m assuming you are after test accounts in our production environment?
Unfortunately, we don’t have test accounts in production. Typically, applications use a small set of real user accounts to test the initial release.
Can you provide details on when you are planning to go live and if this is for your Web app only? If you can provide this information we can put
support in place for when you go live and possibly assist with some of you testing.
Thanks,
Alan
From: Manvir Singh 9(2)(a)
Sent: Wednesday, 26 April 2023 9:34 am
To: Alan Monnox <[email address]>; Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>; Kate A Williams <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Alan,
Sorry but please take this little urgent, we don’t have My Health Account production login credentials. These are required for our testing. If you can
please provide us few production logins so that we can test.
We need something similar as we have got for INT environment. e.g., as below:
Username
Levels
9(2)(c)
Leave at Level 1
Leave at Level 1
1982
Level 2
Level 2
Level 2N
Act
Level 2N
Level 3
Level 3N
Level 3N
Regards,
Manvir
From: Alan Monnox <[email address]>
Sent: Monday, 24 April 2023 10:30 am
To: Sanju Nannuri 9(2)(a)
Manvir Singh 9(2)(a)
; Chakerveersingh Sandhu
9(2)(a)
Information
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>; Kate A Williams <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Sanju and Manvir,
Can we get some confirmed dates on when you are planning to go live with My Health Account?
I’ve heard indirectly that you are targeting 27th April? Will this just be for you web app, as previously you were also doing development work on a
Official
mobile app?
Thanks,
Alan
the
From: Sanju Nannuri 9(2)(a)
Sent: Thursday, 13 April 2023 1:50 pm
To: Alan Monnox <[email address]>; Manvir Singh 9(2)(a)
; Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>
under
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Thanks Alan.
We received the keys.
Regards
Sanju
From: Alan Monnox <[email address]>
Sent: Thursday, April 13, 2023 11:29 AM
To: Sanju Nannuri 9(2)(a)
; Manvir Singh 9(2)(a)
Chakerveersingh Sandhu
Released
9(2)(a)
Cc: Rama Kumble 9(2)(a)
Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Sanju,
I sent these out earlier by encrypted email. Please let me know if you have any trouble receiving them.
Email sent to yourself and Manvir.
Alan
From: Sanju Nannuri 9(2)(a)
Sent: Thursday, 13 April 2023 12:47 pm
To: Alan Monnox <[email address]>; Manvir Singh 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
Asfahaan Mirza 9(2)(a)
Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Alan,
Can you please reissue the prod credentials.
Regards
Sanju
From: Alan Monnox <[email address]>
Sent: Thursday, April 13, 2023 8:30 AM
To: Manvir Singh 9(2)(a)
Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi,
These are now set up against your prod app registration.
Any luck with the creds? Let me know and I can reissue if necessary.
Cheers,
Alan
From: Manvir Singh9(2)(a)
Sent: Wednesday, 12 April 2023 12:25 pm
To: Alan Monnox <[email address]>; Sanju Nannuri 9(2)(a)
; Chakerveersingh Sandhu
1982
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Act
Hi Alan,
Thank you.
Mistakenly these below URLs should be part of production environment. I have mentioned them earlier for INT environment. I apologise for that.
Pre-Prod
9(2)(c)
I could not find the production credentials, however I will ask my team and come back.
Regards,
Manvir
From: Alan Monnox <[email address]>
Information
Sent: Wednesday, 12 April 2023 11:13 am
To: Manvir Singh 9(2)(a)
Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Manvir,
Official
The new URLs have been added to your prod app registration.
Cheers,
Alan
the
From: Manvir Singh 9(2)(a)
Sent: Tuesday, 11 April 2023 1:42 pm
To: Alan Monnox <[email address]>; Sanju Nannuri 9(2)(a)
; Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
under
Health Identity Integration <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Alan,
Thank you for adding more return URLs in INT environment.
When your request for production is completed. Please let us know the credentials as well for production e.g. (clientId, authority URI)
Yes, we have got different credentials for both web app and mobile app in INT environment. I hope this answer your question.
Regards,
Manvir
From: Alan Monnox <[email address]>
Released
Sent: Tuesday, 11 April 2023 12:52 pm
To: Manvir Singh 9(2)(a)
; Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Dylan Nyika <[email address]>; Digital
Health Identity Integration <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi,
I’ve updated the INT environment URIs but will need to raise an internal change request for prod.
I noticed the app reg is set up as both a web app and a SPA. Is that correct?
Cheers,
Alan
From: Manvir Singh 9(2)(a)
Sent: Tuesday, 11 April 2023 12:33 pm
To: Alan Monnox <[email address]>; Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Rama Kumble 9(2)(a)
; Asfahaan Mirza 9(2)(a)
>; Dylan Nyika <[email address]>
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Alan,
Hope you had a great weekend.
These MMH return URLs are for Web.
@Chakerveersingh Sandhu & @Sanju Nannuri should be able to reply on your mobile app queries.
Once those URLs are added for Web, please let us know.
Regards,
Manvir
From: Alan Monnox
Sent: Tuesday, 11 April 2023 10:05 AM
To: Sanju Nannuri
Cc: Digital Health Identity Integration; Rama Kumble; Asfahaan Mirza; Manihandan Nagarajan; Chakerveersingh Sandhu; Dylan Nyika
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Sanju,
I can add those URLs to the INT environment but can you confirm if these are for you Web or mobile app? We have separate app registrations for
each.
You should have the prod creds for the web app but you haven’t been supplied with anything for the mobile app. Note the PIA and security report
is still outstanding for mobile.
Please let me know if you’d like a session to discuss your plans for the mobile app, so we can move things along.
1982
Cheers,
Alan
From: Sanju Nannuri 9(2)(a)
Act
Sent: Tuesday, 11 April 2023 11:54 am
To: Alan Monnox <[email address]>
Cc: Digital Health Identity Integration <[email address]>; Rama Kumble 9(2)(a)
Asfahaan Mirza
9(2)(a)
Manihandan Nagarajan 9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
Subject: FW: Estimation - MHA Phase 1 Dev Completion
Hi Alan
Can you please setup below MMH return URLs.
Regards
Sanju
From: Manvir Singh 9(2)(a)
Information
Sent: Thursday, April 6, 2023 4:32 PM
To: Sanju Nannuri 9(2)(a)
; Rama Kumble 9(2)(a)
Cc: Samuel Wong 9(2)(a)
Subject: RE: Estimation - MHA Phase 1 Dev Completion
Hi Sanju,
As discussed, we would require below return urls for MHA.
For MHA Dev environment
Official
Dev:
9(2)(c)
the
UAT:
9(2)(c)
Pre-Prod
9(2)(c)
under
Also, we require MHA api production credentials to go live and below return urls in it.
Production:
9(2)(c)
Regards
Manvir
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
Released
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
1982
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
Act
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
Information
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of Health's Content and Virus Filtering Gateway
****************************************************************************
Official
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
the
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
under
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
Released
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
1982
Act
Information
Official
the
under
Released
From:
Alan Monnox
To:
Manvir Singh; Tony Madsen; Lisa Hautler
Cc:
Asfahaan Mirza; Sanju Nannuri; Devanathan R; Roslynne Alburo Alejandro; Kesavan N; Chakerveersingh Sandhu
Subject:
RE: MMH integration with MHA
Date:
Friday, 7 July 2023 10:10:00 am
Attachments:
image001.png
image002.png
Hi Manvir,
No problem. I’ve sent the details to you as an encrypted email.
Cheers,
Alan
From: Manvir Singh9(2)(a)
Sent: Thursday, 6 July 2023 10:58 am
To: Tony Madsen <[email address]>; Lisa Hautler <Lisa.Hautler@health govt.nz>; Alan Monnox <Alan.Monnox@health govt.nz>
Cc: Asfahaan Mirza <[email address]>; Sanju Nannuri <[email address]>; Alan Monnox <Alan.Monnox@health govt.nz>; Devanathan R <[email address]>; Roslynne Alburo Alejandro <[email address]>; Kesavan N <[email address]>;
Chakerveersingh Sandhu <csandhu@mmhglobal com>
Subject: RE: MMH integration with MHA
Hi Alan,
As we were discussing yesterday, I found this email thread where I asked for mobile app credential. However, I couldn’t find mobile credentials being send to us. I would really appreciate if you can send us mobile app credentials once again.
Regards,
Manvir
From: Manvir Singh
Sent: Thursday, 25 May 2023 8:54 pm
To: Tony Madsen <[email address]>; Lisa Hautler <Lisa.Hautler@health govt.nz>
Cc: Asfahaan Mirza9(2)(a)
Sanju Nannuri 9(2)(a)
Alan Monnox <Alan.Monnox@health govt.nz>; Devanathan R9(2)(a)
Roslynne Alburo Alejandro <[email address]>; Kesavan N9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
Subject: RE: MMH integration with MHA
Hi Tony,
Thank you for a quick and nice chat this morning regarding further changes happening in My Health Account for us.
We are happy with the content you have shown for Manage My Health.
Regarding Manage My Health link in your “Other services” section, we can navigate it to our dashboard view. However, we need to authenticate the request coming to us, for this we would require access token for the logged in user in My Health Account. Token can be sent along with the URL as a query string. Once
we got your token, we will proceed the same way as we are doing it now i.e., calling your userinfo end point to validate the token. From here we can allow the user into our application once all the checks(e.g., confidence level etc) are done. Please let us know your thought about this.1982
Also as discussed, we require My Health Account production credentials(e.g., clientId, secret) for our mobile app. Earlier we have received the production credentials for the web app.
Please let me know if you have any questions.
Regards,
Manvir
Act
From: Tony Madsen <[email address]>
Sent: Wednesday, 24 May 2023 10:40 am
To: Manvir Singh9(2)(a)
Lisa Hautler <[email address]>
Cc: Asfahaan Mirza9(2)(a)
Sanju Nannuri 9(2)(a)
Alan Monnox <Alan Monnox@health govt nz>; Devanathan R 9(2)(a)
Roslynne Alburo Alejandro <Roslynne AlburoAlejandro@health govt nz>; Kesavan N 9(2)(a)
Subject: RE: MMH integration with MHA
Hi Manvir
Just checking to see how you are getting on with your changes and also to find out a suitable time to take you through the changes we have done for Manage My Health in our “Other services” section.
Want to verify that you are happy with content and I would also like to do a test in our SIT env to see if I get taken correctly into you app rather than to your login page.
Cheers Tony
Information
Official
the
under
From: Manvir Singh
Sent: Thursday, 18 May 2023 11:58 am
9(2)(a)
To: Tony Madsen <[email address]>; Lisa Hautler <Lisa.Hautler@health govt.nz>
Cc: Asfahaan Mirza
Sanju Nannuri
Alan Monnox <Alan.Monnox@health govt.nz>; Devanathan R
Roslynne Alburo Alejandro <[email address]>; Kesavan N
Subject: RE: MMH integration with MHA
9(2)(a)
9(2)(a)
9(2)(a)
9(2)(a)
Released
Hi Tony,
Our QA is completing their testing now. Can you please degrade confidence level back to 2 for those two users. One thing QA reported when they follow the steps to upgrade the confidence level, the level went from 2 to 3N, without them manually adding the NHI.
Regards,
Manvir
From: Tony Madsen <[email address]>
Sent: Wednesday, 17 May 2023 1:46 pm
To: Manvir Singh
Lisa Hautler <[email address]>
Cc: Asfahaan Mirza
Sanju Nannuri
Alan Monnox <Alan.Monnox@health govt.nz>; Roslynne Alburo Alejandro <Roslynne.AlburoAlejandro@health govt.nz>
9(2)(a)
Subject: RE: MMH integration with MHA
9(2)(a)
9(2)(a)
Hi Manvir
I have changed confidence level to a level 2 by removing NHI number on both accounts
You will need to signin via our portal and add the NHI number. This should happen automatically when you click on Add your NHI number.
Let me know if you have any issues.
Cheers Tony
From: Manvir Singh9(2)(a)
Sent: Wednesday, 17 May 2023 1:23 pm
To: Tony Madsen <[email address]>; Lisa Hautler <Lisa.Hautler@health govt.nz>
Cc: Asfahaan Mirza9(2)(a)
Sanju Nannuri 9(2)(a)
Alan Monnox <Alan.Monnox@health govt.nz>
Subject: RE: MMH integration with MHA
Hi Tony,
Thank you so much for this nice document to explain the steps.
I had tested user 9(2)(a)
These above users are now coming with confidence level 3N, so I can login now.
Is it possible for you to downgrade these users back to 2N now, so that I can test other scenarios. I wish I was able to do this in INT environment to save your time, as once I completed my testing our QA team might test again.
I would really appreciate if you could please let me know once this is done.
Regards,
Manvir
From: Tony Madsen <[email address]>
Sent: Monday, 15 May 2023 1:58 pm
To: Manvir Singh9(2)(a)
com>; Lisa Hautler <[email address]>
Cc: Asfahaan Mirza9(2)(a)
; Sanju Nannuri 9(2)(a)
Alan Monnox <Alan.Monnox@health govt.nz>
Subject: RE: MMH integration with MHA
Hi Manvir
Sorry I didn’t get this to you on Friday we were completing our current Sprint
Attached is screen shots on how to upgrade from Level 2N to 3N
I have set both 2N accounts up with the same Healthcare provider data to make it easier.
Once you have upgraded to level 3N you will not be able to repeat the process unless you get me to downgrade them again
Cheers Tony
PS let me know if you have any issues
From: Manvir Singh9(2)(a)
Sent: Friday, 12 May 2023 3:29 pm
To: Lisa Hautler <Lisa.Hautler@health govt.nz>; Tony Madsen <Tony.Madsen@health govt.nz>
Cc: Asfahaan Mirza9(2)(a)
net>; Sanju Nannuri 9(2)(a)
Alan Monnox <Alan.Monnox@health govt.nz>
Subject: RE: MMH integration with MHA
1982
Hi Tony,
Thank you for your time today for discussing confidence level testing scenarios.
I will wait for your reply when you can add additional information to make confidence level of 3/3N for the users(2N) I provided today and how we can change confidence level back to 2/2N.
Regarding adding Manage My Health URL in other services in My Health Account as we discussed, below are the URLs.
Act
For Int/Dev
9(2)(c)
For Production:
9(2)(c)
After login here, user will be navigated to dashboard view. For other scenario of single sign on click of above links which you were mentioning, would require further discussion between your and our dev team.
Regards,
Manvir
From: Lisa Hautler <Lisa.Hautler@health govt.nz>
Sent: Wednesday, 10 May 2023 4:21 pm
To: Manvir Singh9(2)(a)
Cc: Asfahaan Mirza9(2)(a)
Tony Madsen <Tony.Madsen@health govt.nz>; Sanju Nannuri9(2)(a)
Subject: RE: MMH integration with MHA
You don't often get email from [email address]. Learn why this is important
Brilliant, have just sent through an invite.
Thanks Manvir!
Information
Cheers
Lisa
From: Manvir Sing 9(2)(a)
Sent: Wednesday, 10 May 2023 2:09 pm
To: Lisa Hautler <Lisa.Hautler@health govt.nz>
Cc: Asfahaan Mirza 9(2)(a)
Tony Madsen <Tony.Madsen@health govt.nz>; Sanju Nannuri9(2)(a)
Subject: RE: MMH integration with MHA
Hi Lisa,
Thank you for your email.
Official
Friday is all good for me. Can we schedule any time between 11 am – 1 pm on Friday.
Regards,
Manvir
From: Lisa Hautler <[email address]>
Sent: Wednesday, 10 May 2023 1:55 pm
To: Manvir Singh
the
9(2)(a)
Cc: Asfahaan Mirza 9(2)(a)
Tony Madsen <Tony Madsen@health govt nz>
Subject: MMH integration with MHA
You don't often get email from [email address]. Learn why this is important
Hi Manvir,
Lovely to meet you yesterday.
Just following up on an action to set up a session with you to walk through the user flows in a test environment with our Test Lead (Tony Ccd), to better understand the issues you are currently experiencing, and determine way forward.
If you could let me know a time that suits, I will follow up with a meeting request. At this stage, Tony’s diary is looking relatively clear on Friday..
under
Cheers
Lisa Hautler
Lisa Hautler Product Delivery Lead
Data & Digital
9(2)(a)
E [email address]
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
Released
immediately and delete this message.
****************************************************************************
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
1982
Act
Information
Official
the
under
Released
From:
Asfahaan Mirza
To:
Samuel Wong; Alan Monnox; Sanju Nannuri; Chakerveersingh Sandhu
Cc:
Digital Health Identity Integration; Rama Kumble; Richard Hill
Subject:
Re: Manage My Health Mobile
Date:
Tuesday, 19 September 2023 6:26:47 pm
Attachments:
image001.png
image002.jpg
Ok no problem Samuel.
We wanted to make our app live that’s why I was following up.
Kind regards
Asfahaan
1982
Get Outlook for iOS
From:
Act
Samuel Wong <[email address]>
Sent: Tuesday, September 19, 2023 5:49:47 PM
To: Asfahaan Mirza <9(2)(a)
>; Alan Monnox <[email address]>;
Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Cc: Digital Health Identity Integration <[email address]>; Rama Kumble
9(2)(a)
Richard Hill <[email address]>
Information
Subject: RE: Manage My Health Mobile
Hi Asfahaan,
Official
Thought it might be easier to cover both topics given the relevance to both parties, It shouldn’t
take too long to discuss at the Friday meeting.
the
Kind regards
Samuel
under
From: Asfahaan Mirza 9(2)(a)
Released
Sent: Tuesday, 19 September 2023 5:47 pm
To: Alan Monnox <[email address]>; Sanju Nannur9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
Cc: Digital Health Identity Integration <[email address]>; Rama Kumble
9(2)(a)
; Samuel Wong <[email address]>; Richard Hill
<[email address]>
Subject: Re: Manage My Health Mobile
Hi Alan
The mobile onboarding is separate from the meeting set by Samuel for Friday.
Friday meeting is regarding integrating with NES.
Kind regards
Asfahaan
9(2)(a)
Get Outlook for iOS
From: Alan Monnox <[email address]>
Sent: Tuesday, September 19, 2023 5:19:32 PM
To: Asfahaan Mirza9(2)(a)
Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
1982
Cc: Digital Health Identity Integration <[email address]>; Rama Kumble
9(2)(a)
Samuel Wong <[email address]>; Richard Hill
Act
<[email address]>
Subject: RE: Manage My Health Mobile
Hi Asfahaan,
Samuel has set up a call for Friday. If that suites your timelines I suggest we discuss your mobile
app onboarding during that session.
Information
Cheers,
Alan
Official
From: Asfahaan Mirza 9(2)(a)
Sent: Tuesday, 19 September 2023 4:24 pm
To:
the
Alan Monnox <[email address]>; Sanju 9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
Cc: Digital Health Identity Integration <[email address]>; Rama Kumble
9(2)(a)
Samuel Wong <[email address]>; Richard Hill
under
<[email address]>
Subject: Re: Manage My Health Mobile
Dear Alan and Samuel
Could you please clarify what we need to do in order to get the production keys for the Mobile
Released
Apps.
Do we need fill out any onboarding form? If yes, please let me know which ones, so I can do the
needful.
Kind Regards
Asfahaan Mirza PhD
GM Strategy & Innovation
9(2)(a)
9(2)(a)
W: managemyhealth.co.nz
Level 1, 48 Market Place, Viaduct Harbour,
Auckland 1010, New Zealand
This communication is and may be privileged and/or contain copyright material. If you are not the intended recipient of this
email, any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you have received this
communication in error, immediately contact us by return email or by calling +6493799166 and then irretrievably delete it
and any attachments. We will preserve the contents of any email message that you send us if we believe that we have an
obligation to do so and we will otherwise comply with the provision of the Privacy Act 1993 and any amendments thereto to
the extent that it applies. Email sent from or to us may be monitored for the purposes of quality control, systems
administration and compliance. You should check for virus and other harmful components before opening or using any
1982
attachments to this email. No reliance may be placed upon the contents of this email as content can become corrupted in
transmission. Our liability is limited only to re-supplying any affected attachment if applicable
Act
From: Alan Monnox <[email address]>
Date: Wednesday, 13 September 2023 at 4:34 PM
To: Sanju Nannuri 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
Information
Cc: Asfahaan Mirza 9(2)(a)
Digital Health Identity Integration
<[email address]>, Rama Kumble 9(2)(a)
Samuel
Wong <[email address]>, Richard Hill <[email address]>
Subject: RE: Manage My Health Mobile Official
Hi Sanju,
the
I checked back through my emails and it looks like there’s been some confusion. You don’t have
an app registration for the mobile app in prod, as we were going to handle that under a separate
onboarding process. under
I sent Manvir the client ID for the mobile app registration in INT. My mistake, as I see now that
he was after the production environment.
I will send you through the client ID for INT but I suggest we discuss the next steps if you are
wanting to move the mobile application into production.
Released
Cheers,
Alan
From: Sanju Nannuri 9(2)(a)
Sent: Wednesday, 13 September 2023 1:30 pm
To: Alan Monnox <[email address]>; Chakerveersingh Sandhu
9(2)(a)
Cc: Asfahaan Mirza 9(2)(a)
Digital Health Identity Integration
<[email address]>; Rama Kumble 9(2)(a)
Subject: RE: Manage My Health Mobile
Hi Alan
We have yet to receive your response on this. Could you kindly provide us with an update, as we
are in the process of preparing for the production release of the applications later this week?
Regards
Sanju
From: Sanju Nannuri
Sent: Monday, September 11, 2023 9:00 AM
To: Alan Monnox <[email address]>; Chakerveersingh Sandhu
9(2)(a)
1982
Cc: Asfahaan Mirza 9(2)(a)
; Digital Health Identity Integration
<[email address]>
Act
Subject: RE: Manage My Health Mobile
Hi Alan
Can you please check below request?
Regards
Information
Sanju
From: Sanju Nannuri
Sent: Wednesday, September 6, 2023 7:39 PM
Official
To: Alan Monnox <[email address]>; Chakerveersingh Sandhu
9(2)(a)
Cc: Asfahaan
the
9(2)(a)
Digital Health Identity Integration
<[email address]>
Subject: RE: Manage My Health Mobile
under
Hi Alan
Manvir has moved on from Manage My Health and is no longer with us. the link you previously
provided for accessing the client ID has expired.
We have been unable to locate the client ID required for the Mobile Apps production Client Id.
Released
Could you kindly re-share this information at your earliest convenience?
Regards
Sanju
From: Alan Monnox <[email address]>
Sent: Wednesday, September 6, 2023 1:37 PM
To: Chakerveersingh Sandhu 9(2)(a)
Cc: Sanju Nannuri 9(2)(a)
Asfahaan Mirza 9(2)(a)
Digital Health Identity Integration <[email address]>
Subject: RE: Manage My Health Mobile
Hi,
Can you give me the client ID. The mobile app isn’t showing as expired as there’s no secret
associated with it, just the redirect uri.
Can you confirm the redirect uris you are using?
Thanks,
Alan
1982
From: Chakerveersingh Sandhu 9(2)(a)
Sent: Wednesday, 6 September 2023 3:27 pm
Act
To: Alan Monnox <[email address]>
Cc: Sanju Nannuri 9(2)(a)
com>; Asfahaan Mirza 9(2)(a)
Subject: Re: Manage My Health Mobile
Hi Alan,
Could you please again send us the Mobile app ClientId for MHA sign in.
Information
The previous client id link has expired.
Kind regards
Official
Chakraveer
the
From: Manvir Singh 9(2)(a)
Sent: Friday, July 7, 2023 11:11:03 AM
To: Chakerveersingh Sandhu 9(2)(a)
under
Cc: Sanju Nannuri 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Subject: FW: Manage My Health Mobile
Hi Chakraveer,
Forwarding you the Mobile app ClientId for MHA
Released
Regards
Manvir
From: Alan Monnox <[email address]>
Sent: Friday, 7 July 2023 10:10 am
To: Manvir Singh 9(2)(a)
Subject: Manage My Health Mobile
Alan Monnox ([email address]) has sent you a protected message.
Read the message
Learn about messages protected by Microsoft Purview Message Encryption.
1982
Privacy Statement
Act
Learn More on email encryption.
Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
*************************************************************************
***
Statement of confidentiality: This e-mail message and any accompanying
Information
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
Official
immediately and delete this message.
*************************************************************************
the
***
*************************************************************************
***
Statement of confidentiality: This e-mail message and any accompanying
under
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
Released
*************************************************************************
***
*************************************************************************
***
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
*************************************************************************
***
*************************************************************************
***
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
*************************************************************************
***
1982
Act
Information
Official
the
under
Released
From:
Dylan Nyika
To:
Jeanette Elley
Cc:
Digital Health Identity Integration; Alan Monnox; Kate A Williams; Asfahaan Mirza; Samuel Wong; Sanju
Nannuri; Manvir Singh
Subject:
RE: My Health Account: changes to logout endpoint
Date:
Friday, 9 December 2022 12:53:49 pm
Attachments:
image001.png
Many thanks for your response Jeanette. The change has now been implemented in our INT
environment so I would suggest you just double check that you don’t get any unexpected errors
when you complete the MSAL logout in INT.
Kind regards,
Dylan
From: Jeanette Elley9(2)(a)
Sent: Thursday, 8 December 2022 2:22 pm
1982
To: Dylan Nyika <[email address]>
Cc: Digital Health Identity Integration <[email address]>; Alan Monnox
Act
<[email address]>; Kate A Williams <[email address]>; Asfahaan
Mirza 9(2)(a)
Samuel Wong 9(2)(a)
; Sanju Nannuri
9(2)(a)
; Manvir Singh 9(2)(a)
Subject: RE: My Health Account: changes to logout endpoint
Hi @Dylan
Thanks for making contact.
I have checked with our developers, and it appears that we do NOT use the MHA logout
Information
endpoint, so it sounds like we’re in the clear.
I am advised that “We are using Microsoft Authentication Library (MSAL) and using Logout of
MSAL. The logout process for MSAL takes two steps. Clear the MSAL cache. Clear the session on
the identity server.”
Official
I hope this information is useful.
Thanks & Regards
Jeanette E.
the
From: Dylan Nyika <[email address]>
Sent: Wednesday, 7 December 2022 3:10 pm
To: Jeanette Elley 9(2)(a)
under
Cc: Digital Health Identity Integration <[email address]>; Alan Monnox
<[email address]>; Kate A Williams <[email address]>
Subject: RE: My Health Account: changes to logout endpoint
Hi Jeanette,
How are you?
I sent you an encrypted email on Friday 25th November (subject:
My Health Account: upcoming
Released
changes to logout endpoint). I’m just checking that you received it OK and if you had any
questions around the impact. I'm unsure if Manage My Health is using the My Health Account
logout endpoint, but if you are there are some changes you'll need to make either by the 26th
January, or before you go-live (whichever comes later).
Could you please let me know if you have any questions about the action needed, or
alternatively if you know that you don't use this endpoint let me know and I’ll take you off the list
for future communications.
Many thanks,
Dylan
Dylan Nyika (he/him)
Product Owner – My Health Account (Digital Health identity)
Data & Digital
waea pūkoro: 9(2)(a)
|
īmēra: [email address]
133 Molesworth Street, Wellington 6011 | PO Box 5013, Wellington 6145
Te Whatu Ora – Health New Zealand
TeWhatuOra.govt.nz
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
1982
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
Act
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
Information
Official
the
under
Released
From:
Alan Monnox
To:
"Jeanette Elley"
Cc:
"Samuel Wong"; "Asfahaan Mirza"; Dylan Nyika; "Sanju Nannuri"; "Rama Kumble"; "Manvir Singh";
"Chakerveersingh Sandhu"; Digital Health Identity Integration
Subject:
RE: MMH Video demo of Successful RealMe Login via Mob
Date:
Wednesday, 16 November 2022 3:52:00 pm
Attachments:
image001.png
Sorry. Hi Jeanette!
From: Alan Monnox
Sent: Wednesday, 16 November 2022 3:40 pm
To: Jeanette Elley 9(2)(a)
Dylan Nyika <[email address]>
Cc: Samuel Wong9(2)(a)
; Asfahaan Mirza 9(2)(a)
Sanju Nannuri 9(2)(a)
; Rama Kumble 9(2)(a)
Manvir Singh 9(2)(a)
Chakerveersingh Sandhu
1982
9(2)(a)
Digital Health Identity Integration
<[email address]>
Act
Subject: RE: MMH Video demo of Successful RealMe Login via Mob
Hi Janelle,
Perfect. Thanks for sending this through. I’ll mark the compliance tests as complete.
Let us know when you have a pen test you can share.
Thanks,
Alan
From: Jeanette Elley 9(2)(a)
Information
Sent: Tuesday, 15 November 2022 5:36 pm
To: Alan Monnox <[email address]>; Dylan Nyika <[email address]>
Cc: Samuel Wong 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Sanju Nannuri 9(2)(a)
; Rama Kumble 9(2)(a)
Official
Manvir Singh 9(2)(a)
Chakerveersingh Sandhu
9(2)(a)
the
Subject: MMH Video demo of Successful RealMe Login via Mob
Hi Alan & Dylan,
Apologies for the delay.
Please find attached a video demonstration of a successful RealMe Login via Mob.
under
We managed to make this one small enough to be able to attach to an email. Please let me know
if you have any trouble viewing it.
I believe that this demo the last requirement for technical compliance.
We still need to send you our latest pen test results, coming soon …
Thanks & Regards
Jeanette Elley PhD
Released
Senior Business Analyst / Project Manager
9(2)(a)
W: managemyhealth.co.nz
Level 1, Cereus Health House
48 Market Place, Viaduct Harbour, Auckland 1010
This communication is and may be privileged and/or contain copyright material. If you are not the intended recipient of this email,
any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you have received this communication in error,
immediately contact us by return email or by calling +6493799166 and then irretrievably delete it and any attachments. We will
preserve the contents of any email message that you send us if we believe that we have an obligation to do so and we will otherwise
comply with the provision of the Privacy Act 1993 and any amendments thereto to the extent that it applies. Email sent from or to us
may be monitored for the purposes of quality control, systems administration and compliance. You should check for virus and other
harmful components before opening or using any attachments to this email. No reliance may be placed upon the contents of this
email as content can become corrupted in transmission. Our liability is limited only to re-supplying any affected attachment if
applicable
1982
Act
Information
Official
the
under
Released
From:
Jeanette Elley
To:
Dylan Nyika; Asfahaan Mirza; Sanju Nannuri
Cc:
Alan Monnox; Rama Kumble; Samuel Wong
Subject:
RE: Manage My Heath Mobile App Compliance Tests - Meeting Minutes
Date:
Wednesday, 9 November 2022 3:30:40 pm
Attachments:
image002.png
image003.jpg
Hi Dylan,
Thanks for the update.
At our end, we still need to send you –
1. The final MHA for mob video demonstrating a successful RealMe login (due very shortly)
2. A Pen test for our Mobile App (could take a bit longer)
With regards to deployment due date, I’m afraid we cannot yet confirm exactly, but it will
depend on 2 above, and also the rollout of our v2 provider portal, which is likely to include v2
1982
self-registration. Unfortunately, we have experienced some delays and I expect that these are
both still at least a month away.
Act
As for volumes, self-registered users make up only a small proportion of MMH users, so the
uptake will not be great at the start.
Most of our users register via their GP practice (via email plus a practice generated verification
code), so the volume of MHA registrations will increase significantly once we implement phase 2
of this project, which will allow existing MMH users to switch over to an MHA login if a clear
match can be made via NHI, backed up by other identity fields.
Once we have implemented that phase 2 aspect of the MHA integration, then at that point yes,
Information
we do plan to publicise this feature widely to practices, patients, and beyond.
From your perspective, I would not anticipate any significant increase in user support
requirements at your end until we have implemented phase 2, with its accompanying publicity,
which could conceivably be in December, or failing that, early next year.
I’ll be back in touch shortly, once I can pin down that last video.
Official
I will also keep you posted regarding the various due dates, and will see if I can find some
indicative numbers to send you.
the
Hope this helps.
Regards
Jeanette E.
under
From: Dylan Nyika <[email address]>
Sent: Friday, 4 November 2022 10:59 am
To: Jeanette Elley 9(2)(a)
Asfahaan Mirza 9(2)(a)
Sanju
Nannuri 9(2)(a)
Cc: Alan Monnox <[email address]>; Rama Kumble9(2)(a)
Subject: FW: Manage My Heath Mobile App Compliance Tests - Meeting Minutes
Released
Hi team,
Apologies I couldn’t make it to the compliance demonstration. I heard it went well and that we
are well on our way to being ready for a Production release, pending a few outstanding items. I
understand the main action point relates to a decision on using a single or separate app
registrations for the Mobile and Web app. Let us know what you decide so we can make any
changes (if needed) to the integration.
In preparation for the Production planning, I was hoping you could let us know a few things:
1. What is your
target date for moving to Production?
2. Do you have any indicative
or projected numbers on uptake of the use of My Health
Account for creating a Manage My Health profile?
The 2nd point is for us to assess if we have appropriate support in place should the move to
Production result in increased volumes to our support channels. For example:
How many people sign-up for Manage My Health profiles per month/week currently?
What proportion of these are likely to choose My Health Account for sign-up / log in?
Are you planning any promotion for existing Manage My Health users to match their
profile to a My Health Account?
Any information you can provide will be very useful in our planning, and will ensure we can
provide a good experience for anyone who needs assistance during sign-up.
Many thanks,
Dylan
Dylan Nyika (he/him)
Product Owner – My Health Account (Digital Health identity)
Data & Digital
1982
waea 9(2)
|
īmēra: [email address]
133 Molesworth Street, Wellington 6011 | PO Box 5013, Wellington 6145
Act
Te Whatu Ora – Health New Zealand
TeWhatuOra.govt.nz
From: Megan Robinson <[email address]>
Sent: Wednesday, 2 November 2022 4:38 pm
Information
To: Alan Monnox <[email address]>; Jeanette Elley 9(2)(a)
Asfahaan Mirza 9(2)(a)
Sanju Nannuri 9(2)(a)
Rama Kumble9(2)(a)
Tony Madsen <[email address]>
Cc: Dylan Nyika <[email address]>
Official
Subject: Manage My Heath Mobile App Compliance Tests - Meeting Minutes
Hi all,
Please find the minutes from this afternoons meeting attached.
the
Many thanks,
Megan Robinson
Programme Coordinator
under
Data and Digital
133 Molesworth Street, Wellington
Released
Te Whatu Ora – Health New Zealand
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
1982
Act
Information
Official
the
under
Released
From:
Jeanette Elley
To:
Tony Madsen
Cc:
Alan Monnox; Dylan Nyika; Chakerveersingh Sandhu; Manvir Singh; Asfahaan Mirza; Samuel Wong; Rama
Kumble; Sanju Nannuri
Subject:
RE: RealMe test data for MMH MHA Integration
Date:
Thursday, 3 November 2022 9:29:48 am
Attachments:
image001.png
Awesome. Thanks
From: Tony Madsen <[email address]>
Sent: Thursday, 3 November 2022 9:28 am
To: Jeanette Elley 9(2)(a)
Cc: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Chakerveersingh Sandhu 9(2)(a)
; Manvir Singh
9(2)(a)
Asfahaan Mirza 9(2)(a)
; Samuel Wong1982
9(2)(a)
Rama Kumble 9(2)(a)
; Sanju Nannuri
9(2)(a)
Act
Subject: RE: RealMe test data for MMH MHA Integration
Here’s the FLT
9(2)(c)
From: Jeanette Elley 9(2)(a)
Sent: Thursday, 3 November 2022 9:22 am
To: Tony Madsen <[email address]>
Cc: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Information
Chakerveersingh Sandhu 9(2)(a)
; Manvir Singh
9(2)(a)
Asfahaan Mirza 9(2)(a)
Samuel Wong
9(2)(a)
Rama Kumble 9(2)(a)
; Sanju Nannuri
9(2)(a)
Official
Subject: RE: RealMe test data for MMH MHA Integration
Hi Tony,
the
Interesting! Sorry about that. We must have created it ourselves.
Let’s jump to 9 with 9(2)(c)
If that’s taken already, then any other inserted number will do.
Thanks & Regards
under
Jeanette E.
From: Tony Madsen <[email address]>
Sent: Thursday, 3 November 2022 9:19 am
To: Jeanette Elley 9(2)(a)
Cc: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Chakerveersingh Sandhu 9(2)(a)
Manvir Singh
Released
9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Samuel Wong
9(2)(a)
Rama Kumble 9(2)(a)
; Sanju Nannuri
9(2)(a)
Subject: RE: RealMe test data for MMH MHA Integration
Looks like that email address has already been used on 18 Aug
Can I have another, or I can delete that account
Cheers Tony
From: Jeanette Elley 9(2)(a)
Sent: Thursday, 3 November 2022 9:07 am
To: Tony Madsen <[email address]>
Cc: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Chakerveersingh Sandhu 9(2)(a)
com>; Manvir Singh
9(2)(a)
Asfahaan Mirza 9(2)(a)
Samuel Wong
9(2)(a)
; Rama Kumble 9(2)(a)
; Sanju Nannuri
9(2)(a)
Subject: RE: RealMe test data for MMH MHA Integration
Hi Tony,
Thank-you. Shall we run with say 9(2)(c)
?
In response to your question yes, we prefill the MMH email field using the provided MHA email
address when creating the MMH user at sign-up.
After that the user can change their email address at either end, in MHA or in MMH, and the
login will still work fine (as demonstrated yesterday) but at account creation we do use the
1982
supplied MHA email address.
Thanks & Regards
Jeanette E.
Act
From: Tony Madsen <[email address]>
Sent: Thursday, 3 November 2022 8:59 am
To: Jeanette Elley 9(2)(a)
>
Cc: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Chakerveersingh Sandhu 9(2)(a)
Manvir Singh
9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Samuel Wong
Information
9(2)(a)
; Rama Kumble 9(2)(a)
; Sanju Nannuri
9(2)(a)
Subject: RE: RealMe test data for MMH MHA Integration
If you provide me with an email address that I can use I will create a new MHA RealMe account
and change the email address to one provided
Official
For login you won’t need the email address only the FLT unless you get a verification request.
Question: are you using the email address passed by the claim as MMH email address?
the
Cheers Tony
From: Jeanette Elley 9(2)(a)
Sent: Thursday, 3 November 2022 8:40 am
To:
under
Tony Madsen <[email address]>
Cc: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Chakerveersingh Sandhu 9(2)(a)
Manvir Singh
9(2)(a)
; Asfahaan Mirza 9(2)(a)
; Samuel Wong
9(2)(a)
Rama Kumble 9(2)(a)
; Sanju Nannuri
9(2)(a)
Released
Subject: RE: RealMe test data for MMH MHA Integration
Hi All,
Just a follow-up from my previous email. I am advised that we will be updating our email
validation to conform to the latest standards which do allow “+” sign (and various other special
characters), and that work will be commencing shortly.
However, in the meantime, while we wait for that work to be done, it would be great if you could
provide us with a simpler RealMe email address, to allow us to do the requested video for you of
a successful RealMe login.
Thanks & Regards
Jeanette E.
From: Jeanette Elley
Sent: Thursday, 3 November 2022 8:17 am
To: Tony Madsen <[email address]>
Cc: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Chakerveersingh Sandhu 9(2)(a)
com>; Manvir Singh
9(2)(a)
Asfahaan Mirza 9(2)(a)
; Samuel Wong
9(2)(a)
; Rama Kumble9(2)(a)
; Sanju Nannuri
9(2)(a)
Subject: RealMe test data for MMH MHA Integration
Hi Tony,
Good to meet you yesterday.
Thanks for providing us with a RealMe test case.
Unfortunately, we have a small problem with the RealMe email address that you provided
1982
because our email validation does not allow a “+” sign as part of the email address. A dash is
fine, but we don’t allow “+”.
Are you able to provide us with a RealMe test case without a “+” sign in the email address?
Act
Much appreciated
Thanks & Regards
Jeanette Elley PhD
Senior Business Analyst / Project Manager
9(2)(a)
Information
W: managemyhealth.co.nz
Official
Level 1, Cereus Health House
48 Market Place, Viaduct Harbour, Auckland 1010
This communication is and may be privileged and/or contain copyright material. If you are not the intended recipient of this email,
the
any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you have received this communication in error,
immediately contact us by return email or by calling +6493799166 and then irretrievably delete it and any attachments. We will
preserve the contents of any email message that you send us if we believe that we have an obligation to do so and we will otherwise
comply with the provision of the Privacy Act 1993 and any amendments thereto to the extent that it applies. Email sent from or to us
may be monitored for the purposes of quality control, systems administration and compliance. You should check for virus and other
harmful components before opening or using any attachments to this email. No reliance may be placed upon the contents of this
under
email as content can become corrupted in transmission. Our liability is limited only to re-supplying any affected attachment if
applicable
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
Released
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
1982
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
Act
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
Information
Official
the
under
Released
From:
Alan Monnox
To:
"Jeanette Elley"; Dylan Nyika; Megan Robinson; Tony Madsen
Cc:
"Asfahaan Mirza"; "Samuel Wong"; "Karanti Kaur Shergill"; "Rama Kumble"; "Sanju Nannuri"; "Manvir
Singh"; "Chakerveersingh Sandhu"
Subject:
RE: MMH My Health Account Integration for mob - meeting files attached
Date:
Wednesday, 2 November 2022 1:05:00 pm
Attachments:
image001.png
Hi Jeanette,
If you just run it during the session that will be fine.
Thanks,
Alan
From: Jeanette Elley9(2)(a)
Sent: Wednesday, 2 November 2022 12:55 pm
To: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
1982
Megan Robinson <[email address]>; Tony Madsen
<[email address]>
Act
Cc: Asfahaan Mirza 9(2)(a)
net>; Samuel Wong9(2)(a)
Karanti Kaur Shergill 9(2)(a)
Rama Kumble9(2)(a)
Sanju Nannuri 9(2)(a)
Manvir Singh 9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
Subject: RE: MMH My Health Account Integration for mob - meeting files attached
Hi All,
My apologies. It seems that the video was too big to send by email and I didn’t notice, so you
Information
may have received a restricted link instead.
I’ll see what I can do, but it may be simplest to just wait until the meeting to view the video.
See you then.
Regards
Official
Jeanette E.
From: Jeanette Elley
Sent:
the
Wednesday, 2 November 2022 11:11 am
To: Alan Monnox <[email address]>; Dylan Nyika <[email address]>;
Megan Robinson <[email address]>; Tony Madsen
<[email address]>
under
Cc: Asfahaan Mirza 9(2)(a)
; Samuel Wong 9(2)(a)
Karanti Kaur Shergill 9(2)(a)
Rama Kumble 9(2)(a)
Sanju Nannuri 9(2)(a)
; Manvir Singh 9(2)(a)
Chakerveersingh Sandhu 9(2)(a)
Subject: MMH My Health Account Integration for mob - meeting files attached
Hi @Alan,
Released
Looking forward to catching up this afternoon.
I thought it might be helpful to send you a couple of files in advance of our meeting this
afternoon.
Please find attached –
1. A demo video of the MMH mob app, showing MHA login (7 min)
2. A pptx showing screen shots for some of the required scenarios and error messages.
I realise that you may not have time to go through these in advance of the meeting, but here
they are, in case you want to do that.
We plan to go through these in the meeting.
We also have the tail end of another video (not attached here) which will demo the confidence
level decline that is described in the pptx.
For anything that is not sufficiently described here, we may be able to do a live demo in the
meeting if needed, or alternatively follow-up with another video if necessary.
Regards
Jeanette Elley PhD
Senior Business Analyst / Project Manager
9(2)(a)
W: managemyhealth.co.nz
1982
Level 1, Cereus Health House
48 Market Place, Viaduct Harbour, Auckland 1010
This communication is and may be privileged and/or contain copyright material. If you are not the intended recipient of this email,
any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you have received this communication in error,
Act
immediately contact us by return email or by calling +6493799166 and then irretrievably delete it and any attachments. We will
preserve the contents of any email message that you send us if we believe that we have an obligation to do so and we will otherwise
comply with the provision of the Privacy Act 1993 and any amendments thereto to the extent that it applies. Email sent from or to us
may be monitored for the purposes of quality control, systems administration and compliance. You should check for virus and other
harmful components before opening or using any attachments to this email. No reliance may be placed upon the contents of this
email as content can become corrupted in transmission. Our liability is limited only to re-supplying any affected attachment if
applicable
Information
Official
the
under
Released
From:
Jeanette Elley
To:
Alan Monnox; Bhumika Talsania; Dylan Nyika
Cc:
Asfahaan Mirza; Sanju Nannuri; Rama Kumble; Digital Health Identity Integration
Subject:
RE: MMH My Health Account Integration for mobile - demo around 3pm Wed 2 Nov?
Date:
Friday, 28 October 2022 10:40:02 am
Attachments:
image001.png
Hi @Alan,
Apologies for the delay. We’d like to aim for this coming Wednesday 2 Nov, at our usual time (it
was 3pm wasn’t it?) if that suits you?
I will double check that we’ve got everything covered and that our demo video will be ready, and
will let you know as soon as possible if we hit any obstacles and need to change it.
Thanks & Regards
Jeanette E.
From: Alan Monnox <[email address]>
1982
Sent: Wednesday, 26 October 2022 1:48 pm
To: Jeanette Elley 9(2)(a)
; Bhumika Talsania
Act
<[email address]>; Dylan Nyika <[email address]>
Cc: Asfahaan Mirza 9(2)(a)
; Sanju Nannuri 9(2)(a)
Rama Kumble9(2)(a)
; Digital Health Identity Integration
<[email address]>
Subject: RE: MMH My Health Account Integration for mobile - demonstration requirements
Hi Jeanette,
Further to my last email, do you have a date in mind for the demo?
Information
I’m happy to set something up once you are ready on your side.
Cheers,
Alan
From: Jeanette Elley 9(2)(a)
Official
Sent: Tuesday, 25 October 2022 5:32 pm
To: Bhumika Talsania <[email address]>; Dylan Nyika
the
<[email address]>; Alan Monnox <[email address]>
Cc: Asfahaan Mirza 9(2)(a)
; Sanju Nannuri 9(2)(a)
Rama Kumble 9(2)(a)
Subject: MMH My Health Account Integration for mobile - demonstration requirements
under
Hi @Bhumika at al,
It was earlier indicated that the mobile version of MMH My Health Account Integration would
require a separate demonstration session to gain approval and sign-off.
I understand that our mobile side of the development is almost complete, so I’d like to arrange
the demo.
[Note that the 9(2)(c)
not sign-up. Sign-up can, however, be
Released
done via web browser on a mobile phone, using the already approved version.]
My first question is whether you will require (or prefer) an
in-person online demo, or will a
video demo suffice?
Secondly, I assume that the demo will need to show the following. Please confirm?
1. A new MMH user
signing-up via MHA in v2 self-registration but rejected due to
confidence level too low (can’t easily demo with mob sign-in unless change confidence
level for existing user, suggest repeat web version to show logic).
2. A new MMH user
self-registering via MHA in v2 self-registration, logging out, and then
logging in again successfully via mob app.
3. Use the MHA test back end to go in to the MHA account and
change the email address,
and show that the mob login still works.
4. Use the MHA test back end to go in to the MHA account and
decline consent, then show
the error message from the mob app.
5. Demonstrate handling a
failed MHA login from the mob app.
6. Demonstrate handling a
failed Real Me login from the mob app.
7. Also demonstrate the
error message from the mob if the MMH user had not previously
registered via MHA.
Please let us know if anything else will be required to get our mobile app over the line.
Much appreciated.
Thanks & Regards
Jeanette Elley PhD
Senior Business Analyst / Project Manager
1982
9(2)(a)
Act
W: managemyhealth.co.nz
Level 1, Cereus Health House
48 Market Place, Viaduct Harbour, Auckland 1010
This communication is and may be privileged and/or contain copyright material. If you are not the intended recipient of this email,
Information
any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you have received this communication in error,
immediately contact us by return email or by calling +6493799166 and then irretrievably delete it and any attachments. We will
preserve the contents of any email message that you send us if we believe that we have an obligation to do so and we will otherwise
comply with the provision of the Privacy Act 1993 and any amendments thereto to the extent that it applies. Email sent from or to us
may be monitored for the purposes of quality control, systems administration and compliance. You should check for virus and other
harmful components before opening or using any attachments to this email. No reliance may be placed upon the contents of this
email as content can become corrupted in transmission. Our liability is limited only to re-supplying any affected attachment if
applicable
Official
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
the
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
under
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
Released
From:
Sanju Nannuri
To:
Alan Monnox
Cc:
Jeanette Elley; Asfahaan Mirza; Bhumika Talsania; Digital Health Identity Integration
Subject:
RE: MHA OIDC-Client ID and Secret for MMH NZ Mobile Apps
Date:
Tuesday, 18 October 2022 4:07:22 pm
Attachments:
image001.png
Got it. Thanks Alan.
From: Alan Monnox <[email address]>
Sent: Tuesday, 18 October 2022 12:56 PM
To: Sanju Nannuri 9(2)(a)
Cc: Jeanette Elley 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Bhumika Talsania <[email address]>; Digital Health Identity Integration
<[email address]>
Subject: RE: MHA OIDC-Client ID and Secret for MMH NZ Mobile Apps
1982
Hi Sanju,
You asked for support for a mobile app, which uses authorization code with PKCE. As that flow is
Act
all from the front end it doesn’t use a shared secret but instead relies on the redirect uri for
whitelisting.
If you want support for the authorization code grant type then we can also set you up as a Web
app.
Cheers,
Alan
From:
Information
Sanju Nannuri 9(2)(a)
Sent: Tuesday, 18 October 2022 3:31 pm
To: Alan Monnox <[email address]>
Cc: Jeanette Elley 9(2)(a)
Asfahaan Mirza 9(2)(a)
Bhumika Talsania <[email address]>; Digital Health Identity Integration
Official
<[email address]>
Subject: RE: MHA OIDC-Client ID and Secret for MMH NZ Mobile Apps
the
Hi Alan
We got the client ID from DHI team. Where do I access client secret for it.
Regards
Sanju
under
From: Alan Monnox <[email address]>
Sent: Tuesday, 4 October 2022 5:45 AM
To: Sanju Nannuri 9(2)(a)
Cc: Jeanette Elley 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Bhumika Talsania <[email address]>; Digital Health Identity Integration
Released
<[email address]>
Subject: RE: MHA OIDC-Client ID and Secret for MMH NZ Mobile Apps
Hi Sanju,
Your mobile app will probably need a new registration at our end.
Can you fill out this form with the details of the app and specifically let us know the redirect URI.
We can then get you set up with INT access.
Here’s the form 9(2)(c)
This form will most likely be a cut and paste of the last one for the Web app but can you ensure
you call out any differences with the mobile version’s use of My Health Account
Cheers,
Alan
From: Sanju Nannuri 9(2)(a)
Sent: Monday, 3 October 2022 7:09 pm
To: Alan Monnox <[email address]>
Cc: Jeanette Elley 9(2)(a)
; Asfahaan Mirza 9(2)(a)
Bhumika Talsania <[email address]>
Subject: MHA OIDC-Client ID and Secret for MMH NZ Mobile Apps
Hi Alan
We are working on MMH NZ Mobile Apps – MHA SSO now. Can you please let me know details
required to get new Client Id and Secret for Mobile Apps.(for both Android and iOS)
Kind regards,
Sanju
1982
Sanju Nannuri
Act
So utions Architect
9(2)(a)
W: managemyhea th.co.nz
Information
Level 1, 48 Market Place,
Viaduct Harbour,
Auckland 1010,
New Zealand
This communication is and may be privileged and/or contain copyright material. If you are not the intended
recipient of this email, any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you
have received this communication in error, immediately contact us by return email or by calling +6493799166 and
Official
then irretrievably delete it and any attachments. We will preserve the contents of any email message that you
send us if we believe that we have an obligation to do so and we will otherwise comply with the provision of the
Privacy Act 1993 and any amendments thereto to the extent that it applies. Email sent from or to us may be
the
monitored for the purposes of quality control, systems administration and compliance. You should check for virus
and other harmful components before opening or using any attachments to this email. No reliance may be
placed upon the contents of this email as content can become corrupted in transmission. Our liability is limited
only to re supplying any affected attachment if applicable
under
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
Released
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
1982
Act
Information
Official
the
under
Released
From:
Sanju Nannuri
To:
Alan Monnox; Bhumika Talsania
Cc:
Jeanette Elley; Digital Health Identity Integration
Subject:
RE: redirect Uri for Mobile Apps
Date:
Tuesday, 18 October 2022 3:25:18 pm
Attachments:
image001.png
Hi Alan
Thank you. I will get back to you for additional URIs if required.
Regards
Sanju
From: Alan Monnox <[email address]>
Sent: Monday, 17 October 2022 12:06 PM
To: Sanju Nannuri 9(2)(a)
; Bhumika Talsania
<[email address]>
1982
Cc: Jeanette Elley 9(2)(a)
Digital Health Identity Integration
<[email address]>
Act
Subject: RE: redirect Uri for Mobile Apps
Hi Sanju,
We’re getting the other app reg set up for you.
I have to the two localhost URIs. Any others you’d like us to add?
Cheers
Alan
From:
Information
Sanju Nannuri 9(2)(a)
Sent: Monday, 17 October 2022 10:58 am
To: Bhumika Talsania <[email address]>; Alan Monnox
<[email address]>
Cc: Jeanette Elley9(2)(a)
Official
Subject: RE: redirect Uri for Mobile Apps
Hi Bhumika
the
Initially we have decided to have separate client Id and secret for Mobile Apps. Can you pls check
with your Team on this.
Currently we are using web credentials for development.
Regards
under
Sanju
From: Bhumika Talsania <[email address]>
Sent: Wednesday, 12 October 2022 4:42 AM
To: Sanju Nannuri 9(2)(a)
; Alan Monnox <[email address]>
Cc: Jeanette Elley 9(2)(a)
Released
Subject: RE: redirect Uri for Mobile Apps
Hi Sanju,
Additional redirect URLs have been added to the app registration in INT.
Thanks and Regards,
Bhumika Talsania Delivery Lead
Data & Digital
M +64 22 070 2194
E [email address]
From: Bhumika Talsania
Sent: Tuesday, 11 October 2022 7:28 am
To: Sanju Nannuri 9(2)(a)
Alan Monnox <[email address]>
Cc: Jeanette Elley 9(2)(a)
Subject: RE: redirect Uri for Mobile Apps
Thanks Sanju,
Alan is on leave, so I will take up the follow up on this task.
Thanks and Regards,
Bhumika Talsania Delivery Lead
Data & Digital
9(2)(a)
E [email address]
From: Sanju Nannuri 9(2)(a)
1982
Sent: Monday, 10 October 2022 7:20 pm
To: Alan Monnox <[email address]>
Cc:
Act
Jeanette Elley 9(2)(a)
Bhumika Talsania
<[email address]>
Subject: redirect Uri for Mobile Apps
Hi Alan
Please add below Uris for MMH mobile App Redirect Uris
9(2)(c)
Information
Kind regards,
Sanju
Sanju Nannuri
So utions Architect
Official
9(2)(a)
the
W: managemyhea th.co.nz
under
Level 1, 48 Market Place,
Viaduct Harbour,
Auckland 1010,
New Zealand
This communication is and may be privileged and/or contain copyright material. If you are not the intended
recipient of this email, any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you
have received this communication in error, immediately contact us by return email or by calling +6493799166 and
then irretrievably delete it and any attachments. We will preserve the contents of any email message that you
Released
send us if we believe that we have an obligation to do so and we will otherwise comply with the provision of the
Privacy Act 1993 and any amendments thereto to the extent that it applies. Email sent from or to us may be
monitored for the purposes of quality control, systems administration and compliance. You should check for virus
and other harmful components before opening or using any attachments to this email. No reliance may be
placed upon the contents of this email as content can become corrupted in transmission. Our liability is limited
only to re supplying any affected attachment if applicable
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
1982
If you have received this message in error, please notify the sender
immediately and delete this message.
Act
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
Information
Official
the
under
Released
From:
Jeanette Elley
To:
Robyn Tipene; Asfahaan Mirza; Digital Health Identity Integration; Alan Monnox
Cc:
Rama Kumble; Sanju Nannuri; Samuel Wong; Gerard Keenan
Subject:
RE: Security Report for My Health Account
Date:
Thursday, 13 October 2022 8:47:54 am
Attachments:
image001.png
image002.jpg
image003.jpg
image004.png
HI @Robyn,
Apologies. The mob app was intended to be developed alongside the web app but there was a
delay with resourcing.
We will discuss internally and get back to you shortly with estimated dates for
a. Mob app demo
b. Web deployment
1982
Thanks & Regards
Jeanette E.
Act
From: Robyn Tipene <[email address]>
Sent: Wednesday, 12 October 2022 4:08 pm
To: Jeanette Elley 9(2)(a)
Asfahaan Mirza 9(2)(a)
; Digital
Health Identity Integration <[email address]>; Alan Monnox
<[email address]>
Cc: Rama Kumble 9(2)(a)
; Sanju Nannur 9(2)(a)
Samuel Wong 9(2)(a)
Gerard Keenan <[email address]>
Information
Subject: RE: Security Report for My Health Account
Hi Jeanette,
A demo will be required as this is a new onboarding request.
Better clarity around delivery dates would be greatly appreciated please. If we had known that
things were delayed on your end, we wouldn’t have pushed the web app production credential
Official
requests through with urgency.
If you could advise dates for both onboarding requests that would be great.
the
Kind regards,
Robyn
From: Jeanette Elley 9(2)(a)
under
Sent: Wednesday, 12 October 2022 12:51 pm
To: Asfahaan Mirza 9(2)(a)
; Digital Health Identity Integration
<[email address]>; Robyn Tipene <[email address]>; Alan Monnox
<[email address]>
Cc: Rama Kumble 9(2)(a)
; Sanju Nannuri 9(2)(a)
Samuel Wong9(2)(a)
Gerard Keenan <[email address]>;
Released
Sushant Balajee <[email address]>
Subject: RE: Security Report for My Health Account
Hi Megan, Alan, & Robyn,
We need to completely finish the mobile app side of the development before we can go live.
The mob solution does not include registration (sign-up), it just consists of the sign-in component
(assuming that sign-up has occurred via web).
For mob, the login page is essentially the same as the MHA sign-in from the web.
Do you require a demo of our mobile solution once it is done, or will the demo we have given
already for web suffice?
Thanks & Regards
Jeanette E.
From: Asfahaan Mirza 9(2)(a)
Sent: Wednesday, 12 October 2022 12:44 pm
To: Digital Health Identity Integration <[email address]>; Robyn Tipene
<[email address]>; Jeanette Elley 9(2)(a)
Alan Monnox
<[email address]>
Cc: Rama Kumble 9(2)(a)
Sanju Nannur 9(2)(a)
Samuel Wong 9(2)(a)
Gerard Keenan <[email address]>;
Sushant Balajee <[email address]>
Subject: Re: Security Report for My Health Account
Dear Megan
Confirming that I have received the credentials.
Thank you
1982
Asfahaan Mirza PhD
GM Strategy & Innovation
Act
9(2)(a)
W: managemyhealth.co.nz
Information
Level 1, 48 Market Place, Viaduct Harbour,
Auckland 1010, New Zealand
This communication is and may be privileged and/or contain copyright material. If you are not the intended recipient of this
email, any use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you have received this
communication in error, immediately contact us by return email or by calling +6493799166 and then irretrievably delete it and
any attachments. We will preserve the contents of any email message that you send us if we believe that we have an
obligation to do so and we will otherwise comply with the provision of the Privacy Act 1993 and any amendments thereto to
Official
the extent that it applies. Email sent from or to us may be monitored for the purposes of quality control, systems
administration and compliance. You should check for virus and other harmful components before opening or using any
attachments to this email. No reliance may be placed upon the contents of this email as content can become corrupted in
transmission. Our liability is limited only to re-supplying any affected attachment if applicable
the
From: Megan Robinson <[email address]> on behalf of Digital Health
Identity Integration <[email address]>
Date: Wednesday, 12 October 2022 at 11:08 AM
under
To: Robyn Tipene <[email address]>, Jeanette Elley
9(2)(a)
Alan Monnox <[email address]>, Asfahaan Mirza
9(2)(a)
Cc: Rama Kumble 9(2)(a)
Sanju Nannuri
9(2)(a)
, Samuel Wong 9(2)(a)
Gerard Keenan
<[email address]>, Sushant Balajee <[email address]>
Released
Subject: RE: Security Report for My Health Account
Hi all,
Prod credentials were sent through to Asfahaan yesterday afternoon - @Asfahaan, can you please
confirmed that you received these details?
If you could advise us of your planned go live date as soon as you are able that would be greatly
appreciated.
Many thanks,
Digital Health Identity Integration Team
1982
Act
Information
Official
the
under
Released
9(2)(a)
; Sanju Nannuri 9(2)(a)
Samuel Wong
9(2)(a)
Subject: RE: Security Report for My Health Account
Hi Jeanette,
Thanks for the quick response.
The privacy assessment should be okay. I’ll chase this up at our end, as it looks like I’ve missed a
checkbox in our tracking system. No further action required on the PIA from you but I will confirm.
If you can provide an existing security risk assessment that covers the medium question set that
would be ideal. Otherwise, a concise report covering each question will be fine, as we also have
your pen test.
Thanks,
Alan
From: Jeanette Elley 9(2)(a)
1982
Sent: Monday, 3 October 2022 3:49 pm
To: Alan Monnox <[email address]>
Cc: Digital Health Identity Integration <[email address]>; Robyn Tipene
Act
<[email address]>; Asfahaan Mirza 9(2)(a)
; Rama Kumble
9(2)(a)
Sanju Nannuri 9(2)(a)
Samuel Wong
9(2)(a)
Subject: RE: Security Report for My Health Account
Hi @Alan
My apologies. I thought that the Strong Box report would be considered to be the risk assessment
report, and that the other questions only needed to be answered in the absence of a security risk
Information
assessment report.
However, from what you say below I gather that what I have sent you is only considered to fulfil
the pen test and OWASP components.
It appears that you still require us to send you a more comprehensive security report as well.
Official
I agree that, due to the sensitivity of the data, we do fall into the medium risk category.
As far as the PIA is concerned, I sent through a privacy assessment which was written in relation to
the
our full PIA, but the latter is currently being modified following external review and is not yet
available. If the privacy assessment I sent is not sufficient then I will augment it or replace it with
more extensive PIA detail.
I’ll attempt to address these two issues and will be back in touch as soon as I can.
under
Thanks & Regards
Jeanette E.
From: Alan Monnox <[email address]>
Sent: Monday, 3 October 2022 3:14 pm
To: Jeanette Elley 9(2)(a)
>
Cc: Digital Health Identity Integration <[email address]>; Robyn Tipene
Released
<[email address]>; Asfahaan Mirza 9(2)(a)
; Rama Kumble
9(2)(a)
; Sanju Nannuri 9(2)(a)
Samuel Wong
9(2)(a)
Subject: RE: Security Report for My Health Account
Hi Jeanette,
Thanks for providing the pen test report.
I’ve discussed the report with our security team and it good to see that you’ve remediated the
issues discovered. However, as part of the on-boarding process we still need a report that answers
the questions in the compliance section of the process.
See
9(2)(c)
For these baselines questions, we still need the PIA but you have completed the independent pen
test and addressed OWASP. If you have also completed a security risk assessment then we would
like to have more information on the findings, i.e. when run and a risk summary if available.
The main security topic you need to cover are the “Medium Risk Solution” questions, as defined
on the Compliance page. The medium risk question set is deemed applicable given the size of
MMH. Can you please provide your response to these questions in report form.
If you have any questions about the report please let me know and I can arrange a call.
Cheers,
Alan
From: Jeanette Elley 9(2)(a)
Sent: Thursday, 29 September 2022 11:40 am
To:
1982
Alan Monnox <[email address]>
Cc: Digital Health Identity Integration <[email address]>; Robyn Tipene
<[email address]>; Asfahaan Mirza 9(2)(a)
; Rama Kumble
Act
9(2)(a)
; Sanju Nannuri 9(2)(a)
; Samuel Wong
9(2)(a)
Subject: RE: Security Report for My Health Account
Hi Alan,
Attached is our most recent VAPT report, from 9 Feb 2022. I believe that it covers all the areas
required by your specifications.
It clearly shows that all Critical and High-risk issues were fixed immediately, but that a few
Information
medium and low risk issues remained outstanding as at the time of the report.
I am advised that all remaining Medium and Low-risk issues mentioned in this report were
subsequently fixed, but that was after the report was released, so all I can do at this point is advise
you of the fixes (see below), and let you know that our
next scheduled VAPT report is scheduled
Official
for the end of October, once the MMH v2 provider portal upgrade has been completed.
List of MHA Security Issues outstanding in Feb VAPT report from StrongBox
the
Severity
Description
Comment
MMH Fix
1
Medium
Missing rate limiting
9(2)(c)
under
2
Medium
Unauthorised Google
Maps API Key (Known
issue)
3
Medium
Session token in URL
4
Low
Web server
Released fingerprinting
5
Low
Clickjacking
6
Low
Information exposure
through error message
We will send you a copy of the latest VAPT report once that becomes available.
Regards
Jeanette Elley PhD
Senior Business Analyst / Project Manager
9(2)(a)
W: managemyhealth.co.nz
Level 1, Cereus Health House
48 Market Place, Viaduct Harbour, Auckland 1010
This communication is and may be privileged and/or contain copyright material. If you are not the intended recipient of this email, any
use, forwarding, printing or reproduction of it or any attachment, is prohibited. If you have received this communication in error,
immediately contact us by return email or by calling +6493799166 and then irretrievably delete it and any attachments. We will
preserve the contents of any email message that you send us if we believe that we have an obligation to do so and we will otherwise
comply with the provision of the Privacy Act 1993 and any amendments thereto to the extent that it applies. Email sent from or to us
may be monitored for the purposes of quality control, systems administration and compliance. You should check for virus and other
harmful components before opening or using any attachments to this email. No reliance may be placed upon the contents of this email
1982
as content can become corrupted in transmission. Our liability is limited only to re-supplying any affected attachment if applicable
From: Alan Monnox <[email address]>
Sent: Thursday, 29 September 2022 9:35 am
Act
To: Jeanette Elley 9(2)(a)
Cc: Digital Health Identity Integration <[email address]>; Robyn Tipene
<[email address]>
Subject: Security Report for My Health Account
Hi Jeanette,
Any update on the security report for completing the onboarding process for My Health Account?
Once we have this and the signed off terms of use we can get you sorted out with your production
Information
access.
Cheers,
Alan
Alan Monnox
Official
Solutions Architect
Data & Digital
the
waea pūkoro: 9(2)(a)
|
īmēra: [email address]
Follow us on LinkedIn | Facebook | Instagram
under
Te Whatu Ora – Health New Zealand
TeWhatuOra.govt.nz
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to legal privilege.
Released
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to legal privilege.
1982
If you are not the intended recipient, do not read, use, disseminate,
distribute or copy this message or attachments.
Act
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
****************************************************************************
Information
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
Official
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
the
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway
under
****************************************************************************
Statement of confidentiality: This e-mail message and any accompanying
attachments may contain information that is IN-CONFIDENCE and subject to
legal privilege.
If you are not the intended recipient, do not read, use, disseminate,
Released
distribute or copy this message or attachments.
If you have received this message in error, please notify the sender
immediately and delete this message.
****************************************************************************
This e-mail message has been scanned for Viruses and Content and cleared by the Ministry of
Health's Content and Virus Filtering Gateway