Biomedical Concepts are CDISC metadata objects that provide a semantically unambiguous description of a clinically or biologically relevant matter, independent of any single data standard implementation. Their two-layer model links an abstract meaning with specific SDTM dataset specializations at the variable level. This makes it possible to explicitly model relationships between measurement, result, unit, permissible terminology, and dataset structure.<\/p>\n
The abstract level of a Biomedical Concept contains the subject-matter meaning without yet tying it to a specific study variable or a specific eCRF field. CDISC largely aligns this semantics with concepts from the NCI Thesaurus. A concept can therefore serve as a reusable definition, even if different studies represent the same matter in different technical environments.<\/p>\n
This level provides clarity particularly where a term could be implemented differently across multiple standards or therapeutic areas. It captures not merely a name, but the characteristics that make up the subject-matter unit. For study planning, it can therefore make the link between the Schedule of Activities, the data collection requirement, and the later data representation easier to understand.<\/p>\n
Standard independence does not mean that every concept can be adopted into every study without adaptation. The concept fixes the meaning; study conduct still determines whether, when, and by which method an assessment is performed. This separation is precisely what allows subject-matter semantics to be reused without confusing the protocol-specific observation plan with a technical dataset definition. It also improves comparability of the same assessments across studies.<\/p>\n
The second layer consists of valid CDISC dataset specializations. It describes how a Biomedical Concept is implemented as an extension of an SDTM dataset structure. This includes value-level metadata, variable relationships, data types, formats, permissible terminology subsets, and assignment to a domain context. A specialization can thus serve as a preconfigured building block for Define-XML.<\/p>\n
The model supports metadata-driven automation. When the subject-matter definition and the variable level are linked, parts of a CRF, the transformation specification, or the Define-XML metadata can be derived from the same objects. However, automation does not remove the need to verify whether the study protocol actually meets the prerequisites of the respective specialization.<\/p>\n
Between concept and specialization, a one-to-many relationship may exist. The same subject-matter can be represented by multiple specialized variants depending on dataset context or implementation needs. The unique identifier of the concept and the identifier of the specialization make this linkage machine-readable. For programming and metadata review, this makes it clear which parts share a common semantics and which merely represent different technical implementations.<\/p>\n
Biomedical Concepts are not another core standard alongside SDTM, ADaM, SEND, or CDASH. They act as a linking layer between these standards and complement them with explicit semantics, variable relationships, and operational metadata. SDTM remains the model for tabular submission data; the Biomedical Concept explains which subject-matter is represented by a specialization of that structure.<\/p>\n
The existing neighbouring entry \u201cCDISC Standards\u201d refers to the overarching standards portfolio. By contrast, a Biomedical Concept is a single, identifiable metadata object. Nor is it equivalent to controlled terminology: terminology provides coded values, whereas the concept describes the meaning and composition of the matter to which such values may belong.<\/p>\n
CDASH, in turn, defines which data elements are intended for harmonised collection. A Biomedical Concept can support this planning semantically, but it does not itself prescribe the selection of clinical questions in the eCRF. ADaM is even further downstream: it shapes study data into analysable datasets and does not assume the role of a standard-independent subject-matter definition.<\/p>\n
With complex endpoints, gaps can easily arise between the protocol, CRF design, data model, and submission metadata. Biomedical Concepts make it possible to align the subject-matter definition of an assessment early on with the required variables, units, and terminology references. For recurring measurements, this can reduce the number of individually designed specifications and improve traceability through to the Define-XML description.<\/p>\n
Full-service CROs such as Mediconomics provide support in mapping endpoints and assessments to available concepts, in designing CRF and SDTM specifications, and in transferring suitable value-level metadata into Define-XML. In doing so, they verify whether the selected dataset specialization fits the planned data collection, the units used, and the terminology of the specific study.<\/p>\n
Does a Biomedical Concept already describe a complete SDTM dataset?<\/strong><\/p>\n No. It provides the semantic definition and can be linked to an SDTM dataset specialization. The complete study dataset is created only through the protocol-specific implementation and the actual data.<\/p>\n What do value-level metadata represent in this context?<\/strong><\/p>\n They specify requirements at the level of specific values or variable instances within a dataset structure. In dataset specializations, they make the technical implementation of a Biomedical Concept usable for Define-XML.<\/p>\n Who maintains the semantic foundations of the concepts?<\/strong><\/p>\n CDISC develops the Biomedical Concepts. The conceptual level is largely aligned with the terminology of the NCI Thesaurus; CDISC also publishes the content via the CDISC Library API.<\/p>\n Biomedical Concepts are CDISC metadata objects that provide a semantically unambiguous description of a clinically or biologically relevant matter, independent of any single data standard implementation. Their two-layer model links an abstract meaning with specific SDTM dataset specializations at the variable level. This makes it possible to explicitly model relationships between measurement, result, unit, permissible […]<\/p>\n","protected":false},"author":10,"featured_media":0,"parent":0,"template":"","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"glossary-cat":[25],"class_list":["post-8088","glossary","type-glossary","status-publish","hentry","glossary-cat-datenmanagement-eclinical"],"acf":[],"related_terms":"","external_url":"","internal_reference_id":"","_links":{"self":[{"href":"https:\/\/mediconomics.com\/en\/wp-json\/wp\/v2\/glossary\/8088","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mediconomics.com\/en\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/mediconomics.com\/en\/wp-json\/wp\/v2\/types\/glossary"}],"author":[{"embeddable":true,"href":"https:\/\/mediconomics.com\/en\/wp-json\/wp\/v2\/users\/10"}],"version-history":[{"count":0,"href":"https:\/\/mediconomics.com\/en\/wp-json\/wp\/v2\/glossary\/8088\/revisions"}],"wp:attachment":[{"href":"https:\/\/mediconomics.com\/en\/wp-json\/wp\/v2\/media?parent=8088"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/mediconomics.com\/en\/wp-json\/wp\/v2\/glossary-cat?post=8088"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Regulatory References<\/h2>\n
\n