We've shown in previous posts that
mirthSync can be used to move code between different Mirth Connect systems
and can also be used in conjunction with Git for tracking code/config
changes. In this post we'll dive into implementing a simple CI/CD pipeline by
wiring together Github Actions, mirthSync, and multiple Mirth Connect
deployments. This will show how changes can be implemented, tracked, and
automatically deployed to a staging environment from a development
Ensuring the integrity and confidentiality of protected health information (PHI) is of
the utmost importance. In this post we give a high level overview of what constitutes PHI and
many important factors for ensuring that your handling of PHI is consistent with regulatory
guidelines and software engineering best practices.
This is Part 1 of a series of posts describing the usage and
benefits of utilizing mirthSync with Mirth Connect
instances. Future posts will cover more sophisticated usages
that allow for you to safely manage environments and view
changes being applied.
Please keep in mind that mirthSync is a free and
open source tool that is under active development. Ensure that you have read the License and understand that Saga-IT LLC or any project contributors
are not responsible for any issues related to use of the
tool. We highly recommend that you utilize the tool only with
development or staging environments.
In the previous
post we have an overview of mirthSync and indicated that it
can be used for many purposes beyond just simple pulling and
pushing of Mirth Connect channels and configuration. In this
post we will demonstrate how mirthSync can be integrated with Git and Git's features
can be used to track changes to view, review, and if necessary
roll back changes to code and configuration.
utilizing mirthSync is a vital part of our workflow. It enables
us to track and visualize changes to our environments over time
which gives us extra confidence to make even significant
changes and enhancements without risk.