Axis Streamlines Medication Management in Japan with Twilio’s Programmable SMS Platform
Technology Category
- Drones - Flight & Control Systems
- Platform as a Service (PaaS) - Application Development Platforms
Applicable Industries
- Pharmaceuticals
- Telecommunications
Applicable Functions
- Sales & Marketing
About The Customer
Axis, Inc. is a technology company based in the Asia-Pacific region, specifically Japan. It is a small-sized company that operates in the healthcare industry, providing solutions to streamline and improve the management of patients' medication records. The company developed Medixs, a cloud-based, cost-efficient, electronic medication record system that is easy to implement. The system supports patients’ safety while helping to streamline pharmacists’ guidance and communications post the administration of certain medications, especially those with high-risk and potential interactions. Axis is committed to leveraging the potential of IT and healthcare to further reduce burdens on pharmacists and patients.
The Challenge
In Japan, managing patients’ medication records is a daunting task due to the country's population of over 126 million people. The challenge is to keep track of numerous medications for each patient with utmost precision. The situation was further complicated in September of the previous year when the Pharmaceutical Affairs and Medical Device Act enacted a revision requiring patient follow-ups after specific medications were dispensed. This increased the workload of pharmacists, necessitating an efficient communication solution. Previously, medication guidance was primarily given over the phone, requiring the pharmacist to keep a record of the conversation with the patient. However, many patients didn’t answer their phones, making it difficult to conduct necessary follow-up calls. The revision to the September Act presented an opportunity to re-examine communication tools that could help reduce the burden on pharmacists while ensuring patients received the necessary medication guidance.
The Solution
Axis, Inc., under the direction of Kazuma Kondo, identified SMS as a viable platform to address these challenges. Given that the majority of patients are in the older age groups, SMS text messaging was determined to be the most effective and cost-efficient method for reaching the widest group of patients. Axis evaluated several options for building a messaging platform and chose Twilio’s Programmable Messaging for Medixs, its cloud-based electronic medication record solution. Twilio provided many value-add features as part of its standard Programmable Messaging offering, while other companies’ basic plans had limitations, such as the number of characters and carrier support, hence having to pay extra. The Medixs service based on Twilio’s Programmable Messaging platform eased the process of conducting follow-ups and properly keeping records. Axis is also looking at extending pharmacists’ ability to connect with patients anytime, anywhere by implementing Twilio Studio.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Case Study: Pfizer
Pfizer’s high-performance computing software and systems for worldwide research and development support large-scale data analysis, research projects, clinical analytics, and modeling. Pfizer’s computing services are used across the spectrum of research and development efforts, from the deep biological understanding of disease to the design of safe, efficacious therapeutic agents.
Case Study
Fusion Middleware Integration on Cloud for Pharma Major
Customer wanted a real-time, seamless, cloud based integration between the existing on premise and cloud based application using SOA technology on Oracle Fusion Middleware Platform, a Contingent Worker Solution to collect, track, manage and report information for on-boarding, maintenance and off-boarding of contingent workers using a streamlined and Integrated business process, and streamlining of integration to the back-end systems and multiple SaaS applications.
Case Study
Process Control System Support
In many automated production facilities, changes are made to SIMATIC PCS 7 projects on a daily basis, with individual processes often optimised by multiple workers due to shift changes. Documentation is key here, as this keeps workers informed about why a change was made. Furthermore, SIMATIC PCS 7 installations are generally used in locations where documentation is required for audits and certification. The ability to track changes between two software projects is not only an invaluable aid during shift changes, but also when searching for errors or optimising a PCS 7 installation. Every change made to the system is labour-intensive and time-consuming. Moreover, there is also the risk that errors may occur. If a change is saved in the project, then the old version is lost unless a backup copy was created in advance. If no backup was created, it will no longer be possible to return to the previous state if and when programming errors occur. Each backup denotes a version used by the SIMATIC PCS 7 system to operate an installation. To correctly interpret a version, information is required on WHO changed WHAT, WHERE, WHEN and WHY: - Who created the version/who is responsible for the version? - Who released the version? - What was changed in the version i.e. in which block or module of the SIMATIC PCS 7 installation were the changes made? - When was the version created? Is this the latest version or is there a more recent version? - Why were the changes made to the version? If they are part of a regular maintenance cycle, then is the aim to fix an error or to improve production processes? - Is this particular version also the version currently being used in production? The fact that SIMATIC PCS 7 projects use extremely large quantities of data complicates the situation even further, and it can take a long time to load and save information as a result. Without a sustainable strategy for operating a SIMATIC PCS 7 installation, searching for the right software version can become extremely time-consuming and the installation may run inefficiently as a result.
Case Study
Vodafone Hosted On AWS
Vodafone found that traffic for the applications peak during the four-month period when the international cricket season is at its height in Australia. During the 2011/2012 cricket season, 700,000 consumers downloaded the Cricket Live Australia application. Vodafone needed to be able to meet customer demand, but didn’t want to invest in additional resources that would be underutilized during cricket’s off-season.
