Redox and Kinvey team up in hopes of making healthcare apps easier to build


[ad_1]

Creating a software application that can communicate with a hospital or clinic’s patient record keeping system can be complicated. As a result, many third-party developers choose to use an application programming interface, like the one created by Madison, WI-based startup Redox, to get data in and out of healthcare organizations’ registration systems.

Still, app builders, no matter what industry they work in, need to configure the backend of a software product, which encompasses things like user authentication, libraries, and analytics. Backend components tend to vary less between different applications than frontend ones, which control what a user sees, hears and feels – the user experience. Several companies, such as Boston-based Kinvey, specialize in providing backend services.

Now comes the news that Redox and Kinvey have partnered up. The companies say the deal will help shorten developers’ path from concept to product, and allow them to focus on what they know and love to do best.

“For mobile developers, access [health records] data is heavy and time consuming, ”said Jikku Venkat, Kinvey vice president of products, in a prepared statement. “With Redox and Kinvey, developers benefit from a standardized way to access [health records] systems, hiding the intricacies of each system and turning a six-month project into a one-month project.

James Lloyd, co-founder and chief technology officer of Redox, says his company is constantly looking for instances where people are building apps that use health data and “doing redundant work that isn’t really at stake. heart of their activity ”. When Redox has identified an area with significant overlap, he says, one option is to add it to Redox’s software. “Or we can partner with people who are doing it really well today,” he says, which is the case with Kinvey and the management of the mobile backend.

Much of Kinvey’s business is building tools for mobile developers. In April, the company announced a collaboration with one of the major hosting players, Google Cloud Platform. Kinvey said it used Google’s platform to launch software, which Kinvey described as a mobile backend as a service, or mBaaS, compliant with HIPAA, a law that regulates the use, disclosure, and transmission of protected information on the health of patients. HIPAA compliance is important to application developers and users alike, as unauthorized sending of sensitive patient data can result in hefty fines and even jail time. The law, originally passed in 1996, has since been updated with provisions that can apply to mobile devices.

Part of the challenge with writing software for the healthcare industry is that many applications widely used today, including those for managing patient records, “were designed without thinking about mobile,” says Kinvey. in a press release.

Grahame Grieve, a consultant who is co-leading a project to update so-called interoperability standards for electronic health data interchange, says he first worked on projects related to interoperability in healthcare systems. 1970s. These standards are known as HL7, short for Health Level Seven International, Ann Arbor, MI, the nonprofit that manages them. Grieve says bringing HL7 into the current computer age means “having to catch up on a technical level.”

What also complicates matters is the fact that “most [health records] the systems have been highly personalized, [meaning] integration is difficult without detailed knowledge of each system, ”according to the press release.

Judy Faulkner, founder and CEO of Verona, WI-based Epic Systems, made a similar point in an interview published earlier this week. A typical system that uses patient recording software from Epic or one of its competitors would have approximately 150,000 data items. “Maybe the initial set includes 30 responses to that data element, or 30 coded responses,” Faulkner said. IT health news. “Maybe your organization has 20 … Next page “

One pageCurrently on the page: 1 2

Trends on Xconomy

[ad_2]

Comments are closed.