message exchange protocol between to healthcare partners
Overview
The GeneralNotificationManager is an ATL COM module which provides methods to generate an email like structured message exchange between two partners. The produced XML infoset is transported electronically to the recipient and optionally can be signed and/or encrypted.
The generalNotification systems differs from other Sumex1 processes in that the notification system is symmetric. Thus there is no distinction between request and response.
Architectural blueprint
Either a new notification is produced from scratch by using the IGeneralNotificationRequest interface or a received notification is loaded into the module by the LoadXML method and a reply to that message is generated thereafter. The all data can be visualized using the Print method.
Eventually the data is transformed into a standards-compliant generalNotification XML infoset that is sent to the recipient over a intermediate.
Please also have a look at the Important Documents that serves as a jump start and might effect the ease of the implementation.
Keyfacts at a glance
Version 451 | ||
---|---|---|
Last update: | Thursday, 27 October 2022 - 16:21:12 | |
Module version/date: | 4.51.004 | 27 Oct 2022 |
Interface version/date: | 4.51 | 28 Sep 2018 |
Covering: | XML schema 4.51 from 28. Sep. 2018 |
Version 450 | ||
---|---|---|
Last update: | Tuesday, 20 July 2021 - 12:18:03 | |
Module version/date: | 4.50.004 | 20 Jul 2021 |
Interface version/date: | 4.50 | 2 Sep 2016 |
Covering: | XML schema 4.50 from 2. Sep. 2016 |
Version 440 | ||
---|---|---|
Last update: | Monday, 21 January 2019 - 14:49:57 | |
Module version/date: | 4.40.003 | 21 Jan 2019 |
Interface version/date: | 4.40 | 15 Nov 2013 |
Covering: | XML schema 4.40 from 13. Sep. 2013 |
API browser
Date | Time | API version |
---|---|---|
12.09.22 | 10:32:56 | V4.51: View API browser |
12.09.22 | 10:32:56 | V4.51: Download API browser .CHM file |
20.07.21 | 12:15:31 | V4.50: View API browser |
20.07.21 | 12:15:31 | V4.50: Download API browser .CHM file |
16.10.17 | 12:02:06 | V4.40: View API browser |
16.10.17 | 12:02:06 | V4.40: Download API browser .CHM file |
Download area for generalNotification related files
-
outbound to medSRS.ch - port 80|443
The communication service is triggered inside the method IGeneralNotificationRequest::SetTransport by using the queryRHS() patch as described in the API documentation.
Information about the Restful Webservice is available at medSRS.ch
INSTALLDIR=full_path_to_install_dir
Silent install:
generalNotificationInstaller.exe /s /v"/quiet INSTALLDIR=\"c:\my test\" "
Silent uninstall:
generalNotificationInstaller.exe /s /v"/quiet REMOVE=ALL INSTALLDIR=\"c:\my test\" "
Date | Version | Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
27.10.22 | 4.51.004 | generalNotificationManager with the new restserver generalNotificationManagerServer451 - cf. history Download generalNotificationManager installer (13.9 MB) |
|||||||||||||
Versioning
Revision history
Actions for developers: possibly integrate Actions for end users: install |
|||||||||||||||
show older builds ... | |||||||||||||||
20.07.21 | 4.51.003 | generalNotificationManager installer with cumulative updates - cf. history |
|||||||||||||
Revision history
Code enhancements, performance optimization and internal bug fixes have been integrated as given by the following list:
|
|||||||||||||||
06.04.20 | 4.51.002 | generalNotificationManager with a new feature for improving connectivity - cf. history |
|||||||||||||
Revision history
The electronic reachability of a recipient for a certain version of generalNotification is kind of a chicken and egg problem. To solve this connectivity problem, the webservice medSRS (medical Standard Routing Service) has been created. By using the RESTful webservice method queryRHS one can find out, how and whether a specific recipient can be reached electronically. Please refer to the website medSRS.ch for getting an introduction to the topic or detailed information about the functionality of the webservice. Instead of inputting the argument bstrToEan literal, the string queryRHS(glnProvider,glnRecipient) is supplied virtually as a webservice call in the IGeneralNotificationRequest::SetTransport method. The such given data is actually translated into the RESTful call of the same name. Please study the following URLs as well
It is strongly recommended that this new feature is use/implemented by the main software! Actions for developers: implement Actions for end users: install |
|||||||||||||||
17.06.19 | 4.51.001 | generalNotificationManager installer - initial version |
|||||||||||||
Revision history
Initial version V4.51 Please read the document "Changes from V4.50 to V4.51..." for an overview about the major changes Actions for developers: implement Actions for end users: install |
Date | Version | Description | |
---|---|---|---|
20.07.21 | 4.50.004 | generalNotificationManager installer with cumulative updates - cf. history Download generalNotificationManager installer (17.6 MB) |
|
Revision history
Code enhancements, performance optimization and internal bug fixes have been integrated as given by the following list:
|
|||
show older builds ... | |||
06.04.20 | 4.50.003 | generalNotificationManager with a new feature for improving connectivity - cf. history |
|
Revision history
The electronic reachability of a recipient for a certain version of generalNotification is kind of a chicken and egg problem. To solve this connectivity problem, the webservice medSRS (medical Standard Routing Service) has been created. By using the RESTful webservice method queryRHS one can find out, how and whether a specific recipient can be reached electronically. Please refer to the website medSRS.ch for getting an introduction to the topic or detailed information about the functionality of the webservice. Instead of inputting the argument bstrToEan literal, the string queryRHS(glnProvider,glnRecipient) is supplied virtually as a webservice call in the IGeneralNotificationRequest::SetTransport method. The such given data is actually translated into the RESTful call of the same name. Please study the following URLs as well
It is strongly recommended that this new feature is use/implemented by the main software! Actions for developers: implement Actions for end users: install |
|||
21.01.19 | 4.50.002 | generalNotificationManager installer with cumulative updates - cf. history |
|
Revision history
Code enhancements, performance optimization and internal bug fixes have been integrated as given by the following list:
|
|||
09.06.17 | 4.50.001 | generalNotificationManager installer - initial version |
|
Revision history
Initial version V4.50 Please read the document "Changes from V4.40 to V4.50..." for an overview about the major changes Actions for developers: implement Actions for end users: install |
Date | Version | Description | |
---|---|---|---|
21.01.19 | 4.40.003 | generalNotificationManager installer with cumulative updates - cf. history Download generalNotificationManager installer ( 17.4 MB) |
|
Revision history
Code enhancements, performance optimization and internal bug fixes have been integrated as given by the following list:
|
|||
show older builds ... | |||
06.07.16 | 4.40.002 | generalNotificationManager installer with code improvements. |
|
Revision history
Code enhancements and internal bug fixes have been integrated as given by the following list
Please do update to this build! Actions for developers: none Actions for end users: install |
|||
14.11.13 | 4.40.001 | Installer of the generalNotificationManager - initial version. |
|
Revision history
Initial V4.4 version Actions for developers: implement Actions for end users: install |