CONNECT NIST XDS Document Registry and Repository ...

perchmysteriousΔιαχείριση Δεδομένων

30 Νοε 2012 (πριν από 4 χρόνια και 8 μήνες)

624 εμφανίσεις









CONNECT
NIST XDS Document Registry
and Repository Installation and
Configuration Manual


ersion 4.0

CONNECT Release 2.4

18 March 2010






CONNECT_
NIST
_
Manual

i

Release 2.4

3/18/10


REVISION HISTORY


REVISIO
N

DATE

DESCRIPTION

1.0

7 July 2009

Initial Release

2.0

29 September 2009

Updated to reflect CONNECT Release 2.2

3.0

05 January 2010

Updated to reflect CONNECT Release 2.
3

4.0

18 March
2010

Updated to reflect CONNECT Release 2.
4


























CONNECT_
NIST
_
Manual

ii

Release 2.4

3/18/10


TABLE OF CONTENTS

1.0

INTRODUCTION

................................
................................
................................
.............

1

1.1

P
URPOSE

................................
................................
................................
......................

1

1.2

S
COPE

................................
................................
................................
..........................

1

1.3

D
OCUMENT
D
ESCRIPTION

................................
................................
...............................

1

2.0

REFERENCED DOCUMENTS

................................
................................
........................

1

3.0


INSTALLATION AND CON
FIGURATION CHECKLIST

................................
................

2

4.0


ENVIRONMENT FOOTPRIN
T

................................
................................
.......................

2

4.1

H
ARDWARE
R
EQUIREMENTS FOR
I
NSTALLATION

................................
................................

2

4.2

S
OFTWARE
R
EQUIREMENTS FOR
I
NSTALLATION

................................
................................

3

5.0


OBTAIN MEDIA/ SOFTWA
RE

................................
................................
.......................

4

6.0


WINDOWS INSTALL AND
CONFIGURATION INSTRU
CTIONS

................................
..

4

6.1

U
NZIP THE
NHIN

CONNECT

G
ATEWAY
F
ILE

................................
................................
...

4

6.2

I
NSTALL
S
OFTWARE ON
W
INDOWS

................................
................................
...................

4

6.2.1

JAVA SE Development Kit

................................
................................
.......................

4

6.2.2


INSTALL PostgreSQL

................................
................................
.............................

5

6.2.3


Create the NIST Supporting Databases

................................
................................
..

8

6.2.4


Install Tomcat Servers

................................
................................
...........................

14

6.2.5


Install the XDS Server Code into Tomcat

................................
..............................

15

6.2.6


Configure the Installation

................................
................................
.......................

18

6.2.6.1

Change the Physical Location where Documents are Stored on the NIST XDS
Repository

................................
................................
................................
.........................

18

6.2.6.2

Change the Metadata Codes that are Validated by the NIST XDS Registry and
Repository

................................
................................
................................
.........................

20

6.2.6.3

Change the Assigning Authority Value for Patients that will have Documents
Stored in the Repository

................................
................................
................................
....

22

6.2.6.4

Change the Document Repository Unique Id

................................
......................

23

6.2.6.5

Change the NIST XDS Registry and Repository Software to not Validate Patient
Ids

24

6.2.7


Test the Installation

................................
................................
...............................

26

6.2.7.1

Store a Test Document to the NIST XDS Repository

................................
.........

26

6.2.7.2

Query for a Test Document from the NIST XDS Repository

...............................

30

6.2.7.3

Retrieve a Test Document from the NIST XDS Repository
................................
.

31

6.2.8


Configure CONNECT to Connect to the NIST XDS Repository

............................

33

7.0


EXAMPLE TEST REQUEST

MESSAGES
................................
................................
...

35

7.1

D
OCUMENT
S
TORAGE

................................
................................
................................
...

35

7.2

D
OCUMENT
Q
UERY
................................
................................
................................
.......

43

7.3

D
OCUMENT
R
ETRIEVAL

................................
................................
................................
.

44

8.0


USEFUL LINKS

................................
................................
................................
...........

45

9.0


ACRONYMS

................................
................................
................................
.................

46



CONNECT_
NIST
_
Manual

1

Release 2.4

3/18/10


1.0

INTRODUCTION

1.1

Purpose

This document is the installation and configuration
manual

for installing the
National Institute of
Standards Technology (NIST) XDS Document Registry and Repository software
.

This document describes the process for installing the NIST XDS Document Registry and
Repository software with the NHIN CONNECT Gateway and Adapter software.
The NIST XDS
Registry and Repository software is the chosen NHIN CONNECT document registry and
repository components for enterprise
-
type installations for this release of NHIN CONNECT.

This document includes installation and configuration instructions for
the Windows Operating
Systems. The NIST XDS Document Registry and Repository software contains installation
instructions (see C:
\
xds_support_bin_2
\
install.pdf file after executing the steps in section 6.1
in this document) for a Unix
-
like platform, which
this document is based on. The reader should
feel free to use the NIST XDS install.pdf installation guide as needed.

1.2

Scope

The procedures in this document are applicable to CONNECT users.

1.3

Document Description

This document includes the following se
ctions:



Section 1.0 Introduction



Section 2.0 Referenced Documents



Section 3.0 Installation and Configuration Checklist



Section 4.0 Environment Footprint



Section 5.0 Obtain Media/Software



Section 6.0 Windows Install and Configuration Instructions



Section 7.
0 Example Test Request Messages



Section 8.0 Useful Links



Section 9.0 Acronyms


2.0

REFERENCED DOCUMENTS

The following list of documents is referenced within this manual and can be found on the
CONNECT web site:



CONNECT

Release

2
.3
System

Installation and
Configuration

Full

Binary

Manual



CONNECT

Release

2
.3
System

Installation and Configuration

Source Code Manual

In addition to those documents listed above, the original NIST software installation manual can
be found in the zip file downloaded from the
CONNECT site (see section 5
.0
). When extracted
(see section 6.1) the original NIST installation manual can be located at



C:
\
xds_support_bin_2
\
install.pdf


CONNECT_
NIST
_
Manual

2

Release 2.4

3/18/10


3.0


INSTALLATION AND CON
FIGURATION CHECKLIST


Item

Procedural Step



Download the NIST XDS Registry
and Repository software from the
NHIN CONNECT Release Site. See section 5.


Unzip the NIST XDS Registry and Repository software to the
appropriate location. See section
6.1
.


Ensure the Java 1.6 update 13 software is installed. See section 6.2.1


Install PostgreSQL. See section 6.2.2


Create the NIST supporting databases. See section 6.2.3


Install the
T
omca
t servers. See section 6.2.4


Install the XDS server code into tomcat. See section 6.2.5


Configure the installation. See section 6.2.6


Test the installation. See section 6.2.7


Configure the CONNECT gateway server to point to the NIST XDS
Document
Registry and Repository servers. See section 6.2.8.


4.0


ENVIRONMENT FOOTPRIN
T

4.1

Hardware Requirements for Installation

This section describes the recommended minimum hardware component infrastructure,
including processor performance, disk space, and RAM for the application server platform.
This information is subject to change based on continued development. This informat
ion
mirrors the hardware requirements for CONNECT Release
2.2

and is repeated here for your
convenience.

Item

Version

Processor

Minimum dual 2GHz CPU

RAM

Minimum of 4 GB

Hard Disk Size

Application Dependent on
the deployment
configuration. For sizing
purposes, assume 100K
per CCD record, 1K per
audit log record.

Hard Disk Speed

Minimum of 7200 RPM
and 10000 RPM preferred.


CONNECT_
NIST
_
Manual

3

Release 2.4

3/18/10


Item

Version

Network Interface

100MB Ethernet
acceptable; 1GB Ethernet
desirable

4.2

Software Requirements for Installation

This section
describes dependent software products.



Item

Description

Operating
System

Windows Server 2003 and above


Java
-
JRE/JDK

Java SDK 1.6 Update 13, Build 3.

Application
Servers

Apache Tomcat Version 5.5.23 (for the
NIST software)

Apache Tomcat Version 5.0.19

(for the
backend xmlrr document registry)

Communicatio
n Stack

Axis2 v1.3

Network
Protocol

TCP/IP

Relational
Database

PostgreSQL v.8.1 or higher

Recommende
d Test Tools
(Optional)

soapUI v2.5.1


CONNECT_
NIST
_
Manual

4

Release 2.4

3/18/10



5.0


OBTAIN MEDIA/ SOFTWA
RE

Download the NIST components packages from the CONNECT Site.

Step

Action Input

Expected Result

1

Download the
NIST_XDS_Registry_Repository_
2.3
.x.xxx
.zip file from the NHIN
CONNECT release site.

The file is now located on your
computer.




6.0


WINDOWS

INSTALL AND CONFIGUR
ATION INSTRUCTIONS

In order to install the NIST XDS Document Registry and Repository CONNECT Adapter
component, you will need to download and install both the NIST software as well as the
PostgreSQL database server software. The zip fi
le you downloaded from the CONNECT
website will contain both the NIST software (which will come with the needed Apache Tomcat
application servers) and the PostgreSQL database installation program.

6.1

Unzip the NHIN CONNECT Gateway File


Step

Action Input

Expected Result

1

Unzip the
NIST_XDS_Registry_Repository_
2.3
.x.xxx
.zip file downloaded from NHIN
CONNECT release site.


