PD 6610:1997

Foreword
Introduction
1 Scope
2 References
3 Definitions and acronyms
    3.1 Definitions
    3.2 Acronyms
4 Summary of the overall activities in the context of
    standard healthcare EDI message development
    4.1 The context and purpose of the message development
          activity
    4.2 The overall standard message development process
          4.2.1 Identify healthcare messaging need
          4.2.2 The message development approach
          4.2.3 Prepare message for implementation
          4.2.4 Change control
          4.2.5 Electronic Data Interchange Agreements
5 Message development activities: detailed description
    5.1 Scope specification
          5.1.1 Introduction
          5.1.2 What, why
          5.1.3 Process overview
          5.1.4 When
          5.1.5 Specific guidelines
          5.1.6 Scope Specification: summary
          5.1.7 Scope Specification: example
    5.2 User requirements and scenarios
          5.2.1 Introduction
          5.2.2 What, why
          5.2.3 Process overview
          5.2.4 When
          5.2.5 How to achieve quality
          5.2.6 User requirements and scenarios: summary
          5.2.7 Scenarios: example
    5.3 Communication roles and supported services
          5.3.1 Introduction
          5.3.2 What, why
          5.3.3 Process overview
          5.3.4 When
          5.3.5 Representation
          5.3.6 Quality requirements
          5.3.7 Communication roles & supported services:
                  summary
          5.3.8 Example
    5.4 Build Domain Information Model
          5.4.1 Introduction
          5.4.2 What, why
          5.4.3 When
          5.4.4 Process summary
          5.4.5 DIM: identify and define classes
          5.4.6 DIM: identify and define relationships
                  between classes
          5.4.7 DIM: define attribute layer
          5.4.8 DIM: identify subjects
          5.4.9 DIM: list of components
          5.4.10 DIM: Quality requirements
          5.4.11 Build domain information model: summary
          5.4.12 Example
    5.5 General Message Descriptions
          5.5.1 Introduction
          5.5.2 What, why
          5.5.3 When
          5.5.4 Process details
          5.5.5 GMD: list of components
          5.5.6 General Message Description: summary
          5.5.7 Example
    5.6 Mapping GMDs to hierarchical GMDs
          5.6.1 Why hierarchical GMDs are needed
          5.6.2 Hierarchical GMD: what
          5.6.3 General approach
          5.6.4 Representation
          5.6.5 Process details
          5.6.6 Activity summary
    5.7 Development of Implementable Message Specifications
          (IMS)
          5.7.1 What
          5.7.2 General requirements (correspondence between
                  GMD and IMS)
          5.7.3 EDIFACT IMS
          5.7.4 ASN.1 Implementable Message Specification
          5.7.5 Example of an EDIFACT IMS specification
Annex A Framework for Healthcare Communications and
          Messages
      A.1 Healthcare EDI applications
      A.2 Framework model
          A.2.1 Healthcare EDI services
          A.2.2 Information and communication Technology
          A.2.3 Organisational aspects
      A.3 Requirements for Standards for Healthcare
          Communications and Messages
          A.3.1 Introduction
          A.3.2 Categories of standards
Annex B Message development process management issues
      B.1 Iteration
      B.2 Project Management activities
      B.3 Quality assurance activities
      B.4 Project organisation
          B.4.1 Core team
          B.4.2 Organising an extended team
          B.4.3 Liaising with advisory/consultative groups
Annex C Attribute data type
      C.1 Overview
      C.2 String
      C.3 Calendar date
      C.4 Time of calendar date
      C.5 Boolean
      C.6 Integer
      C.7 Real
      C.8 Coded value
      C.9 Coded value or string
      C.10Coded value and string
      C.11List of coded values
      C.12List of coded values or string
      C.13List of coded values and string
      C.14Coded value without code meaning
      C.15Attribute group
      C.16Common attribute group
      C.17Data type assignment decision table
Annex D Mapping an OO-GMD into a hierarchical GMD: transform-
          ation tools
      D.1 Transformation using inference througgh derivation
          D.1.1 Introduction
          D.1.2 Activity details
          D.1.3 Building the Semantic Graph
      D.2 Transformation using direct inference
          D.2.1 Basic Mapping Rules
          D.2.2 Understanding relations through their
                  constraints
          D.2.3 Data Structure Mapping in Detail
          D.2.4 Hierarchical transformation versus
                  hierarchical building
          D.2.5 Hierarchy and the trees
          D.2.6 Example
Annex E Moving to implementation
      E.1 GMD profiles
          E.1.1 Introduction
          E.1.2 What
          E.1.3 Where used
          E.1.4 When
          E.1.5 Who
          E.1.6 Representation
          E.1.7 Notes
          E.1.8 GMD components by message profile
      E.2 IMS profiles
          E.2.1 Development of notations
          E.2.2 Cardinalities
          E.2.3 Presence/absence
          E.2.4 Dependencies
      E.3 Registration mechanisms for profiles
          E.3.1 Pre-emptive
          E.3.2 Historic
          E.3.3 Registration of combined GMD/IMS profiles
      E.4 Communication roles in the context of EDI systems
          implementation
Annex F Method in the context of tightly coupled systems
Annex G Paradigm annex on how to read the models
      G.1 Model components
                Subjects
                Classes, class-&-objects
                Types of Relationships
      G.2 Symbols
                Notes
                Warnings
      G.3 Hierarchical GMDs
Annex H Executive Summary

Defines a method of developing European Standard message specifications for electronic exchange of structured character-based information, between autonomous computer systems within and between organisations for healthcare purposes. Also defines the activities of the message development process, together with the structure and components of resulting deliverables.

The scope of this CEN report is to specify a method for the development of European Standard message specifications for the electronic exchange of structured character-based information, between autonomous computer systems within and between organisations, for purposes related to healthcare. Such message standards are essential if healthcare services are to obtain the benefits of open systems and avoid the constraints of proprietary interfaces. The method specifics the activities of the message development process and the structure and the components of the resulting deliverables.

The scope of this report does not include method specifications for the development of other subject areas covered by working groups of CEN/TC 251, EWOS EG-MED and WEEB/MD9.

The scope covers the development process of standardised messages, starting from the user requirements up to the delivery of message specifications using EDIFACT and ASN.1, the two international syntax standards selected in view of CR 1350:1993, but the report does not exclude other syntaxes (e.g. SGML) from being used for the syntax specific message specifications.

The scope of the Report is limited to the specification of standardised messages, therefore it does not include in its scope areas such as conformance testing of messaging applications, the implementation method for messaging standards, the maintenance of the messaging standards. It does not include in its scope issues relating to data secrecy and data protection. It does not specify methods for establishing directories of coding schemes, for data sets or for messages. It does not include specifications related to the messaging standards approval process.

The method defined by this CEN Report supports and is validated for the development of message specifications for the electronic exchange of structured character-based information in healthcare, but it does not by its nature exclude the method to be used in a wider domain (i.e. other types of information or other domains).