Testing Readiness Checklist

pleasantrollΑσφάλεια

16 Φεβ 2014 (πριν από 3 χρόνια και 4 μήνες)

127 εμφανίσεις


eHealth Exchange

Page
1

of
3

Testi
ng Readiness Checklist (Rev.7/2
5
/13)


Testing
Readiness Checklist


(Rev.
7/
2
5
/2013)


Dear Applicant,


Thank you for your continued interest in onboarding to the eHealth Exchange.


After an organization has
been approved as
eligible to participate in the eHealth Exchange by the Coordinating Committee
, t
he
next step in the onboarding process is to prepare for and move to begin the testing process.


As part of
this process, we are asking all Applicants to complete the following

Test
ing

Readiness Checklist to help
us determine your readiness and timing to begin testing.


You can

e
-
mail the completed checklist to
admin@healthewayinc.org
.


Please note that the most significant step yo
ur organization can take to reduce the amount of calendar
time to complete testing is to prepare in advance and to have all key staff members engaged during the
testing process.


TEST
ING

READINESS CHECKLIST


Test Environment & Testing POC:
Please verify
the following information and update if necessary


1)

Applicant Name:

2)

System Under Test (Please identify which underlying systems, such as HIE or EHR system and/or
gateway you w
ill test and use in production.
Include

the system components that are relevant
t
o validation, including those components used to create or modify messages in accordance
with the Performance and Service Specifications, as well as generating the clinical
documentation that is exchanged)

3)

Version(s):

4)

Version of the eHealth Exchange
Specifications (formerly NwHIN specifications) that your
system supports:

-

Version 2010 (v1); or

-

Version 2011 (v2); or

-

Both 2010 and 2011

5)

Target Go
-
Live Date:

6)

Primary Testing Point of Contact

Contact Name:

Contact Title:

Contact Phone Number:

Contact E
-
mail
:

7)

Secondary Testing Point of Contact

Contact Name:

Contact Title:

Contact Phone Number:

Contact E
-
mail:




eHealth Exchange

Page
2

of
3

Testi
ng Readiness Checklist (Rev.7/2
5
/13)


Exchange Readiness

8)

Does the test environment mirror the production environment to the extent that any
differences between your production and test en
vironments, including in such areas as physical
deployment and network configuration, will not result in differences in your standards
conformance or the structure of the clinical content you produce?

a.

For example, the test environment should be identical
to the production environment,
as follows
:



Software and hardware and product versions (but at a reduced capacity)



Physical deployment topology



IT configuration (except for IP addresses, server names, etc.)



Firewall rules, patches, antivirus, and other
security configuration



Software and hardware configuration (other than for IP addresses, server names,
etc.)

b.

The test environment does not have to be identical to the production environment
,
for
the following:



The capacity of the testing environment (i.e.
response times) may be significantly
lower than the production environment



Port numbers



Hostnames



The test environment must use a “test” x.509 certificate and the production
environment must use a “production” x.509 certificate



The test environment must u
se synthetic patient data (PHI is not permitted for
testing purposes)


9)

Are your test systems generally on
-
line 24/7; or, are they down for long periods on a regular
basis?

10)

If you are using a gateway product, such as CONNECT, have all adapters been develop
ed and
implemented with the gateway?



11)

Has end user access been set up in the system in order to execute the tests?

12)

Is your test environment configured to allow end users to initiate messages during the testing
process by performing the application workfl
ows intended for use in production? (Please note:
using a simulate mechanism such as SOAP UI or sample GUIs is not permitted)


13)

Are all relevant services needed by the system running?

14)

Are your endpoints publicly visible (i.e. published to DNS)?

15)

Does your
network/firewall configuration allow:

a)

External traffic to reach your gateway?

b)

Your system to access external testing end
-
points?

16)

Is your system able to communicate with an UDDI service registry to discover partner end
-
points?


17)

Validate whether your system
is operational to exchange:

a)

Have you implemented a system that was previously validated for compliance with
eHealth Exchange specifications under the prior onboarding process supported by
ONC?



b)

Have you completed any testing in preparation for the eHealth

Exchange testing
process?


If so, please describe how?





eHealth Exchange

Page
3

of
3

Testi
ng Readiness Checklist (Rev.7/2
5
/13)


For example, have you performed a self
-
test (where your system initiates and
responds to messages), peer
-
to
-
peer testing against another testing
environment or testing services using a NIST
validator tool, etc.)?

18)

Do you have technical staff engaged:

a)

Who can install your x.509 certificate in the testing environment?

b)

Who can install test data into your testing environment?

c)

To analyze web services/SOAP issues, security issues, IT issues, and con
tent issues?

d)

Who have the ability to retrieve, edit, and submit log files for your gateway and/or
product?

19)

Please indicate the date that you will have each of the above steps completed and thus be ready
to begin testing:


Content Readiness

20)

Please indicate
which of the following documents you plan to support in production:

(Select
one or more)

a)

HITSP C
-
32 (Based upon the standards required for Stage 1 Meaningful Use (2011
Edition)



b)

Bridge C
-
32 (
http://www.healthewayinc.org/index.php/in
-
the
-
news/44
-
exchange
-
specifications
-
manifest
)

c)

Consolidated CDA (C
-
CDA)
-

Based upon the standards required for Stage 2 Meaningful
Use (2014 Edition)

d)

Other:

21)

Has the system you

will use in production for your eHealth Exchange connection been certified
for either Stage 1 or Stage 2 Meaningful Use?


If so, please specify.

22)

If your system has not been certified for Stage 1 or Stage 2 meaningful use, have you conducted
any testing in

preparation for the eHealth Exchange content testing process (e.g. executing tests
against the NIST content test tools, etc.)?