UML Notation Used in the Models The Care Plan model is expressed as a single UML (Unified Modeling Language) model with various class diagrams that emphasize different features and aspects of the model. UML classes represent concepts from the domain and may and may not always map one to one to an implementable class. The model makes use of the following UML capabilities: UML Class Expresses a domain concept. – UML Property Represent intrinsic attributes of the concept. – UML Association Specifies a relation between concepts. – UML Association Class - An association class can be seen as an association with data properties. For example, the association class used in the Care Plan model specifies Participation attributes which identify where, when and how an individual care team was involved in an occurrence of the plan, goals, concerns, interventions, etc. These attributes are part of the associative type of Participation. Figure Participation Association Class Example UML Template - are model elements with unbound formal parameters that you can use to define families of classifiers. In the model, these are used to represent unconstrained place holders for clinical object references. For example, the reason for a Health Concern may be a Condition, an Allergy, a Medication, etc. The unbound place holder parameter allows specifying a Health Concern pertaining to any of these disjoint concepts. UML Stereotype Used to extend UML at the meta-level. This model uses a – “<<Temporal Awareness>>”stereotype for UML associations. The Awareness>>”stereotype “<<Temporal indicates the association requires special temporal awareness by the care team (awareness of before and after values). For example, a priority attribute may be changed and the awareness of the change can be of special importance to care team decision making. The use of the stereotype in the model explicitly informs downstream artifacts that they should consider the capability to support awareness of the change through time. Care Plan Conceptual Model The conceptual model is designed to capture high level business requirements and delineates the scope of the domain necessary to support definition of the logical information model and derived technical interoperability standards. Its focus is to identify the necessary concepts and relationships only. The model does not specify data properties; the data properties are elaborated in the logical information model. The conceptual model establishes common semantics for concepts and relationships required to establish the scope of electronic interoperability for point-in-time care plan exchanges and dynamic, shared and collaborative care plan interactions.
UML Notation Used in the Models The Care Plan model is expressed as a single UML (Unified Modeling Language) model with various class diagrams that emphasize different features and aspects of the model. UML classes represent concepts from the domain and may and may not always map one to one to an implementable class. The model makes use of the following UML capabilities: UML Class – Expresses a domain concept. UML Property – Represent intrinsic attributes of the concept. UML Association – Specifies a relation between concepts. UML Association Class - An association class can be seen as an association with data properties. For example, the Participation association class used in the Care Plan model specifies attributes which identify where, when and how an individual care team was involved in an occurrence of the plan, goals, concerns, interventions, etc. These attributes are part of the associative type of Participation. Figure Participation Association Class Example UML Template - are model elements with unbound formal parameters that you can use to define families of classifiers. In the model, these are used to represent unconstrained place holders for clinical object references. For example, the reason for a Health Concern may be a Condition, an Allergy, a Medication, etc. The unbound place holder parameter allows specifying a Health Concern pertaining to any of these disjoint concepts. UML Stereotype – Used to extend UML at the meta-level. This model uses a “<<Temporal Awareness>>”stereotype for UML associations. The “<<Temporal Awareness>>”stereotype indicates the association requires special temporal awareness by the care team (awareness of before and after values). For example, a priority attribute may be changed and the awareness of the change can be of special importance to care team decision making. The use of the stereotype in the model explicitly informs downstream artifacts that they should consider the capability to support awareness of the change through time. Care Plan Conceptual Model The conceptual model is designed to capture high level business requirements and delineates the scope of the domain necessary to support definition of the logical information model and derived technical interoperability standards. Its focus is to identify the necessary concepts and relationships only. The model does not specify data properties; the data properties are elaborated in the logical information model. The conceptual model establishes common semantics for concepts and relationships required to establish the scope of electronic interoperability for point-in-time care plan exchanges and dynamic, shared and collaborative care plan interactions.