• There are no items in your cart

ENV 13730-2 : DRAFT 2002

Current

Current

The latest, up-to-date edition.

HEALTHCARE INFORMATICS - BLOOD TRANSFUSION RELATED MESSAGES - PART 2: PRODUCTION RELATED MESSAGES (BTR-PROD)

Published date

12-01-2013

FOREWORD
INTRODUCTION
1 SCOPE
2 NORMATIVE REFERENCES
3 TERMS, DEFINITIONS AND ABBREVIATIONS
4 REQUIREMENTS
   4.1 GENERAL CONFORMANCE REQUIREMENTS
   4.2 IMPLEMENTATION RECOMMENDATIONS
5 COMMUNICATION ROLES
   5.1 GENERAL
        5.1.1 Sending role requirements
        5.1.2 Receiving role requirements
   5.2 USE CASE DIAGRAM AND SCENARIOS (GENERAL USE CASE)
   5.3 GROUP 2: MESSAGE SEQUENCES
        5.3.1 Blood component production message domain
6 REQUIREMENTS AND GENERAL MESSAGE DESCRIPTIONS
   6.1 CONFORMANCE REQUIREMENTS
   6.2 GENERAL MESSAGE DESCRIPTIONS
   6.3 BLOOD/BLOOD COMPONENT COLLECTION REQUEST MESSAGE
        6.3.1 Scope of this message
        6.3.2 Blood/blood component collection request message
   6.4 BLOOD/BLOOD COMPONENT CLASSIFICATION REQUEST MESSAGE
        6.4.1 Scope of this message
        6.4.2 Blood/blood component classification request
                message
   6.5 BLOOD/BLOOD COMPONENT CLASSIFICATION REPORT MESSAGE
        6.5.1 Scope of the message
        6.5.2 Blood/blood component classification report
                message
   6.6 BLOOD/BLOOD COMPONENT COLLECTED DELIVER NOTE MESSAGE
        6.6.1 Scope of this message
        6.6.2 Blood/blood component collected delivery note
                message
   6.7 BLOOD COMPONENT REQUEST MESSAGE
        6.7.1 Scope of this message
        6.7.2 Blood component request message
   6.8 BLOOD COMPONENT MANUFACTURED DELIVERY NOTE MESSAGE
        6.8.1 Scope of this message
        6.8.2 Blood component manufactured delivery note
                message
   6.9 BLOOD COMPONENT PROCESSING REQUEST MESSAGE
        6.9.1 Scope of this message
        6.9.2 Blood component processing request message
   6.10 BLOOD COMPONENT PROCESSED DELIVERY NOTE MESSAGE
        6.10.1 Scope of this message
        6.10.2 Blood component processed delivery note
                message
7 DOMAIN INFORMATION MODEL (DIM)
   7.1 INTRODUCTION
        7.1.1 The modelling approach
        7.1.2 Presentation of attributes from generalisations
   7.2 GENERAL MESSAGE SUBSYSTEM
Class Descriptions
        7.2.1 requested item message
        7.2.2 issued item message
        7.2.3 blood/blood components collector
        7.2.4 blood components manufacturer
        7.2.5 blood components dispenser
        7.2.6 blood components processor
   7.3 SPECIFIC MESSAGE SUBSYSTEM
Class Descriptions
        7.3.1 original message identification
        7.3.2 blood/blood component collection request
                message
        7.3.3 blood/blood component classification request
                message
        7.3.4 blood/blood component classification report
                message
        7.3.5 blood/blood component collected delivery note
                message
        7.3.6 blood component request message
        7.3.7 blood component manufactured delivery note
                message
        7.3.8 blood component processing request message
        7.3.9 blood component processed delivery note message
   7.4 COMMUNICATING PARTIES SUBSYSTEM
Class descriptions
        7.4.1 message sender
        7.4.2 message receiver
   7.5 HEALTHCARE AGENT SUBSYSTEM
Class descriptions
        7.5.1 healthcare agent in context
        7.5.2 healthcare agent relationship
        7.5.3 healthcare agent [3.30]
        7.5.4 healthcare party [3.33]
        7.5.5 healthcare organisation [3.32]
        7.5.6 healthcare professional [3.34]
   7.6 COLLECTED ITEM SUBSYSTEM
Class descriptions
        7.6.1 collected item
        7.6.2 blood component 13.91
   7.7 REQUESTED ITEM
Class Descriptions
        7.7.1 requested item
        7.7.2 requested blood component information
        7.7.3 delivery location
   7.8 ISSUED ITEM SUBSYSTEM
Class Descriptions
        7.8.1 issued blood component
        7.8.2 blood component characteristic
        7.8.3 blood component unit
        7.8.4 quantity of blood component
        7.8.5 issued blood component administrative details
        7.8.6 issued blood component information
        7.8.7 unit (container) characteristic
   7.9 PAYMENT GUARANTOR SUBSYSTEM
Class Descriptions
        7.9.1 payment details
        7.9.2 payment guarantor
        7.9.3 payment
   7.10 LABORATORY INVESTIGATION SUBSYSTEM
        7.10.1 laboratory investigation (ENV 16 13)
        7.10.2 requested laboratory investigation (ENV 16 13)
        7.10.3 laboratory investigation report (ENV 1613)
   7.11 BLOOD DONOR SUBSYSTEM
Class Descriptions
        7.11.1 blood donor [3.13]
        7.11.2 clinical information [3.18]
        7.11.3 clinical information item
   7.12 COMMON SUBCLASSES
Class Descriptions
        7.12.1 address
        7.12.2 event date and time
        7.12.3 general message information
        7.12.4 identifier
        7.12.5 language details
        7.12.6 measurement
        7.12.7 message identification
        7.12.8 party identifier
        7.12.9 person name details
        7.12.10 structured address
        7.12.11 structured person name
        7.12.12 time interval
        7.12.13 time period
        7.12.14 unstructured address
        7.12.15 unstructured name details
        7.12.16 value of quantity
ANNEX A (INFORMATIVE) HOW TO READ THE MODELS
ANNEX B (INFORMATIVE) COMPOUND AND SIMPLE DATA TYPES
        RATIONALE AND HOW TO USE THE DATA TYPES IN MESSAGES
ANNEX C (NORMATIVE) GUIDE TO USAGE OF CEN/TC 251/ENV 1613
INDEX

Defines general messages for electronic information interchange between computer systems used by healthcare parties in the blood transfusion domain.

Committee
TC 251
DocumentType
Draft
PublisherName
Comite Europeen de Normalisation
Status
Current

View more information
Sorry this product is not available in your region.

Access your standards online with a subscription

Features

  • Simple online access to standards, technical information and regulations.

  • Critical updates of standards and customisable alerts and notifications.

  • Multi-user online standards collection: secure, flexible and cost effective.