Lab 4: Use Case Overview
The immediate need that must be addressed is to get patient data out of Epic and create a patient 360 view that also includes data from Salesforce Health Cloud, which will be used by MHS staff throughout the organization. When MHS is ready to begin their Patient Portal initiative, they will be able to reuse the APIs from this patient 360 initiative.
Fortunately, MHS has an existing MuleSoft implementation that is used to support other initiatives within the organization. After a discussion of your assignment with the lead MuleSoft architect you have discovered that an Application Network supported by MuleSoft is already in place. From your discussion it has been determined that it will be easy to deliver a Patient 360 View by reusing several existing APIs that are already in production. You will only need to add or reuse the following APIs to deliver your project:
-
Review the existing System API that accesses data in Epic. Note that this exercise will be demoed by your instructor.
-
Create a new System API that will be used to create an appointment in Salesforce Health Cloud.
-
Create a Process API to synchronize appointment data between Epic and Salesforce Health Cloud.
-
Use Salesforce Health Cloud to test an Experience API by creating a new appointment via the Patient 360 view that MuleSoft enables.
Summary
Please proceed to Lab 5: Review a System API to Access Epic (Instructor Demonstration) to begin your exploration of the Anypoint Platform.