Client Meetings & Feedback
We kept in constant contact with our client right from our initial meeting, through development all the way until our final delivery meeting. We see the client-developer relationship one of the most important aspects of the project and always tried to have a constant, clear communication chain with him. We did this through a variety of in-person meetings, web conferences and telephone calls all of which are summarised below. You can also see the clients final feedback for our final Proof Of Concept application which we delivered to him on 18th April 2017.
Meetings Summary
| Meeting | Date | Topic | Summary |
|---|---|---|---|
| 1 | 16/10/16 | Introduction | Completed an hour and a half conference call Introduced ourselves and discussed our strengths and interests Provided an overview of the history behind the OpenEyes project Provided an outline of two potential projects The 1st project was based around exporting the current database format to openEHR format The 2nd project was based around data dictionaries Asked to research openEHR and data dictionaries |
| 2 | 2/11/16 | Project Update | Completed a 2 hour meeting at the Across Health’s office in London Provided instructions of software and tools to download (OpenEHR clinical modelling tools) |
| 3 | 18/11/16 | Project Decision | Third meeting with client which took place at Across Health’s office in London Chose one project: database/data dictionary project Discussed data dictionaries and relational databases Discussed low level and high level requirements. |
| 4 | 21/11/16 | Meeting with technical team | We arranged a meeting with Peter Gallagher, who works for Across Health It was the fourth meeting with client We were provided help to download software that enabled us to the access the OpenEyes tool via Vagrant |
| 5 | 29/11/16 | Requirements Finalised | 5th meeting with client which was at Royal Festival Hall (near Waterloo) Meeting was completed using an agenda with a prepared list of questions Discussed the initial requirements created and made changes Confirmed a project description Developed a good understanding of the application to be developed Discussed the format of the application Discussed what research and experiment should be conducted Discussed tools and frameworks that can help us |
| 6 | 27/01/17 | Update | Discussed latest project developments Talked about potential dates for meeting |
| 7 | 15/02/17 | Iteration 1 Demo & Feedback | Discussed latest project developments Discussed the required design for application Discussed the required format for database Talked about potential dates for next meeting |
| 8 | 9/03/17 | Iteration 2 Demo & Feedback | Discussed the current state of application with client Client made suggestions about changing the front end design No longer a priority to implement CSV file upload and parsing |
| 9 | 23/03/17 | Iteration 3 Demo & Feedback | Client tested our current iteration, checked that we had implemented the changes he requested Mapping section discussed - client went through suggestions for the design and how he wants to integrate it with the current state of the application We also talked about to implement the search feature. |
| 10 | 05/04/17 | Iteration 4 Demo & Feedback | Demonstrated 4th iteration of application Updates to mapping section discussed |
| 11 | 19/04/17 | Final Delivery | Delivered final application to client and received his feedback |
Final Client Feedback
Our client gave us some feedback via email after our final meeting on Wednesday 19th April 2017. His comments were:
"Thank you for running through the Maple product today. This tool is going to help with managing the data dictionaries associated with OpenEyes and the other clinical systems it shares data with. I especially liked how clean and easy it is to update dictionary entries and make mappings between dictionary data points. Very good job. I look forward to using Maple and adding even more features in the near future.
Thank you for your great work. It has been a pleasure working with you."