Note that this should be unzipped to
C:
\

and it will create the correct
directory structure.

It should uncompress into the
C:
\
postgres,

C:
\
xds_support_bin_2 and
C:
\
xds_support_bin_1 folders.




6.2

Install Software
o
n Windows

This section describes the installation of the additional software required for the NIST XDS
Document Registry and Repository software to be installed on
your computer.

6.2.1

JAVA SE Development Kit

Install the Java JDK 1.6 update 13 onto your computer if it has not already been installed.
These installation instructions will assume that the appropriate java version is already installed
on your computer

with the JAVA_HOME environment variable preset. Installation instructions
for this required component are contained in the following CONNECT installation manuals
located on the CONNECT web site and will not be repeated here.


CONNECT_
NIST
_
Manual

5

Release 2.4

3/18/10




CONNECT

Release

2
.3
System

Installation and Configuration

Source Code Manual



CONNECT

Release

2
.3
System

Installation and Configuration

Full

Binary

Manual

6.2.2


INSTALL PostgreSQL

Install PostgreSQL v8.3 onto your computer.

Step

Action Input

Expected
Result

1

Start the PostgreSQL

v.8.3 installation program that
was included in the zip file you downloaded from the
NHIN CONNECT website by:





Double clicking on the “C:
y
po獴s牥r
y
pos瑧牥獱l
J
U⸳KT
J
N
J
windows.exe” file from windows
exp汯牥爮
=
=
qhe⁰o獴s牥猠
楮獴a汬a瑩tn=
app汩捡瑩tn⁷楬氠
獴s
牴n⁹ou爠
捯mpu瑥爮
=
O
=
=
=
Click on the “Next” button.
=
=
vou⁷楬氠le=
瑡步n⁴o=瑨e=
nex琠楮獴a汬a瑩tn=
獣牥sn⁷he牥r
you⁷i汬⁢e=
a獫sd=瑯=
p牯r楤i⁴he=
楮獴a汬a瑩tn=
d楲e捴c特⁦o爠
po獴s牥献
=
P
=
=
=
bn瑥爠rhe=de獩sed⁩=獴sl污l楯i=ca瑩tn=fo爠po獴g牥猠and=
捬c捫⁴he=
“Next” button.
=
vou⁷楬氠le=
瑡步n⁴o=瑨e=
nex琠楮獴a汬a瑩tn=
獣牥sn⁷he牥r
you⁷i汬⁢e=
a獫sd=瑯=
p牯r楤i⁴he=
汯捡瑩tnf=瑨e=
da瑡⁤楲e捴c特=
景爠ro獴s牥猠
da瑡ba獥sK
=

CONNECT_
NIST
_
Manual

6

Release 2.4

3/18/10


Step

Action Input

Expected
Result


~or~


Simply accept the default location and click on the
“Next” button to continue.

4




Enter the desired location for the postgres data
directory for postgres databases and click on the
“Next” button to continue.


~or~


Simply accept the default location and click on the
“Next” button to continue.

You will be
taken to the
next installation
screen where
you will be
asked to
provide the
password of
the “root”
postgres user.

5



Enter the desired password of the “root” database
You will be
taken to the
next installation
screen where
you will be
asked to
provide the port
number your
postgres
database
server will be
listening on.


CONNECT_
NIST
_
Manual

7

Release 2.4

3/18/10


Step

Action Input

Expected
Result

user and click on the “Next” button. For purposes of
this installation
manual
, a password of “password” will
be use
d.

6



ACCEPT THE DEFAULT VALUE
! DO NOT ENTER
ANY OTHER VALUE FOR THE DATABASE PORT.


Click the
“Next” button to continue.

You will be
taken to the
next installation
screen where
you will be
asked to
provide your
preferred
locale.

7



Use the drop
-
down menu to select your preferred
locale. Click on the “Next” button to continue.

You will be
taken
to the
next installation
screen.


CONNECT_
NIST
_
Manual

8

Release 2.4

3/18/10


Step

Action Input

Expected
Result

8



Click on the “Next” button to continue.

Postgres will
begin
installation
.

9


Installation of
the
PostgreSQL
database
software on
your computer
should be
completed
successfully.


6.2.3


Create the NIST
S
upporting
D
atabases

The NIST XDS Registry and Repository software requires several supporting databases in the
PostgreSQL database server you just installed. Follow the steps listed below to create those
databases on your newly installed database server.


CONNECT_
NIST
_
Manual

9

Release 2.4

3/18/10



Step

Action Input

Expected Result

1

Open the System Properties window
for entering system environment
variables.


Note: Under Windows XP, the
environment variables can be
located under Control Panel
-
>System
-
>Advanced
-
>Environment
Variables. Under Windows Vist
a,
the environment variables can be
located under Control Panel
-
>System
-
>Advanced System
Settings
-
>Environment Variables.



The System Properties window
should appear as the next step
will display.



2

Click on the “New” button under the
“User variables”
獥捴楯nf=瑨e=
“Environment Variables”
w楮iowK
=
The “New User Variable” dialog
w楮iow=w楬氠lppea爮
=
P
=
Enter “POSTGRESQL_HOME” as
瑨e=name=of⁴he=env楲onmen琠
va物ab汥l⁡nd⁴hen=en瑥爠瑨e=ca瑩tn=
of⁴he⁰o獴s牥猠da瑡ba獥⁡pp汩捡瑩tn=
⡥⹧⸬⁃=
y
mo獴s牥rni
y
U⸳


y
m牯r牡r⁆楬es
y
mo獴g牥r兌
y
UKPⰠ
e瑣tF
=
=
The “POSTGRESQL_HOME”
u獥爠rnv楲onment⁶a物ab汥l
va汵l猠si汬⁢e⁥nte牥r⁩n⁴he=
“New User Variable” dialog
w楮iow⁳業楬a爠瑯⁴he⁥xamp汥l
獨own⁴o⁴he=晴K
=

CONNECT_
NIST
_
Manual

10

Release 2.4

3/18/10


Step

Action Input

Expected Result


4

Click on the “OK” button.

The POSTGRESQL_HOME
environment variable will be
created and you should see the
System Properties window.



5

Create or modify the “PATH” user
environment variable. If the PATH
user environment variable does not
exist, use the steps above as a
guide for creating this variab
le.

The PATH user environment
variable is created.

6

Set the PATH user environment
variable to include the
“%POSTGRESQL_HOME%
\
bin”
value, and click on the OK button.

The PATH user environment
variable will be created with the
value described on the left.




CONNECT_
NIST
_
Manual

11

Release 2.4

3/18/10


Step

Action Input

Expected Result

7

Create or modify the “CLASSPATH”
user environment variable (using the
steps listed above as a guide) with
the following value:


.;%JAVA_HOME%
\
lib;%POSTGRE
SQL_HOME%
\
lib

The CLASSPATH user
environment variable will be
created with the value described
in the left.



8

Click on the OK buttons to accept
these changes and close the
Environment Variables and System
Properties windows.

The Environment Variables and
System Properties windows
should be closed.

9

Open a command window in the
“c:
\
xds_support_bin_2” folder as
created in section 6.2 above.

A command window should be
open in the
c:
\
xds_support_bin_2 directory.

10

Execute the following command:


createuser
-
U postgres
-
s
-
P ebxmlrr

The createuser postgres
command will execute and
prompt you for the new role
password.

11

Hit the return key when prompted for
the new role’s password.


Enter password for the new role:
<return_key>

You will then be prompted to
confirm the password.

12

Hit the return key when prompted to
enter the new

role’s password again.


Enter it again: <return_key>

You will then be prompted for
another password


the user’s
password to which the
createuser command is
executed under.

13

Enter the postgres user’s password
that you established in step 5 of
section 6
.2.2


Password:<postgres_user_passwor
d>

The ebxmlrr user will have been
created without a password.

14

Execute the following command:


The createuser postgres
command will execute and

CONNECT_
NIST
_
Manual

12

Release 2.4

3/18/10


Step

Action Input

Expected Result

createuser
-
U postgres
-
s
-
P
xdsoper

prompt you for the xdsoper
user’s
password.

15

Enter “xdsoper” when prompted for
the new role’s password:


Enter password for new role:xdsoper

You will then be prompted to
enter the password in again.

16

Enter the same password as in step
15


Enter it again:xdsoper

You will then be
prompted for
another password


the user’s
password to which the
createuser command is
executed under.

17

Enter the postgres user’s password
that you established in step 5 of
section 6.2.2


Password:<postgres_user_passwor
d>

The xdsoper user will have been

created.

18

Execute the following command:


createuser
-
U postgres
-
s
-
P logs

The createuser postgres
command will execute and
prompt you for the logs’ user
password.

19

Enter “xdslogs” when prompted for
the new role’s password.


Enter password for new
role:xdslogs

You will then be prompted to
enter the password in again.

20

Enter the same password as in step
19.


Enter it again:xdslogs

You will then be prompted for
another password


the user’s
password to which the
createuser command is
executed under
.

21

Enter the postgres user’s password
that you established in step 5 of
section 6.2.2


Password:<postgres_user_passwor
d>

The xdslogs user will be
created.

22

Execute the following command:


createuser
-
U postgres
-
s bill

The createuser postgres
command

