Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The NwHIN Administrative Distribution (AD) Web Service is intended to provide a mechanism for NHIEs to exchange non-patient specific data using a "push" mechanism. The Administrative Distribution transaction is a one way transaction, meaning there is no application-level response.
The AD message, also called the Send Alert Message Request, is a collection of metadata and documents or structured XML data transferred between a Message Sender and a Message Receiver.

for case 404 or 500 error, server.log must be verified.

Overview

The Administrative Distribution (AD) service is verify by the Audit-record, that a service request had been made and audit. The test cases covers different type of data-set, that can be send by the web service (AD).

Test Detail

Administrative Distribution (Passthrough) run with JMX script configuration without application server restart.

  • Clear the audit-log

  • Send the AD Request

  • Verify the audit-log

Admin-Distribution-Passthrough

NHINC Proxy Request with a Binary Doc

  1. Clear audit table

  2. Set User ID

  3. SOAP: NHINC Request (binary doc)

  4. Delay 60,000 milliseconds (1 minute)

  5. Verify audit events

NHINC Proxy Request with XML data

  1. Clear audit table

  2. Set User ID

  3. SOAP: NHINC Request (XML Data)

  4. Delay 60,000 milliseconds (1 minute)

  5. Verify audit events

NHINC Proxy Request with multiple documents (Binary and XML)

  1. Clear audit table

  2. Set User ID

  3. SOAP: NHINC Request (binary and xml)

  4. Delay 60,000 milliseconds (1 minute)

  5. Verify audit events

NHINC Proxy Request with multiple documents (multiple content objects)

  1. Clear audit table

  2. Set User ID

  3. SOAP: NHINC Request (multiple content objects)

  4. Delay 30,000 milliseconds (30 seconds)

  5. Verify audit events

NHINC Proxy Request without a Content Object

  1. Clear audit table

  2. Set User ID

  3. SOAP: NHINC Request (without content object)

  4. Delay 30,000 milliseconds (30 seconds)

  5. Verify audit events

NHINC Proxy Request with an empty Content Object

  1. Clear audit table

  2. Set User ID

  3. SOAP: NHINC Request (empty content object)

  4. Delay 60,000 milliseconds (1 minutes)

  5. Verify audit events

NHINC Proxy Request - 404 or 500 error

Requires manual verification of the server.log for 404 or 500 error (badURL-endpoint).

  1. Modify Endpoint (causing 404 or 500 error)

  2. SOAP: NHINC Request

  • No labels