Clinical trials integration using FHIR R4 specifications

Yogesh Dhimate (00:08):
Mythical Healthcare has partnered up with the life sciences organization for clinical trials. As part of this program, they want to capture the side effects of a trial on the patient using AdverseEvent API. So our developer, Sarah, has been asked to implement the AdverseEvent API following the FHIR specifications. The challenge is that while Sarah is an expert of medical IT's internal systems, she's not very familiar with the FHIR specifications.

Yogesh Dhimate (00:36):
Sarah also knows how important this is, given that the new interoperability requirements from the Cures Act will eventually require Mythical Healthcare to make that patient data captured available for the patient via a FIHR R4 API end point.

Yogesh Dhimate (00:52):
With our familiarity now with the MuleSoft accelerator for healthcare, she knows that's a great place to start to learn more. So she goes into Exchange to explore the assets. From this list she can quickly see that the pre-built API specification is available for her to leverage. She reviews the API specification and verifies that it meets her needs. Since Sarah is new to FHIR, it's great that MuleSoft has already built this spec out for her to leverage.

Yogesh Dhimate (01:48):
To test and use the API, she quickly fires up Anypoint Studio and creates a new project. She's given the option to import the API from Anypoint Exchange through the Studio UI. And with just a few clicks, Studio automatically scaffolds the API into an implementation of the API. She can quickly see that the necessary methods and attributes are available in the flows. With this done, Sarah can also deploy this API using the built in run time in Studio.

Yogesh Dhimate (03:00):
Within this view, just as she was able to in Exchange, she can also try out and test the API using the API console. With all this done, Sarah can now connect this implementation with Mythical Healthcare's backend IT system. She can use any of the 100 plus connectors that MuleSoft provides out of box, to quickly integrate with systems like AdverseEvent database to capture the adverse event information.

Yogesh Dhimate (03:52):
In addition, Sarah can easily use the AdverseEvent API alongside the patient API built from the first demo to complete the integration flow necessary to securely provide trial patients with access to their data, and adhere to new interoperability requirements. Using the Accelerator for Healthcare, Sarah was able to take the API specification provided by MuleSoft to quickly build her FHIR end point to meet the compliance without having to be a FHIR expert. And best of all, she was able to complete this critical project well ahead of time, and accelerate the pace of delivery.