We spent three years developing a mobile application platform that can handle the operational nuances of the healthcare industry.
We collaborated with recognized innovators, thought leaders, and healthcare technologists to design a system that answered the question, "If the healthcare industry were created today – how would the technology be designed to work with the aging infrastructure of existing stakeholders while planning for the future?"
We designed a sustainable future-proof platform because we plan on being in healthcare for a long time. What we’ve built from scratch is a HIPAA compliant point-of-care platform that is strong, secure, and scalable. By laying a technology foundation that can process the ICD-9, CPT, HCC and other codes required for Medicare reimbursement – we’re flexible enough to link into software platforms providing transactional support for major stakeholders in the healthcare industry. Think of this like tailoring an expensive old suit to fit the lifestyle of a modern gentlemen.
Partners appreciate Remedy Systems because we leverage our existing platform when inventing new product lines for their businesses. This cuts down significantly on costs, internal resource requirements and speed to market. Our assembled team is fluent in healthcare IT, health care services, and new school technology – which is rare to have under one roof. Even though we’re known for our mobile products, all data and functionality is accessible on both a mobile device and a web portal sharing a common server. By designing a MASI (mobile application server interface), Remedy Systems is able to remain device agnostic (Android, iPhone, iPad) while still building native applications for each operating system. We’re good at what we do because our platform draws on the insights, optimization strategies, and best practices we learned while building and managing mobile applications with millions of active users across multiple industries.
Remedy Systems is built atop the ubiquitous LAMP (Linux, Apache, MySQL, and PHP) application stack made popular by Facebook and now used in more than 70% of web portals. So if our functionality for messaging and grouping patients or providers feels a bit like Facebook - that’s because we’re leveraging the same flexible backend structure they helped pioneer.
The system is designed around MySQLʼs InnoDB database engine that offers strong transactional protections and good performance - at a cost low enough that allows Remedy to stay lean and mean. The system is designed to use one of Apacheʼs threaded processes managers and PHP. This configuration enables large pools of client devices to maintain idle connections to the server, improving latency and lowering connection overhead for mobile users.
Remedy Systems was optimized for speed and the efficient transfer of data. We believe a main barrier to physician adoption is the slow processing speeds and spinning load wheels found on other mobile applications. Remedy only stores transient data on the iPhone when its needed to power transactions, otherwise there is no personal health information (PHI) or sensitive data ever stored on the mobile device. We also use fully encrypted SSL communications between mobile applications and our servers, and never store any encryption keys on the device itself.
Remedy uses a data abstraction layer that exploits the natural data clustering in the practice/physician/patient model. This data clustering combined with smart load balancers allows us to direct traffic to server-groups containing the most pertinent data for the specific user. In setting out to build a healthcare platform, we were okay taking our time and losing a ‘first to market advantage’ if it meant we could design and build a sustainable system which could scale. Now Remedy has a fundamentally sound system and is still first to market with thick mobile applications for healthcare.