At MuleSoft, we work with a number of hospitals, healthcare systems, insurers, and other healthcare organizations. These organizations use different computer systems–from billing and Electronic Health Records (EHRs) to laboratory and pharmaceutical management systems. A common and critical use case that we come across is how we can enable these organizations and their partners to seamlessly exchange data with one another across different systems. 
 

Read more

I’m proud to be part of a company that works with leading hospitals including UCSF, Mount Sinai, and many others who are on the forefront of innovation in healthcare. But at its core, while some hospitals have embraced transformation, most remain stuck in the past, and here’s why.

Read more

With the advent of next generation, easy to use integration toolsets, the following is becoming a very familiar scenario. 

The business has a use case to move customer records from a database (DB) to Salesforce (SFDC). A system analyst in the line of business quickly creates an integration with a connector and deploys it.

A few weeks later, the customer support team comes up with another use case to display customer data on the support web portal.

Read more

There is hardly any argument on the fact that APIs are increasingly becoming an important part of how companies do business. API has become the de facto standard to unlock one of their most valuable resources, data.

And as organizations are publishing more APIs, the observed trend is that REST is replacing SOAP as the data transfer protocol of choice. When it comes to the data that APIs serve up, XML is still the most used format.

Read more

In the previous post in the “APIfy your integrations” series, we went through an API design-first approach to building integrations to back-end systems.

We defined the API specification using RAML, implemented the API by importing the RAML into Anypoint Studio and deployed the implementation to mule runtime in cloud or on-premise.

We are now ready to share the API with the developer community.

Read more

This blog post is a continuation of our first How To series, “APIFy your integrations,” where we started off by creating a SOAP API around a database.

Some organizations are entirely invested in either SOAP or RESTful web services. There is plenty of material already written on SOAP vs. REST, so there’s no need for us to take that on here.

It can be a use case driven decision where SOAP and REST can co-exist.

Read more

We recently introduced our HowTo blog series, which is designed to present simple use-case tutorials to help you as you evaluate Anypoint Platform. This first blog in Series 1 will show you how to insulate your backend systems like databases by exposing a system API using SOAP over HTTP.  The principle behind this approach is our API led connectivity methodology, which is an evolution of SOA.

Read more

This series of HowTo blog posts are simple use-case based tutorials to help you as you do your evaluations with the Anypoint Platform. Based on a theme each series consists of up to three tutorials.

We created the series by collecting common use-cases encountered by our field teams and feedback from our massive customer and partner base. 

We will be launching the first series this month followed by a new series each quarter.

Read more