1.安裝JDK，推薦安裝JDK8 64位，版本jdk-8u201-windows-x64.exe.
安裝JDK后，同時必須配置win10的系統環境變量【示例如下】：
JAVA_HOME ： F:\Java\jdk8
JAVA_TOOL_OPTIONS ： -Dfile.encoding=UTF-8 -Duser.language=en -Duser.country=US
CLASSPATH ： .;%JAVA_HOME%\lib;%JAVA_HOME%\lib\dt.jar;%JAVA_HOME%\lib\tools.jar;
Path環境變量需要添加一個變量值:
點'新建'后直接把%JAVA_HOME%\bin和%JAVA_HOME%\jre\bin輸入進去。
- 變量值：%JAVA_HOME%\bin
- 變量值：%JAVA_HOME%\jre\bin
注意：輸入的時候不要有分號
2.安裝Mirth，推薦安裝3.10.1 64 位，版本mirthconnect-3.10.1.b280-windows-x64.exe，安裝說明如下：
（圖1，安裝目錄不要帶有空格）
（圖2，不勾選安裝Administrator Launcher）
（圖3，啟動URL地址 https://localhost:8443 ）
3.安裝客戶端啟動工具，推薦安裝1.1.0 64 位，版本mirth-administrator-launcher-1.1.0-windows-x64.exe，安裝說明如下：
（圖4，安裝在第2步的根目錄下且目錄不能有空格）
4.停止Mirth服務，設置‘系統環境變量’，配置說明如下：
（圖5，右鍵‘我的電腦’，設置系統環境變量，解決Mirth客戶端界面中文GBK亂碼問題）
在安裝目錄中有個 F:\MirthConnect\custom-lib文件夾，這里是擴展Mirth功能，此目錄放置的是用戶自定義JAR包功能擴展庫；因此需要把此路徑加到‘系統的環境變量’CLASSPATH的配置中：
CLASSPATH ： .;%JAVA_HOME%\lib;%JAVA_HOME%\lib\dt.jar;%JAVA_HOME%\lib\tools.jar;F:\MirthConnect\custom-lib;
JDK8安裝特別說明：首先java8安裝目錄不能使用默認目錄，必須是手動選擇安裝到非空格非中文的目錄；
然后配置JAVA_HOME系統變量，如上圖所示。
經過大量測試，如果java8安裝在默認的有空格目錄，web service channel信道會報錯，用不了，報錯截圖如下：
特別提示：改變環境變量，mirth 駕駛艙的管理界面正常顯示不再有亂碼；
但信道描述和日志的中文顯示會亂碼；但接收和發送中文不受影響。
故這樣改系統環境變量后再使用 mirth 時，建立信道寫信道相關描述或日志請用英文。
5.安裝FHIR信道擴展，推薦版本fhir-3.10.1.b286.zip；
安裝步驟，解壓fhir-3.10.1.b286.zip后，拷貝解壓后的fhir整個目錄到mirth服務插件目錄F:\MirthConnect\extensions中，如圖所示：
（圖6，解壓FHIR擴展並拷貝到mirth服務的擴展extensions根目錄）
6.啟動Mirth服務；然后以管理員模式啟動F:\MirthConnect\AdministratorLauncher目錄中的mirth administrator launcher程序launcher.exe，如圖所示：
（圖7，管理客戶端截圖）
特別說明：
導入FHIR部署實例：
https://github.com/Fdawgs/ydh-fhir-listeners
（圖8，擴展視圖中可見FHIR擴展已經導入且啟用）
（圖9，Mirth完整安裝包）
MIRTH CONNECT README
Contents
==================================================
1. General Information
2. Installation and Upgrade
3. Starting Mirth Connect
4. Running Mirth Connect in Java 9 or greater
5. More Information
1. General Information
==================================================
Mirth Connect is an open source health care integration engine. By supporting numerous standards (like HL7, EDI/X12, XML, NCPDP, DICOM, and Delimited Text) and protocols (like TCP/LLP, HTTP, JDBC, and File/FTP/SFTP), Mirth Connect allows for the filtering, transformation, and routing of messages between disparate systems to allow them to share data.
2. Installation and Upgrade
==================================================
Mirth Connect installers are available for individual operating systems (EXE for Windows, RPM and SH for Linux, and DMG for Mac OS X). Pre-packaged distributions are also available for individual operating systems (ZIP for Windows, TAR.GZ for Linux, and TAR.GZ for Mac OS X). The installer allows you to automatically upgrade previous Mirth Connect installations (starting with version 1.5).
Mirth Connect installers also come with the option to install and start a service which will run the background. You also have the option of installing and running the Mirth Connect Server Manager, which allows you to start and stop the service on some operating systems, change Mirth Connect properties and backend database settings, and view the server logs.
An optional Mirth Connect Command Line Interface can be installed, allowing you to connect to a running Mirth Connect Server using a command line. This tool is useful for performing or scripting server tasks without opening the Mirth Connect Administrator.
After the installation, the Mirth Connect directory layout will look as follows:
/appdata/mirthdb: The embedded database (Do NOT delete if you specify Derby as your database). This will be created when the Mirth Connect Server is started. The path for appdata is defined by the dir.appdata property in mirth.properties.
/cli-lib: Libraries for the Mirth Connect Command Line Interface (if installed)
/client-lib: Libraries for the Mirth Connect Administrator
/conf: Configuration files
/custom-lib: Place your custom user libraries here. These libraries will be loaded on the Mirth Connect Server classpath when it is started, making them accessible to channel scripts.
/docs: This document and a copy of the Mirth Connect license
/docs/javadocs: Generated javadocs for the installed version of Mirth Connect. These documents are also available when the server is running at http://[server address]:8080/javadocs/ (i.e. http://localhost:8080/javadocs/).
/extensions: Libraries and meta data for Plug-ins and Connectors
/logs: Default location for logs generated by Mirth Connect and its sub-components
/manager-lib: Libraries for the Mirth Connect Server Manager (if installed)
/public_html: Directory exposed by the embedded web server
/server-lib: Mirth Connect server libraries
/webapps: Directory exposed by the embedded web server to host webapps
3. Starting Mirth Connect
==================================================
Once Mirth Connect has been installed, there are several ways to connect to launch the Mirth Connect Administrator. On a Windows installation, there is a Mirth Connect Administrator item in the Start Menu which launches the application directly.
If the option is not available, you can connect to the Mirth Connect Administrator launch page which by default should be available at http://[server address]:8080 (i.e. http://localhost:8080). Clicking the Launch Mirth Connect Administrator button will connect you to the server which will be listening on https://[server address]:8443 (i.e. https://localhost:8443). If running a new installation, the default username and password for the login screen is admin and admin. This should be changed immediately for security purposes.
If you are launching the administrator for the first time, you will notice that the libraries for the Mirth Connect Administrator will be loaded. This feature allows you run the Administrator from any remote Mirth Connect server without having to download and install a separate client.
You may also notice a security warning when starting the administrator (dialog box depends on browser being used). This is normal and you should click Run to continue launching the administrator.
4. Running Mirth Connect in Java 9 or greater
==================================================
In order to run Mirth Connect in Java 9 or greater, copy the options from /docs/mcservice-java9+.vmoptions and append them to either mcserver.vmoptions or mcservice.vmoptions, depending on your deployment. Then restart Mirth Connect.
To run the Mirth Connect Command Line Interface, create a new file named mccommand.vmoptions in the Mirth Connect root directory. Copy all of the options from /docs/mcservice-java9+.vmoptions into mccommand.vmoptions and save before launching the Command Line Interface.
5. More Information
==================================================
You can find the latest Mirth Connect release information, documentation, and more at: https://www.nextgen.com/products-and-services/integration-engine
Join the Mirth Connect Community at: http://www.mirthcorp.com/community/registration