CONNECT Development Environment Version 2.1 Item Version Java JRE/JDK 1.6 Update 16 (32-bit version) GlassFish 2.1 NetBeans 6.7.1 Metro 1.5 MySQL 5.1.41 SoapUI 3.0.1
Major Changes in 2.4
Support of the Updated NHIN Specs:
Also added as part of release 2.3.1
Certificate Revocation List (CRL)
Also added as part of release 2.3.1
Performance and Build Time Improvements
Progress toward IDE Neutral Build Scripts
Dynamic Document Assembly Components
Asynchronous Messaging Research
Support of the Updated NHIN Specifications Document Submission Kieran Dunne
Document Submission V 1.1.0 Dated: 10/26/2009
HITSP/T31 Document Reliable Interchange Transaction Version 1.3 July 8, 2009
IHE ITI TF Supplement XDR TI 2009-8-10
IHE ITI TF Revision 6.0 Vol. 2b, 2x, 3 2009-8-10
Document Submission Specification has not been finalized.
Purpose of the Document Submission Framework
Provide the ability to “push” data for a given patient from one NHIE to another via configuration on the submission side.
This is a different model of exchange than subscription because the sender decides who the data should go to and the receiver receives data on an appropriate available endpoint from the sources it authorizes
Document Submission is viable where XDS Registry/Repositories are not yet implemented or available for the exchange of information.
Intended only for exchange of patient related medical documents and not intended to address all cross‐enterprise EHR communication needs
Receiver does not need to know about the sender
Differs from the Publish/Subscribe model currently in place.
Sender controls who receives the data.
Built on XDS.b specification
Uses the same ProvideAndRegisterDocumentSet-b message
CRL (Certificate Revocation Lists) Sai Valluripalli
Certificate Revocation List
Certificate Revocation Lists (CRLs) are lists of certificates that are no longer valid or that have been revoked by a CA (Certificate Authority).
Each NHIN initiating and responding gateway MUST implement either Online Certificate Status Protocol (OCSP) based x.509 certificate revocation checking or use CRLs against an NHIN-governed CA to determine the revocation status of each certificate as per NHIN policy.
Various reasons to revoke a certificate are Unspecified, Key compromise, CA Compromise, Affiliation Changed, Superseded Privileges withdrawn etc.,
We have to configure Glassfish application server to achieve dynamic CRL functionality. The details of configuring JVM OPTIONS can be found in our documentation at: http://developer.connectopensource.org/display/NHINR24/Certificate+Validation+Using+Certificate+Revocation+Lists
Performance & Build Time Improvements Neil Webb
Performance & Build Time Improvements
EJB web services now hosted as POJO web services in web applications
Consolidated 58 EJB projects into 6 web applications
Contribution from TATRC/NGC based on their development effort to support DoD/VLER Phase 1a.
Developed against CONNECT R2.1.
This is an EJB implementation which has yet to be converted to POJO.
Replacement of the reference version of DocumentRespositoryEJB provided with CONNECT.
Templates used for dynamic document generation to support Patient Information, Medications, Problems and Allergies sections of CDA document.
Database tables allow the user to configure which sections are included in a generated document.
AHLTA interface is stubbed out using XML files
SoapUI Updates Scott Borst
The property file is now renamed to have the same name as the soapUI project itself and should be placed in the same directory where the soapUI project file resides.
The property file is now loaded at the project level instead of being loaded within every test case.
The Load Script includes Groovy code to load the property file at the project level, when the project is loaded into soapUI.
The project level properties as well as the test case level properties are now embedded directly in the request XML itself via property expansion, eliminating the need of a Property Transfer step.
The Load Script also includes Groovy code to add dynamic properties to the property list that are created during the test case for just that test case run.
SQL and GetDates Steps
The Load Script includes a Groovy method to access the database at the project level, when the project is loaded into soapUI.
All the SQL steps within each test case are now simplified to use the new withSql method in the Load Script.
The Load Script includes a test case listener to set the StartDate, EndDate, SigDate and ExpireDate at the project level, when the project is loaded into soapUI.
This eliminated the step to set dates within a particular test case.
With all of the above changes…
The self-tests are now portable and can be executed from any folder as long as the project and properties file are in the same folder.
The self tests are platform independent, the same test can be run on Windows and Solaris.
When running the soapUI GUI, when a change is made to a properties file, the change is not reflected within the soapUI project until the Load Script at the project level runs again. To run the script, double click on the Project name in soapUI and go the Load Script tab on the right panel and click on the Green arrow.
CONNECT Asynchronous Support Les Westberg
Transport-neutral mechanisms to address web services and messages
MessageId: Unique ID for the message
ReplyTo: URL to send response to
RelatesTo: Message ID for which the message is a response