The roles involved here are:
| Expand | ||
|---|---|---|
| ||
This is someone that understands the overall workflow. It’s awesome if this person can educate the other roles to help give them context of the overall system. |
| Expand | ||
|---|---|---|
| ||
This the role of building out the interfaces in with Iguana. This person needs to understand the data flow and how to manipulate it to achieve the end result. |
| Expand | ||
|---|---|---|
| ||
This is role over over seeing that everything is completed correctly as part of the project plan. |
These are the tasks which need to be performed:
| Expand | ||
|---|---|---|
| ||
This is the process of testing an interface with sample data. Getting good sample data is difficult. Roles: Integration Engineer and Quality Assurance Engineer |
| Expand | ||
|---|---|---|
| ||
Putting the system into production. To do this well it’s essential to look at the complete end to end workflow - it should be possible to see the Epic screens and understand how the users interact with them and how the data flows through into your application. Roles: Integration Engineer and Quality Assurance Engineer |
| Expand | ||
|---|---|---|
| ||
Is the overall system able to handle the volume of data coming through the interface? This involves trying out the system and seeing what the bottlenecks are in its performance. Roles: Integration Engineer and Quality Assurance Engineer |
| Expand | ||
|---|---|---|
| ||
We need to make sure that the implementation and set up complies with HIPAA regulations. Roles: Security Engineer Legal |
| Expand | ||
|---|---|---|
| ||
What are the most likely operational failure points in the system and for each point what is the mitigation measure? i.e. what happens if the virtual machine Iguana is running on fails. Roles: Quality Assurance Engineer |
| Expand | ||
|---|---|---|
| ||
How will the system be turned on in production and verified to work as intended? |