Blood Pressure Cross-Country Cross-Language Cross-Paradigm (Demo) IG
0.7.1 - ci-build

Blood Pressure Cross-Country Cross-Language Cross-Paradigm (Demo) IG, published by FO. This guide is not an authorized publication; it is the continuous build for version 0.7.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/bloodpressure/ and changes regularly. See the Directory of published versions

Notation

This page is intended to explain the notation being used in the different models. It should help to read and understand the models, especially the class diagrams:

NotationNotationAbstract ClassgeneralAttributeClass 1specialAttributeForClass1Class 2specialAttributeForClass2related ClasscompositedClassaggregatedClassrelated to relationshipattributes for this specific relationshipto abstracta..bm..n

Explanation:

  • all boxes represent classes
  • "Abstract Class" is an abstract class that cannot be instantiated. (It is written in italics.)
  • "Class 1" and "Class 2" are specialisations of the "Abstract Class" which is documented by the arrow.
    • both can be instantiated because they are not abstract.
  • "generalAttribute" is an attribute in the abstract class, that is inherited to the specialisations.
  • "specialAttributeForClass" is an attribute that is valid in this class, and perhaps inherited to further specialised classes.
  • "related Class" is a class that is somehow related to "Abstract Class", i.e. with the class to which the connection goes.
  • Aggregation:
    • It represents a "part of" relationship.
    • this class is part of "related class".
    • Many instances (denoted by the *) of Class2 can be associated with Class1.
    • Objects of "related class" and tis class have separate lifetimes.
  • Composition:
    • A special type of aggregation where parts are destroyed when the whole is destroyed.
    • Objects of this class live and die with "related class".
    • Class2 cannot stand by itself.
  • "to abstract" with the small arrows denotes the direction of the connection/relationship.
  • "a..b" denotes the cardinality of "abstract class" for each element of "related class" element. For example, each "related class" instance can have "a" to "b" related "abstract class" instances.
  • "m..n" denotes the cardinality of "related element" for each element of "abstract class".
  • Classes can be grouped together to help with reading.
  • the related class is a set of information the belongs to the relationship between the two associated classes