Information Models

Main Events

  1. Receive public health report
  2. Send public health report
  3. Receive acknowledgement
  4. Send acknowledgement

Entity Relationship Diagram (ERD)

Data Structure: This establishes a preliminary organization of the defined data elements into logical records and the relationships between these logical records.  The data are organized in a way that facilitates the processing of inputs to generate outputs and satisfy other computational requirements.  Generally, this is best accomplished by defining data structure that models the way in which data naturally occurs in the environment.  As a part of this task, the project team organizes required data elements into logical records or schemas and develops an initial specification for these data element groups and group relationship.  A data structure chart is then prepared to illustrate the logical relationships among the records defined above.  Connecting lines may be used to indicate that one record can be logically accessed from another.  In addition, a key is identified for each record that may be directly accessed.  The objective of this task is to define a logical set of records and record relationships that satisfy the user-based requirements of the new system.

8. High Level Data Flow Diagrams

Class Diagram

Parent/Child (Inheritance) and Hierarchical Permissions
 
For example, the "Patient" grouping has multiple permissions that can be configured, such as read patient name, read patient identifiers, and read patient SSN.  These permissions are structured in a hierarchy where an undefined permission inherits its value from its parent permission.  This hierarchy model essentially limits the number of permissions that must be set to achieve a desired security policy.
As shown below, the user (with Roles B, D and H assigned) can read the selected patient's name but not the patient's SSN.