TermautoCodeId[1] : ulongstatus[1] : Enumerationdescription[1] : stringacronym[*] : stringcommonTerm[1] : string/systematicName[1] : string

Blockname : stringcode : ushortlabel : stringdescription : string

1

*

+general

0..1

+specific *

BaseConceptlabeldefinition

* 1..1

systematic name

SemanticLinklabel : stringdescription : string

1*

NomenclatureProfileprofileIdprofileTypestatuseffectiveDatedescription

NomenclatureVersionProfilemajorminor

UseCaseActorRoleProfileregistrationIduseCaseactorrole

* *

Descriptorlabeldefinition

CodedTermcode : ushortreferenceId : stringcategory : ushort

EnumeratedTermvalueType/enumValue

* *coded term value enumeration

PartitionpartitionName : stringdescription : stringlowerRange : ushortupperRange : ushorttermTableRefId : string

1*

ExternalTermtermSystem[1] : ushortlabel[*] : chartermCode[*] : char

-general

0..1

-specific

0..1

0..1

0..1

*

*plesionym

0..1

0..1 partition table ref

Note: All labels, descriptions, etc., are locale based, allowing for language/country versions.

TermMapSet-mapLabel : string-description : string-bidirectional : bool 1..*

1..*

1

*

*can contain

DifferentiatingCriteriaSet-setID : Enumeration-purpose : string-description : string

1* 0..1

0..1

1*

Discriminator Set-setId-range-description

-may be modified by

*

0..1

Enumeration-enumId : string-valueType : ushort-enumValue : string 0..1

1

1..*

1

SpecializationProfile

Blockname : stringcode : ushortlabel : stringdescription : string

BaseConceptlabeldefinition

1

1..*

SemanticLinklabel : stringdescription : string

DescriptorSetdescription

1

1..*

Descriptorlabeldefinition

1

1..*

Discriminatoroffset : ushortpostFixRefId : string

PartitionpartitionName : stringdescription : stringlowerRange : ushortupperRange : ushorttermTableRefId : string

1 *

Enumeration-enumId : string-valueType : ushort-enumValue : string

0..1

* allowed subsequent links

0..1

*allowed subsequet descriptor sets

0..1

1

may have an

1

*

terms may be modified by

Discriminator Set-setId-range-description

1

1..*

DifferentiatingCriteriaSet-setID : Enumeration-purpose : string-description : string

0..1

0..11

-may be specialized by1..*11..*

1

1..*

EnumerationSet-setId : int-range : ushort-description : string

1

1..*

Note; “allowed subsequent” relationships support directed definition of terms (i.e., adds determinism). It also includes (as a component) support for generalization/specialization of concepts.

For example:Pressure|Continuous,Positive|Gas|Airway - CPAP Pressure - CPAP - <desc> - MDC_PRESS_AWAY_CTS_POS - 20724

orFlow|Inspiration,Maximum|Gas|Ventilator - Vent Insp Max Flow - <abrev> - <desc> - MDC_VENT_FLOW_INSP_MAX - 20877

Base Concepts: Pressure, Flow, Mode, Duration, Concentration, Compliance/Resistence, Index, Duration, …

1st Set Differentiating Criteria - “measurement features”:Semantic Link “has method”: Dynamic/Static/Occlusion, Pressure/Transthoracic, Continuous,

Applied/Intrinsic/Positive/PositiveEndexpiratorySemantic Link “has time criterion”: Inspiration/InspirationPhase/Expiration/ExpirationPhase/Endexpiratory,…Semantic Link “is computed as”: Mean/Maximum/Minumum, Difference(…), Ratio(…)

2nd Set Differentiating Criteria - “target of the measurement”:Semantic Link “concerns”: Breathing, Ventilation, Gas/CO2/O2/Desflurane/…

3rd Set Differentiating Criteria - “context (functional or organic system) in which term is relevant”:Semantic Link “has context”: Airway/Breathing/LungStructure/RespiratoryProcess/RespiratoryTract, Ventilator

Notes:(1) Need mechanism for referencing tables from descriptions. Question: Is there a 1:1 relationship between Partitions and tables in the nomenclature document?

(2) A synonym relationship has been added to Term. This is intended to support terms from different blocks that have the same semantic. For example, some ECG terms in the SCADA Block and the ECG Extensions (Annotations) block.

(3) Need to add a mechanism to support directed selection of Descriptors. For example, when you select item A, then you can only select subsequent items C & D, but not E. If you select item B, then you can do D & E but not C. Etc. This could be as simple as specifying how systematic names are developed, starting at the Base Concept, 1ST Set Differentiating Criteria, 1st Semantic Link, 2nd Semantic Link, 2nd Set Differentiating Criteria… IOW - The reflexive relationships on the systematic name objects provide the scoping needed to direct the development of systematic names.

NOTE: There is a difference between the relationships on the model that define a specific instance of a systematic name vs. separate relationships that indicate ALL the valid options for systematic names that support definition functions. See model on Systematic Name Definition Support page.

(4) Is the synonym relationship on Descriptors simply there to help with country / language differences or is it really needed? If it is the former, then we don’t need the relationship but rather could use Locale specific version of the label and description attributes.

(5) Do we need to include Rationale for constraints in the set of semantic links or descriptors that are allowed given the selection of a “higher” concept?

(6) Should we add the idea of Category to sets of terms at a shared level of generalization?