The communication interface for AudaxCeph is based on exchange of data with the use of XML documents. A software that wishes to pass data to AudaxCeph can do so by creating an XML file according to the XSD schema and then execute AudaxCeph executable (AxCeph.exe) with that xml file as a parameter.

For example if the XML filename is Integration.xml then AudaxCeph should be invoked in the following manner:

            AxCeph.exe »C:\IntegrationFolder\Integration.xml«

There are two options for integration:

1.    AudaxCeph data is kept in the AudaxCeph database. This interface allows for patient data to be passed to AudaxCeph. AudaxCeph only returns result/debug messages for interface calls. Patients are indexed with provided IDs (from PMS software) which allows for data consistency without patient duplication and without the need for the calling software to store any information from AudaxCeph. This interface requires minimal development on PMS side.

Pros:

• Easy to implement
• Fast loading time
• AudaxCeph can be started as a stand alone software

Cons:

• No data is passed back from AudaxCeph to caller application

2.    All data is stored in the caller application. AudaxCeph only works on data in the folder where the integration.xml is located. When working with AudaxCeph all created documents are stored in the same folder. Upon exiting AudaxCeph the integration.xml is updated which can then be read by the caller application. This requires bigger effort for development on PMS side.

Pros:

• Data created in AudaxCeph is passed back to caller application.

Cons:

• Slow operation: all files that are to be shown in AudaxCeph need to be copied to a bridge folder each time AudaxCeph is invoked. This causes significantly longer loading times.
• Significantly bigger effort than Integration type 2
• AudaxCeph needs to be started from the caller application

Ask Audax Team for additional information.