Embedded Files
Introduction
Introduction
Both Phio Access and Engage are built so they can fit into your service seamlessly. We offer a variety of integration options that will fit your unique needs. From providing you a self-referral landing page, to fully automated API solutions everything is possible. Choosing the right integration for you will depend on:
The Phio offering you chose
How you receive referrals currently
Tech resources available on your end
The below sections explain all the different options for referring into Phio as well as retrieving data.
Example process: Self-referral
Example process: Self-referral
The below shows a typical integration process flow for self referral where EQL provides Clinical Services for the management of Phio Engage and the customer covers the other outcomes.
Example process: Health App integration
Example process: Health App integration
Integration Case Studies
Integration Case Studies
Case study 1 - Creating landing pages to allow self-referral
Case study 1 - Creating landing pages to allow self-referral
Phio was originally built with a suite of APIs to allow customers to refer patients to the Phio platform and retrieve data upon completion.
Integration Hurdle
We faced two key problems with Customer X:
They wished for their patients to self refer to Phio meaning no patient data existed prior to referral and our customer would have no record of the patient until we provided them with the completed Phio Access assessment.
In addition, our customer lacked the technical resources internally to attach to our API's in order to collect the completed triage data
Proposed Integration Solution
The below solutions were proposed to Customer X by EQL:
EQL proposed a Landing page solution to enable patients to self register for Phio. This Landing Page allowed Customer X to specify which specific data fields they wished to collect from the patient at the time of registration and how they wished to validate the patient was a legitimate patient.
EQL proposed to build a secure, access controlled Portal which allowed Customer X users to login and retrieve complete triage data via an PDF report, built and rendered by EQL.
EQL Resource
This Integration Solution was built over 3 sprint cycles, utilising a team of 1 Product Manager 3 Developers and 1 Quality Engineering.
Customer Resource
Due to the solution being a non-integrated solution there weren't any dependencies on the customers resources. However, the customer was asked throughout the scoping stage to sign off on the proposed requirements and to complete some Alpha and Beta testing.
Timeframes
From start to finish this integration solution was scoped, built and tested over a 6 week timeframe, split up into 3 x 2 weekly sprints.
Case study 2 - Allowing customers to display the Phio link within their portal
Case study 2 - Allowing customers to display the Phio link within their portal
Integration Hurdle
Customer Y had their own web application and in order to optimise the journey they wished for their users to be able to refer themselves to Phio from within this web application, rather than via an external instance.
Proposed Integration Solution
To enable this, EQL proposed to build a new API endpoint for referrals that allowed us to send the users unique Phio Access link back to the customer within the payload response. This enabled the customer to have a dedicated space within their Web App for Phio Access, whereby the user selects the CTA to initiate Phio Access, resulting in the API call and allowing users to gain immediate access to their unique Phio Access URL.
EQL Resource
This Integration Solution was built over 1 sprint cycle, utilising a team of 1 Product Manager 1 Developers and 1 Quality Engineering.
Customer Resource
Once the API endpoint was developed from EQL, the Customer had to ensure resources were available to develop the necessary area within their web application. With the help of EQL’s API documentation, the customer was able to attach to the endpoint with ease.
Timeframes
From start to finish this integration solution was scoped, built and tested over a 4 week timeframe.
Case Study 3 - Integrating Phio with a 3rd party case management system
Case Study 3 - Integrating Phio with a 3rd party case management system
Integration Hurdle
Customer Z wished to use a 3rd party software to run their Case Management System and expressed a desire to integrate Phio Access into this 3rd party system.
Proposed Integration Solution
EQL proposed to work with the 3rd party supplier on the project, leading the integration plan, developing the necessary API endpoints and helping with testing.
The solution included a patient facing portal which had referral integration into Phio Access. Along with an integration back into the customer case management system on completion of Phio Access. This integration, migrated data from EQL to the system, attached the summary report to the system, registered the signposted outcome and placed the user in the correct next steps for the customer.
EQL Resource
This integration utilised the existing endpoints available for our API. However we provided Technical, Product Management and Operational support to the Case Management provider for this project.
Customer Resource
The customer's resource was needed for requirement and user story gathering for the solution. Following this, EQL worked directly with the Case Management provider until such time as the solution was in BETA and ready to share back to the customer for some user testing.
Timeframes
This project was scoped, built, tested and deployed to live for the customer within 4 months.
Page updated
Report abuse