This wiki has undergone a migration to Confluence found Here
CTS2/doc/CTS2 SFM ConceptDomainAttributes
Jump to navigation
Jump to search
CTS SFM and PIM attribute mapping
This section describes the relationship between the attributes and associations described in the CTS2 SFM and the corresponding entries in the PIM
Class | SFM | PIM | Description |
---|---|---|---|
ConceptDomain | id | ConceptDomainCatalogEntry.about (redefinition of ConceptDomainCatalogEntry.entryID) |
|
name | ConceptDomainCatalogEntry.conceptDomainName | ||
description[0..1] | ConceptDomainCatalogEntry.resourceSynopsis[0..1] | ||
status | ValueSetCatalogEntry.entryState | The SFM defines status as "A status (status) to identify the state (mainly for curation)". entryState provides the state of the concept domain with respect to the service (ACTIVE or INACTIVE) | |
ValueSetCatalogEntry.status[0..1] | The status of the value set within an external workflow, which covers the "curation" portion of the description | ||
statusDate[0..1] | ChangeDescription.changeDate (Not shown in this diagram) |
The date that the last change occurred. Note that this applies to all changes - a client will have to locate a METADATA change type where the status changed or, if not present, the CREATE change type where the first entry was created. | |
provenanceDetails[0..1] | (multiple fields) | ConceptDomainCatalogEntry.property covers anything not explicitly called out in the model | |
ValueSetContextBinding | effectiveDate | (none) | Defined as '"date for evaluating the value set expansion for the binding" in the SFM. The CTS2 PIM spells out specific value set definitions and/or code system versions - either through specific identifiers, through meta tags (CURRENT, DEVELOPMENT, etc), or, if the service supports the TEMPORAL perspective, through the reference date. |
ruleSetID[0..1] | (none) | The CTS2 PIM does not support the assignment of designations to value sets as component of the actual binding | |
bindingQualifier[0..1] | ConceptDomainBinding.bindingQualifier[0..1] | ||
provenanceDetails[0..1] | (none) | additional provenance is not included in the CTS2 model - the design group thought that the various fields in the ConceptDomain itself would be sufficient - this may be a point of expansion, however, in a subsequent version. | |
DesignationValueSetMembership | (none) | The CTS2 PIM does not support the assignment of designations to value sets as component of the actual binding | |
JurisdictionalDomain | (none) | The CTS2 PIM does not support the assignment of designations to value sets as component of the actual binding | |
UsageContext | ConceptDomainBinding.applicableContext[0..1] |
Home |
About CTS2 |
---|
Purpose |
CTS2 History |
Business Case |
How it works |
Federation |
Functionality |
Implementing CTS2 |
Architecture |
Development |
Resources |
Purpose |
FAQ |
Business Case |
Glossary of Terms |
Specification |
REST |
SOAP |
HL7 SFM |
Development |
CTS2 Development Framework |
Implementations |
Github Page |
Community |
Who is Using CTS2? |
Get Help |
Links |