aduane

• A CapabilityStatement is generated automagically by a channel that has a "FHIR Listener" source connector.
• The default CapabilityStatement does not conform to the requirements laid out in https://www.hl7.org/fhir/capabilitystatement.html
• CapabilityStatement.rest.resource.searchParams are not specified
• CapabilityStatement.status is not specified
• CapabilityStatement.implementation is not specified
• CapabilityStatement.document is not required, is specified, but is invalid (missing the profile element)

To remedy these issues or just otherwise customize the CapabilityStatement:

• Find the "Capability Statement Template" option in the FHIR Listener source connector configuration screen.

jonbartels

Mirth Connect is awesome! One common question on the forums and Slack is how to manage SSL connctions. These questions mainly focus on HTTPS but also include TCP connections.

The quick rundown is:

1. The built-in MC HTTP Sender connector will do HTTPS if:

• The endpoint has a certificate which is signed by a CA already present in the JVM truststore and has the right DN or SAN for the hostname. This is logically equivalent to the "green check" if you open the URL in a browser.
• The certificate has been added to the truststore for the JVM that MC is running under
• Changes to DNS or host files allow a hostname to match the DN or SAN already present in the cert (not reccomended)
• The connector may flag these connections with a warning or red x. Test the channel first as the validator makes assumptions about SSL that may not apply in this case.

2. The built-in MC HTTP Listener connector will not do SSL directly. A plugin or a proxy is necessary.

• Tony Germano has a plugin implemented for SSL l

dvdbng

mkdir ~/vim
cd ~/vim

# Staically linked vim version compiled from https://github.com/ericpruitt/static-vim
# Compiled on Jul 20 2017
curl 'https://s3.amazonaws.com/bengoa/vim-static.tar.gz' | tar -xz

export VIMRUNTIME="$HOME/vim/runtime"
export PATH="$HOME/vim:$PATH"
cd -