1. Homepage
  2. Release Notes

  3. MuleSoft Accelerator for Healthcare Release Notes

MuleSoft Accelerator for Healthcare Release Notes

2.23

May 14, 2024

What’s New

You can now de-identify FHIR patient datasets with the new Patient De-identification Solution use case. Use the pre-built assets to power innovative research and AI initiatives while maintaining patient privacy.

This use case includes a web-based configuration tool as part of the Patient De-identification Process API, which lets you create various de-identification rules and apply them across a variety of scenarios. The tool is designed to simplify the process of converting business requirements into deployable application logic.

Additionally, you can now discover and deploy the integration applications from Salesforce via MuleSoft Direct as part of the Appointment Scheduling use case. The use case implementation is now simplified by incorporating the Generic FHIR Client to integrate with various electronic medical record (EMR) systems.

2.22

January 16, 2024

What’s New

This release introduces the Qualified Health Information Networks Integration (QHIN) use case which enables organizations to streamline the patient onboarding process. This solution provides a collection of applications that accelerate the integration of Salesforce Health Cloud and Kno2, enabling patient information to be ingested across a network of other providers and removing the need for manual data entry.

The downloadable assets for this use case are available on the use case page in Exchange.

2.21

October 12, 2023

What’s New

  • Launched a new version of the FHIR JSON-to-RAML autogenerator to improve representation of key FHIR concepts in the generated RAML specification, including support for descriptions and notes, constraining cardinality, element flags, linking to relevant value sets, extensions, and slicing.

  • Upgraded all implementation templates to leverage new API specifications published in MuleSoft Accelerator for Healthcare 2.20 and the latest version of the parent POM.

2.20

August 23, 2023

What’s New

This release extends the solution provided for the Patient 360 use case to allow customers to discover and deploy from Salesforce using MuleSoft Direct for Health Cloud. The following updates are included:

  • Patient Summary - EMR Integration | Application

  • Event-based ingestion into Health Cloud | Application

  • Enhanced FHIR R4 RAML libraries and specifications to leverage the new version of AMF parser to better align with industry standards.

2.19

May 30, 2023

What’s New

This release includes the following enhancements to the Patient 360 use case and FHIR API assets and converters:

  • Expanded the library of assets to allow organizations to more easily ingest critical information from clinical systems into Salesforce Health Cloud, which enables users to view the information included in the supported HL7 v2 events natively in their Salesforce console.

    • Added support for ADT^A02, ADT^A03, ADT^A04, ADT^A05, SIU^S12, SIU^S13, SIU^S14, and SIU^S15.

    • Enhanced existing assets that support ADT^A01, ADT^A08, ADT^A28, and ORU^R01 events.

  • Enriched the data available to Salesforce Health Cloud users by making updates to the Health Cloud System APIs through improved mappings and code optimizations.

  • Enhanced the FHIR JSON-to-RAML autogenerator to provide more control to generate specifications with base HL7 resources and Implementation guides, such as Carin Blue Button and USCDI, across all versions.

  • Enhanced the C-CDA-to-FHIR converter to support additional mappings to process clinical notes from supported CDA document sections.

2.18

December 13, 2022

What’s New

This release extends the solution provided for Population health management to enable organizations to surface valuable population health data from EHR systems into Amazon HealthLake and Salesforce Customer Data Platform to improve clinical outcomes.

2.17

October 20, 2022

What’s New

This release provides a solution for Population health management to enable organizations to convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes.

As part of this release, existing assets used to convert from HL7 v2, C-CDA and X12 formats to FHIR R4 were enhanced to fix defects and enable use with Amazon HealthLake.

2.16

July 26, 2022

What’s New

This release provides a support to additional CDA document types in convert C-CDA messages to FHIR use case.

2.15

June 23, 2022

What’s New

This release provides Healthcare organizations with a reference implementations to convert FHIR R4 resources from HL7 FHIR JSON format to RAML specification and convert C-CDA messages to FHIR.

2.14.1

May 26, 2022

What’s New

This minor release includes an upgrade to the dependencies on the assets that perform FHIR resource validation.

2.14

April 19, 2022

What’s New

This release provides Healthcare organizations with a reference implementation to convert X12 messages to FHIR.

2.13

January 18, 2022

What’s New

This release provides an end-to-end solution for prior authorization, which includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations:

2.12.1

December 9, 2021

What’s New

This minor release includes an upgrade to the assets to be EMR agnostic, which allows customers to choose any EMR as a System of Record:

2.12

November 9, 2021

What’s New

This release provides an end-to-end solution for prior authorization support, which automates the prior authorization process for more immediate authorizations. The following assets are also available:

2.11

September 14, 2021

What’s New

This release provides an end-to-end solution for benefits and eligibility verification using Health Cloud, Epic, and Cerner as the reference backend systems:

2.10

July 28, 2021

What’s New

The focus of the 2.10 release is to provide assets for the patient sync capabilities:

The following assets were also enhanced and improved for this release:

The following assets are modified to support XML format for existing Epic System APIs:

The following assets are modified to support updated API specifications for existing Cerner System APIs:

2.9

June 22, 2021

What’s New

This release provides API specifications and implementation templates for the Appointment Scheduling use case described here:

It also includes the following Cerner assets for Patient 360:

The following assets were also enhanced and improved for this release:

2.8

May 18, 2021

What’s New

This release includes:

2.7

April 6, 2021

What’s New

This release includes:

2.6

March 2, 2021

What’s New

This release includes:

  • API specifications for Patient 360 to support the Spring 2021 release of the Health Cloud data model.

  • Added support for the ORU message type in the HL7 v2 to FHIR converter.

2.5

February 5, 2021

What’s New

This release provides Healthcare organizations with a reference implementation to convert HL7 v2 messages to FHIR to integrate with different systems using the guidelines provided by the HL7 v2 to FHIR Implementation Guide.

2.4

November 24, 2020

What’s New

The focus of release 2.4 is on providing the API specifications and implementation templates for CMS Interoperability and Patient Access final rule. The release contains the following assets:

2.3

October 22, 2020

What’s New

The focus of release 2.3 is on providing the API specifications and implementation templates for CMS Interoperability and Patient Access final rule. The release contains the following assets:

2.2

September 18, 2020

What’s New

The focus of release 2.2 is on providing the implementation template for Electronic Laboratory Reporting to CalREDIE. The release contains the following assets:

2.1.1

August 21, 2020

What’s New

The focus of release 2.1.1 is on providing mapping and cosmetic fixes in the implementation templates. The release includes the following fixes:

  • Mapping for additional fields in the patient resource, such as the shipping address, the billing address, the phone number and the gender.

  • Minor bug fixes.

2.1

July 31, 2020

What’s New

The focus of release 1.1 is on providing API specifications and RAML library assets for all 145 FHIR resources. These assets will help healthcare providers and payers in meeting CMS interoperability rules.

  • NEW: API specifications for resources in the following FHIR modules:

    • Foundation

    • FHIR Exchange

    • Terminology

    • Conformance

    • Security and Privacy

    • Implementation Support

    • Administration

    • Clinical

    • Diagnostic

    • Medications

    • Workflow

    • Financial

See Also