will execute and
prompt you for the postgres
user’s password.

23

Enter the postgres user’s password
that you established in step 5 of
section 6.2.2


Password:<postgres_user_passwor
d>

The user “bill” will be created.
This user exists in some of the
databa
ses from NIST. It is
anticipated that future releases
of the NIST XDS software will
remove this dependency.

24

Execute the following command to
The createdb postgres

CONNECT_
NIST
_
Manual

13

Release 2.4

3/18/10


Step

Action Input

Expected Result

create the registry database:


createdb
-
U postgres
-
O xdsoper
registry

command will be
executed.

25

Enter the postgres user’s password
that you established in step 5 of
section 6.2.2


Password:<postgres_user_passwor
d>

The registry database will be
created with the user xdsoper as
its owner.

26

Execute the following command to
create the
registry database:


createdb
-
U postgres adt

The createdb postgres
command will be executed.

27

Enter the postgres user’s password
that you established in step 5 of
section 6.2.2


Password:<postgres_user_passwor
d>

The adt database will be
created.

28

Execute the following command to
create the registry database:


createdb
-
U postgres
-
O logs log2

The createdb postgres
command will be executed.

29

Enter the postgres user’s password
that you established in step 5 of
section 6.2.2


Password:<
postgres_user_passwor
d>

The log2 database will be
created.

30

Initialize the registry database by
executing the following command:


pg_restore
-
U postgres
-
d registry
-
F
t init_data/xds/xds_init.tar

The postgres database restore
utility will begin executi
on and
prompt you for the postgres
user’s password.

31

Enter the postgres user’s password
that you established in step 5 of
section 6.2.2


Password:<postgres_user_passwor
d>

The registry database will now
be populated.

32

Initialize the adt database by
executing the following command:


pg_restore
-
U postgres
-
d adt
init_data/adt/adt.dump

The postgres database restore
utility will begin execution and
prompt you for the postgres
user’s password.

33

Enter the postgres user’s password
The adt database will now be

CONNECT_
NIST
_
Manual

14

Release 2.4

3/18/10


Step

Action Input

Expected Result

that you established i
n step 5 of
section 6.2.2


Password:<postgres_user_passwor
d>

populated.


6.2.4


Install
T
omcat
S
ervers

The two tomcat servers were already extracted as part of the instructions in section 6.1. This
section will create a user
environment variable that you will use to start the two versions of
tomcat and verify that they can be started correctly.

For an explanation of the two tomcat versions, please refer to the NIST XDS installation guide.

Step

Action Input

Expected Result

1

Create the “CATALINA_HOME” user
env楲onmen琠va物ab汥lu獩湧⁴he=
楮獴牵捴楯i猠sn⁴he⁰牥r楯i猠獥c瑩tn=
a猠s⁧u楤iⰠand⁩=楴ia汬礠獥琠the=
䍁CAi䥎f_䡏eb⁶a物ab汥lto㨠
=
=

y
xd獟獵ppo牴_b楮_O
y
瑯mca琱
=
qhe⁃=qAi䥎f_䡏eb⁵獥爠
env楲onmen琠va物ab汥li猠捲sa瑥dK
=
O
=
佰en=
a=new⁣=mmand⁷楮iow⁡nd=
en瑥爠rhe=景汬ow楮i⁣=mmandW
=
=
捤‥䍁qAi䥎f_䡏eb%
y
b楮
=
qhe⁣=mmand⁷楮io眠w牯浰r=
wi汬⁢e⁩=⁴he=

y
xd獟獵ppo牴_b楮_O
y
瑯mca琱
y
b楮id楲e捴o特K
=
P
=
p瑡牴⁴omca琱=by⁥xe捵瑩tg⁴he=
景汬ow楮i⁣=mmandW
=
=
獴s牴rpKbat
=
qhe⁴omca琱⁳e牶e爠w楬氠le=
獴s牴rd⁷楴iou琠any⁥牲o牳⸠rou=
捡n⁶e物fy⁴h楳⁢ypening⁡⁷eb=
b牯r獥爠rnd⁥n瑥物ng⁴he=
景汬ow楮i⁕剌=
=
=
h瑴pW⼯汯捡lho獴sVMUML
=
=
qhe⁴omca琠汯l=f楬e猠捡n⁡汳漠be=
u獥d=瑯⁶e物fy⁡⁳=捣es獦s氠獴l牴r=
qhey⁡牥r捡ted=
a琺
=
=

y
xd獟獵ppo牴_b楮_O
y
瑯mca

y
汯ls
=
Q
=
䍯Cy⁴he⁸a污l⹪K爠f楬e=晲fm⁴he⁺楰i
f楬e⁹ou=down汯lded⁩==獥捴楯n=P=
f牯mW
=

y
xd獟獵ppo牴_b楮_O
y
xa污l⹪Kr
=
=
瑯W
=
qhe⁸a污l⹪K爠f楬e⁩n捬畤ed⁩==瑨e=
z楰if楬e⁤own汯lded=f牯m⁴he=
䍏乎b䍔⁷eb⁳楴=⁩猠now⁩==
瑨e=景汬ow楮i⁤楲e捴c特W
=
=

y
xd獟獵ppo牴_b楮_O
y
瑯mca琲
y

CONNECT_
NIST
_
Manual

15

Release 2.4

3/18/10


Step

Action Input

Expected Result

C:
\
xds_support_bin_2
\
tomcat2
\
weba
pps
\
ebxmlrr
\
WEB
-
INF
\
lib

xalan.jar

webapps
\
ebxmlrr
\
WEB
-
INF
\
lib

5

Modify the “CATALINA_HOME” user
environment variable using the
instructions in the previous section
as a guide, an
d set its value to:


C:
\
xds_support_bin_2
\
tomcat2

The CATALINA_HOME user
environment variable is now set
to:


C:
\
xds_support_bin_2
\
tomcat2.

6

Open a new command window and
enter the following command:


cd %CATALINA_HOME%
\
bin

The command window prompt
will

be in the
C:
\
xds_support_bin_2
\
tomcat2
\
bin directory.

7

Start tomcat2 by executing the
following command:


startup.bat

The tomcat2 server will be
started without any errors. You
can verify this by opening a web
browser and entering the
following URL:


http://localhost:8080/


The tomcat log files can also be
used to verify a successful start.
They are located at:


C:
\
xds_support_bin_2
\
tomca
t2
\
logs

8

Stop both tomcat servers by closing
their respective command
windows.

Both tomcat servers will be
stopped. You can verify this by
opening a browser and hitting
the two URL values listed above
and receiving a failed to
connect message in return.


6.2.5


Install the XDS
S
erver
C
ode into
T
omcat

The precompiled NIST XD
S software can be found in the C:
\
xds_server_bin_1_0 directory as
extracted from the instructions in section 6.1. This section will install the precompiled software
into the appropriate tomcat version.

Step

Action Input

Expected Result

1

Copy the xds.aar file from:
C:
\
xds_server_bin_1_0


to:
C:
\
xds_support_bin_2
\
tomcat1
\
weba
A copy of the xds.aar file will be
located in the
C:
\
xds_support_bin_2
\
tomcat1
\
webapps
\
axis2
\
WEB
-
INF
\
services directory.


CONNECT_
NIST
_
Manual

16

Release 2.4

3/18/10


Step

Action Input

Expected Result

pps
\
axis2
\
WEB
-
INF
\
services

2

Copy the
xdsref.war file from:
c:
\
xds_server_bin_1_0


to:

C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps

A copy of the xdsref.war file will
be located in the
C:
\
xds_support_bin_2
\
tomcat1
\
webapps directory.

3

Copy the LogReader.war file from:
C:
\
xds_server_bin_1_0


To:

C:
\
x
ds_support_bin_2
\
tomcat1
\
weba
pps

A copy of the LogReader.war
file will be located in the
C:
\
xds_support_bin_2
\
tomcat1
\
webapps directory.

4

Copy the xdstools.war file from:
C:
\
xds_server_bin_1_0


to:

C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps

A copy of the
xdstools.war file
will be located in the
C:
\
xds_support_bin_2
\
tomcat1
\
webapps directory.

5

Ensure that the postgres database
server is running by either checking
with the Window Services utility or by
typing the following command at a
new command prompt:


psql
-
U postgres

The postgres command will attempt
to log you in after entering the
postgres user’s password.

The postgres database server
will be running.

6

Modify the CATALINA_HOME user
environment variable to a value of:


C:
\
xds_support_bin_2
\
tomcat1

The CATALINA_HOME user
environment variable will point
to
C:
\
xds_support_bin_2
\
tomcat1

7

Follow the rest of the steps outlined
in section 6.2.4 to verify that both
tomcat servers can be started
without error.

Both tomcat servers should
start without error
.


The tomcat log files can also be
used to verify a successful start.
They are located at:




C:
\
xds_support_bin_2
\
to
mcat1
\
logs



C:
\
xds_support_bin_2
\
to
mcat2
\
logs

8

Open a web browser and hit the
following URL:


The browser
should display an
image similar to the following
screen shot:


CONNECT_
NIST
_
Manual

17

Release 2.4

3/18/10


Step

Action Input

Expected Result

http://localhost:9080/xdstools/



9

Open a web browser and hit the
following URL:


http://localhost:8080/

The browser should display an
image similar to the following
screen shot:



