Content deleted Content added
No edit summary |
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 1:
[[Image:HL7 Reference Information Model.jpg|thumb|360px|Example of a generic data model.<ref>Amnon Shabo (2006). [https://www.hhs.gov/healthit/ahic/materials/01_07/phc/genomics.html Clinical genomics data standards for pharmacogenetics and pharmacogenomics] {{Webarchive|url=https://web.archive.org/web/20111018032946/http://www.hhs.gov/healthit/ahic/materials/01_07/phc/genomics.html |date=2011-10-18 }}.</ref>]]
'''Generic data models''' are generalizations of conventional [[data model]]s. They define standardised general relation types, together with the kinds of things that may be related by such a relation type.
== Overview ==
Line 11:
== Generic data model topics ==
=== Generic patterns ===
There are generic patterns that can be used to advantage for modeling business. These include entity types for PARTY (with included PERSON and ORGANIZATION), PRODUCT TYPE, PRODUCT INSTANCE, ACTIVITY TYPE, ACTIVITY INSTANCE, CONTRACT, GEOGRAPHIC AREA, and SITE. A model which explicitly includes versions of these entity classes will be both reasonably robust and reasonably easy to understand.
More abstract models are suitable for general purpose tools, and consist of variations on THING and THING TYPE, with all actual data being instances of these. Such abstract models are on one hand more difficult to manage, since they are not very expressive of real world things, but on the other hand they have a much wider applicability, especially if they are accompanied by a standardised dictionary. More concrete and specific data models will risk having to change as the scope or environment changes.
Line 20:
* Every individual thing is an instance of a generic entity called 'individual thing' or one of its subtypes.
* Every individual thing is explicitly classified by a kind of thing ('class') using an explicit classification relationship.
* The classes used for that classification are separately defined as standard instances of the entity 'class' or one of its subtypes, such as 'class of relationship'. These standard classes are usually called 'reference data'. This means that ___domain specific knowledge is captured in those standard instances and not as entity types. For example, concepts such as car, wheel, building, ship, and also temperature, length, etc. are standard instances. But also standard types of relationship, such as 'is composed of' and 'is involved in' can be defined as standard instances.
This way of modeling allows the addition of standard classes and standard relation types as data (instances), which makes the data model flexible and prevents data model changes when the scope of the application changes.
Line 55:
== External links ==
*
* [https://archive.today/20121220163431/http://gellish.wiki.sourceforge.net/ Gellish English] and the Gellish Dictionary and documents about Gellish [
{{Data model}}
| |||