|
·ÖÀർº½ |
 |
|
|
|
The HL7 Development Framework |
|
×ÊÔ´´óС£º 2.74 MB |
×ÊÔ´ÀàÐÍ£º¿Î¼þ |
ÏÂÔØ»ý·Ö£º 10 |
|
|
|
×ÊÔ´½éÉÜ |
|
The HL7 Development Framework
The basis for all products in V3 are models:
symbolic, structured representations of (part of)
the real world
• The UML (Universal Modelling Language) is the
most commonly used modelling format
¨C HL7 uses minor variations
• Models in V3 offer a ¡®language¡¯ for understanding
Ringholm GmbH Integration Consulting 2
and recording of the contents, the structure (static
aspect) and the behaviour of information
exchange in healthcare (dynamic aspect)
• Message specifications are the result of
combining data and process models: when do I
sent what?
• HDF HL7 Development Framework
• Storyboards
• RIM Reference Information Model
• D-MIM Domain Message Information Model
• R-MIM Refined Message Information Model
• CMET Common Message Element Type
Ringholm GmbH Integration Consulting 3
• HMD Hierarchical Message Description
• MT Message Types
• TE Trigger Events
• IN Interaction Model
• AR Application Roles
• ITS Implementation Technology Specification
• Structured method to start with a description of
the real world for a certain domain and derive:
¨C An information model for the domain (static model);
¨C An interaction model for the domain (dynamic model);
¨C And finally: message specifications that bind a static
Ringholm GmbH Integration Consulting 4
model to a dynamic model.
• The HDF is not required knowledge to
implement V3 interfaces, but it is necessary to
understand why they are the way they are. |
|
ÏÂÔØµØÖ· |
|
|
|
|
|