This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Template:SAIF Generic IM Relationships"
Jump to navigation
Jump to search
(Created page with "<noinclude><span style="color:#0000FF">Generic Relationships for SAIF Information models.<br/> <b>Only the content appearing...") |
|||
| Line 8: | Line 8: | ||
*This model and its encoded attributes must be bound to content from a specific [[Vocabulary Model Artifact Definition|Vocabulary Model]]. | *This model and its encoded attributes must be bound to content from a specific [[Vocabulary Model Artifact Definition|Vocabulary Model]]. | ||
**<i>Rationale</i> Over 40 per-cent of RIM-derived attributes carry encoded values. The expected terminology binding for those attributes must be carefully defined. | **<i>Rationale</i> Over 40 per-cent of RIM-derived attributes carry encoded values. The expected terminology binding for those attributes must be carefully defined. | ||
| + | *Traceability of model content to content expressed in a [[Conceptual Information Model Artifact Definition|Conceptual Information Model]] from the relevant domain or project. | ||
| + | **<i>Rationale</i> Provide traceability from project requirements expressed in a Conceptual Data Model to their realization as part of the model(s) in the PIM and PSM layers. | ||
Revision as of 20:25, 9 April 2011
Generic Relationships for SAIF Information models.
Only the content appearing below in black font will appear in the inclusion.
These elements are intended to appear under the following section:
Relationships and traceability
- This model and its attributes must be bound to content from a specific "abstract" data type model formally adopted by HL7.
- Rationale The data structures that derive from the RIM draw much of their "type" information from data types assigned to RIM attributes.
- This model and its encoded attributes must be bound to content from a specific Vocabulary Model.
- Rationale Over 40 per-cent of RIM-derived attributes carry encoded values. The expected terminology binding for those attributes must be carefully defined.
- Traceability of model content to content expressed in a Conceptual Information Model from the relevant domain or project.
- Rationale Provide traceability from project requirements expressed in a Conceptual Data Model to their realization as part of the model(s) in the PIM and PSM layers.
