Skip to content

Slot: id

The 'logical' identifier of the entity within the system of record. The simple value of this attribute stands for an identifier of this data object within the system, it can be used as a reference from other objects within the same system (i.e. primary and foreign keys), and it should be unique per type of object. The same data object copied to a different system will likely have a different "id" in the new system since "id" values are system specific and do not represent persistent business identifiers. Business identifiers are assigned outside the information system and are captured in the "identifier" field. The "id" field is more likely to be a serially or randomly generated value that is assigned to the data object as it is created in a system.

URI: crdch:researchProject__id

Domain and Range

ResearchProject0..1 CrdchString

Parents

Children

Used by

Other properties

Comments: FHIR naming conventions are followed here, where 'id' is used for logical identifiers, and 'identifier' for business identifiers. The identified entity may have a different 'id' in a different system, and have many external business 'identifiers' associated with it. If an "id" value can also be considered to be a business identifier, and should be transmissible to other systems, it should be duplicated in the "identifier" attribute along with the additional metadata needed to give context to the value of "id". An entity in this model that does not have an "id" field is considered to be an embeddable entity that can not stand on its own.
Examples:
Direct Mappings: GDC:Program.id
PDC:Program.program_id
PDC:Project.project_id
GDC:Project.id
ICDC:Study.clinical_study_id