10

Open a web browser and hit the
following URL:


http://localhost:9080/xdsref/

The browser should display an
image similar to the following
screen shot:



11

Open a web browser and hit the
following URL:


http://localhost:9080/LogReader/

The LogReader web application
reads data from the

log2
database which will be
initialized by the server the first
time there is something to log.
In the meantime, you will
receive some http 500 errors
and a page that looks similar to
the following screen shot:



CONNECT_
NIST
_
Manual

18

Release 2.4

3/18/10


Step

Action Input

Expected Result


As a quick reference, the NIST XDS start

order as noted from the NIST XDS installation guide
that you extracted in section 6.1 and will be located at “c:
\
xds_support_bin_2
\
install.pdf” is:



Start the postgres server



Start the tomcat2 server



Start the tomcat1 server



Check the log files to verify t
he two application servers started correctly.

6.2.6


Configure the
I
nstallation

The following steps will need to be performed to configure your installation of the NIST XDS
software. Some of the configuration steps are optional.

6.2.6.1

Change
t
he Physical

Location
where

Documents
a
re Stored
o
n
t
he NIST
XDS Repository

This process is necessary in order to store documents on your computer properly. By default,
the NIST software ships with a Unix
-
like reference to a user’s local directory that will not work
f
or windows.

Step

Action Input

Expected Result

1

Stop both tomcat servers by closing
their respective command windows.

Both tomcat servers will be
stopped.

2

Copy the xds.aar file from
C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
axis2
\
WEB
-
INF
\
services to a
temporary location with nothing else
in the directory (e.g.,
c:
\
temp
\
xds_aar).

A copy of the xds.aar file will be
in the empty folder.

3

Execute the following command:


jar
-
xf xds.aar

The xds.aar file will be
expanded in this directory.

4

Open the
xds.properties file in the
text editor of your choice.

The xds.properties file will be
opened in your favorite text
editor.

5

Change the repository_base_dir
property to
/xds_support_bin_2/tomcat1/webapp
s/ROOT/Repository/

The repository_base_dir
property will have a new valid
physical location on your
computer.


CONNECT_
NIST
_
Manual

19

Release 2.4

3/18/10


Step

Action Input

Expected Result


and save your changes.


Note: mai
ntain the forward slash file
-
directory notation


* Other xds configuration changes
may be made while you are here.
Some changes are referenced in this
document. For other changes,
please see the original NIST XDS
install
ation

guide located at
c:
\
xds_suppor
t_bin_2
\
install.pdf.

6

Execute the following command to
reconstruct the xds.aar file:


jar
-
cf xds.aar *


Note: you may have to type the text
of this command by
hand as a mere
cut
-
and
-
paste operation from this
document has been known to not
execute the command properly.

The xds.aar file will be
recreated with the modified
xds.properties file within.

7

Copy the modified xds.aar file back
to the following directory
:


C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
axis2
\
WEB
-
INF
\
services

The modified xds.aar file will
have replaced the previous file.

8

Create the following directory:


C:
\

xds_support_bin_2
\
tomcat1
\
webapp
s
\
ROOT
\
Repository

The directory where documents
will be
physically stored on your
computer will have been
created.

9

Restart both tomcat servers as
outlined in section 6.2.4 and 6.2.5 to
verify that both tomcat servers can
be started without error.

Both tomcat servers should
start without error.


The tomcat
log files can also be
used to verify a successful start.
They are located at:




C:
\
xds_support_bin_2
\
to
mcat1
\
logs



C:
\
xds_support_bin_2
\
to
mcat2
\
logs



CONNECT_
NIST
_
Manual

20

Release 2.4

3/18/10


6.2.6.2

Change the
M
etadata
C
odes that are
V
alidated by the NIST XDS Registry and
Repository

The NIST XDS
Registry and Repository software will validate certain metadata values using a
file called, “codes.xml”, located at

C:
\
xds_support_bin_2
\
tomcat1
\
webapps
\
xdsref
\
codes
\
codes.xml

Some of the codes used with NHIN have been included in a codes.xml file included

in the zip
file you downloaded in section 6. You may choose to use these codes in your NIST software
installation. If so, simply follow the steps below.

Step

Action Input

Expected Result

1

Rename the codes.xml file found at
the following location

C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
xdsref
\
codes
\
codes.xml

to

codes.xml.orig.

The original codes.xml file will
be renamed.

2

Copy the codes.xml file from:


C:
\
xds_support_bin_2
\
codes.xml


to:


C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
xdsref
\
codes
\
codes.xml

The codes.xml file from the zip
file downloaded from the
CONNECT web site will be in
the following location:


C:
\
xds_support_bin_2
\
tomcat1
\
webapps
\
xdsref
\
codes
\
codes.x
ml



As additional NHIN
codes or the needs of your organization change such that new codes need
to be added or existing codes need to be modified, the following steps outline how this may be
accomplished by using an example. The example will use the NHIN document class code
metad
ata item to illustrate where to go to modify this code should it ever need to change (e.g.,
the XNHIN
-
CONSENT class code may change to a real LOINC document class code at some
point in the future).

Step

Action Input

Expected Result

1

Open the following
file in a text editor
of your choice:


C:
\
xds_support_bin_2
\
tomcat1
\
weba
The codes.xml file will be open
in your text editor and will be
ready for your modifications.


CONNECT_
NIST
_
Manual

21

Release 2.4

3/18/10


Step

Action Input

Expected Result

pps
\
xdsref
\
codes
\
codes.xml

2

Locate the “classCode” metadata
item.



Your editor should
be on the
line that looks like the following:


<CodeType name="classCode"
classScheme="urn:uuid:41a588
7f
-
8865
-
4c09
-
adf7
-
e362475b143a">


Note: Document class codes
will be listed as sub
-
elements to
the classCode element
identified here.

3

Find the class co
de sub
-
element for
“XNHIN
-
CONSENT”. If there is no
such element, one can be created by
entering the following text within the
class code element (e.g., as the last
sub
-
element in the list):


<Code code="XNHIN
-
CONSENT"
display="XNHIN Consent CPP doc"
codingScheme="2.16.840.1.113883.
6.1"/>

You editor will display the line
containing the XNHIN
-
CONSENT class code.

4

Change the code, display, or coding
scheme attribute as appropriate to
your circumstance.


The following is a brief explanation of
the att
ributes:



Code


the actual document
class code as found in the
“nodeRepresentation”
attribute of the “Classification”
XDS metadata element for a
document.



Display


the display name of
the class code (e.g., XNHIN
Consent CPP doc) as found in
the “Name”
sub
-
element of
the “Classification” XDS
metadata element for a
document.



Coding Scheme


the coding
scheme of the class code
(e.g., LOINC, SNOMED, an
OID coded value representing
The code, display or coding
scheme value will be changed
to the values needed by your
organization.


CONNECT_
NIST
_
Manual

22

Release 2.4

3/18/10


Step

Action Input

Expected Result

a coding scheme, etc.) as
found in the “slot” sub
-
element named,
“codingSchem
e”, of the
“Classification” XDS metadata
element for a document.

5

Save the codes.xml document. Your
changes may be tested by
submitting a document to the
repository as discussed in the next
section.

The codes.xml document will be
saved.


6.2.6.3

Change the Assigning Authority
V
alue for
P
atients that will have
D
ocuments
S
tored in the
R
epository

Documents can only be stored in the NIST XDS Registry and
Repository for patients that have
a valid assigning authority as defined in the codes.xml file. The NIST registry has a mechanism
for assigning patient ids using an assigning authority; but that functionality is used more during
the IHE XDS Connect
-
a
-
thon
testing events, and will not be modified here. For more
information, check the original NIST XDS Registry and Repository installation guide located at
c:
\
xds_support_bin_2
\
install.pdf.

The following steps provide an example of modifying the patientId assig
ning authority value.
This value will need to match the other assigning authority properties found in your CONNECT
Full Binary Installation and Configuration Manual

(e.g.
,

adapter.properties file. See section
7.5
).

Step

Action Input

Expected Result

1

Op
en the following file in a text editor
of your choice:


C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
xdsref
\
codes
\
codes.xml

The codes.xml file will be open
in your text editor and will be
ready for your modifications.

2

Locate the “AssigningAuthority”
e汥浥l琮=
=
=
=
vou爠rd楴i爠獨ou汤⁢e=on⁴he=
汩ne⁴ha琠汯l歳⁳業楬a爠ro⁴he=
景汬ow楮iW
=
=
YA獳楧n楮iAu瑨o物瑹=
楤㴢iampXN⸳KS⸱⸴KN⸲NPST⸲M
MR⸳⸷Camp㭉p伢⼾
=
P
=
Modify the “id” attribute value to
ma瑣h⁴he⁏䥄fa獳楧n楮i⁡u瑨o物瑹=
de獩sedK
=
=
The OID portion of the “id”
a瑴物bute⁶a汵lf
=
瑨e⁡獳楧n楮i=
au瑨o物瑹⁥汥len琠w楬氠le=
捨anged=瑯⁹ou爠re獩sed⁶a汵lK
=

CONNECT_
NIST
_
Manual

23

Release 2.4

3/18/10


Step

Action Input

Expected Result

