Common data model: Difference between revisions

Revision as of 14:26, 12 April 2022

Latest revision as of 02:11, 26 July 2025

(25 intermediate revisions by 15 users not shown)

Line 1:

{{Short description|A standardised data model allowing for data exchange between sources and applications}}

A '''common data model''' ('''CDM''') can refer to any standardised [[data model]] which allows for [[data]] and [[information exchange]] between different [[Application software|applications]] and [[Database|data sources]]. Common data models aim to standardise logical infrastructure so that related applications can "operate on and share the same data",<ref>[https://www.synopsys.com/glossary/what-is-common-data-model.html What is a Common Data Model? – How Does it Work? | Synopsys]</ref> and can be seen as a way to "organize data from many sources that are in different formats into a standard structure".<ref>[https://www.jamesserra.com/archive/2019/06/common-data-model/ Common Data Model | James Serra's Blog]</ref>

A common data model has been described as one of the components of a "[[Technical data management system#Comparison between strong information systems and weak information systems|strong information system]]".<ref>[http://www.marcolazzari.it/publications/weak-information-systems-for-technical-data-management-preprint.pdf Salvaneschi, Paolo; Lazzari, Marco (1997). Weak information systems for technical data management (PDF). Worldwide ECCE Symposium on computers in the practice of building and civil engineering. Lahti, Finland. pp. 310–314. Retrieved 2015-11-29]</ref> A standardised common data model has also been described as a typical component of a well designed [[agile application]] besides a common communication protocol.<ref>{{citationCite neededweb |title=What is Data Modeling? {{!}} IBM |url=https://www.ibm.com/topics/data-modeling |access-date=2023-07-04 |website=www.ibm.com |language=en-us}}</ref> Providing a single common data model within an organisation is one of the typical tasks of a [[data warehouse]].

== Examples of common data models ==

Line 11 ⟶ 12:

=== General information technology ===

Within [[service-oriented architecture]], [[S-RAMP]] is a specification released by [[Hewlett-Packard|HP]], [[IBM]], [[Software AG]], [[TIBCO]], and [[Red Hat]]<ref name="Lublinsky 2010">Boris Lublinsky HP, IBM, Software AG and TIBCO Releases Version 0.9 of the SOA Repository Specification - http://www.infoq.com/news/2010/04/SOARepository InfoQ, April 27, 2010</ref> which defines a common data model for SOA repositories<ref name="Stam 2014">Kurt Stam, Eric Wittmann S-RAMP Version 1.0. Part 1: Foundation - http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/s-ramp-v1.0-part1-foundation.html OASIS, December 23, 2013</ref> as well as an interaction protocol to facilitate the use of common tooling and sharing of data.<ref name="Smithson 2014">Martin Smithson, Vincent Brunssen S-RAMP Version 1.0. Part 2: Atom Binding - http://docs.oasis-open.org/s-ramp/s-ramp/v1.0/s-ramp-v1.0-part2-atom-binding.html OASIS, December 23, 2013</ref>

[[Content Management Interoperability Services]] (CMIS) is an open standard for inter-operation of different [[content management system]]s over the internet, and provides a common data model for typed files and folders used with with [[version control]].<ref>{{Cite journal |last=Vstath |first=Bill |title=Content Management Interoperability Services (CMIS) Version 1 |url=https://www.academia.edu/9403826}}</ref>

The NetCDF software libraries for array-oriented scientific data implements a common data model called the [[NetCDF#NetCDF-Java common data model|NetCDF Java common data model]], which consists of three layers built on top of each other to add successively richer semantics.

Line 19 ⟶ 20:

=== Health ===

{{main|Electronic health record#Common data model (in health data context)}}

Within [[genomic and medical data]], the Observational Medical Outcomes Partnership (OMOP) research program established under the U.S. [[National Institutes of Health]] has created a common data model for claims and electronic health records which can accommodate data from different sources around the world. PCORnet, which was developed by the [[Patient-Centered Outcomes Research Institute]], is another common data model for health data including electronic health records and patient claims. The Sentinel Common Data Model was initially started as Mini-Sentinel in 2008. It is used by the Sentinel Initiative of the USA's Food and Drug Administration. The Generalized Data Model was first published in 2019. <ref>{{Cite journal |last1=Danese |first1=Mark D. |last2=Halperin |first2=Marc |last3=Duryea |first3=Jennifer |last4=Duryea |first4=Ryan |date=2019-06-24 |title=The Generalized Data Model for clinical research |journal=BMC Medical Informatics and Decision Making |volume=19 |issue=1 |pages=117 |doi=10.1186/s12911-019-0837-5 |doi-access=free |issn=1472-6947 |pmc=6591926 |pmid=31234921}}</ref> It was designed to be a stand-alone data model as well as to allow for further transformation into other data models (e.g., OMOP, PCORNet, Sentinel). It has a hierarchical structure to flexibly capture relationships among data elements. The [[JANUS clinical trial data repository]] also provides a common data model which is based on the [[SDTM]] standard to represent clinical data submitted to regulatory agencies, such as tabulation datasets, patient profiles, listings, etc.

=== Logistics ===

Line 25 ⟶ 26:

=== Microsoft Common Data Model ===

The [[Microsoft Common Data Model]] is a collection of many standardised extensible data schemas with entities, attributes, semantic metadata, and relationships, which represent commonly used concepts and activities in various businesses areas such as "automotive, banking, commerce, educational, healthcare, marketing, sales, legal and non-profit institutions".<ref>[https://www.avantiico.com/microsoft-power-platform/common-data-model/ Common Data Model -{{cn|date=February Avantiico]</ref>2024}} It is maintained by [[Microsoft]] and its partners, and is published on [[GitHub]].<ref>[https://github.com/Microsoft/CDM GitHub - microsoft/CDM: The Common Data Model (CDM) is a standard and extensible collection of schemas (entities, attributes, relationships) that represents business concepts and activities with well-defined semantics, to facilitate data interoperability. Examples of entities include: Account, Contact, Lead, Opportunity, Product, etc.]</ref> Microsoft's Common Data Model is used amongst others in [[Microsoft Dataverse]]<ref>[https://docs.microsoft.com/en-us/common-data-model/use About - Common Data Model - Common Data Model | Microsoft Docs]</ref> and with various [[Microsoft Power Platform]]<ref>[https://radacad.com/what-is-the-common-data-model-and-why-should-i-care-part-3-of-dataflow-series-in-power-bi What is the Common Data Model and Why Should I Care? Part 3 of Dataflow Series in Power BI - RADACAD]</ref> and [[Microsoft Dynamics 365]]<ref>[https://www.nigelfrank.com/insights/microsoft-dynamics-365-the-common-data-model-explained Microsoft Dynamics 365: the Common Data Model explained | Nigel Frank]</ref> services.

=== Rail transport ===

[[RailSystemModelRailTopoModel]] is a common data model for the [[Rail transport|railway sector]].<ref>[https://uic.org/com/enews/nr/365/article/uic-and-railml-act-for-creating-3939?page=modal_enews UIC and railML act to create the foundations for a Universal Infrastructure Data Exchange Format | UIC Communications]</ref>

=== Other ===

Line 37 ⟶ 38:

* [[Canonical model]]

* [[Data Reference Model]], one of five reference models of the U.S. government [[federal enterprise architecture]]

* [[Data platform (disambiguation)|Data platform]]

* [[Metadata]]

* [[Open Semantic Framework]], which internally uses the [[Resource Description Framework|RDF]] to convert all data to a common data model

* [[Requirements Interchange Format]]

* [[Generic data model]]

== References ==

<references/>

{{Data model}}

[[Category:Sharing]]