1.0 Introduction

1.1 Service Collaboration Overview and Scope

The Administrative Transport to Health Plan Service Collaboration provides the transport mechanism for conducting administrative transactions with health plans. This Service Collaboration utilizes:

HITSP/T17 Secure Communications Channel as a pre-condition

HITSP/SC109 Security Audit Service Collaboration

HITSP/SC108 Access Control Service Collaboration

For more information about the underlying capabilities, pre-conditions, post-conditions, data flows and other detailed information, please refer to the constructs that are composed by this Service Collaboration.

The Service Collaboration document illustrates one internal view diagram and sequence table for each service interface. The diagrams are descriptive and the sequences are not mandatory. They may be affected by policy, chosen architecture, and implementation details. Conformance is measured against the underlying constructs.

1.2 Service Collaboration Invocation

Table 1-1 Service Collaboration Transactions and Data

Service Collaboration

Service Collaboration description

Interface

HITSP/SC114

Provides the ability to request an administrative transport transaction to a Health Plan.

Request Administrative Transport to Health Plan

HITSP/SC114

Provides the ability to respond to a request for administrative transport transaction to health plan.

Respond to Administrative Request to Health Plan

1.3 External View (i.e.,black box diagram)

Figure 1-1 Administrative Transport to Health Plan External View Diagram

Unified Modeling Language (UML) diagram representing Administrative Transport to Health Plan External View

1.3.1 Service Collaboration Source Constructs

Table 1-2 List of Constructs

Construct

HITSP/SC108 - Access Control Service Collaboration

HITSP/SC109 - Security Audit Collaboration

HITSP/T17 - Secured Communication Channel

HITSP/T85 - Administrative Transport to Health Plan

1.4 Internal View Diagram with Sequencing (i.e., white box diagram)

There is one example diagram included for each service interface. The diagrams are descriptive and the sequences are not mandatory. They may be affected by policy, chosen architecture, and implementation details. Conformance is measured against the underlying constructs.

1.4.1 Interface: Request Administrative Transport to Health Plan Internal View

Figure 1-2 Request Administrative Transport to Health Plan Internal View

UML diagram representing Request Administrative Transport to Health Plan Interntal View

1.4.1.1 Sequence Details

Table 1-3 Request Administrative Transport to Health Plan Pre-conditions

Pre-condition

Uses SC, T, TP or C

Interface

Purpose

None

Table 1-4 Request Administrative Transport to Health Plan Sequence of Constructs

Step Number

Uses SC, T, TP or C

Interface

Purpose

1

HITSP/SC108 - Access Control

Request Access Control Decision

If required by organizational and mutual agreed upon policies, perform access controls to ensure that the payload in the request can be shared with administrative server

2

HITSP/T17 - Secured Communication Channel

Secure Node

A secure communications channel must be open in order to protect the confidentiality, authenticity and integrity of the information being transmitted

3

HITSP/T85 - Administrative Transport to Health Plan

Administrative Client

Administrative client initiates a request and receives a response from Administrative Server

4

HITSP/SC109 - Security Audit

Send Security Audit Event

Send an audit event to the audit record repository

Table 1-5 Request Administrative Transport to Health Plan Post-conditions

Post-condition

Uses SC, T, TP or C

Interface

Purpose

None

1.4.2 interface: Respond to Administrative Request to Health Plan

Figure 1-3 Respond to Administrative Request to Health Plan Internal View

UML diagram representing Respond to Administrative Request to Health Plan Internal View

1.4.2.1 Sequence Details

Table 1-6 Respond Administrative Transport to Health Plan Pre-conditions

Pre-condition

Uses SC, T, TP or C

Interface

Purpose

None

Table 1-7 Respond Administrative Transport to Health Plan Sequence of Constructs

Step Number

Uses SC, T, TP or C

Interface

Purpose

1

HITSP/ T17 - Secure Communications Channel

Secure Node

A secure communications channel is open in order to protect the confidentiality, authenticity and integrity of the information being transmitted

2

HITSP/T85 - Administrative Transport to Health Plan

Administrative Server

Administrative server receives a request from the Administrative Client

3

HITSP/SC108 - Access Control

Request Access Control Decision

If required by organizational and mutual agreed upon policies, perform access controls to ensure whether the request is authorized to be processed

4

n/a (Loopback)

Internal Processing

Process the request from the administrative client

5

HITSP/T85 - Administrative Transport to Health Plan

Administrative Server

The administrative server returns the response to the administrative client

6

HITSP/SC109 - Security Audit

Send Security Audit Event

Send an audit event to the audit record repository

Table 1-8 Respond Administrative Transport to Health Plan Post-conditions

Post-condition

Uses SC, T, TP or C

Interface

Purpose

None