Note: make sure to leave the
"&
amp;” and “ISO” values. Just
change the OID value. This will
ensure that the
“XDSDocumentEntry.patientId”
metadata item for your document
submissions match on the assigning
authority and are in the HL7 format.

4

Save the codes.xml file. Your
changes may be tested by
submitting a document to the
repository as discussed in the next
section.

File will be saved.


6.2.6.4

Change the Document Re
pository Unique Id

You may need to modify the NIST XDS Repository software’s unique document repository
identifier value.

The following steps provide an example of modifying the document repository’s unique
identifier value. This value will need to match the other document repository unique id
properties found in your CONNECT installation.

Step

Action Input

Expected Result

1

Stop both tomcat servers by closing
their respective command windows.

Both tomcat servers will be
stopped.

2

Copy the xds.aar file from
C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
axis2
\
WEB
-
INF
\
services to a
temporary location with nothing else
in the
directory (e.g.,
c:
\
temp
\
xds_aar).

A copy of the xds.aar file will be
in the empty folder.

3

Execute the following command:


jar
-
xf xds.aar

The xds.aar file will be
expanded in this directory.

4

Open the xds.properties file in the
text editor of your c
hoice.

The xds.properties file will be
opened in your favorite text
editor.

5

Change the “repository_unique_id”
p牯re牴r⁴o⁹ou爠re獩sed⁏䥄⁶a汵l=
and⁳ave⁹ou爠捨ange献
=
=
⨠G瑨e爠rd猠捯nf楧u牡瑩on⁣=ange猠
may⁢e=made⁷h楬e⁹ou⁡牥rhe牥r=
pome⁣=ange猠sre=
牥晥牥r捥d⁩=⁴h楳i
do捵men琮⁆o爠r瑨e爠rhange猬s
qhe⁲=po獩瑯特_un楱ue_楤i
p牯re牴r⁷楬氠lave⁴he=de獩sed=
va汵lK
=

CONNECT_
NIST
_
Manual

24

Release 2.4

3/18/10


Step

Action Input

Expected Result

please see the original NIST XDS
installation guide located at
c:
\
xds_support_bin_2
\
install.pdf.

6

Execute the following command to
reconstruct
the xds.aar file:


jar

cf xds.aar *


Note: you may have to type the text
of this command by hand as a mere
cut
-
and
-
paste operation from this
document has been known to not
execute the command properly.

The xds.aar file will be
recreated with the modified

xds.properties file within.

7

Copy the modified xds.aar file back
to the following directory:


C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
axis2
\
WEB
-
INF
\
services

The modified xds.aar file will
have replaced the previous file.

8

Create the following directory:


C:
\

xds_support_bin_2
\
tomcat1
\
webapp
s
\
Root
\
Repository

The directory where documents
will be physically stored on your
computer will have been
created.

9

Restart both tomcat servers as
outlined in section 6.2.4 and 6.2.5 to
verify that both tomcat servers

can
be started without error.

Both tomcat servers should
start without error.


The tomcat log files can also be
used to verify a successful start.
They are located at:




C:
\
xds_support_bin_2
\
to
mcat1
\
logs



C:
\
xds_support_bin_2
\
to
mcat2
\
logs


6.2.6.5

Change t
he NIST XDS Registry and Repository
S
oftware to not
V
alidate
P
atient
I
ds

In accordance with the NIST software installation guide, the registry does not accept a real
XDS patient identity feed transaction, but uses an internal web page to allocate patient
ids for
validation. You may wish to turn off this validation for this release of CONNECT
(recommended). The following steps demonstrate how this is done.




CONNECT_
NIST
_
Manual

25

Release 2.4

3/18/10


Step

Action Input

Expected Result

1

Stop both tomcat servers by closing
their respective command w
indows.

Both tomcat servers will be
stopped.


2

Copy the xds.aar file from
C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
axis2
\
WEB
-
INF
\
services to a
temporary location with nothing else
in the directory (e.g.,
c:
\
temp
\
xds_aar).

A copy of the xds.aar file will be
in the empty folder.

3

Execute the following command:


jar
-
xf xds.aar

The xds.aar file will be
expanded in this directory.

4

Open the xds.properties file in the
text editor of your choice.

The xds.properties file will be
opened in your favorite text
ed
itor.

5

Change the
“validate_patient_id=true” property to
“validate_patient_id=false”.


* Other xds configuration changes
may be made while you are here.
Some changes are referenced in this
document. For other changes,
please see the original NIST XDS
install
ation

guide located at
c:
\
xds_support_bin_2
\
install.pdf.

The validate_patient_id property
will be re
-
assigned a value of
false so that patient id values
will not be validated using the
NIST software.

6

Execute the following command to
reconstruct t
he xds.aar file:


jar

cf xds.aar *


Note: you may have to type the text
of this command by hand as a mere
cut
-
and
-
paste operation from this
document has been known to not
execute the command properly.

The xds.aar file will be
recreated with the modified
xds.properties file within.

7

Copy the modified xds.aar file back
to the following directory:


C:
\
xds_support_bin_2
\
tomcat1
\
weba
pps
\
axis2
\
WEB
-
INF
\
services

The modified xds.aar file will
have replaced the previous file.

8

Create the following directory:


C:
\

xds_support_bin_2
\
tomcat1
\
webapp
s
\
Root
\
Repository


The directory where documents
will be physically stored on your
computer will have been
created.


CONNECT_
NIST
_
Manual

26

Release 2.4

3/18/10


Step

Action Input

Expected Result

9

Restart both tomcat servers as
outlined in section 6.2.4 and 6.2.5 to
verify that both tomcat servers

can
be started without error.

Both tomcat servers should
start without error.


The tomcat log files can also be
used to verify a successful start.
They are located at:




C:
\
xds_support_bin_2
\
to
mcat1
\
logs



C:
\
xds_support_bin_2
\
to
mcat2
\
logs


6.2.7


Test the
I
nstallation

Now that the NIST XDS software is installed and configured, you should test your installation.
Tests referenced in this document use the soapUI application to submit SOAP request
messages and receive SOAP response message to/from the NIST repo
sitory. NIST offers a
free test kit that can be used to help test your installation. Setup and use of this test kit is
beyond the scope of this document. The test kit can be downloaded at the following location:

http://ihexds.nist.gov:9080/XdsDocs/testkit/

After initially testing the NIST XDS software installation, you may choose to use the document
query and document retrieve tests from the SelfTestSuite as downloadable from the
CONNECT website.
Details of using that test suite are beyond the scope of this document.

The following steps outline some of the tests you may wish to execute.

6.2.7.1

Store a
T
est
D
ocument to the NIST XDS
R
epository


Step

Action Input

Expected Result

1

Copy the SOAP 1.1

store document request
message located in section 7.0 of this
document and paste it as a new file into your
text/xml editor of choice.

A new xml file will be created
with the store document request
message.

2

Locate the metadata entry for the patient id
by
searching for:


"289fb07d8a6f441^^^&amp;1.3.6.1.4.1.21367
.2005.3.7&amp;ISO"

Your editor should advance you
within your new document to the
patient id value on the left.

3

If you have changed your assigning authority
value as outlined in the NIST XDS
co
nfiguration section, then you need to
change the OID portion of the patient id to
match the assigning authority OID value
found in your codes.xml file. The assigning
The patient’s assigning authority
po牴ron=of⁴he=pa瑩en琠id⁳=ould=
ma瑣h⁴he⁡獳楧n楮i⁡u瑨o物瑹=
佉䐠found⁩n⁴he⁣=des⹸m氠l楬eK
=

CONNECT_
NIST
_
Manual

27

Release 2.4

3/18/10


Step

Action Input

Expected Result

authority portion of the patient id is highlighted
below.


"289fb07d8a6f441^^^&amp;
1.3.6.1
.4.1.21367
.2005.3.7
&amp;ISO"

4

Save the file for later reference.

The new file will be saved.

5

Open the soapUI.

The soapUI
application will start.

6

Click on the File|New Project menu item



The “New soapUI Project” menu
item will appear.

7

Enter the following values in the new project
dialog box appropriate to your environment.
For an example, refer to the screen shot
below:




Be sure to use the correct port as configured
in the previous section of this document.

The soapUI project name and
wsdl location match your
environment.

8

Click on the OK button.

The new project will be created
and soapUI will connect to the
w
sdl location entered in the last
step. The soapUI application will
then look similar to the following
screen shot
.



CONNECT_
NIST
_
Manual

28

Release 2.4

3/18/10


Step

Action Input

Expected Result


9

Expand the xdsrepositorybSOAP11Binding
node if it has not already been expanded.

The soapUI application will
display the following
sub
-
nodes:



getServiceName



ProvideAndRegisterDocu
mentSetRequest



RetrieveDocumentSetRe
quest



runContentValidationServ
ice

10

Expand the
ProvideAndRegisterDocumentSetRequest
node and double click on the sub
-
node
entitled, “Request 1”.



The soapUI application

will
generate a stub SOAP 1.1
request and open it for editing.




Note: feel free to maximize this
window for convenience.

11

Copy the contents of the store documents
request file you created in steps 1


4 above
into the “Request 1” window overwriting
the
soapUI generated request.


The new store documents
request message is copied into
the soapUI “Request 1” window.


CONNECT_
NIST
_
Manual

29

Release 2.4

3/18/10


Step

Action Input

Expected Result


12

