connect release 2 4 dynamic document installation and configuration 031810

8/3/2019 CONNECT Release 2 4 Dynamic Document Installation and Configuration 031810

1/15

CONNECT Dynamic Document

Installation and Configuration ManualVersion 1.0

CONNECT Release 2.4

18 March 2010


2/15

CONNECT_Dynamic_Document i Release 2.4

03/18/10

REVISION HISTORY

REVISION DATE DESCRIPTION

1.0 18 March 2010 Initial Release


3/15

TABLE OF CONTENTS

1.0 INTRODUCTION ......................................................................................... 1

1.1 PURPOSE ........................................................................................................... 1

1.2 SCOPE ............................................................................................................... 22.0 INSTALLATION CHECKLIST ..................................................................... 2

3.0 INSTALLATION OF DYNAMIC DOCUMENT COMPONENTS................... 2

4.0 DATABASE CONFIGURATION.................................................................. 2

4.1 CONFIGURATION OF DOMAIN.XML ..........................................................................34.2 CONFIGURE DYNAMIC DOCUMENT COMPONENT ENDPOINTS................................... 64.3 CONFIGURATION OF PROPERTY FILES ................................................................... 7

4.3.1 $NHINC_PROPERTIES_DIR/adapter_common_datalayer.properties. ........ 74.3.2 $NHINC_PROPERTIES_DIR/repository.properties ......................................84.3.3 $NHINC_PROPERTIES_DIR/Hibernate/dyndocrepo.hibernate.cfg.xml ....... 8

