In technical deployment, the Gillie.AI platform is integrated into the organisation's existing information systems and activated for production use. After technical deployment, the rollout phase is initiated.
Some of the technical deployment tasks are optional. These are marked as optional below.
A. Project planning
The deployment project begins with project planning, where its phases and goals are determined. The end result of planning is a work plan. The project lasts from 1 to 8 weeks, depending on the number of integrations to be implemented. The tasks of the planning phase are listed below.
| No | Task | Checklist |
|---|---|---|
| 1 | Appoint a project manager. The project manager shoukd have technical skills. Name the members of the project team who have the necessary expertise in software and substance. |
|
| 2 | Set the steering group. The technical deployment is monitored in the steering group, which meets once a month. The steering group approves e.g. moving into production. |
|
| 3 | Make a work plan. It includes the tasks, their schedule and the responsible person for each task. The tables on this page can be used as a basis for the plan. |
|
| 4 |
Enumerate the functionalities to be implemented. Functionalities include, for example:
|
|
| 5 | Identify user organisations and users |
|
| 6 | Identify the end customers. The potential end customers are e.g. home care clients, emergency service clients, nursing home clients, patients discharged from the hospital and patients monitored remotely. |
|
| 7 | List the information systems to be integrated. Typical systems are customer, patient record and alarm systems. |
|
| 8 | List the device types to be integrated. optional Typical devices are emergency phones and various measuring devices. |
|
B. Deployment planning
In deployment planning, the project and application are presented to different stakeholders. In addition, post-deployment support is planned and a preliminarily contingency plan is prepared with the user organisation.
| No | Task | Checklist |
|---|---|---|
| 1 | Hold a kick-off meeting for project team members. optional In the meeting, the work plan is presented and the weekly meeting of the project group is agreed upon to monitor the technical deployment. |
|
| 2 | Describe the system architecture and integrations. optional |
|
| 3 | Present the application to a potential architecture group. optional If the organisation has a department or function responsible for the overall systems architecture, the deployment of the application may require the approval of that body. |
|
| 4 | Present the application to data security. optional The implementation of the application may require the approval of the information security manager. |
|
| 5 | Introduce / inform the user organisation. optional |
|
| 6 | If necessary, update the end customers' consent / care and service plan optional |
|
| 7 |
Plan post-implementation support. The processes and responsibilities in the event of deviations must be described. For example, an integration stops working or a regional communication failure prevents the use of the application. Make instructions and a contingency plan for end users in this situation. For the necessary parties (including suppliers), information on how to act during the deviation and who to contact. Guidance for both technical support and admin users. Make sure IT service production has information about available integrations with Gillie. This list is used for version changes and incidents. |
|
| 8 | Inform the suppliers of systems and devices to be integrated. optional |
|
C. Integrations
The most significant work of deployment is the implementation and testing of integrations. For this purpose, the Gillie.AI platform has a SandBox environment where integrations can be tested before starting production use.
| No | Task | Checklist |
|---|---|---|
| 1 | Set up a Sandbox. Ask Gillie Support (support@gillie.ai) to set up a SandBox environment. |
|
| 2 |
If necessary, create a VPN connection. optional |
|
| 3 |
Open the necessary ports on the firewall. optional |
|
| 4 |
Configuration and testing of information system integration x (make an own task for each information system to be integrated). |
|
| 4.1 |
Configuration and testing of customer social security number fetch optional |
|
| 4.2 |
Configuration and testing of customer basic data retrieval optional |
|
| 4.3 |
Configuration and testing of care notes fetch optional |
|
| 4.4 |
Configuration and testing of medication data retrieval optional |
|
| 4.5 |
Configuring and testing lab data retrieval optional |
|
| 4.6 |
Configuration and testing of diagnoses fetch optional |
|
| 4.7 |
Configuration and testing of emergency call retrieval optional |
|
| 5 |
Configuration and testing of device integration x (make each type of device to be integrated its own task). optional |
|
| 6 |
AD configuration and testing. optional |
|
| 7 |
Decision on moving into production. The steering group gives permission for moving into production. Apply for change management approval (CAB) before the steering group. |
|
D. Moving into production
This describes the tasks that must be performed before the production use of the application.
| No | Task | Checklist |
|---|---|---|
| 1 | Set up the production environment. Contact Gillie support (support@gillie.ai) to set up a production environment. |
|
| 2 |
Configure the production environment |
|
| 3 |
Activate the integrations. Activate the integrations identified in the planning phase. |
|
| 4 |
Ensure the operation of the application in production. Check that the end customer information is displayed in the application. |
|
| 5 |
Grant access rights. Grant users access either from the application's administrator view or from an external access management application (e.g. AD). |
|
| 6 |
Pair devices to end customers. optional If end customers have devices that do not automatically pair with Gillie.AI, pair the devices manually. |
|
| 7 | Train admin and support users |
|
Comments
Article is closed for comments.