Click on the arrow at the left
-
top most corner
of the “Request 1” window to submit the
request.



The request to store the test
document will be submitted to
the repository.

13

Check the response to the request. If
successful, you will see a response similar to
the following:


<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/
soap/envelope/">


<soapenv:Body>


<
rs:RegistryResponse
status="urn:oasis:names:tc:ebxml
-
regrep:ResponseStatusType:
Success
"
xmlns:rs="urn:oasis:names:tc:ebxml
-
regrep:xsd:rs:3.0">


</rs:RegistryResponse>


</soapenv:Body>

</soapenv:Envelope>

A successful response message
should be retur
ned similar to the
one shown to the left.



CONNECT_
NIST
_
Manual

30

Release 2.4

3/18/10


6.2.7.2

Query for a
T
est
D
ocument from the NIST XDS
R
epository


Step

Action Input

Expected Result

1

Copy the SOAP 1.1 query document request
message located in section 7 of this
document and paste it as a new file
into your
text/xml editor of choice.

A new xml file will be created
with the store document request
message
.

2

Locate the metadata entry for the patient id by
searching for:


"289fb07d8a6f441^^^&amp;1.3.6.1.4.1.21367
.2005.3.7&amp;ISO"

Your editor should a
dvance you
within your new document to the
patient id value on the left.

3


If you have change your assigning authority
value as outlined in the NIST XDS
configuration section, then you need to
change the OID portion of the patient id to
match the assigni
ng authority OID value
found in your codes.xml file. The assigning
authority portion of the patient id is highlighted
below.


"289fb07d8a6f441^^^&amp;
1.3.6.1.4.1.21367
.2005.3.7
&amp;ISO"

The patient’s assigning authority
portion of the patient id should
mat
ch the assigning authority
OID found in the codes.xml file.

4

Save the file for later reference.

The new file will be saved.

5

Open the soapUI and create a new project
similar to the one created for the store
document test using the following wsdl
location as a guide:


http://localhost:9080/axis2/services/xdsregistr
yb?wsdl


Note: make sure you use the same port that
you configured in the configuration section
above.

A new soapUI
project will be
created pointing to the NIST
registry web service.

6

Expand the xdsregistrybSOAP11Binding node
if it has not already been expanded.

The soapUI application will
display the following sub
-
nodes:



AdhocQueryRequest



getServiceName



runContentValidationServ
ice



SubmitObjectsRequest

7

Expand the AdhocQueryRequest node and
double click on the sub
-
node entitled,
“Request 1”.

The soapUI application will
generate a stub SOAP 1.1
request and open it for editing.

8

Copy the contents of the
query documents
request file you created in step 1


4 above
The new adhoc query request
message is copied into the

CONNECT_
NIST
_
Manual

31

Release 2.4

3/18/10


Step

Action Input

Expected Result

into the “Request 1” window overwriting the
soapUI generated request.



soapUI “Request 1” window.

9

Click on the arrow at the left
-
top mo
st corner
of the “Request 1” window to submit the
request.



The query request for the test
patient will be submitted to the
registry.

10

Check the response to the request. If
successful, you will see a response containing
the metadata associated with
the document
submitted previously.

A successful response message
should return the document
metadata submitted to the
repository earlier.


6.2.7.3

Retrieve a
T
est
D
ocument from the NIST XDS
R
epository


Step

Action Input

Expected Result

1

Copy the SOAP
1.1 retrieve document
request message located in section 7.0 of this
document and paste it as a new file into your
text/xml editor of choice.

A new xml file will be created
with the store document request
message.

2

Make sure that the DocumentUniqueId
element value contains the same document id
as the document previously stored and
queried (i.e., the
$XDSDocumentEntry.UniqueId metadata
The DocumentUniqueId element
should have a value of
“192.168.25.94.101”.


CONNECT_
NIST
_
Manual

32

Release 2.4

3/18/10


Step

Action Input

Expected Result

item). This value should “192.168.25.94.101”.

3

Make sure that the RepositoryUniqueId
element value contains the same repository id
as that configured previously.

The RepositoryUniqueId
element should have a value
consistent with the repository id
assigned in the configuration
section above.

4

Save

the file for later reference.

The new file will be saved.

5

Open the soapUI project used to store the test
document as previously created in this
document.


A new soapUI project that was
used to store a test document
should be open.

6

Expand the xdsregi
strybSOAP11Binding node
if it has not already been expanded.

The soapUI application will
display the following sub
-
nodes:



getServiceName



ProvideAndRegisterDocu
mentSetRequest



RetrieveDocumentSetRe
quest



runContentValidationServ
ice

7

Expand the
RetrieveDocumentSetRequest
node and double click on the sub
-
node
entitled, “Request 1”.

The soapUI application will
generate a stub SOAP 1.1
request and open it for editing.

8

Copy the contents of the retrieve document
request file you created in steps 1


4 above
into the “Request 1” window overwriting the
soapUI generated request.



The new retrieve document
request message is copied into
the soapUI “Request 1” window.

9

Click on the arrow at the left
-
top most corner
of the “Request 1” window to submit

the
request.


The retrieve document request
for the test patient will be
submitted to the registry.


CONNECT_
NIST
_
Manual

33

Release 2.4

3/18/10


Step

Action Input

Expected Result


10

Check the response to the request. If
successful, you will see a response containing
the base64 encoded representation of the
document submitted pr
eviously.

A successful response message
should return the base64
encode representation of the
document submitted to the
repository earlier.


6.2.8


Configure CONNECT to
C
onnect to the NIST XDS
R
epository

In order for the CONNECT software to communicate
with your newly installed NIST XDS
Repository server, you will need to modify the internalConnectionInfo.xml file on the
CONNECT gateway machine as referenced in the other CONNECT installation manuals. From
the CONNECT pre
-
configured installation manual, t
he location of this file is referenced by the

NHINC_PROPERTIES_DIR”

environment variable. This variable should have the following
value:

NHINC_PROPERTIES_DIR=$AS_HOME/domains/domain1/config/nhin

The steps to modify this file so that the CONNECT software
will use the NIST XDS Repository
server is as follows:

Step

Action Input

Expected Result

1

Open the internalConnectionInfo.xml file in
your preferred text editor on the CONNECT
gateway machine. The
internalConnectionInfo.xml file is located in
the
directory referenced by the
NHINC_PROPERTIES_DIR environment
variable as mentioned above.

The internalConnectionInfo.xml
file will be open in your preferred
text editor.

2

Search for the following text:


“adapterxdsbdocrepository”
=
vou爠r牥fe牲ed=瑥x琠
ed楴o爠r楬氠
汯捡瑥=瑨e⁳=a牣r⁴ex琠on⁴he=晴K
=
P
=
Modify the “<endpointURL> tag to point to
you爠rewly⁩=獴s汬ed⁎䥓q⁘䑓a牥ro獩瑯特=
a捣c牤楮g⁴o=瑨e=fo汬ow楮iW
=
=
Yendpoin瑕剌t
=
K
=
qhe⁥ndoin瑕剌t景爠瑨e=
adap瑥牸d獢do捲cpo獩so特⁩猠
upda瑥d⁴o⁰o楮琠瑯⁹ou爠rewly=
楮獴a汬ed⁎=p吠q䑓a牥ro獩瑯特=
獥牶e爮
=

CONNECT_
NIST
_
Manual

34

Release 2.4

3/18/10


Step

Action Input

Expected Result


Where the “<NISTXDS
-
IP>”text is the real IP
address of the machine with the
NIST XDS
repository.

4

Search for the following text:


“adapterxdsbdocregistry”

Your preferred text editor will
locate the search text
on the left.

5

Modify the “<endpointURL> tag to point to
your newly installed NIST XDS registry
according to the following:


<endpointURL>http://<NISTXDS
-
IP>:9080/axis2/services/xdsregistryb</endpoi
ntURL>


Where the “<NISTXDS
-
IP>”text is the real IP
address of the machine with the NIST XDS
registry.

The endointURL for the
adapterxdsbdocregistry is
updated to point to your newly
installed NIST XDS registry
server.

6

Save the file.

The internalConnectionInfo.xml
file is saved.

You will also need to ve
rify the assigning authority and the home community id property
settings in the CONNECT adapter.properties file.

The steps to verify the above properties in this file are as follows:

Step

Action Input

Expected Result

1

Open the adapter.properties file in

your
preferred text editor on the CONNECT
gateway and adapter machine. The
adapter.properties file is located in the
directory referenced by the
NHINC_PROPERTIES_DIR environment
variable as mentioned above.

The adapter.properties file will
be open in your

preferred text
editor.

2

Search for the following text:


