如何讀 CDA RMIM Model

HL7 Graphic Conventions for Derived Information Models

出處： http://wiki.hl7.org/index.php?title=Naming_Rules_For_HL7_Static_Information_Models

Although HL7's graphic conventions for representing derived models (RMIMs) are not strictly part of the naming rules, they reflect other rules imposed on the information model designers that do interact with the names to affect one's understanding of models. This section looks at the sub-set of those conventions that reflects class and association names.

The figure below represents a small "RMIM design" presented using HL7's graphic conventions with annotations (numbered boxes and colored arrows) added.

The diagram shows five regular (rectangular) classes from the backbone, two "arrow" classes" and one class from outside the backbone (deep blue). The conventions of interest are:

• All "non-arrow" classes have their class name as their primary label (annotations 1 & 2)
• The "arrow" classes have their association name (from the perspective of the starting class) as their primary label (annotation 1A)
• The class names of the "non-arrow" classes may be either their "formal name" (annotation 1) or a business name (annotation 2)
• Association names from any class to a "non-arrow" class are displayed adjacent to the class at the end of the association. This name must be the formal name which may be either the name of the ending class (annotation 3) or an alternate (annotation 4).
• Association names from any class to an "arrow" class are displayed as the primary label of the "arrow" class (annotation 1A).

For comparison, the following figure shows the same model diagramed using UML conventions.

In this circumstance, the figure shows the class name for all classes and associations, but it fails to illustrate:

• The associative function of the "arrow classes"
• The cardinality constraints imposed on attributes
• The appearance constraints (mandatory and required) imposed on attributes..
• Vocabulary domain constraints applied to classCode, typeCode and moodCode values which establish the essential semantic meaning of each class
• The coding strength constraint applied to coded attributes