Corolar Cloud v5.1 Release Notes

This release note highlights new enhancements and features released within this version of Corolar Cloud which can now be accessed by upgrading to Corolar Cloud v5.1.

What’s New in Corolar Cloud v5.1

• Corolar Azure Function Apps were upgraded to version 3 and .NET core 3.1.

• Several additional advancements were made to improve performance of the product.

Corolar Cloud v5.0 Release Notes

This release note highlights new enhancements and features released within this version of Corolar Cloud which can now be accessed by upgrading to Corolar Cloud v5.0.

What’s New in Corolar Cloud v5.0

• Introduced several security measures of Corolar APIs such as using oAuth2, JWT, etc.

• Client Management within Operations section in IMP to create and update client id, secret.

• Summary report to view message flow through interfaces.

• New MLLP Sender REST Api service to send messages to MLLP endpoint.

• Several additional advancements were made to improve performance and stability of the product.

Corolar Cloud v4.0 Release Notes

This release note highlights new enhancements and features released within this version of Corolar Cloud which can now be accessed by upgrading to Corolar Cloud v4.0.

What’s New in Corolar Cloud v4.0

• Ability to resubmit messages received or sent by MLLP interfaces.

• New MLLP Sender REST Api service to simplify interaction with MLLP out interfaces and support for large message sizes.

• Custom Ack messages for MLLP IN interfaces where standard Ack responses (specific to MSA-1) can be overridden by custom response messages for accept, error, reject, commit accept, commit error, and commit reject.

• Several additional advancements were made to improve performance and stability of the product.

Corolar Cloud v3.0.1 Release Notes

This release note covers the highlights of the Corolar Cloud version 3.0.1 Release. Though this is a minor release, Dapasoft has made significant changes to the Corolar Cloud product in this release support some of the key-technologies in Azure to provide more flexibility to customers.

What’s new in Corolar Cloud 3.0.1

• Corolar Cloud now supports the Azure App Service Environment (ASE) an isolated offering to host App services from Azure.

• Corolar Cloud now support SQL Server Managed Instance SKU of Azure SQL

• Customers can now continue using existing instances of Service Bus instead of creating new instance in each installation

• Several minor bug fixes were done to enhance the user experience

Corolar Cloud v3.0 Release Notes

This release note covers the new features and improvements you will experience when upgrading from previous versions of Corolar Cloud.

What’s New in Corolar Cloud v3.0

• Corolar Cloud now supports Azure SQL and PostgreSQL as back-end data stores, in order to support large message sizes (up to 2 GB) and to optimize operational costs.

• Simplified deployment and operations of managing Corolar Cloud interfaces in a disaster recovery configuration

• Reduced operations costs by optimizing the usage of azure resources

• New user group permission has been introduced to restrict access to sensitive contents stored to the database

• We added new feature in MLLP interface, to forward messages to an external service to process the messages before being parsed by the HL7 parser

• MLLP interfaces have been enhanced to support large size messages (up to 2 GB)

• Corolar cloud Visual Studio Add-On now supports the new FHIR version 4 release

• We enhanced message searching capabilities in the Interface Management Portal (IMP). Refer to our User Guide for more details

• Several numbers of improvements were added in Corolar and IMP to improve the usability and performance of the product. Refer to our user guide for more details

Corolar Cloud v2.1 Release Notes

This release note covers the new features and improvements you will experience when upgrading from previous versions of Corolar Cloud.

What’s New in Corolar Cloud v2.1

Deployment Experience

• Corolar Cloud now also supports the use of Azure AD B2C for authentication, users can now set up authentication mode to be either AAD or B2C at the time of deployment

• We have updated our deployment guide to include changes made for Corolar Cloud v2.1, please refer to our updated deployment guides for more details

• Enhancement to the Azure usage reporting by providing more visibility into the status of the Corolar Cloud deployment and consumption of Azure resources. The data is collected and governed by Microsoft's privacy policies.