4.3.4 $NHINC_PROPERTIES_DIR/CAL_Emulator/xml/*.xml................................ 84.4 RESTARTING GLASSFISH AND VERIFICATION OF CONFIGURATION ............................ 94.5 DEPLOY DYNAMIC DOCUMENT GENERATION EJBS...............................................104.6 EXECUTE SOAPUITESTS ................................................................................... 11

LIST OF FIGURES

FIGURE 4.4-1 VERIFY CONFIGURATION............................................................................... 9

FIGURE 4.5-1 SELECT EJBMODULES .............................................................................. 10FIGURE 4.5-2 DEPLOY COMPONENTS............................................................................... 11FIGURE 4.6-1 VIEW TEST CASES ..................................................................................... 12

CONNECT_Dynamic_Document ii Release 2.4

03/18/10


4/15

1.0 INTRODUCTION

1.1 Purpose

This document is the installation and configuration manual for installing the Dynamic

Document components. These adapter components are independent components toreplace the reference adapter side components delivered with CONNECT. TheDynamic Document generation components were generated by Telemedicine &Advanced Technology Research Center and Northrop Group Corporation in support ofthe DoD/VLER Phase 1a Pilot demonstration. The FHA has taken this contribution andincorporated the Dynamic Document generation portion into CONNECT R2.4.

In general, the process flows as follows:

1. A Document Query request is received by the adapter.

2. Document Assembly validates with the Templates Manager that the

requested document is supported. Upon successful validation of thedocument type, Document Assembly validates that the patient exists in the

system.

3. Upon successful validation of the patient, the Document Query request is

passed to the CDA Document Builder component.

4. CDA Document Builder requests templates information from Templates

Manager for the requested document. For example, when the requested

document is a C32 document, the Templates Manager will respond with a list

of CDA sections, such as Patient Information, Allergies, Medications and so

on, that constitute a C32 document.

5. CDA Document Builder then makes a request to the CDA SectionsAssembler to get the necessary sections in order to construct the requested

document.

6. CDA Sections Assembler requests templates information from the Templates

Manager for the requested section. For example, when the requested section

is a Problem List, the Templates Manager will respond with a list of one CDA

Condition module.

7. CDA Sections Builder makes a request to the CDA Modules Assembler to

obtain the necessary modules in order to construct a CDA section in

accordance with the HITSP/C83 CDA Content Modules Specification.

8. CDA Modules Assembler makes request(s) to the Data Access Service to

obtain contents for the module's data elements and construct a CDA module

in accordance with the HITSP/C83 CDA Content Modules Specification.

9. Document Assembly returns the document to the calling entity.

CONNECT_Dynamic_Document 1 Release 2.403/18/10


5/15

1.2 Scope

The procedures in this document are specific to the installation of the Adapter DynamicDocument Generation components on a Windows Operating System.

2.0 INSTALLATION CHECKLISTThe installation of the Dynamic Document components assumes the successfulcompletion of the CONNECT System Installation and Configuration procedure:

http://developer.connectopensource.org/display/NHINR24/Release+2.4+Home

The following steps are required to complete the installation and configuration.

Item Procedural Step1 Install the Dynamic Document Generation components

2 Configure the Glassfish domain.xml to support Dynamic DocumentGeneration databases

3 Update internalConnectionInfo.xml to include endpoints for DynamicDocument Generation components.

4 Configure properties files

5 Restart Glassfish and Verify configuration

6 Deploy Dynamic Document Generation EJBs

7 Execute default CONNECT SoapUI Tests

3.0 INSTALLATION OF DYNAMIC DOCUMENT COMPONENTS

There are five EJB components that comprise the Dynamic Document Generationfunctionality. These components are available in theNHIN_CONNECT_DynamicDocuments_2.4.0.xxx.zip file where xxx is the release buildnumber. Extract the components into C:\temp. This will create the C:\temp\bin directorythat contains the components. The deployment of these components is detailed insection

4.0 DATABASE CONFIGURATION

The Dynamic Document Generation capabilities utilize Toplink and Hibernate databasedrivers to access MySQL database tables in support of generating dynamic documents.The existing database schema docrepository is altered in support of this feature, andadditional database schemas and tables are created. The database scripts are providedin the delivery in NHIN_CONNECT_Binaries_2.4.0.xxx.zip. Explode the zip file into

http://developer.connectopensource.org/display/NHINR24/Release+2.4+Homehttp://developer.connectopensource.org/display/NHINR24/Release+2.4+Home


6/15

C:\temp. The database scripts to support dynamic document generation are located inDBScripts\dynamicdocuments.

The existing CONNECT system user nhincuser/nhincpass is used in support ofDynamic Document database access. The following steps assume that the MySQLinstallation resides at C:\Program Files\MySQL\MySQL Server 5.1\bin. Otherwise, usethe directory path to MySQL that applies to the target environment.

cd C:\Program Files\MySQL\MySQL Server 5.1\bin

mysql uroot pNHIE-Gateway


7/15

Add tags, which describe the connection pools referenced inthe tags.

Connection pool for docassembly schema



8/15

Connection pool for templates schema



9/15

Add tags to the node, then enter the following reference tags toensure that the connection resources are available to the adapter components.

< resource-refenabled="true"ref="jdbc/dasDS"/>

< resource-refenabled="true"ref="jdbc/templateDS"/>

4.2 Configure Dynamic Document Component Endpoints

The Dynamic Document component endpoints are defined in theinternalConnectionInfo.xml. The following endpoints need to be updated:

adapterdocquerysecured

Adapter Document Query

https://localhost:8181/NhinConnect/AdapterDocQuerySecured

adapterdocretrievesecured

Adapter Document Retrieve Secured

https://localhost:8181/NhinConnect/AdapterDocRetrieveS

ecured

adapterxdsbdocrepository

Adapter Document Repository

http://localhost:8080/DocumentRepository/DocumentRepo

sitory_Service



10/15


11/15

emulate an interface to a specific HER system. To enable the emulation, set the *_testflags to Y.

medications_test=Y

allergies_test=Y

problems_test=Y

patient_info_test=Y

4.3.2 $NHINC_PROPERTIES_DIR/repository.properties

This property file contains the default repository id used by theAdapterDocumentRepositoryEJB when storing generated documents in the repository.

The repositoryId is used by the DocumentManagerEJB. For this version of the DynamicDocument Generation, the policyRespositryId and the inboundDocumentRepositoryIdare not currently used.

The documentUniqueOID is used when creating a document unique id.

4.3.3 $NHINC_PROPERTIES_DIR/Hibernate/dyndocrepo.hibernate.cfg.xml

This file contains the Hibernate configuration for the document repository. The DynamicDocument Generation feature uses an altered version of the reference docrepositorydatabase table provided with CONNECT. There are no configuration modificationsrequired on this property file.

4.3.4 $NHINC_PROPERTIES_DIR/CAL_Emulator/xml/*.xml

These are the support data files used for Dynamic Document Generation. These filesare stubs to be replaced by an Adapter Agencys specific interface to patient records.These are a set of files with the following naming conventions:

__ALLERGIES_CareRecordQUOCIN043200UV01Response.xml

__PATIENT_INFO_PatientDemographicsPRPAMT201303UV02Response.xml

__MEDS_CareRecordQUOCIN043200UV01Response.xml

__PROBLEMS_CareRecordQUOCIN043200UV01Response.xml



12/15

These files can be modified to change the default set of patient health recordinformation to return from Dynamic Document Generation. The modifications are thenincorporated into the document and accessible in the repository. Medications, allergies,problems, and patient info can be changes in these files and the results present in thenext dynamic document generated.

4.4 Restarting Glassfish and Verification of Configuration

Perform the following steps to restart the Glassfish application and verify theconfiguration:

1. Restart Glassfish by executing asadmin start-domain domain1.

2. Verify that the connection pools are defined from the Glassfish console. You willneed to first log on to the Glassfish admin console.

3. Open the URL http://localhost:4848/login.jsf. The default user name is admin,and the default password is admin/adminadmin. If you customized any of thesesettings in your installation, use your custom settings instead.

4. Select the Resources task from the navigation panel on the left.

5. Expand out the JDBC node. Then expand the JDBC Resources to verify thejdbc/dasDS and jdbc/templateDS are defined.

6. Expand the Connection Pools to verify the docassemblyPool and templatedbPoolare defined.

Figure 4.4-1 Verify Configuration



13/15

4.5 Deploy Dynamic Document Generation EJBs

The Dynamic Document Generation functionality is provided through five EJBs. Thecomponent below is a replacement for the reference version provided with the defaultCONNECT installation:

DocumentRepositoryEJB is replaced with AdapterDocumentRepositoryEJB

The complete list of the EJBs to be deployed is as follows:

AdapterCommonDataLayerEJB

AdapterDocumentAssemblyProxyEJB

AdapterDocumentRepositoryEJB

DocumentManagerEJB

NhinAdapterServiceEJB

Each of these EJBs is deployed manually from the Glassfish console by executing thefollowing steps for each component.

1. From the Glassfish console, select EJB Modules from the navigation panel onthe left.

Figure 4.5-1 Select EJB Modules



14/15

2. Select the Deploy button. From this page, you can select the Browse button tonavigate to each of the Dynamic Document components to be deployed. Thenselect the OK button to initiate the deployment.

Figure 4.5-2 Deploy Components

3. Follow these same steps for each of the five EJBs listed above. Then stop/startGlassfish via:

asadmin stop-domain domain1

asadmin start-domain domain1

4. Monitor the server.log to verify a clean/successful restart.

4.6 Execute SoapUI Tests

The CONNECT System comes with a set of SoapUI tests to execute the core systemusing a reference version of the adapter components. The SoapUI tests for DynamicDocument Generation are included with these tests with the tests cases in a default



15/15

disable state. The tests are called Dynamic Document Query and Dynamic DocumentRetrieve.

NOTE: When the CONNECT System is in the Dynamic Document Generationconfiguration, the default Document Query and Document Retrieve SoapUI tests will failto execute successfully.

After launching the SoapUI GUI and loading the DynamicDocumentTest-Internal-soapui-project.xml and DynamicDocumentTest-EndtoEnd-soapui-project.xml fromC:\Temp\SelfTest\DynamicDocumentTest, expand the test suite nodes to view theindividual test cases. By default, the dynamic versions of Document Query andDocument Retrieve may have disabled.

Prior to running the tests, the dynamic test cases have to be enabled.

Figure 4.6-1 View Test Cases

The tests can be run as a suite or individually. The only test case applicable to DynamicDocument Generation is the Dynamic Document Query and Dynamic DocumentRetrieve tests.
