|
Comment |
Description: AI-generated or human-generated proposal for a taxonomy mapping before governance approval. Usage: This core business record is used in the 02 Developmental Taxonomy subject area as the authoritative representation of mapping proposal data. It is referenced through Framework Version has Mapping Proposals. |
|
Name |
Comment |
|
Mapping Proposal ID |
Description: Stable system identifier for a Mapping Proposal record. Usage: Used as the conceptual primary identifier and as the stable reference from relationships to Mapping Proposal. Required for every record. |
|
Source Entity Type |
Description: Controlled classification value for source entity type. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Source Entity Reference |
Description: Traceable reference used to locate, correlate, or audit the source entity reference. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Target Entity Type |
Description: Controlled classification value for target entity type. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Target Entity Reference |
Description: Traceable reference used to locate, correlate, or audit the target entity reference. Usage: Used for provenance, external integration, traceability, and reviewer verification. Required for every record. |
|
Proposed Relationship Type |
Description: Controlled classification value for proposed relationship type. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Required for every record. |
|
Confidence4 |
Description: Normalized numeric measure representing confidence. Usage: Used by evaluation, ranking, threshold, explanation, and quality-control logic; it must not be presented as clinical certainty unless explicitly validated. Optional and recorded only when known or applicable. |
|
Model Name |
Description: Controlled classification value for model name. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Optional and recorded only when known or applicable. |
|
Model Version |
Description: Version identifier for the model logic or content. Usage: Used to reproduce historical decisions, invalidate derived projections when logic changes, and support controlled migration. Optional and recorded only when known or applicable. |
|
Prompt Version |
Description: Version identifier for the prompt logic or content. Usage: Used to reproduce historical decisions, invalidate derived projections when logic changes, and support controlled migration. Optional and recorded only when known or applicable. |
|
Supporting Text |
Description: Human-readable content for supporting text on the Mapping Proposal record. Usage: Used by authoring, localization, parent-facing presentation, explainability, or reviewer workflows according to the entity context. Optional and recorded only when known or applicable. |
|
Competing Candidate Count |
Description: Calendar date associated with competing candidate count. Usage: Used by services, rules, search, reporting, or audit processing that operates on Mapping Proposal records. Optional and recorded only when known or applicable. |
|
Status8 |
Description: Lifecycle or workflow status of the Mapping Proposal record. Usage: Used to gate workflow transitions, exclude inactive or incomplete records, support operations dashboards, and preserve processing history. Required for every record. |
|
Reviewer Comment |
Description: Business value storing reviewer comment for the Mapping Proposal record. Usage: Used by services, rules, search, reporting, or audit processing that operates on Mapping Proposal records. Optional and recorded only when known or applicable. |
|
Reviewed At2 |
Description: Timestamp recording when the reviewed event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Optional and recorded only when known or applicable. |
|
|
|