“assigningAuthorityId”
=
vou爠r牥fe牲ed=瑥x琠ed楴o爠r楬氠
汯捡瑥=瑨e⁳=a牣r⁴ex琠on⁴he=晴K
=
P
=
se物fy⁴ha琠the=a獳楧n楮i⁡u瑨o物瑹a瑣te猠
瑨e=a獳楧n楮i⁡u瑨o物瑹t景und⁩=⁴he⁣=de献sm氠
f楬e=
牥晥牥n捥d⁩n⁳=捴con‶⸲KS⸳K
=
qhe⁡獳楧n楮iAutho物瑹䥤=
p牯re牴ra瑣tes⁴he⁡獳楧n楮i=
au瑨o物瑹⁰牯re牴r⁩=⁹ou爠rew汹=
installed NISTXDS server’s
捯de献sm氠f楬eK
=
Q
=
pea牣栠景爠瑨e=景汬ow楮i⁴ex琺
=
=
“XDSbHomeCommunityId”
=
vou爠r牥fe牲ed=瑥x琠ed楴o爠r楬氠
汯捡瑥=瑨e⁳=a牣r⁴ex琠on⁴he=晴K
=
R
=
se物fy⁴ha琠the=home⁣ommun楴i⁩=a瑣he猠
瑨e=ca氠lome⁣=mmun楴i⁩=⁰牯re牴r⁳=瑴楮i猠
qhe⁘䑓a䡯浥䍯mmun楴i䥤=
ma瑣he猠she=

CONNECT_
NIST
_
Manual

35

Release 2.4

3/18/10


Step

Action Input

Expected Result

found in the gateway.properties file in the
same directory as the adapter.properties file
you are verifying.


Note: This step is
applicable provided the
newly installed NIST software resides in the
same home community as the CONNECT
gateway.

localHomeCommunityId value
found in the gateway.properties
file.

6

Save the file if modifications were
made.

The adapter.properties file is
saved.


7.0


EXAMPLE TEST REQUEST

MESSAGES

This section will list some sample SOAP 1.1 request messages that you may modify and use
to test your NIST XDS Registry and Repository software.

7.1

Document Storage


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">


<soapenv:Header/>


<soapenv:Body>


<xdsb:ProvideAndRegisterDocumentSetRequest
xmlns:xdsb="urn:ihe:iti:xds
-
b:2007">


<l
cm:SubmitObjectsRequest
xmlns:lcm="urn:oasis:names:tc:ebxml
-
regrep:xsd:lcm:3.0">



<rim:RegistryObjectList
xmlns:rim="urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0">




<rim:ExtrinsicObject id="Document1"
mimeType="text/plain" objectType="urn:uuid:7edca82f
-
0
54d
-
47f2
-
a032
-
9b2a5b5186c1">





<rim:Slot name="creationTime">






<rim:ValueList>







<rim:Value>20051224</rim:Value>






</rim:ValueList>





</rim:Slot>





<rim:Slot name="languageCode">






<rim:ValueList>







<rim:Value>en
-
us</rim:Value>






</rim:ValueList>





</rim:Slot>





<rim:Slot name="serviceStartTime">


CONNECT_
NIST
_
Manual

36

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message






<rim:ValueList>







<rim:Value>200512240800</rim:Value>






</rim:ValueList>





</rim:Slot>





<rim:Slot name="serviceStopTime">






<rim:ValueList>







<rim:Value>200512
241100</rim:Value>






</rim:ValueList>





</rim:Slot>





<rim:Slot name="sourcePatientId">






<rim:ValueList>







<rim:Value>89765a87b^^^fj34r</rim:Value>






</rim:ValueList>





</rim:Slot>





<rim:Slot name="sourcePatientInfo">






<rim:Value
List>







<rim:Value>PID
-
3|pid1^^^domain</rim:Value>







<rim:Value>PID
-
5|Doe^John^^^</rim:Value>







<rim:Value>PID
-
7|19560527</rim:Value>







<rim:Value>PID
-
8|M</rim:Value>







<rim:Value>PID
-
11|100 Main
St^^Riverton^Ut^84065^USA</rim:Value>






</rim:ValueList>





</rim:Slot>





<rim:Name>






<rim:LocalizedString
value="Physical" />





</rim:Name>





<rim:Description />





<rim:Classification
classificationScheme="urn:uuid:93606bcf
-
9494
-
43ec
-
9b4e
-
a7748d1a838d"
classifiedObject="Document1" nodeRepresentation=""
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" id="id_1">






<rim:Slot name="authorPerson">







<rim:ValueList>








<rim:Value>^Smitty^Gerald^^^</rim:Value>







</rim:ValueList>






</rim:Slot>


CONNECT_
NIST
_
Manual

37

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message






<rim:Slot name="authorInstitution">







<rim:ValueList>








<rim:Value>Cleveland
Clinic</rim:Value>








<rim:Value>Parma
Community</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Slot name="a
uthorRole">







<rim:ValueList>








<rim:Value>Attending</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Slot name="authorSpecialty">







<rim:ValueList>








<rim:Value>Orthopedic</rim:Value>







</rim:ValueList>






</rim:Slot>





</rim:Classification>





<rim:Classification
classificationScheme="urn:uuid:93606bcf
-
9494
-
43ec
-
9b4e
-
a7748d1a838d" classifiedObject="Document1" nodeRepresentation=""
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification"
id="id_2">






<rim:Slot name="authorPerson">







<rim:ValueList>








<rim:Value>^Dopplemeyer^Sherry^^^</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Slot name="authorInstitution">







<rim:ValueList>








<rim:Value>Cleveland
Clinic</rim:Value>








<rim:Value>Berea
Community</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Slot name="authorRole">







<rim:ValueList>








<rim:Value>Primary
Surgon</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:
Slot name="authorSpecialty">


CONNECT_
NIST
_
Manual

38

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message







<rim:ValueList>








<rim:Value>Orthopedic</rim:Value>







</rim:ValueList>






</rim:Slot>





</rim:Classification>





<rim:Classification
classificationScheme="urn:uuid:41a5887f
-
8865
-
4c09
-
adf7
-
e362475b143a" class
ifiedObject="Document1"
nodeRepresentation="Communication"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" id="id_3">






<rim:Slot name="codingScheme">







<rim:ValueList>








<rim:Value>Connect
-
a
-
thon classCode
s</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Name>







<rim:LocalizedString
value="Education" />






</rim:Name>





</rim:Classification>





<rim:Classification
classificationScheme="urn:uuid:f4f85eac
-
e6cb
-
4883
-
b524
-
f2705394840f"
classifiedObject="Document1"
nodeRepresentation="1.3.6.1.4.1.21367.2006.7.103"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" id="id_4">






<rim:Slot name="codingScheme">







<rim:ValueList>








<rim:Value>Conn
ect
-
a
-
thon confidentialityCodes</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Name>







<rim:LocalizedString
value="Clinical
-
Staff" />






</rim:Name>





</rim:Classification>





<rim:Classification
classificationScheme="urn:uuid:a09d5
840
-
386c
-
46f2
-
b5ad
-
9c3699a4309d" classifiedObject="Document1"
nodeRepresentation="CDAR2/IHE 1.0"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" id="id_5">






<rim:Slot name="codingScheme">


CONNECT_
NIST
_
Manual

39

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message







<rim:ValueList>








<rim:Value>Connect
-
a
-
thon formatCodes</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Name>







<rim:LocalizedString
value="CDAR2/IHE 1.0" />






</rim:Name>





</rim:Classification>





<rim:Classification
classificationScheme="urn:uu
id:f33fb8ac
-
18af
-
42cc
-
ae0e
-
ed0b0bdb91e1" classifiedObject="Document1"
nodeRepresentation="Hospital Setting"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" id="id_6">






<rim:Slot name="codingScheme">







<rim:Valu
eList>








<rim:Value>Connect
-
a
-
thon healthcareFacilityTypeCodes</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Name>







<rim:LocalizedString
value="Hospital Setting" />






</rim:Name>





</rim:Classification>





<
rim:Classification
classificationScheme="urn:uuid:cccf5598
-
8b07
-
4b77
-
a05e
-
ae952c785ead" classifiedObject="Document1"
nodeRepresentation="General Medicine"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" id="id_7">






<rim:Slot name="codingScheme">







<rim:ValueList>








<rim:Value>Connect
-
a
-
thon practiceSettingCodes</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Name>







<rim:LocalizedString
value="General Medicine" />






</rim:Name>





</ri
m:Classification>





<rim:Classification
classificationScheme="urn:uuid:f0306f51
-
975f
-
434e
-
a61c
-
c59651d33983" classifiedObject="Document1"

CONNECT_
NIST
_
Manual

40

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message

nodeRepresentation="34108
-
1"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" i
d="id_8">






<rim:Slot name="codingScheme">







<rim:ValueList>








<rim:Value>LOINC</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Name>







<rim:LocalizedString
value="Outpatient Evaluation And Management" />






</rim:Name>





</rim:Classification>





<rim:ExternalIdentifier
identificationScheme="urn:uuid:58a6f841
-
87b3
-
4a3e
-
92fd
-
a8ffeff98427"
value="289fb07d8a6f441^^^&amp;1.3.6.1.4.1.21367.2005.3.7&amp;IS
O" objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:E
xternalIdentifier" id="id_9"
registryObject="Document1">






<rim:Name>







<rim:LocalizedString
value="XDSDocumentEntry.patientId" />






</rim:Name>





</rim:ExternalIdentifier>





<rim:ExternalIdentifier
identificationScheme="urn:uuid:2e82c1f6
-
a085
-
4c72
-
9da3
-
8640a32e42ab" value="192.168.25.94.101"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:ExternalIdentifier" id="id_10"
registryObject="Document1">






<rim:Name>







<rim:Local
izedString
value="XDSDocumentEntry.uniqueId" />






</rim:Name>





</rim:ExternalIdentifier>




</rim:ExtrinsicObject>








