Approach

Our approach: two phases

Every project guided by Hawking is unique. However, you can state that the average development trajectory of Hawking Healthcare Technology consists of two phases:

1. Proof of Concept

2. Technical Phase

Proof of concept

We assess our client's requirements and existing infrastructure during the POC phase. This is done with a POC team consisting of members from Hawking and the client. Within a predetermined timeframe, the Proof of Concept is delivered, which includes the following components:

• A demo environment containing a realistic and understandable setup of CareOS and Discovery with various sample clients. This environment remains available for a predetermined period;
• A customised reporting screen with information about clients in different sections, with relevant reporting tags for each section based on input from the joint POC team;
• If applicable and as needed, an overview screen or dashboard to view registration data;
• Multiple short-cycle iterations of these screens in consultation with the POC team;
• A clear understanding for the entire team of the desired functionalities of Discovery;
• A demonstration of these screens by Hawking to stakeholders and the POC team.

After the POC, we will organise a session to determine whether and how we should proceed with further implementation.

Technical phase

To enable a sustainable implementation of the CareOS platform after the Proof of Concept, we build a complete integration with the electronic patient record (EPR) used by the client and any other systems (if APIs are available). CareOS is based on open interoperability standards, allowing integrations with EPRs and external systems in principle. Collaborating with the responsible IT personnel within your organisation during this phase is essential. The following points are relevant:

1. Identify the exact data exchange requirements with the EPR and potentially other third parties (functional and technical). This may depend on the chosen implementation within these systems.
2. Configure interfaces with other parties as needed.
3. Set up hosting, including certificates and domains, if necessary.
4. Configure authentication, including potential integration with a Single Sign-On (SSO) solution, such as Azure AD or Google Workspace.
5. Configure communication settings to enable CareOS to send notifications, for example, via email.

This technical phase ensures seamless integration of CareOS with your existing systems and data exchange processes.

Modular approach for deploying CareOS apps

In our implementation plan, we opt for an iterative approach that allows us to work responsibly to build a stable foundation while implementing in your organisation. The CareOS platform is designed to be configured modularly, per process, or role. The starting and ending points of the implementation will be determined in consultation with you.

Initially, we'd like to give you a general estimate of which processes and roles within your organisation will be implemented. If necessary, this can be expanded or streamlined during the implementation process. The configuration of the apps depends on roles, preferences, and requirements. For instance, in Discovery, the setup is done per role and process (e.g., medical staff or group sessions in a clinic), while in Quest, it's based on questionnaires.

During the setup of the apps, we follow a three-phase approach:

1. Inventarisation Phase: In this phase, we gather the requirements and preferences of the end-users, assess the possibilities, and establish a corresponding timeline. We also map the current situation, exploring the business processes and data flows.

2. Configuration and Technology Phase: The technology is adjusted to meet the client's requirements based on the information collected in the inventarisation phase. The points identified during the inventarisation phase are processed and prepared for implementation.

3. Evaluation and Implementation Phase: The configured and technical changes are implemented in the live environment and evaluated during this phase. This approach allows for different configurations to run simultaneously with varying timelines. The duration of this cyclical process depends on the client's preferences.

This iterative approach ensures that the CareOS platform is tailored to your organisation's needs and can adapt to evolving requirements.

Conditions

Information security and privacy

Information security and privacy are fundamental aspects of the CareOS design. Data availability, integrity, and confidentiality are crucial and considered from the design phase through implementation and management. Only data essential for the application's operation is collected, processed, and stored.

Data collection and processing within CareOS are transparent processes. We will collaborate to determine which data needs to be processed. All communication within CareOS and other systems is conducted via secure connections, and personal data can be encrypted upon agreement. The specific configuration of these measures will be determined jointly and depends on hosting arrangements.

Data within CareOS can be restricted to specific users or user groups based on various roles. It is always clear which users can access the data, who has viewed it, and who has modified it. We will implement additional measures to comply with our client's information security policies.

Technical infrastructure

Hosting
The applications within CareOS are ideally offered as a SaaS solution. In this scenario, Hawking takes over all management tasks. Hawking will ensure that the data within the application is encrypted and accessible only to the client.

Integration within the application landscape

Ideally, the components of CareOS should align as closely as possible with the existing application landscape. In the second phase of the action plan, we will map out the technical infrastructure to prepare CareOS for it during the design phase.