Catalyst Accelerator for Healthcare

Catalyst Accelerator for Healthcare

(1 review)

Legislative, market, and technology trends have created a digital transformation imperative in healthcare. Catalyst Accelerator for Healthcare includes pre-built APIs and a prescriptive architecture to help health IT teams jumpstart the development of common healthcare applications, and provides a foundation for 3x faster project delivery.

Key Components

  • Support for core business processes: Healthcare processes, like patient onboarding, appointment scheduling, and patient 360 viewing require real-time integration across EHRs, CRMs, and other core systems of record. MuleSoft’s Catalyst Accelerator for Healthcare provides a set of connectivity assets that deliver on these use cases.
  • Microservices architecture best practice: Catalyst Accelerator for Healthcare provides a prescriptive architecture drawn from our work with industry leaders that promotes asset self-service and reuse.
  • Packaged API designs and implementations: Leveraging HL7 FHIR standards, MuleSoft has built out a set of API definitions and packaged implementations, including HL7 v2 to FHIR mappings

API-Led Microservices Architecture for Healthcare

In addition to providing pre-built APIs, Catalyst Accelerator for Healthcare includes a model for API-led connectivity in healthcare that promotes asset reuse and self-service. In the architecture that follows, we’ve abstracted data from complex EHR systems like Epic into a canonical model that is represented via a set of FHIR REST APIs. Then, we built experience APIs that provide better experiences for both patients and clinicians.

System Layer

System APIs abstract away the complexity of EHRs and other core systems of record from the data’s end user, while providing downstream insulation from any interface changes or rationalization of those systems.

Assets include:

Process Layer

Process APIs decouple business processes that interact with and shape data from the source systems where the data originated. For example, the “schedule appointment” process contains logic that is common across multiple entities, which can be called by product, geography, or channel-specific parent services.

Assets include:

Experience Layer

Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations.

Assets include:

Supporting Assets:

Give it a try and if you have any questions or feedback, let us know at info@mulesoft.com.


Reviews

Type
Custom
Organization
MuleSoft
Created by
MO
MuleSoft Organization
Published onSep 27, 2018

Versions

Version
1.0.0

Categories

Industry Vertical