Underlying all IT architectures are core systems of records that are often not readily available due to its complexity and connectivity concerns. System APIs provide a means of hiding that complexity from the user while exposing data and providing downstream insulation from any interface changes or rationalization of those systems. This API provides an implementation best practice to expose data from patient management systems like Salesforce Health Cloud via a set of RESTful FHIR services in RAML 1.0, making it easy to consume within an enterprise.
This template is subject to the conditions of the MuleSoft License Agreement. Review the terms of the license before downloading and using this template. You can use this template for free with Mule Enterprise Edition, CloudHub, or as a trial in Anypoint Studio.
Accelerator for Healthcare
This FHIR specification is one of many components included in Accelerator for Healthcare. This API provides organizations with connectivity assets that accelerate project delivery in healthcare, including pre-built API designs and implementations that support core healthcare business processes.
Contact firstname.lastname@example.org for more information.
As a user of Healthcare API Led Connectivity Web Portal I want a microservice to act as a system API to provide services to upper layers of the architecture. This include creation, modification and retrieval of medical data from the Salesforce Health Cloud system.
Salesforce Health Cloud to FHIR System API is part of the Healthcare Templates Solution and uses the standardized FHIR structures version 3.0.1 STU3.
The API is defined using RAML 1.0 to provide type information for validation of requests and to help with the data transformation during development by providing useful metadata.
The following FHIR objects and operations are implemented in this API:
- AllergyIntolerance - read, update, create
- Appointment - read, update, create
- Condition - read, update, create
- Device - read, update, create
- MedicationOrder - create
- Observation - read, create
- Patient - read, update, create
- Practitioner - read, update, create
To make this template run, there are certain preconditions that must be considered. Failing to do so can lead to unexpected behavior of the template.
Simple steps to get this template running.
Where to Download Anypoint Studio and the Mule Runtime
If you are new to Mule, download this software:
Import an Anypoint Template into Studio
In Studio, click the Exchange X icon in the upper left of the taskbar, log in with your Anypoint Platform credentials, search for the template, and click Open.
Run on Studio
After you have import your template into Anypoint Studio, follow these steps to run it:
- Locate the properties file
mule.dev.properties, in src/main/resources.
- Complete all the properties required per the examples in the "Properties to Configure" section.
- Right click the template project folder.
- Hover your mouse over
Mule Application (configure).
- Inside the dialog, select Environment and set the variable
mule.envto the value
Run on Mule Stand Alone
Fill in the properties in one of the property files, for example in mule.prod.properties and run your app with the corresponding environment variable to use it. To follow the example, use
Run on CloudHub
If creating your application on CloudHub, go to Manage Application > Properties to set all environment variables detailed in "Properties to Configure".
Deploy Your Template on CloudHub
In Studio, right click your project name in Package Explorer and select
Anypoint Platform > Deploy on CloudHub.
Properties to Configure
To use this template you need to configure the properties that follow either in a properties file or in CloudHub as environment variables.
SalesForce Connector Configuration