Current leader : Satbir

Progress

We first established what our E2E scenario would be for WeChat and Whatsapp.

For WhatsApp, we initially intended for the connector to allow any person using the app to use the camera to extract data from the physical invoice, insert it in a template used in WhatsApp and send it to an NHS clerk who can quickly process the data.

However, this solution would be deemed too technical and time consuming so we had to think of a solution which was just as impactful but easier to implement. We settled on sending appointment reminders and prescription ID to patients which was much less technical for it required fewer components in the design.

Personas and End-to-End scenario

Personas and End-to-End scenario

For WeChat, we struggled to think of a scenario as it had a lot of existing solutions to what we thought of. Eventually, we asked if the same scenario which was used for WhatsApp could be used for WeChat. We were told this was okay. (WhatsApp can work for the NHS and WeChat can work in China’s healthcare system).

Our next step was to develop the HCI. We decomposed the process into the following: Requirements, Scenarios and Personas; Sketches, Prototypes and Prototype Evaluation.

Throughout the presentation development, we sought to highlight the key skills and principles covered in the HCI lectures.

Greater reference is in the HCI section

The Connector proposal is a README file sent to Microsoft which secures the publishing rights to a certain connector. As we were working with Microsoft for this project, our proposal was given priority over individual developers

ReadME file

ReadME file

Proposal on the Microsoft Github

Proposal on the Microsoft Github

Plans

Learn about the development process of the connector - Become familiar with each step of the process, its purpose and possible blockers

Research Oauth - this is a possible authentication method that will be used for our connector, so understanding how/why it is used can help troubleshooting and development

Create Microsoft 365 developer account + Meta Developer account - This is necessary for us to acquire the resources and environment to develop the connectors