• License Agreement
• Use Case
• Considerations
• Run it!
  • Running on premise
  • Running on Studio
  • Running on Mule ESB stand alone
  • Running on CloudHub
  • Deploying your Anypoint Template on CloudHub
  • Properties to be configured (With examples)

Note that using this template is subject to the conditions of this License Agreement. Please review the terms of the license before downloading and using this template. In short, you are allowed to use the template for free with Mule ESB Enterprise Edition, CloudHub, or as a trial in Anypoint Studio.

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 1.0.2 DSTU2.

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 Anypoint Template run, there are certain preconditions that must be considered. Failling to do so could lead to unexpected behavior of the template. Use Anypoint Studio v6.1.0+ and Mule ESB 3.8.1+ to run this template.

Simple steps to get Healthcare Salesforce Health Cloud to FHIR System API running. See below.

In this section we detail the way you should run your Anypoint Template on your computer.

First thing to know if you are a newcomer to Mule is where to get the tools.

• You can download Anypoint Studio from this Location
• You can download Mule ESB from this Location

Anypoint Studio offers several ways to import a project into the workspace, for instance:

• Anypoint Studio generated Deployable Archive (.zip)
• Anypoint Studio Project from External Location
• Maven-based Mule Project from pom.xml
• Mule ESB Configuration XML from External Location

You can find a detailed description on how to do so in this Documentation Page.

Once you have imported you Anypoint Template into Anypoint Studio you need to follow these steps to run it:

• Locate the properties file mule.dev.properties, in src/main/resources
• Complete all the properties required as per the examples in the section Properties to be configured
• Once that is done, right click on you Anypoint Template project folder
• Hover you mouse over "Run as"
• Click on "Mule Application"

Fill in all 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, this will be mule.env=prod.

While creating your application on CloudHub (Or you can do it later as a next step), you need to go to "Manage Application" > "Properties" to set all environment variables detailed in Properties to be configured. Follow other steps defined here and once your app is all set and started, there is no need to do anything else.

Anypoint Studio provides you with really easy way to deploy your Template directly to CloudHub, for the specific steps to do so please check this link

In order to use this Mule Anypoint Template you need to configure properties (Credentials, configurations etc.) either in properties file or in CloudHub as Environment Variables. Detail list with examples:

• http.port 8081

• sfdc.username [email protected]
• sfdc.password sfdcPassword
• sfdc.token 12345dfnsjad54s54da54w5d4a5