<rim:RegistryPackage id="SubmissionSet01"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:RegistryPackage"
>





<rim:Slot name="submissionTime">






<rim:ValueList>







<rim:Value>20041225235050</rim:Value>






</rim:ValueList>


CONNECT_
NIST
_
Manual

41

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message





</rim:Slot>





<rim:Name>






<rim:LocalizedString
value="Physical" />





</rim:Name>





<rim:Description>






<rim:Local
izedString value="Annual
physical" />





</rim:Description>





<rim:Classification
classificationScheme="urn:uuid:a7058bb9
-
b4e4
-
4307
-
ba5b
-
e3f0ab85e12d" classifiedObject="SubmissionSet01"
nodeRepresentation="" objectType="urn:oasis:names:tc:ebxml
-
regrep:O
bjectType:RegistryObject:Classification" id="id_20">






<rim:Slot name="authorPerson">







<rim:ValueList>








<rim:Value>^Dopplemeyer^Sherry^^^</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Slot name="authorInstitution">







<rim:
ValueList>








<rim:Value>Cleveland
Clinic</rim:Value>








<rim:Value>Berea
Community</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Slot name="authorRole">







<rim:ValueList>








<rim:Value>Primary
Surgon</rim:Value>







<
/rim:ValueList>






</rim:Slot>






<rim:Slot name="authorSpecialty">







<rim:ValueList>








<rim:Value>Orthopedic</rim:Value>







</rim:ValueList>






</rim:Slot>





</rim:Classification>





<rim:Classification
classificationScheme="urn:uuid:aa543740
-
bdda
-
424e
-
8c96
-
df4873be8500" classifiedObject="SubmissionSet01"
nodeRepresentation="History and Physical"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:Registr
yObject:Classification" id="id_21">


CONNECT_
NIST
_
Manual

42

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message






<rim:Slot name="codingScheme">







<rim:ValueList>








<rim:Value>Connect
-
a
-
thon contentTypeCodes</rim:Value>







</rim:ValueList>






</rim:Slot>






<rim:Name>







<rim:LocalizedString
value="History and Physical" />






</rim:Name>





</rim:Classification>





<rim:ExternalIdentifier
identificationScheme="urn:uuid:96fdda7c
-
d067
-
4183
-
912e
-
bf5ee74998a8" value
="192.168.25.94.104"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:ExternalIdentifier" id="id_22"
registryObject="SubmissionSet01">






<rim:Name>







<rim:LocalizedString
value="XDSSubmissionSet.uniqueId" />






</rim:Name>





</rim:ExternalIdentifier>





<rim:ExternalIdentifier
identificationScheme="urn:uuid:554ac39e
-
e3fe
-
47fe
-
b233
-
965d2a147832" value="129.6.58.92.1.1"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Ex
ternalIdentifier" id="id_23"
registryObject="SubmissionSet01">






<rim:Name>







<rim:LocalizedString
value="XDSSubmissionSet.sourceId" />






</rim:Name>





</rim:ExternalIdentifier>





<rim:ExternalIdentifier
id
entificationScheme="urn:uuid:6b5aea1a
-
874d
-
4603
-
a4bc
-
96a0a7b38446"
value="289fb07d8a6f441^^^&amp;1.3.6.1.4.1.21367.2005.3.7&amp;IS
O" objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:ExternalIdentifier" id="id_24"
registryObject="Submis
sionSet01">






<rim:Name>







<rim:LocalizedString
value="XDSSubmissionSet.patientId" />






</rim:Name>





</rim:ExternalIdentifier>




</rim:RegistryPackage>




<rim:Association

CONNECT_
NIST
_
Manual

43

Release 2.4

3/18/10


Sample
SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message

associationType="urn:o
asis:names:tc:ebxml
-
regrep:AssociationType:HasMember"
sourceObject="SubmissionSet01" targetObject="Document1"
id="ID_25276323_1" objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Association">





<rim:Slot name="SubmissionSetStatus">






<rim:ValueList>







<rim:Value>Original</rim:Value>






</rim:ValueList>





</rim:Slot>




</rim:Association>





<rim:Classification
classifiedObject="SubmissionSet01"
classificationNode="urn:uuid:a54d6aa5
-
d40d
-
43f9
-
88c
5
-
b4633d873bdd" id="ID_25276323_3"
objectType="urn:oasis:names:tc:ebxml
-
regrep:ObjectType:RegistryObject:Classification" />



</rim:RegistryObjectList>


</lcm:SubmitObjectsRequest>


<xdsb:Document
id="Document1">VGhpcyBpcyBteSBkb2N1bWVudC4KCkl0IGlzIGdyZ
WF0
IQoK</xdsb:Document>



</xdsb:ProvideAndRegisterDocumentSetRequest>



</soapenv:Body>

</soapenv:Envelope>


7.2

Document Query


Sample SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ser="http://serviceclasses.ws.registry.nist.gov">


<soapenv:Header/>


<soapenv:Body>



<query:AdhocQueryRequest
xmlns:xsi="http://www.w3.org/2001/XMLSchema
-
instance"


xm
lns:query="urn:oasis:names:tc:ebxml
-
regrep:xsd:query:3.0"


xmlns="urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0"


CONNECT_
NIST
_
Manual

44

Release 2.4

3/18/10


Sample SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message


xmlns:rs="urn:oasis:names:tc:ebxml
-
regrep:xsd:rs:3.0">


<query:ResponseOption returnCom
posedObjects="true"
returnType="LeafClass"/>


<AdhocQuery id="urn:uuid:14d4debf
-
8f97
-
4251
-
9a74
-
a90016b0af0d">


<Slot name="$XDSDocumentEntryPatientId">


<ValueList>









<Value>'289fb0
7d8a6f441^^^&amp;1.3.6.1.4.1.21367.2005.3.7&
amp;ISO'</Value>


</ValueList>


</Slot>


<Slot name="$XDSDocumentEntryStatus">


<ValueList>



<Value>('urn:oasis:names:tc:ebxml
-
regrep:StatusType:Approved')</Value>


</ValueList>


</Slot>


</AdhocQuery>


</query:AdhocQueryRequest>




</soapenv:Body>

</
soapenv:Envelope>


7.3

Document Retrieval


Sample SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ser="http://serviceclasses.ws.registry.nist.gov">


<soapenv:Header/>


<soapenv:Body>



<RetrieveDocumentSetRequest xmlns="urn:ihe:iti:xds
-
b:2007"


xmlns:xsi="http://www.w3.org/2001/XMLSchema
-
instance"


xsi:schemaLocation="urn:ihe:iti:xds
-
b:2007
file:/Users/bill/ihe/Frameworks/ITI
-
4/XDS.b/schema/IHE/XDS.b_DocumentRepository.xsd">


<DocumentRequest>


<RepositoryUniqueId>1.19.6.24.109.42.1.1</RepositoryUniqueId>


<DocumentUniqueId>192.1
68.25.94.101</DocumentUniqueId>


</DocumentRequest>

</RetrieveDocumentSetRequest>


CONNECT_
NIST
_
Manual

45

Release 2.4

3/18/10


Sample SOAP 1.1 ProvideAndRegisterDocumentSet Request
Message




</soapenv:Body>

</soapenv:Envelope>


8.0


USEFUL LINKS

http://ihexds.nist.gov/

-

the main NIST XDS web site

http://ihexds.nist.gov:9080/XdsDocs/testkit/

-

NIST XDS test kit

http://ihexds.nist.gov:9080/XdsDocs

-

Other NIST downloads

http://ihewiki.wustl.edu/wiki/index.php/XDS_Test_Kit_2007
-
2008_Test_Descriptions

-

For use
with the XDS test kit.



CONNECT_
NIST
_
Manual

46

Release 2.4

3/18/10


9.0


ACRONYMS


CA

Certificate Authority or Composite Application
depending on

the context.

CAC

Common Access Card

CD

Compact Disk

CDC

Centers for Disease Control & Prevention

CMS

Centers for Medicare & Medicaid Services

DAT

Digital Audio Tape

DOD

Department of Defense

DURSA

Data Use and Reciprocal Support Agreement

DVD

Digital Video Disc

EHR

Electronic Health Record

EMR

Electronic Medical Record

ESB

Enterprise Service Bus

FHA

Federal Health Architecture

GB

Gigabyte

HDD

Hard Disk Drive

HITSP

Healthcare Information Technology Standards
Panel

IDE

Integrated Drive
Electronics

IHS

Indian Health Services

IPv6

Internet Protocol Version 6

MB

Megabyte

MPI

Master Patient Index

NCI

National Cancer Institute

NDMS

National Disaster Medical System

NHIE

NHIN Health Information Exchange

NHIN

Nationwide Health
Information Network

NIST

National Institute of Standards and Technology

OID

Object Identifier or Home Community ID

ONC

Office of the National Coordinator

OS

Operating System


CONNECT_
NIST
_
Manual

47

Release 2.4

3/18/10


QA

Quality Assurance

RAID

Redundant Arr
ay of Inexpensive Disks

RAM

Random Access Memory

SCSI

Small Computer System Interface

SDK

Software Development Kit

SSA

Social Security Administration

SSL

Secure Sockets Layer

TBD

To Be Determined

USB

Universal Serial Bus

VA

Department of Veterans
Affairs

XDS

Cross Document Sharing