Common data model: Difference between revisions

Content deleted Content added
No edit summary
Line 1:
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.{{citation needed}}
 
== Examples of common data models ==
Line 11:
 
The [https://cds.climate.copernicus.eu/toolbox/doc/how-to/15_how_to_understand_the_common_data_model/15_how_to_understand_the_common_data_model.html Climate Data Store Common Data Model] is a common data model set up by the [[Copernicus Climate Change Service]] for harmonising essential [[climate change|climate variables]] from different sources and data providers.
 
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>
 
[[Once-only principle#X-trans.eu|X-trans.eu]] was a cross-border pilot project between the [[Bavaria|Free State of Bavaria]] (Germany) and [[Upper Austria]] with the aim of developing a faster procedure for the application and approval of cross-border large-capacity transports. The portal was based on a common data model that contained all the information required for approval.
Line 18 ⟶ 20:
[[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]].
 
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 [[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.
 
There are many more examples of various common data models for different uses published by different sources.<ref>[https://www.ibm.com/docs/en/taddm/7.3.0?topic=kit-introducing-common-data-model Introducing the Common Data Model - IBM Documentation]</ref><ref>[https://op.europa.eu/en/web/eu-vocabularies/cdm Common Data Model (CDM) - EU Vocabularies - Publications Office of the EU]</ref><ref>[https://docs.workato.com/features/common-data-model.html Common data model | Workato Docs]</ref><ref>[https://docs.bmc.com/docs/ac2002/common-data-model-concepts-908213436.html Common Data Model concepts - Documentation for BMC CMDB 20.02 - BMC Documentation]</ref><ref>[https://docs.evolveum.com/midpoint/reference/schema/common-data-model/ Common Data Model - Evolveum Docs]</ref>