Business Views
Class Diagram 2. Register EHRi Application

Description

This model view is intended to clarify the information necessary to recognize specific POS and other applications that interface with or through the EHRi.

Key characteristics (attributes): Id, Interaction Artifact Id, Profile Ids, Template Ids, Effective Date/Time.

Rationale

Applications intending to use the EHRi capabilities must be registered along with their communication and application capabilities to support EHR transactions.

Implementation Considerations

Business Processes and accompanying data stores must be created to operationalize the registration and configuration processes. The ability to test the capability expressed in Implementation Profiles is also expected.

Source Models

HL7 V3 Conformance Work-in-Progress

Privacy Security Architecture

EHRi Business Arrangement Delivery Organization Pos System Organisation Authorized Application Communication And Interface Capabilities Implementation Profile Technical and Information Standards Conformant Application Roles Constrained interactions EHRi Device Delivery Site Place Registers Registers Authorizes Authorizes Has Subject Has Subject Can Perform Can Perform Played By Played By Located At Located At Played By Played By Specified As Specified As Constrains Constrains Constrains Constrains Documenting Documenting Includes Includes Geo-located At Geo-located At Agent For Agent For
Get SVG Format

General Info
Name 2. Register EHRi Application
Type Class Diagram