Integration

ADDI Medical
/
Integration

Through the integration building block, HOPE Platform supports integrations using services that all have manufactured APIs. These APIs are the way in which the different building blocks communicate with each other. Those developed as open APIs can also be integrated with APIs in external systems. For example, a patient list can be retrieved from an external system just as easily as it is done through the Activity Plan in HOPE Platform.

Structured formats and processes that comply with the FHIR (Fast Healthcare Interoperability Resources) standard are used for this.

Payment

HOPE Platform makes digital payment for patient healthcare appointments possible.

Swish

Platform integration with payment service Swish, makes it possible for payment to be made for healthcare appointments in Sweden. Swish facilitates direct payment between bank accounts through a mobile phone number linked to the payment account. Patient use of the Swish service and Mobile BankID make this possible.

PayEx

The platform also offers the “card payment” service via PayEx. This means that patients who choose this method of payment will be navigated to the PayEx page. No card details are processed or saved in the HOPE Platform.

Exemption card

When logging in to the HOPE App, the user can specify the method of payment for medical care as an exemption card. The user indicates in the HOPE App if the amount of the exemption card has been reached and will then not have to pay for the visit.

Listning

GetAllListing

Though integration of the platform with the proprietary clinical SDK, “GetAllListing” – available for Java and an executable component with the Rest API, parallel calls can be made to the listing register for the Swedish Regions. Information is then obtained about all registered listings (care choices) for the resident for care providers in Sweden irrespective of where they are made.

This delivers significant time saving benefits as the care providers reaches all of the registers in the Regions via just one call.

Authentication

BankID

Through platform integration with BankID, patients, healthcare and nursing administrators or research staff can authenticate themselves. All users must authenticate themselves in accordance with established authentication methods, such as BankID before they can access information and functions in the HOPE Platform. This applies to everything from registering information or participating in an activity such as a video meeting to answering a questionnaire.

SITHS

Integration of the platform with SITHS enables healthcare and nursing staff including doctors, nurses, administrators or research staff to authenticate themselves. These users work in HOPE Practitioner. All users must authenticate themselves before they get access to information and functions in HOPE Practitioner. This applies to everything from consulting self-care data to sending out invitations and taking part in an activity such as using the chat function.

Communication

Integration with the electronic mail service (otherwise known as email) enables a message or reminder to be sent. For example, a reminder can be sent to alert the user that that it is time to perform an activity or that a registered value has exceeded or dropped below a level that requires a certain action to be taken.

SMS

SMS (Short Message Service) is also known as text message and is an integrated service that complements email when there is a need to send fast text messages. It can also be used to send a reminder to alert the same user that it is time to perform an activity.

Chat

Integration of the platform with the proprietary chat function supports both asynchronous and synchronous communication. Using chat staff can exchange written messages between two people via computer or smartphone as a complement to the physical visit. The function ensures that all conversations are saved in accordance with the requirements of the Swedish Patient Data Act (PDL).

Video

The integrated video service makes it possible for healthcare staff to offer the patient a more active and direct form of digital meeting in real time.

Devices/measurement technologies

Omron scales

Integration with HealthKit means weights from the Omro digital scales and App can be transferred to HOPE Platform, made available and visualised via HOPE Practitioner and HOPE App.

Mi Fit activity tracker bracelet

Integration with HealthKit enables steps from the Mit Fit activity tracker bracelet and App to be transferred to HOPE Platform, made available and visualised via HOPE Practitioner and HOPE App.

NuvoAir spirometer

Integration with HealthKit enables spirometry values from the NuvoAir spirometer to be transferred to HOPE Platform, made available and visualised via HOPE Practitioner and HOPE App.

Additional devices Additional devices can be easily and securely integrated with HOPE Platform as needed.

Export function

HOPE Platform has one-click export function that exports all information to a file. For example, data from an entire company complete patient list or data from an activity plan for an individual patient. Data export works with Excel and other compatible CSV formats.

HOPE Platform also has a built-in, ready-made export function in the form of a clipboard. Staff can easily specify the information to be included on the clipboard. Staff then open another system and “paste” the selected information and make any adjustments and additions needed.

The service reduces the need for systems integration between HOPE Platform and external systems. The extra work will only be two clicks or whatever is required for integration with other systems.

Clinical SDK

The HOPE clinical Software Development Kit (SDK) is a set of development tools that enable the HOPE Platform to connect to the National Service Platform (NTjP). In this way, HOPE Platform Clinical SDK tools simplify connection to healthcare APIs and the process of integration with the common NTjP that provides national patient data via APIs.

The HOPE Platform Clinical SDK is intended to simplify and accelerate the process of connecting HOPE to NTjP.

The HOPE Platform Clinical SDK is written in Java and uses the Apache Camel integration framework.

Clinical SDK in HOPE Platform incorporates functions that meet PDL requirements for connection to NTjP – they are “ready to go”.

Integration with other systems

The Integration building block has different integration interfaces to health and medical care quality registers such as laboratory systems. These interfaces allow HOPE Platform and the third-party system to automatically send information to each other without manual input.

Each HOPE Platform building block has a developed API that can either be integrated with the APIs to other building blocks in the HOPE Platform or with the third party system. In practice, this means the HOPE Platform can display a patient list irrespective of the system in which it is created.

Clinical REST

As the name suggests, Clinical Representational State Transfer (REST) in HOPE Platform is a REST-based adaptation of the HOPE Clinical SDK, which enables use of Clinical SDK as a web-based service to NTjP.

The Clinical REST interface in HOPE Platform is often easier to implement, understand, and troubleshoot compared to the HOPE Clinical SDKs. Its simplicity often makes the application of HOPE Clinical REST faster than SDK.

The HOPE Platform Clinical REST and SDK act as a broker between HOPE Platform and NTjP. This means the platforms communicate through the broker instead of directly with each other.