1 / 19

Data Model Harmonization

Data Standards Comparison via:. Data Model Harmonization. Data Standards Expressions The Purpose of Data Modeling Domain Information Models (DIM) The Canonical DIM Model Components Closing Thoughts. Overview.

mduvall
Download Presentation

Data Model Harmonization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Standards Comparison via: Data Model Harmonization

  2. Data Standards Expressions The Purpose of Data Modeling Domain Information Models (DIM) The Canonical DIM Model Components Closing Thoughts Overview

  3. Data standards are expressed in many formats: messages, documents, guides, transactions, schemas, templates, and others. • Common features among these expressions are the assignment of names, data types, and value constraints to data elements. • Comparisons between data standards are complicated by the variation in their expression. • Data models can be a useful as a common expression of data standards. Data Standards Expressions

  4. Various Data Structure Expressions HL7 v2 Segment HL7 v3 XSD HL7 v3 HMD

  5. What is the Purpose of Data Modeling • To aid in understanding data in a particular domain • To communicate the modeler’s understanding of data and allow that understanding to be assessed by others • To aid in reconciling multiple perspectives of data by combining the perspectives into a single specification • To document a data structure design (existing or planned) so that the design may be evaluated

  6. Reveal Assumptions Do you play football? Yes, I do play football. Revealing assumptions is an essential component of effective communication. Data models are an effective means of documenting our assumptions about data

  7. A B 0..* 1 0..* 0..* C Reduce Ambiguity Data modeling provides a language that allows us to unambiguously express our understanding and assumptions about the information in a particular domain.

  8. B X 0..* A B 1 0..* 1 0..* 0..* 0..* 0..* C C Reconcile Conflicts Sharing data models provides an opportunity to identify and reconcile conflicts in our understanding and to validate our assumptions about information.

  9. B A 0..* 1 0..* 0..* C A B (0,M) (0,1) (1,1) (0,M) D Expand Understanding Sharing data models provides an opportunity to identify gaps in our understanding. No one of us has the complete view of the public health information domain.

  10. Value of Data Modeling • Reveal Assumptions • Reduce Ambiguity • Reconcile Conflicts • Expand Understanding

  11. A domain information model is an expression of a proposed or existing data standard (or data requirement). It is a faithful rendering of the standard in the form of a UML class diagram with an accompanying data dictionary. Any data structure, regardless of format, can be expressed as a domain information model. Once a data structure’s expression is re-expressed as a domain information model it can then be compared and harmonized with related data structures. Domain Information Models

  12. B B A X 0..* 0..* 1 1 0..* 0..* 0..* 0..* C C A B (0,M) (0,1) (1,1) (0,M) D Data Structure DIM eXPRESSION HL7 v2 Segment HL7 v3 HMD HL7 v3 XSD

  13. B B X A 0..* 0..* 1 1 E (1,1) G B (0,M) 0..* 0..* (0,M) (0,1) (1,1) (0,1) 0..* 0..* C C (0,M) (0,M) C D A X A B (0,M) (0,1) (1,1) (0,M) D The canonical DIM Domain Information Model Domain Information Model Domain Information Model

  14. Model Components • Class • Name • Description • Attributes • Relationships • Attribute • Name • Description • Datatype • Value Set Binding • Relationship • Name • Type • Source Cardinality • Target Cardinality • Source Role Name • Target Role Name • Constraint • Structural Constraint • Semantic Constraint

  15. Closing Thoughts All models are wrong; some are useful. ~ George Box

  16. Model One «datatype» Person PersonName - name: PersonName - lastName: char - birthDate: dateTime - firstName: char - phone: PersonPhone [0..2] (list) Person constraints Model Two {PersonPhone(1) is Home Phone} - lastName: char {PersonPhone(2) is Work Phone} - firstName: char - birthDate: dateTime - homePhone: char «enumeration» - workPhone: char PhoneKind «datatype» PersonPhone «enum» Home - phoneKind: PhoneKind Work - phoneText: char PersonName Person - personNameKind: PersonNameKind - personNameText: char - birthDate: dateTime 0..2 constraints {PersonNameKind is Unique} Model Three 0..2 PersonPhone «enumeration» «enumeration» PersonPhoneKind PersonNameKind - phoneKind: PersonPhoneKind - phoneText: char «enum» «enum» Home lastName constraints Work firstName {PersonPhoneKind is Unique} Useful models with differing styles

  17. Characteristics of a Useful Model • Salient: Since no model can represent everything, it must selectively represent those things most relevant to the task at hand. • Accurate: The model should precisely encode the actual state of affairs and not an erroneous or biased view. • Complete yet Parsimonious: The model should be as simple as possible, but no simpler. It should concisely capture all the relevant dimensions of the problem without squeezing out the opportunity for serendipitous or creative insight. • Perceptible: Models should be appropriately displayed in high fidelity as they won't be much use if we can't clearly see, hear, or feel them. • Understandable: Once we perceive the model we must be able to make sense of it; it mustn't be too complicated or unfamiliar for us to understand. • Descriptive: The model should clearly and objective describe the true situation. • Emotive: In addition, the model should convey a subjective feel for the emotional and value-laden connotations of the situation being modeled. • Inspiring: Because people are drawn to and inspired by thoughtful design, models should be elegant, i.e. they should synergistically combine style and substance. • Memorable: Models are not of much use if they pass quickly from the mind, or if they cannot be used as a mnemonic device. Models should be easily accessible for future reference and to refresh our understanding. • Flexible: As all models are, to some degree, inaccurate, irrelevant, mistaken, time-sensitive etc., they should be open to recursive revision to reflect new data, our growing understanding, or our evolving needs. • Coherent: Models do not exist in isolation but in interlocking systems, thus any particular model should be coherent with other related models. • Productive: Ultimately, the model has a purpose: the production of effective action. A good model should help define our goals and then specify the actions necessary to reach them. • Useful: Usefulness is the sum of the above properties and the degree to which they combine to promote understanding and effective action. It is important to note that the most accurate, or the most complete, or the most elegant model is not necessarily the most useful. All models are incomplete. All models a compromise. The model maker's art lies in making those shrewd trade-offs that will render the model most useful to the problem at hand.

  18. Questions / Discussion / Feedback

  19. Abdul-Malik ShakirPrincipal Consultant Shakir Consulting1407Foothill Blvd., Suite 145La Verne, CA 91750 Office: (909) 596-6790 Mobile: (626) 644-4491Email: AbdulMalik@ShakirConsulting.com

More Related