Development User Experience

• Users now have the ability to set up MLLP receive interfaces to send messages directly to an external system. This would be useful in situations where the source system would want to receive an acknowledgment from the external system before logging or processing the messages further.

• We have implemented a new feature in the Corolar Visual Studio Toolkit, that would allow users to disable input and/or output schema validation when testing the transformation maps.

• We now support for durable functions as an interface development platform. Developers can now use Durable Functions in addition to Logic Apps and onboard them via Management Portal.

Operations User Experience

• When creating new MLLP interfaces, users can now choose existing service bus topics and queues

• The workflow for managing user permissions have changed in IMP, please refer to our user guide for more details and instructions.

Corolar Cloud v2.0 Release Notes

Cost optimization and performance improvements have been our major focus for this release. This release note covers the new features and improvements you will experience when upgrading from Corolar Cloud version 1.4.1 or earlier.

What’s New in Corolar Cloud v2.0

Deployment Experience

Corolar Cloud v2.0 will use Azure DevOps platform for deployment. Leveraging Azure DevOps allows Dapasoft to deliver value to customers continuously. See our Deployment Guide if you need help with getting started.

Development Experience

• We improved the MLLP adapter to reduce MLLP interface operations cost and improve the deployment and management experience of MLLP adapters via Corolar Interface Management Portal (IMP).

• We have simplified the Corolar Cloud APIs by pre-populating several parameters with default values, so it’s easier for you to use it within a LogicApp.

• We have created a new Service Bus Management API in this release so that you can easily create and manage Service Bus Queues and Topics with a single API

• We have created a new C-CDA Validation API so that you can validate a C-CDA message before parsing it through the interface.

• IMP will automatically query and list all the LogicApp interfaces within an adopted resource group, so you no longer have to add tags to LogicApps in Azure Portal.

• We are now leveraging the new authentication parameter in the Azure LogicApp API calls for additional security

• Corolar Cloud fully supports the ARM VNet

Operational Experience

• We now support export and import of MLLP configuration file, so you can now promote MLLP adapters by simply importing configuration files into an environment.

• We have enhanced LogicApp Interface management capabilities in IMP, so you can now delete all the logs and exceptions associated with a LogicApp

• We have updated Operations Dashboard in the IMP to include ‘Running Status’ for all the interfaces, so it’s easier for you to filter/sort between running and stopped interfaces from the portal.

• The IMP Operations Dashboard is now synchronous so that you will see interface status changes faster

Known Issues

• We are aware that the Audit Report in the IMP does not show the change detail for certain components, we are working on resolving the same in future

Corolar 1.4.1-Hotfix1 Installation Requirements

Installation Requirements 

The Corolar Cloud installation process requires the following prerequisites: 

• Internet connectivity to Microsoft Azure environment  

• Azure IAM access (contributor) to all targeted Corolar environments (Azure Resource Groups)

• Access to the ‘deploy.config’ generated during the installation of Corolar in the target environment

• Download and install Microsoft Azure Storage Explorer (http://storageexplorer.com/) 

Supported Operating System 

Corolar Cloud runs entirely in Azure, but the installation process is executed from a windows environment. Corolar Cloud installations are supported on: 

• Windows 8.1 

• Windows 10 

• Windows Server 2012 R2 

• Windows Server 2016 

PowerShell Requirements 

PowerShell is used extensively in the installation process, and requires the following modules, which can be checked with the associated PowerShell scripts:

Deployment Script Home 

After accessing the Corolar Cloud release container, the ‘DeploymentScripts’ zip archive can be unzipped to a ‘local release folder’. The contents of the unzipped folder will be referred to as the ‘script home’ for the remainder of this document.  

Each Environment will require a distinct configuration file (deploy.config), that is populated through-out the deployment process.  

An appropriate local location is one that: 

• identifies the target environment, and

• is close to the drive root. 

Recommended Script Home: