GovernanceDate
A dated milestone for a study version, a document version or an amendment, such as an approval date, with the geographic scope it applies to.
- Kind
- Concrete class
- Attributes
- 9, 6 required
- NCI code
- C207595
Official definition
Any of the dates associated with event milestones within a clinical study's oversight and management framework.
In practice
In a protocol document: The protocol approval date and amendment dates on the title page.
Attributes
9 attributes, 6 of them required by the USDM API schema.
| Attribute | Type | Card. | Definition |
|---|---|---|---|
| idrequired | string | cardinality 1 | The identifier of this object, unique within the file. |
| namerequired | string | cardinality 1 | The literal identifier (i.e., distinctive designation) of the study governance date |
| label | string | cardinality 0..1 | The short descriptive designation for the study governance date. |
| description | string | cardinality 0..1 | A narrative representation of the study governance date. |
| typerequired | Code | cardinality 1 | A characterization or classification of the study governance date.USDM codelist C207413, 3 values |
| dateValuerequired | date | cardinality 1 | The information contained in the date field. |
| geographicScopesrequired | GeographicScope | cardinality 1..* | A USDM relationship between the GovernanceDate and GeographicScope classes which identifies the set of geographic scopes associated with the governance date. |
| extensionAttributes | ExtensionAttribute | cardinality 0..* | Extension attributes attached to this object, for information the standard does not define. Added by the API; not part of the logical model. |
| instanceTyperequired | string | cardinality 1 | The name of the class, carried by every object in a USDM JSON file. Added by the API; not part of the logical model. |
Allowed values
The coded attributes of GovernanceDate that use a codelist defined by USDM, with every value in it. A file carries the code; the term is its decode.
typecodelist C207413, extensible
| Code | Term | Definition |
|---|---|---|
| C71476 | Approval Date | The date on which the entity receives official approbation, recognition, or acceptance as satisfactory. |
| C215663 | Effective Date | The date on which the entity becomes active, goes into effect, or is slated to begin use. |
| C215664 | Issued Date | The date on which the entity is officially released, made available, or delivered to its intended recipient. |
Smallest valid GovernanceDate
The attributes a JSON file must carry for a GovernanceDate, and the kind of value each takes. This is the shape, with types named in place of values. Everything else in the table above is optional.
{
"id": "GovernanceDate_1",
"name": string,
"type": Code,
"dateValue": date,
"geographicScopes": [GeographicScope, …],
"instanceType": "GovernanceDate"
}
Where GovernanceDate is used
These classes hold or point to a GovernanceDate.
- StudyAmendment.dateValuesnested
- StudyDefinitionDocumentVersion.dateValuesnested
- StudyVersion.dateValuesnested
Example
A GovernanceDate from the example study. Coded values are shortened to one line.
{
"id": "GovernanceDate_1",
"name": "Sponsor approval",
"type": { "code": "C71476", "decode": "Approval Date", … },
"dateValue": "2026-01-15",
"geographicScopes": [
{
"id": "GeographicScope_1",
"type": { "code": "C68846", "decode": "Global", … },
"instanceType": "GeographicScope"
}
],
"instanceType": "GovernanceDate"
}
Related classes
Other classes in study, versions and amendments: