================================================================================================ (2JUB)
Comments (2JUC)
- Ref: http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel_09_2004/OverviewOfThe_DRM_VolIv1#nid2IW3 (2JU8)
- Comment: Inconsistencies exist between the textual descriptions and the examples of the Subject Areas: While the DRM states here in Section 2 that the Subject Areas represent a high-level set of business functions and are obtained from the FEA’s Business Reference Model (BRM) and in Section 3 implies that Subject Areas in the DRM equate to Sub-functions in the BRM, the examples - Exhibit E: DRM Example and Exhibit H: Use of the DRM do not support this statement. In Exhibit E: DRM Example for the HEALTH line of business above,, the Population Health Management sub-function does not exist in version 2 of the BRM. HEALTH (LOB) consists of the following sub-functions: (2JUD)
- Ref: Exhibit E: Example DRM above (2JWA)
- Comment: It should be made clear that the Subject Area is equivalent to the BRM LOB sub-function. It is recommended that the document use the same name as is used in the BRM LOB sub-function. (agency comment / compiled 2004.12.06) (2JWB)
- Ref: Exhibit E: Example DRM above (2K0N)
- Comment: If the goal is to have effective data sharing, then the categorization scheme, Exhibit E above, has some shortcomings. The current DRM suggests that the categorization is derived from BRM's Line of Business and Sub-functions. We believe that the categorization would need to be more encompassing and muti-faceted. That is, categorization would need to be used for both Categorization of Data and the Categorization of Information Packages for data exchanges. In addition, there may need to be additional categorization schemes that are used for locating and accessing the data and the information for use in search and browse. (2K0O)
- Suggested Action: This suggestion may not be appropriate for Version 1 of the DRM, but should be noted for possible inclusion in an additional volume. As the DRM suggests, the categorization of Structure of Data may be derived from the Line of Businesses and Sub-functions within each line of business and associated sub-functions. This allows data to be defined and structured for efficient storage within the organization (may be thought of it as vertical). However, the categorization of the Information Exchange Packages will need to be devised by examining the information sharing needs and sharing patterns across the multiple lines of business and multiple agencies -- this may be thought of as horizontal. (2K0P)
- Proposed Solution: There are two aspects to the solution: a) Defining and using the various types of categorization, and b)Defining the focus of the Structure of the Data and focus of the Information Exchange Package. (2K0Q)
- a) Types of Categorization: Categorization is multi-faceted and it applies to defining, storing, using and exchanging both data and information. When defining the structure of the data we treat categorization to help us define subject areas and super types. These categories cannot be overlapping. But when we are defining Information Exchange packages and associated categories, we consider the business processes associated with data sharing needs of across lines of business and agencies. These categories can be overlapping to meet one or more exchange needs. In addition, to allow us to find and access information for end-use consumption (such as in search and browse), we need taxonomies, categories, and topics that are from multiple viewpoints. These are also overlapping categories. (2K0R)
- b) Defining the Focus of Categorization: The focus of the categorization and associated data analysis differ significantly based on whether we are defining the Structure of the Data or defining the Information Exchange Packages. (2K0S)
- When defining the Structure of Data, we need to focus on the business context within a line of business, associated sub-functions and the data requirements supporting the business. The end result is to store and use the data for that business. This allows us to define the schema and databases to support that specific business. And to define an enterprise data model for that organization. (2K0T)
- When defining the Information Exchange Packages, we need to focus on the data exchange across agencies and organizations (multiple lines of business). We now consider the business processes and information flow across agencies, which require the exchange of the data. This allows us to define information exchange packages (which may eventually result in XML schema) to share the data across agencies. (agency comment / compiled 2004.12.06) (2K0U)
- Proposed Solution: There are two aspects to the solution: a) Defining and using the various types of categorization, and b)Defining the focus of the Structure of the Data and focus of the Information Exchange Package. (2K0Q)
- Ref: Exhibit E: Example DRM above (2K26)
- Comment: There is a lot of semantic information in the "Categorization of Data" and likewise in the "Structure of Data." However, there is no explanation of the relationship between business context and data element except to illustrate an exchange package. "Structure of data" as defined by the DRM should be the organization into useful structures of entities and relationships used to define meaning. Even the DOI example on page 20 is not clear in this regard. Much of the meaning of the message is implicitly created by the information exchange package, without being explicitly defined. Such implicit assumptions are nearly impossible for a machine to ascertain. Similarly, Exhibit H: Use of the DRM illustrates a message whose syntax is roughly defined, but whose meaning is not. (agency comment / compiled 2004.12.06) (2K27)
- Ref: Exhibit E: Example DRM above (2KGE)
- Comment:Clarify Subject Area Usage. Exhibit E refers to the “FEA DRM Subject Area” however, in the next section on Categorization of Data, Subject Area is related to sub-functions from the BRM. Since this is Line of Business focused, the term on Exhibit E should be “FEA BRM Subject Area.” (agency comment / compiled 2004.12.06) (2KGF)
- Ref: Ref: Exhibit E: Example DRM above (2KGG)
- Comment: Correct Health Subject Area Reference. The term “Population Health Management” as the Subject Area and “Immunization” as the Super Type doesn’t quite match the BRM (version 2). The Subject Area should be “Public Health” which includes “Immunization Management”. (agency comment / compiled 2004.12.06) (2KGH)