Content deleted Content added
Tag: Reverted |
→Examples of common data models: Updated Manufacturing links Tags: Reverted Disambiguation links added |
||
Line 21:
{{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.
=== Manufacturing ===▼
The Manufacturing Common Data Model is a ___domain-oriented schema for standardizing data structures. It harmonizes shop-floor events and enterprise records by mapping equipment, material, batch and order entities to the hierarchical object classes defined in [[ISA-95]] and, for production processes, [[ISA-88]].<ref>[https://www.isa.org/isa95 ISA-95: Enterprise–Control System Integration – International Society of Automation]</ref>▼
Each ___domain (Production, Quality, Maintenance, Supply Chain) owns its own CDM; the structure of every table and field is enforced through data contracts, which are validated at the plant’s Edge Intelligence Hub before data is published to the Unified Namespace and persisted in a governed lakehouse layer.<ref>[https://umda.info/framework-details/#cdm UMDA Specification]</ref>▼
By standardizing attribute names, units of measure (e.g. SI, ISA-100), and reference codes such as [[GS1]] GTIN, the model allows MQTT / OPC UA telemetry to be joined consistently with MES, LIMS, CMMS, and ERP data, enabling AI agents to query any site with uniform semantics while maintaining full lineage for [[Title 21 CFR Part 11]] and EU-GMP Annex 11 compliance.<ref>[https://www.gmp-compliance.org/gmp-news/eu-gmp-annex-11-update EU GMP Annex 11 – Computerized Systems]</ref>▼
=== Logistics ===
[[SX000i - International guide for the use of the S-Series of Integrated Logistics Support (ILS) specifications|SX000i]] is a specification developed jointly by the [[Aerospace and Defence Industries Association of Europe]] (ASD) and the American [[Aerospace Industries Association]] (AIA) to provide information, guidance and instructions to ensure compatibility and the commonality. The associated SX002D specification contains a common data model.
▲=== Manufacturing ===
▲The Manufacturing Common Data Model is a ___domain-oriented schema for standardizing data structures. It harmonizes shop
▲Each ___domain (Production, Quality, Maintenance, Supply Chain) owns its own CDM; the structure of every table and field is enforced through data contracts, which are validated at the plant’s Edge Intelligence Hub before data is published to the Unified Namespace and persisted in a governed [[lakehouse]] layer.<ref>[https://umda.info/framework-details/#cdm UMDA Specification]</ref>
▲By standardizing attribute names, units of measure (e.g. SI, ISA-100), and reference codes such as [[GS1]] GTIN, the model allows [[MQTT]] / [[OPC UA]] telemetry to be joined consistently with [[Manufacturing Execution System|MES]], [[LIMS]], [[CMMS]], and [[Enterprise Resource Planning|ERP]] data, enabling AI agents to query any site with uniform semantics while maintaining full lineage for [[Title 21 CFR Part 11]] and EU-GMP Annex 11 compliance.<ref>[https://www.gmp-compliance.org/gmp-news/eu-gmp-annex-11-update EU GMP Annex 11 – Computerized Systems]</ref>
=== Microsoft Common Data Model ===
| |||