The easiest way to get familiar with the eHealth Connector Convenience API is to look at the provided examples in the eHealthConnector demo project, which can be downloaded from the sourceforge SVN (/demo).
You might also want to validate CDA instances generated by the demo application. You can either use the CDA validation feature of the eHealth Connector or an Online-CDA-Validator. See CDA Validation for more information.
Demo application editions
The following demo applications are provided in order to demonstrate and proof the current functionality of the eHealth Connector Convenience API. You may compile them from the open source repository or download them from the members area of IHE Suisse.
Java Demo: ehealthconnectorDemo.jar
This is a Java console application which allows you to simulate the eHealth Connector Convenience API for all implemented main features by providing the appropriate command line arguments. This can either be done from your IDE (e.g. Eclipse) or from the shell.
This is a dotnet Winforms application which provides a UI to start the demo functions.
This is a dotnet console application which provides almost the same functionality as the Java Demo.
Both, the Java and the dotnet applications produce a log file in logs\ehealthconnectordemo.log. By default the application logs only fatal errors to save performance and diskspace. If you want to have a full log, set another threshold or even comment the following line in the rsc\log4jConfigs\log4j.xml:
<param name="Threshold" value="FATAL" />
You may also provide your own log4j config in order to configure the logging behavior yourselves. See Apache Log4j for documentation.
Default output folder
The demos produce some output files such as CDA documents or IHE XDM containers. The destination folder will be defined as follows: If you set an environment variable with the name 'eHCTempPath' the eHealth Connector will use the path specified in this environment variable. If no such environment variable is set, it will try to use /temp. If the path is not writable the eHealth Connector will use the system temp folder.