1.0 Introduction

1.1 Service Collaboration Overview and Scope

Emergency Message Distribution performs a multicast notification to specifically identified populations, such as emergency departments. This Service Collaboration combines these HITSP specifications:

HITSP/SC108 Access Control

HITSP/SC109 Security Audit

HITSP/T17 Secured Communication Channel

HITSP/T63 Emergency Message Distribution Element

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	Interface Optionality [1]
HITSP/SC116	Multicast notification to specifically identified populations	Send Emergency Message Distribution Element	R
HITSP/SC116	Multicast notification to specifically identified populations	Receive Emergency Message Distribution Element	R

1.3 External View (i.e.,black 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.

Figure 1-1 Emergency Message Distribution External View diagram

1.3.1 Service Collaboration Source Constructs

Table 1-2 List of Constructs

Construct
HITSP/SC108 - Access Control
HITSP/SC109 - Security Audit
HITSP/T17 - Secured Communication Channel
HISP/T63 - Emergency Message Distribution Element

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

1.4.1 Interface: Send Emergency Message Distribution Element

Figure 1-2 Send Alert Internal View

UML diagram representing Send Alert Internal View

1.4.1.1 Sequence Details

Table 1-3 Send Emergency Message Distribution Element Pre-conditions

Pre-condition	Uses SC, T, TP or C	Interface	Purpose
None

Table 1-4 Send Emergency Message Distribution Element Sequence of Constructs

Step Number	Uses SC, T, TP or C	Interface	Purpose
1	HITSP/SC108 - Access Control	Request Access Control Decision	To obtain permission to send the message
2	HITSP/T17 - Secured Communication Channel	Node	To establish a secure path for sending the message
3	HITSP/T63 - Emergency Message Distribution Element	Alert Message Transmitter	To send the message
4	HITSP/SC109 - Security Audit	Send Security Audit Event	To record the message-sending event

Table 1-5 Send Emergency Message Distribution Element Post-conditions

Post-condition	Uses SC, T, TP or C	Interface	Purpose
None

1.4.2 Interface: Receive Emergency Message Distribution Element

Figure 1-3 Receive Emergency Message Distribution Element Internal View

UML diagram representing Receive Emergency Message Distribution Elelment Internal View

1.4.2.1 Sequence Details

Table 1-6 Receive Emergency Message Distribution Element Pre-conditions

Pre-condition	Uses SC, T, TP or C	Interface	Purpose
None

Table 1-7 Receive Emergency Message Distribution Element Sequence of Constructs

Step Number	Uses SC, T, TP or C	Interface	Purpose
1	HITSP/T17 - Secured Communication Channel	Node	To establish a secure path for receiving the message
2	HITSP/T63 - Emergency Message Distribution Element	Alert Message Receiver	To receive the message
3	HITSP/SC108 - Access Control	Request Access Control Decision	To assure permission to receive the message from the sending system
4	HITSP/SC109 - Security Audit	Send Security Audit Event	To record the message has been received

Table 1-8 Receive Emergency Message Distribution Element Post-conditions

Post-condition	Uses SC, T, TP or C	Interface	Purpose
None

	Return to detail page at www.hitsp.org	HITSP/SC116
	Prev TOC Next